From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Customizable fs.lst order
Date: Wed, 14 Oct 2009 08:19:39 +0200 [thread overview]
Message-ID: <4AD56D7B.6000305@gmail.com> (raw)
In-Reply-To: <alpine.GSO.2.00.0910131751120.10234@oretfbsg.Jrfg.Fha.PBZ>
Seth Goldberg wrote:
> Hi,
>
> In thinking of optimizing the number of disk operations for various
> operating systems deploying grub, the order of filesystems came up as
> a simple way to reduce the amount of processing. If, for example,
> GRUB2 is deployed on Solaris, and the main use-case is to boot
> Solaris, there there are really only 2 filesystems involed -- either
> UFS (via the ufs1 module) or ZFS. Currently, the fs.lst is sorted
> alphabetically, so those two filesystems would be the last to be
> probed, wasting time. Besides hand-editing the filesystem order, are
> there any plans to include an override or setting for "preferred"
> filesystems in a particular GRUB2 deployment?
>
fs module autoloading is used only for interractive commands and is last
resort on booting. In particular it isn't done if correct module is
already inserted. So just insmod <your fs> before accessing your
filesystem. Look at grub-mkconfig on how it's done
2009-08-23 Vladimir Serbinenko <phcoder@gmail.com>
* commands/search.c (search_fs): Try searching without autoload
first.
* util/grub-mkconfig_lib.in (prepare_grub_to_access_device): Load
filesystem module explicitly for faster booting.
> --S
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
prev parent reply other threads:[~2009-10-14 6:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 0:53 Customizable fs.lst order Seth Goldberg
2009-10-14 6:19 ` Vladimir 'phcoder' Serbinenko [this message]
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=4AD56D7B.6000305@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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