All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Some ideas about new features of grub
Date: Sat, 11 Jul 2009 20:33:22 +0200	[thread overview]
Message-ID: <1247337202.5893.1.camel@fz.local> (raw)
In-Reply-To: <a5d587fb0907110920s286c904egf265e8e4da2d441@mail.gmail.com>

Am Samstag, den 11.07.2009, 18:20 +0200 schrieb Michal Suchanek:
> 2009/7/11 Bean <bean123ch@gmail.com>:
> > On Sat, Jul 11, 2009 at 5:27 AM, BandiPat<magicpage91@earthlink.net> wrote:
> >> Actually Zenwalk provides os-prober as well.  The gentleman that provides
> >> the installer of our Grub2 uses os-prober to detect all OS's installed, so
> >> they may be added to the original grub.cfg.  Works very well, although not
> >> perfect, but we are pretty pleased with the results thus far.
> >>
> >> We also do not have to run any of the Grub2 programs after installing new
> >> kernels.  The developer of our installer patched Grub2 for Zenwalk, so that
> >> no changes were necessary after kernel updates.  He tried to offer this to
> >> you guys as well earlier, but got little response, so we use it for Zenwalk
> >> exclusively at the moment.
> >
> > Hi,
> >
> > IIRC, os-prober is a collection of shell script to detect os, but grub
> > already have them in util/grub.d. This method is based on linux, so
> > you need to enter linux in order to update the menu. On the other
> > hand, lua script generate the menu inside grub, there is no need to
> > enter any os.
> >
> > Another problem is the drive number. It's impossible to decide bios
> > drive number from inside linux, so we can't insert the correct
> > drivemap command required to boot DOS/Windows from secondary drive.
> > This information must be gathered at boot time.
> >
> 
> The other problem is that scripts like os-prober that use linux
> filesystem code for probing filesystems destroy your data.
> 
> Linux cannot mount journalled filesystems readonly. It always modifies
> them. The extent of the modifications and the impact may vary
> depending on the state of the filesystem (clean/mounted) and the way
> you are going to use it in the future (resume the system/fresh boot)
> but until Linux people implement readonly filesystem support any Linux
> based os-probers cannot be recommended.
> 

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/filesystems/ext3.txt;hb=HEAD
ext3 has a noload option which disables journal recovery and with
ro,noload used it's really read-only.
I think it was added recently with 2.6.30 or something like that.
-- 
Felix Zielcke




  parent reply	other threads:[~2009-07-11 18:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  8:48 Some ideas about new features of grub Bean
2009-07-02 17:51 ` Pavel Roskin
2009-07-02 18:38   ` Duboucher Thomas
2009-07-02 20:44     ` Pavel Roskin
2009-07-02 19:38   ` Vladimir 'phcoder' Serbinenko
2009-07-02 21:23     ` Pavel Roskin
2009-07-02 21:37       ` Vladimir 'phcoder' Serbinenko
2009-07-04  4:57         ` Pavel Roskin
2009-07-31  8:18   ` Marco Gerards
2009-07-04 20:18 ` Robert Millan
2009-07-05  3:13   ` Bean
2009-07-07 18:39     ` Robert Millan
2009-07-08  6:19       ` Pavel Roskin
2009-07-10 17:11         ` Robert Millan
2009-07-10 21:27           ` BandiPat
2009-07-11  6:53             ` Bean
2009-07-11 16:20               ` Michal Suchanek
2009-07-11 18:32                 ` Colin Watson
2009-07-11 18:55                   ` Robert Millan
2009-07-11 18:33                 ` Felix Zielcke [this message]
2009-07-11 18:27               ` Robert Millan
2009-07-12 13:40               ` Pavel Roskin
2009-08-23 12:55 ` Robert Millan
2009-08-23 12:56 ` Robert Millan
2009-08-23 15:22   ` adrian15
2009-08-23 16:58     ` Vladimir 'phcoder' Serbinenko
2009-08-23 23:02       ` Robert Millan
2009-09-11 21:48   ` Pavel Roskin

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=1247337202.5893.1.camel@fz.local \
    --to=fzielcke@z-51.de \
    --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 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.