f8 boots!

[Gene Heskett]

On Monday 17 December 2007, Mikkel L. Ellertson wrote:
>Gene Heskett wrote:
>> They don't actually have the same name.  The /dev/hda1 is labeled as /boot
>> if queried by tune2fs -l for fc6, or by querying /dev/sdb1 from f8.
>>
>> /dev/sda1 on the new drive was labeled /boot1 by the installer and once
>> booted, is mounted as boot.
>>
>> The manpage for tune2fs doesn't say if there is supposed to be a '/' in
>> front of the label, and booted to fc6 I get:
>
><--------------------[snip ]-------------->
>
>> [root at coyote mnt]# tune2fs -l /dev/hdd3
>> tune2fs 1.39 (29-May-2006)
>> Filesystem volume name:   amandatapes
>>
>> Now the difference I see there is the missing slash cuz I didn't use one,
>> so I'll relabel it with the slash and try rebooting.  If that fixes it,
>> then maybe the requirement for the leading slash should be noted in the
>> manpage?
>
>You do not have to start the label with a slash, but you have to use
>the same label in /etc/fstab. So you would use LABEL=amandatapes and
>not LABEL=/amandatapes
>
>Mikkel

Which is apparently what I had done. Adding the slash to the drives name fixed 
it all up, except it decided to fsck the drive on that boot & its a big 
bugger, took about 40 minutes.

Now, let me ask the other question I've muttered about.  I'm currently running 
2.6.24-rc5 here, home built of course.

In the kernel config, I don't see an option I can set that will switch it from 
using the ide drivers to using the libata stuff.  This of course will mean I 
have to label everything in the system with tune2fs and edit my fstab and 
grub.conf as I go, but it seems to me that would solve my cross mounting 
problems a lot cleaner than futzing with everything else.  So how do I enable 
these new libata operations in a locally built kernel?

That is tonight's question.

Thanks Mikkel.
-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The system will be down for 10 days for preventive maintenance.