From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gummiboot does not display new kernel
Date: Wed, 11 Mar 2015 08:11:12 +0100 [thread overview]
Message-ID: <3305814.z64DMJDh4F@andromeda> (raw)
In-Reply-To: <CADPrc80n=igdwchhPkqy8dMXDbN0XDU+GvxoOJ1peya2zRoqgQ@mail.gmail.com>
On Sunday, March 08, 2015 11:11:49 AM Canek Peláez Valdés wrote:
> On Sun, Mar 8, 2015 at 11:05 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Sun, 8 Mar 2015 10:51:38 -0600, Canek Peláez Valdés wrote:
> > > > Are the ownership and mode of
> > > > "e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf" the same as the
> > > > two others (although I'd assume that it wouldn't matter) and is it
> > > > formatted correctly?
> > >
> > > The /boot partition in UEFI systems needs to be vfat. Permissions are
> > > not gonna matter that much in that.
> >
> > But filename lengths may do. What is the maximum length for FAT32? Is it
> > possible both files are considered the same?
>
> In that case, it would not work in my case, and it does (see my last
> reply). Besides, it has been working with those filenames for months now.
>
> FAT32 supports (IIRC) 256 long filenames.
Canek,
I don't see these long filenames in your filetree-listing.
You have a directory with the UUID, but then just the kernel-version numbers.
Or am I looking at the wrong email?
--
Joost
next prev parent reply other threads:[~2015-03-11 7:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 15:34 [gentoo-user] gummiboot does not display new kernel Stefan G. Weichinger
2015-03-08 15:59 ` Tom H
2015-03-08 16:10 ` Stefan G. Weichinger
2015-03-08 16:37 ` Stefan G. Weichinger
2015-03-08 16:53 ` Canek Peláez Valdés
2015-03-08 16:59 ` Tom H
2015-03-08 17:09 ` Canek Peláez Valdés
2015-03-08 18:10 ` Stefan G. Weichinger
2015-03-08 19:57 ` Stefan G. Weichinger
2015-03-08 20:17 ` Canek Peláez Valdés
2015-03-08 21:35 ` Stefan G. Weichinger
2015-03-08 20:21 ` Fernando Rodriguez
2015-03-08 21:37 ` Stefan G. Weichinger
2015-03-08 22:20 ` Fernando Rodriguez
2015-03-09 8:16 ` Stefan G. Weichinger
2015-03-10 13:45 ` J. Roeleveld
2015-04-02 21:06 ` Stefan G. Weichinger
2015-04-02 21:14 ` Canek Peláez Valdés
2015-04-02 21:21 ` Stefan G. Weichinger
2015-04-02 21:27 ` Stefan G. Weichinger
2015-04-02 21:19 ` Fernando Rodriguez
2015-03-08 16:51 ` Tom H
2015-03-08 16:56 ` Canek Peláez Valdés
2015-03-08 17:15 ` Tom H
2015-03-08 16:51 ` Canek Peláez Valdés
2015-03-08 17:00 ` Tom H
2015-03-08 17:05 ` Neil Bothwick
2015-03-08 17:11 ` Canek Peláez Valdés
2015-03-11 7:11 ` J. Roeleveld [this message]
2015-03-11 7:14 ` Canek Peláez Valdés
2015-03-08 17:23 ` Tom H
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3305814.z64DMJDh4F@andromeda \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox