Mailinglist Archive: opensuse-factory (286 mails)

["Nikanth Karthikesan" <KNikanth@xxxxxxxxxx>]

> -----

> > > On 8/20/2010 at 07:29 PM, Jeff Mahoney <jeffm@xxxxxxxx> wrote: 
BEGIN PGP 
> SIGNED MESSAGE----- 
> Hash: SHA1 
>  
> On 08/20/2010 09:53 AM, Nikanth Karthikesan wrote: 
> > > ----- 
> >  
> > > > > On 8/20/2010 at 06:53 PM, Jeff Mahoney <jeffm@xxxxxxxx> wrote:  
> > BEGIN PGP  
> > > SIGNED MESSAGE-----  
> > > Hash: SHA1  
> > >   
> > > On 08/20/2010 12:26 AM, Linda Walsh wrote:  
> > > > Carlos E. R. wrote:  
> > > > > On 2010-08-20 06:16, Linda Walsh wrote:  
> > > > > > Stefan Seyfried wrote:  
> > > > > > > Besides, you cannot install a boot record onto XFS, so you always  
> > > > > > > need a  
> > > > > > > second partition  
> > > > > > ----  
> > > > > >     Some have had this problem.  
> > > > > >     I have never had this issue.  My root (and boot) partition are xfs. 
> > > > > >  
> > > > >
> > > > > It is a documented and known problem.  
> > > > ---  
> > > >   
> > > >   
> > > >     Yes -- a documented problem in Grub.  Not in XFS.  
> > > > SuSE maintainers thought GRUB was more important than the ability to use  
> > > > 1 file system for all your file systems.  
> > > >   
> > > >     Personally, I disagree, since it is GRUB that is doing things, that  
> > > > were documented as being problematic, since before GRUB was even 
> > > > conceived.  
>  
> > >   
> > > Personally I don't miss the days of forgetting to run lilo after every  
> > > kernel update and being greeted with LILILILILILI or whatever it was.  
> > >   
> >  
> > But as long as one runs lilo... 
> >  
> > > Lilo should be taken out back and shot. This is even more true as more  
> > > file systems are developed that lilo can't possibly ever work with, like  
> > > btrfs.  
> > >   
> >  
> > I thought LILO is file-system agnostic? 
> >  
> > And LILO is the only possible way to use a brand-new file-system, whenever 
> > a new file-system comes out, till GRUB learns the format?! 
>  
> More specifically, LILO works directly with maps of blocks instead of 
> interpreting the file system. That becomes dangerous when the file 
> system governing those blocks makes no promises about that map remaining 
> static. That promise can be broken easily by a copy-on-write file 
> system, file systems that aren't absolutely block based[1], and also by 
> anything running a defrag tool, which are becoming more common. 
>  

Ah, that explains. I assumed, it copies the actual data. Never thought
that it just notes the bmaps. Thanks.

> The solution should *not* be to teach the defrag tools about LILO. The 
> solution should be to fix any remaining bugs in GRUB. 

Agree.
 
> - -Jeff 
>  
> [1] yes, reiserfs has an ioctl for lilo to call to ensure that the tail 
> of a kernel image or initrd isn't packed so lilo can use it. That is a 
> hack too. 

Wow!

Thanks
Nikanth  

> - --  
> Jeff Mahoney 
> SUSE Labs 
> -----BEGIN PGP SIGNATURE----- 
> Version: GnuPG v2.0.15 (GNU/Linux) 
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ 
>  
> iEYEARECAAYFAkxuiiYACgkQLPWxlyuTD7KWxACgot9kbPgh9zTXz0BuIvjeZTMZ 
> iVUAn3nHPFakYcv2y5r4fmaAAN/RarW5 
> =PJCz 
> -----END PGP SIGNATURE----- 
 


--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx