Well, it seems that after recompiling the kernel with more options enabled, the label has been recognized. What I'm sure is that we need more options that just the RAM disc enabled, but unfortunately as I recompiled with many more options enabled I can't tell which one did the trick. I want to remove some of them so I hope to get the good option in the next days. Juan On Mon, 2004-09-06 at 13:23, Juan L. Pastor wrote: > Hi, > > On Sun, 2004-09-05 at 14:38, Andre Costa wrote: > > I've been bitten by this in the past, too -- back on the (not too > > distant) 2.4.x days. On my case, enabling RAM disk support for my > > custom kernel allowed LABELs to be properly understood (I've been doing > > it this way since then). My bet is that it would help you too. WARNING: > > you might need to compile it as a built-in feature, and not as a module > > I must be missing something because I have enabled the RAM disk support > and recompiled, but the label is still not recognized. I think I will > change the label for the filesystem. I was just curious why it didn't > work, even if I had the initrd in the /boot directory. > > Juan > > -- > Please avoid sending me Word or PowerPoint attachments. > See http://www.fsf.org/philosophy/no-word-attachments.html -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
