From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Jeroen Oortwijn <oortwijn@gmail.com>
Cc: grub-devel@gnu.org
Subject: Re: Be File System identified as bfs
Date: Tue, 28 Jul 2015 21:30:24 +0300 [thread overview]
Message-ID: <20150728213024.21f27a1f@opensuse.site> (raw)
In-Reply-To: <CACRch+Y1Y5gAkwAZ62m9qWp84cxfwd8Y_3zmrc-18u5NUDTzLg@mail.gmail.com>
В Tue, 28 Jul 2015 19:10:39 +0200
Jeroen Oortwijn <oortwijn@gmail.com> пишет:
> Hello,
>
> Currently Grub identifies the Be File System as 'bfs'.
> In Linux however, 'bfs' refers to the Boot File System [1] and 'befs'
> refers to the Be File System.
>
> As a result, the os-prober utility (which uses grub-probe)
where do you see it?
fs_type () {
if (export PATH="/lib/udev:$PATH"; type vol_id) >/dev/null 2>&1; then
PATH="/lib/udev:$PATH" vol_id --type "$1" 2>/dev/null
elif type blkid >/dev/null 2>&1; then
blkid -o value -s TYPE "$1" 2>/dev/null
else
return 0
fi
}x
> doesn't
> correctly recognize the Be File System. And because the grub-mkconfig utility
> uses os-prober to detect other operating systems, it will never add a Haiku
> installation to the Grub menu.
>
> I see two ways of fixing this:
> 1) Modify Grub's Be File System module [2] to identify it as 'befs'.
> 2) Modify os-prober to assume 'befs' on Linux systems when grub-probe
> returns 'bfs'.
>
> I would prefer option 1, but what are your thoughts?
>
>
> Kind regards,
>
> Jeroen Oortwijn
>
> [1] https://en.wikipedia.org/wiki/Boot_File_System
> [2] http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/bfs.c
next prev parent reply other threads:[~2015-07-28 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 17:10 Be File System identified as bfs Jeroen Oortwijn
2015-07-28 18:30 ` Andrei Borzenkov [this message]
2015-07-28 19:05 ` Jeroen Oortwijn
2015-10-29 15:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-29 19:51 ` Andrei Borzenkov
2015-10-29 20:24 ` Vladimir 'phcoder' Serbinenko
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=20150728213024.21f27a1f@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=oortwijn@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.