Coming gotchya
in [Slackware]
|
Prev: ralink USB adapter w/ RT2870 chip
Next: Slackware 12
From: Mikhail Zotov on 11 Jan 2010 15:27 On Sun, 10 Jan 2010 11:24:47 -0800 Handover Phist <jason(a)jason.websterscafe.com> wrote: > From the changelogs: > > ----------- > New kernels... and this deserves a mention/warning: the last bits of the .... > I have 2 ATA and 2 SATA drives. How the hell am I going to tell them > apart now? 3 are 80 gig and the one (my Slackware drive) is 500G. Should > be a fun upgrade once 13.1 comes out! Not such a big problem as it might sound. If your root partition is on a SATA drive, chances are that it won't be renamed and you will just have to fix /etc/fstab (and crypttab if you have one) upon reboot. If it is on an ATA drive, boot up your PC from the installation CD and run something like fdisk -l /dev/sd* You will see then how your previously /dev/hd? drives got renamed. Edit /etc/fstab (/etc/crypttab) and /etc/lilo.conf. If you are using initrd, rebuild it pointing to a new (`sd') root partition. Reboot. A few `gotchyas' can be met after you compile a new kernel using a previously perfect custom config (say, from a 2.6.31.x kernel) but the PC doesn't boot ;-) -- Mikhail
From: Grant on 11 Jan 2010 17:15 On Sun, 10 Jan 2010 11:24:47 -0800, Handover Phist <jason(a)jason.websterscafe.com> wrote: >From the changelogs: > >----------- >New kernels... and this deserves a mention/warning: the last bits of the > "old" IDE/ATA system have been removed now. Everything should be >using > the libata based drivers now, so if you have any drives that are >currently > running as /dev/hda, /dev/hdb, etc., when you reboot with these >kernels all > drives will be renamed as /dev/sda, /dev/sdb, etc. If you had any >/dev/sd* > already, they might get renamed. Adjustments may be required in > /etc/lilo.conf, /etc/fstab, the initrd, and elsewhere. Good luck! >---------- Last bits removed from the Slackware kernel .config, not the linux-kernel. > >I have 2 ATA and 2 SATA drives. How the hell am I going to tell them >apart now? 3 are 80 gig and the one (my Slackware drive) is 500G. Should >be a fun upgrade once 13.1 comes out! You can still use the old drivers by compiling a custom kernel. "< > ATA/ATAPI/MFM/RLL support --->" is still a valid 2.6.32 kconfig option, and the old disk subsystem is actively maintained, it's not going away for a while. My impression is that Slackware is trying to make a one-size-fits-all kernel to suit modern hardware. Older hardware takes a bit more fiddling? Grant. -- http://bugs.id.au
From: Res on 11 Jan 2010 21:08 On Tue, 12 Jan 2010, Grant wrote: > > My impression is that Slackware is trying to make a one-size-fits-all > kernel to suit modern hardware. Older hardware takes a bit more > fiddling? I just hope we dont go down this UUID bullshit road that some other distros have, sure it takes 5 seconds to remove it all and use the real block device, but id rather not have to do that with Slackware, one only has to read anpother distros mailing lsit to see the complaints about it when doing upgrades/restores etc. -- Res "What does Windows have that Linux doesn't?" - One hell of a lot of bugs!
From: Eef Hartman on 12 Jan 2010 09:40
Helmut Hullen <Helmut(a)hullen.de> wrote: > I prefer labelling, but labelling doesn't work with (p.e.) vfat > partitions. Yes, it does, as long as you set the labels with i.e. "mlabel" (mtools package). It is the old MS-Dos label that is set this way and hald also uses those labels for auto-mounting external (USB) sticks etc under /media/<disk_label. > My special problem: labelling doesn't work with the "boot = /dev/xyz" > entry in "/etc/lilo.conf". Not that important, at THAT moment you're running Linux (the boot= entry tells the lio program WHERE to install the lilo bootloader itself), so boot=/dev/sda means: put it in the MBR of disk A (current sda) and boot=/dev/sda1 in the BOOT block of partition 1 ON that disk A, etc. For the latter of course, the MBR should be loaded with some other bootloader. Much more important are the root= entries in the separate bootable partition blocks, they have to point TO the right disk/partition(s) to find the kernel(s). The root itself is mounted/accessed from the init ramdisk, so you may have to rebuild those. -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** ******************************************************************* |