[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grub-bug
Subject:    Re: Error 2 - grub legacy (0.97) with newer ext3 (debian/ubuntu)
From:       adrian15 <adrian15sgd () gmail ! com>
Date:       2008-11-25 21:28:20
Message-ID: 492C6DF4.6070707 () gmail ! com
[Download RAW message or body]

Treutwein Bernhard escribió:
> hmm, nobody replied for a week, I regoogled and found 
> the following:
> 
> http://fixunix.com/debian/336524-bug-463123-grub-does-not-support-256-byte-in
> odes-ext3.html
> 
> which refers to a patch from the Fedora community:
> 
> http://cvs.fedora.redhat.com/viewcvs/devel/grub/grub-support-256byte-inode.pa
> tch?view=markup
> which in turn depends on a larger patch:
> http://cvs.fedora.redhat.com/viewcvs/devel/grub/grub-fedora-9.patch?view=mark
> up
> 
> I know, Grub legacy should fade away and the developers want to get
> rid of it, but since it is still used a lot, and Grub 2 still lacks 
> serious documentation (afaik, if I only have been unable to discover 
> the documentation, I'll be glad for any pointer at least there is none
> in grub-1.96.tar.gz), I would really appreciate, if these patches could 
> be incorporated into the subversion tree ...
I think that grub-1.96 already supports that inode sizes.
I did include the SuSE patch in my own grub legacy fork (super grub 
disk) but it also depended on another patch.

However it is easy to adapt it to grub legacy nude.

Can't you use chainload to chainload each distribution's grub so that 
each one of the grubs understands each own ext3 systems?

http://www.supergrubdisk.org/wiki/Multi_Distribution_Boot_Howto#Chainload_method

Or are you one of these that compile the software from trusted sources? ;)


Depending on my spare time and if you insist too much I might send here 
a patch here for this issue.

adrian15
-- 
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/index.php?pid=10



[prev in list] [next in list] [prev in thread] [next in thread]