Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 19:14, AL13N wrote: Op donderdag 7 maart 2013 12:18:09 schreef Anne Wilson: On 07/03/13 12:03, AL13N wrote: On 07/03/13 04:38, R James wrote: [...] So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ Thanks. It will help a lot for my own use. However, that really needs to be included in the gui disk partitioning, so that people can find and use it. I'm fairly sure there is no way to do that at present. imho: dolphin already shows the filesystem label; but, imho, there is no need to use label instead of uuid on the inside... it's not like most people actually look into fstab... i'm not sure, but i thought the expert had a way to change label in filesystems in the partitioner. label isn't used in fstab, but i don't think it should. OK - when I partition, I do add an identifier, which may be what jpbfree referred to, but what I see in Dolphin is not, IMO, very helpful. The shortcut added to Places shows the long number, not Win_C or anything like that. Maybe this is a Dolphin fault - I don't know. Anne i've always seen the labels of the USB-sticks and such, and they are also just filesystem labels. also i've seen at least in the past also the labels of other filesystems that i didn't mount Interestingly, USB sticks etc. do show their labels in Dolphin. I wonder why the Windows partition behaves differently? Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlE5s2gACgkQj93fyh4cnBeq7gCeIQoBItot1tIX1OrU5cwZa9wa 6mYAoIEDWNbDIL/3ddluGrkIlneITipv =DuyK -END PGP SIGNATURE-
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 04:38, R James wrote: On Wed, Mar 6, 2013 at 1:37 PM, AL13N al...@rmail.be mailto:al...@rmail.be wrote: While I appreciate the intention, from a user PoV, those UUIDs mean b* all. It would be really nice if, when they are first named, it was possible to allocate a nickname for want of a better term. if you use it, filesystems also have label functionalities, which iinm are shown in dolphin. Yeah, I'm not a big fan of UUIDs either so I tend to use labels instead. I always partition and format using command-line tools in the Rescue System. If you do that, you can add the labels yourself. For example: # mkfs.ext4 -m 1 -L mgaroot /dev/sda1 # mkswap -L swap /dev/sda2 # mkfs.ext4 -m 0 -L home /dev/sda3 The -m parameters above specifies the percentage reserved for the superuser. the -L parameters are the filesystem labels. After that, reboot to the installer and choose Custom Partitioning, assign your pre-existing partitions and be sure _untick_ the [ ] Format boxes then continue installing as usual. After the installation, you can edit /boot/grub/menu.lst replacing each UUID=blahblahblah with LABEL=label. For example: root=LABEL=mgaroot (and) resume=LABEL=swap Similarly in /etc/fstab, you can have entries like: LABEL=mgaroot / ext4 relatime 1 1 LABEL=swap swap swap defaults 0 0 So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ Thanks. It will help a lot for my own use. However, that really needs to be included in the gui disk partitioning, so that people can find and use it. I'm fairly sure there is no way to do that at present. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlE4XWAACgkQj93fyh4cnBd1BgCfebtOsKbMe69uhON+HHICDR/T FVwAoIY17Z9H7rOyZcjFLAShzsN6zLB+ =tcMy -END PGP SIGNATURE-
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
Le 07/03/2013 10:27, Anne Wilson a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 04:38, R James wrote: On Wed, Mar 6, 2013 at 1:37 PM, AL13N al...@rmail.be mailto:al...@rmail.be wrote: While I appreciate the intention, from a user PoV, those UUIDs mean b* all. It would be really nice if, when they are first named, it was possible to allocate a nickname for want of a better term. if you use it, filesystems also have label functionalities, which iinm are shown in dolphin. Yeah, I'm not a big fan of UUIDs either so I tend to use labels instead. I always partition and format using command-line tools in the Rescue System. If you do that, you can add the labels yourself. For example: # mkfs.ext4 -m 1 -L mgaroot /dev/sda1 # mkswap -L swap /dev/sda2 # mkfs.ext4 -m 0 -L home /dev/sda3 The -m parameters above specifies the percentage reserved for the superuser. the -L parameters are the filesystem labels. After that, reboot to the installer and choose Custom Partitioning, assign your pre-existing partitions and be sure _untick_ the [ ] Format boxes then continue installing as usual. After the installation, you can edit /boot/grub/menu.lst replacing each UUID=blahblahblah with LABEL=label. For example: root=LABEL=mgaroot (and) resume=LABEL=swap Similarly in /etc/fstab, you can have entries like: LABEL=mgaroot / ext4 relatime 1 1 LABEL=swap swap swap defaults 0 0 So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ Thanks. It will help a lot for my own use. However, that really needs to be included in the gui disk partitioning, so that people can find and use it. I'm fairly sure there is no way to do that at present. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlE4XWAACgkQj93fyh4cnBd1BgCfebtOsKbMe69uhON+HHICDR/T FVwAoIY17Z9H7rOyZcjFLAShzsN6zLB+ =tcMy -END PGP SIGNATURE- hum.. when in disk-patitioning on mcc if you toggle to expert mode therre is a label menu (have not tested it though, so don't know if it goes up to writing the right stanza in fstab). JPB -- GNU/Linux; il y a moins bien mais c'est plus cher!
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 09:55, jpbfree wrote: Le 07/03/2013 10:27, Anne Wilson a écrit : On 07/03/13 04:38, R James wrote: On Wed, Mar 6, 2013 at 1:37 PM, AL13N al...@rmail.be mailto:al...@rmail.be wrote: While I appreciate the intention, from a user PoV, those UUIDs mean b* all. It would be really nice if, when they are first named, it was possible to allocate a nickname for want of a better term. if you use it, filesystems also have label functionalities, which iinm are shown in dolphin. Yeah, I'm not a big fan of UUIDs either so I tend to use labels instead. I always partition and format using command-line tools in the Rescue System. If you do that, you can add the labels yourself. For example: # mkfs.ext4 -m 1 -L mgaroot /dev/sda1 # mkswap -L swap /dev/sda2 # mkfs.ext4 -m 0 -L home /dev/sda3 The -m parameters above specifies the percentage reserved for the superuser. the -L parameters are the filesystem labels. After that, reboot to the installer and choose Custom Partitioning, assign your pre-existing partitions and be sure _untick_ the [ ] Format boxes then continue installing as usual. After the installation, you can edit /boot/grub/menu.lst replacing each UUID=blahblahblah with LABEL=label. For example: root=LABEL=mgaroot (and) resume=LABEL=swap Similarly in /etc/fstab, you can have entries like: LABEL=mgaroot / ext4 relatime 1 1 LABEL=swap swap swap defaults 0 0 So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ Thanks. It will help a lot for my own use. However, that really needs to be included in the gui disk partitioning, so that people can find and use it. I'm fairly sure there is no way to do that at present. Anne hum.. when in disk-patitioning on mcc if you toggle to expert mode therre is a label menu (have not tested it though, so don't know if it goes up to writing the right stanza in fstab). Really? I do normally enable Expert mode, and I've never noticed that! Next time I do an install I'll definitely look for it. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlE4ZikACgkQj93fyh4cnBf9+wCeMw7pPijJ8+Svg3Nxra9H9rBF io8AnRFzqowhspqF4MwS75vWxA4PB3W8 =OCD2 -END PGP SIGNATURE-
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On Thu, Mar 7, 2013 at 10:04 AM, Anne Wilson an...@kde.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/03/13 09:55, jpbfree wrote: Le 07/03/2013 10:27, Anne Wilson a écrit : On 07/03/13 04:38, R James wrote: On Wed, Mar 6, 2013 at 1:37 PM, AL13N al...@rmail.be mailto:al...@rmail.be wrote: While I appreciate the intention, from a user PoV, those UUIDs mean b* all. It would be really nice if, when they are first named, it was possible to allocate a nickname for want of a better term. if you use it, filesystems also have label functionalities, which iinm are shown in dolphin. Yeah, I'm not a big fan of UUIDs either so I tend to use labels instead. I always partition and format using command-line tools in the Rescue System. If you do that, you can add the labels yourself. For example: # mkfs.ext4 -m 1 -L mgaroot /dev/sda1 # mkswap -L swap /dev/sda2 # mkfs.ext4 -m 0 -L home /dev/sda3 The -m parameters above specifies the percentage reserved for the superuser. the -L parameters are the filesystem labels. After that, reboot to the installer and choose Custom Partitioning, assign your pre-existing partitions and be sure _untick_ the [ ] Format boxes then continue installing as usual. After the installation, you can edit /boot/grub/menu.lst replacing each UUID=blahblahblah with LABEL=label. For example: root=LABEL=mgaroot (and) resume=LABEL=swap Similarly in /etc/fstab, you can have entries like: LABEL=mgaroot / ext4 relatime 1 1 LABEL=swap swap swap defaults 0 0 So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ Thanks. It will help a lot for my own use. However, that really needs to be included in the gui disk partitioning, so that people can find and use it. I'm fairly sure there is no way to do that at present. Anne hum.. when in disk-patitioning on mcc if you toggle to expert mode therre is a label menu (have not tested it though, so don't know if it goes up to writing the right stanza in fstab). Really? I do normally enable Expert mode, and I've never noticed that! Next time I do an install I'll definitely look for it. It used to work fine at least :) I remember making some small changes to diskdrake 4 years ago like displaying the label in partition info even in non expert mode and had been using labels for many years through diskdrake I think there is a display bug when people have UTF-8 in the label
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On 07/03/13 12:03, AL13N wrote: On 07/03/13 04:38, R James wrote: [...] So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ Thanks. It will help a lot for my own use. However, that really needs to be included in the gui disk partitioning, so that people can find and use it. I'm fairly sure there is no way to do that at present. imho: dolphin already shows the filesystem label; but, imho, there is no need to use label instead of uuid on the inside... it's not like most people actually look into fstab... i'm not sure, but i thought the expert had a way to change label in filesystems in the partitioner. label isn't used in fstab, but i don't think it should. OK - when I partition, I do add an identifier, which may be what jpbfree referred to, but what I see in Dolphin is not, IMO, very helpful. The shortcut added to Places shows the long number, not Win_C or anything like that. Maybe this is a Dolphin fault - I don't know. Anne attachment: disklabel.png signature.asc Description: OpenPGP digital signature
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On Thursday 7. March 2013 05.38, R James wrote: After the installation, you can edit /boot/grub/menu.lst replacing each UUID=blahblahblah with LABEL=DEFANGED_label. For example: root=LABEL=mgaroot (and) resume=LABEL=swap Similarly in /etc/fstab, you can have entries like: LABEL=mgaroot / ext4 relatime 1 1 LABEL=swap swap swap defaults 0 0 The problem with that is in those situations where one have two partitions with the same label, such as when one install into a new and bigger disk and keeps the old disk installed. A friend of mine does that quite often. I still prefer UUID, as those are unique. -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On 2013-03-07 17:52 (GMT+0100) Johnny A. Solbu composed: R James wrote: After the installation, you can edit /boot/grub/menu.lst replacing each UUID=blahblahblah with LABEL=DEFANGED_label. For example: root=LABEL=mgaroot (and) resume=LABEL=swap Similarly in /etc/fstab, you can have entries like: LABEL=mgaroot / ext4 relatime 1 1 LABEL=swap swap swap defaults 0 0 The problem with that is in those situations where one have two partitions with the same label, such as when one install into a new and bigger disk and keeps the old disk installed. A friend of mine does that quite often. I still prefer UUID, as those are unique. As there are something like 16 or more characters available for volume labels on native partitions, there's no need in the vast majority of situations for them to be non-unique. Even after cloning operations it's a simple enough matter in most cases to alter the copies' and/or originals' labels and UUIDs. I use labels liberally with native partitions in cmdlines and fstabs, UUIDs never. Volume labels can be readily remembered and typed as circumstances dictate, unlike UUIDs. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
Op donderdag 7 maart 2013 12:18:09 schreef Anne Wilson: On 07/03/13 12:03, AL13N wrote: On 07/03/13 04:38, R James wrote: [...] So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ Thanks. It will help a lot for my own use. However, that really needs to be included in the gui disk partitioning, so that people can find and use it. I'm fairly sure there is no way to do that at present. imho: dolphin already shows the filesystem label; but, imho, there is no need to use label instead of uuid on the inside... it's not like most people actually look into fstab... i'm not sure, but i thought the expert had a way to change label in filesystems in the partitioner. label isn't used in fstab, but i don't think it should. OK - when I partition, I do add an identifier, which may be what jpbfree referred to, but what I see in Dolphin is not, IMO, very helpful. The shortcut added to Places shows the long number, not Win_C or anything like that. Maybe this is a Dolphin fault - I don't know. Anne i've always seen the labels of the USB-sticks and such, and they are also just filesystem labels. also i've seen at least in the past also the labels of other filesystems that i didn't mount
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/03/13 17:11, Colin Guthrie wrote: Anything that relies on ordering is just broken by design. We need to handle things gracefully regardless of the order they are detected. This is why UUIDs are the defacto method for filesystem identification these days and why in mga4 we'll likely switch to a consistent naming scheme for networking devices too. While I appreciate the intention, from a user PoV, those UUIDs mean b* all. It would be really nice if, when they are first named, it was possible to allocate a nickname for want of a better term. Anne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlE3SJsACgkQj93fyh4cnBfIYQCfY2j4nJtmCeW+cmX7+EdQOfbq nh8An39bHvwxaAnexSz1UwtbTBIogaHa =cMEE -END PGP SIGNATURE-
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
Op woensdag 6 maart 2013 13:46:06 schreef Anne Wilson: On 05/03/13 17:11, Colin Guthrie wrote: Anything that relies on ordering is just broken by design. We need to handle things gracefully regardless of the order they are detected. This is why UUIDs are the defacto method for filesystem identification these days and why in mga4 we'll likely switch to a consistent naming scheme for networking devices too. While I appreciate the intention, from a user PoV, those UUIDs mean b* all. It would be really nice if, when they are first named, it was possible to allocate a nickname for want of a better term. if you use it, filesystems also have label functionalities, which iinm are shown in dolphin.
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On Wed, Mar 6, 2013 at 1:37 PM, AL13N al...@rmail.be wrote: While I appreciate the intention, from a user PoV, those UUIDs mean b* all. It would be really nice if, when they are first named, it was possible to allocate a nickname for want of a better term. if you use it, filesystems also have label functionalities, which iinm are shown in dolphin. Yeah, I'm not a big fan of UUIDs either so I tend to use labels instead. I always partition and format using command-line tools in the Rescue System. If you do that, you can add the labels yourself. For example: # mkfs.ext4 -m 1 -L mgaroot /dev/sda1 # mkswap -L swap /dev/sda2 # mkfs.ext4 -m 0 -L home /dev/sda3 The -m parameters above specifies the percentage reserved for the superuser. the -L parameters are the filesystem labels. After that, reboot to the installer and choose Custom Partitioning, assign your pre-existing partitions and be sure _untick_ the [ ] Format boxes then continue installing as usual. After the installation, you can edit /boot/grub/menu.lst replacing each UUID=blahblahblah with LABEL=label. For example: root=LABEL=mgaroot (and) resume=LABEL=swap Similarly in /etc/fstab, you can have entries like: LABEL=mgaroot / ext4 relatime 1 1 LABEL=swap swap swap defaults 0 0 So the 'nickname' feature you request is available with a little pre-install preparation and post-install config file editing. Hope this helps -- RJ
[Mageia-dev] Why is AHCI statically compiled into kernel?
I remember when PATA (IDE) drivers were statically compiled into the kernel, then we went to modular IDE which I liked because modprobe ordering could be controlled. (When dealing with parity RAID, its nice to have logical drive enumeration because SATA ports don't have UUID labels.) But now it seems we've come full circle: [root@localhost ~]# grep SATA_AHCI /boot/config-3.8.1-desktop-1.mga3 CONFIG_SATA_AHCI=y CONFIG_SATA_AHCI_PLATFORM=y Is there a compelling reason to do this (other than AHCI is popular)? I'm putting together a home-brewed a file server using an old motherboard plus a couple of add-in SATA controllers. With the Mageia stock kernel, the enumeration looks like: sda = RAID disk 08 (ahci) sdb = RAID disk 09 (ahci) sdc = RAID disk 10 (ahci) sdd = RAID disk 11 (ahci) sde = Mageia OS (sata_nv) (1st port on mobo) sdf = RAID disk 01 (sata_nv) sdg = RAID disk 02 (sata_nv) sdh = RAID disk 03 (sata_nv) sdi = RAID disk 04 (sata_sil) sdj = RAID disk 05 (sata_sil) sdk = RAID disk 06 (sata_sil) sdl = RAID disk 07 (sata_sil) Of course its no problem to re-compile the kernel with AHCI as a module so I can modprobe it last. Just wondering why AHCI is now the exception to modular sata...? Thanks -- RJ
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
'Twas brillig, and R James at 05/03/13 16:20 did gyre and gimble: I remember when PATA (IDE) drivers were statically compiled into the kernel, then we went to modular IDE which I liked because modprobe ordering could be controlled. (When dealing with parity RAID, its nice to have logical drive enumeration because SATA ports don't have UUID labels.) Anything that relies on ordering is just broken by design. We need to handle things gracefully regardless of the order they are detected. This is why UUIDs are the defacto method for filesystem identification these days and why in mga4 we'll likely switch to a consistent naming scheme for networking devices too. Also modprobe ordering is increasingly not true either as many modules are automatically loaded when the hardware is present. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On Tue, Mar 5, 2013 at 9:41 AM, Thomas Backlund t...@mageia.org wrote: It's needed to be able to boot new hw without need for initrd. https://wiki.mageia.org/en/Feature:BootSansRamdisk Ah, I didn't know about that. It seems like the target systems will need to be simple AND have ahci compliant boot controllers. Otherwise a bunch of SATA drivers will need to be statically compiled in kinda like the old IDE days. It'll be interesting to see how many users complain because they think they shouldn't need an initrd... :o)
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On Tue, Mar 5, 2013 at 11:11 AM, Colin Guthrie mag...@colin.guthr.iewrote: Anything that relies on ordering is just broken by design. We need to handle things gracefully regardless of the order they are detected. This is why UUIDs are the defacto method for filesystem identification these days and why in mga4 we'll likely switch to a consistent naming scheme for networking devices too. Yes, I understand that cryptic-looking UUIDs are the defacto identifiers but when mdadm reports that /dev/sdf1 has failed in a parity RAID setup, it will be good if a mere mortal can know which drive to replace. :o) Also modprobe ordering is increasingly not true either as many modules are automatically loaded when the hardware is present. Yes, but it is possible to override the automatic loading...which is why I like the modular approach. Now that I understand the reasons for going back to statically compiled drivers, I'm OK with rolling my own. Thanks -- RJ
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
R James skrev 5.3.2013 19:34: On Tue, Mar 5, 2013 at 9:41 AM, Thomas Backlund t...@mageia.org mailto:t...@mageia.org wrote: It's needed to be able to boot new hw without need for initrd. https://wiki.mageia.org/en/Feature:BootSansRamdisk Ah, I didn't know about that. It seems like the target systems will need to be simple AND have ahci compliant boot controllers. Otherwise a bunch of SATA drivers will need to be statically compiled in kinda like the old IDE days. It'll be interesting to see how many users complain because they think they shouldn't need an initrd... :o) yeah, we / I chose to make only AHCI builtin as pretty much all new hw coming out theese days are ahci-compliant, so it works out of the box. And to not bloat the kernel the rest of the hw support got left as modules. Now this feature booting without initrd is obviously targetted for laptops/netbooks desktops where people care about fast boot. For servers ( bigger workstations) where you rely on SCSI / SAS / FC / you still need initrds, and usually you dont really care if a boot take a little longer. -- Thomas
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
R James skrev 5.3.2013 19:53: On Tue, Mar 5, 2013 at 11:11 AM, Colin Guthrie mag...@colin.guthr.ie mailto:mag...@colin.guthr.ie wrote: Anything that relies on ordering is just broken by design. We need to handle things gracefully regardless of the order they are detected. This is why UUIDs are the defacto method for filesystem identification these days and why in mga4 we'll likely switch to a consistent naming scheme for networking devices too. Yes, I understand that cryptic-looking UUIDs are the defacto identifiers but when mdadm reports that /dev/sdf1 has failed in a parity RAID setup, it will be good if a mere mortal can know which drive to replace. :o) If you follow raid devel list you will soon learn that they dont recommend trusting the /dev/sd* naming either as it is by no means static... :) depending on your hw, they may for example hange place if you happend to have a usb disk plugged at boot and so on. so the thing to check is for example what disk is mapped as /dev/disk/by-id/* where you can match on actual disc serial number and so on... then you can be sure wich disk is failing / has failed... -- Thomas
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On Tue, Mar 5, 2013 at 12:19 PM, Thomas Backlund t...@mageia.org wrote: If you follow raid devel list you will soon learn that they dont recommend trusting the /dev/sd* naming either as it is by no means static... :) depending on your hw, they may for example hange place if you happend to have a usb disk plugged at boot and so on. so the thing to check is for example what disk is mapped as /dev/disk/by-id/* where you can match on actual disc serial number and so on... then you can be sure wich disk is failing / has failed.. Great advice. I'll make sure the drive's serial numbers are visible without removal and then use ls /dev/disk/by-id/ to make sure I get the right one, if/when the time ever comes... Thanks again -- RJ
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
Op dinsdag 5 maart 2013 20:10:20 schreef Thomas Backlund: [...] For servers ( bigger workstations) where you rely on SCSI / SAS / FC / you still need initrds, and usually you dont really care if a boot take a little longer. does this mean that AHCI is enabled only for desktop kernels?
Re: [Mageia-dev] Why is AHCI statically compiled into kernel?
On Tue, Mar 5, 2013 at 12:54 PM, AL13N al...@rmail.be wrote: Op dinsdag 5 maart 2013 20:10:20 schreef Thomas Backlund: [...] For servers ( bigger workstations) where you rely on SCSI / SAS / FC / you still need initrds, and usually you dont really care if a boot take a little longer. does this mean that AHCI is enabled only for desktop kernels? AHCI is definitely enabled for all kernels. Its also statically compiled into all kernels as well: # cd /usr/src/linux-3.8.1-1.mga3/arch/x86/configs # grep SATA_AHCI * i386_defconfig:CONFIG_SATA_AHCI=y i386_defconfig-desktop:CONFIG_SATA_AHCI=y i386_defconfig-desktop:CONFIG_SATA_AHCI_PLATFORM=y i386_defconfig-desktop586:CONFIG_SATA_AHCI=y i386_defconfig-desktop586:CONFIG_SATA_AHCI_PLATFORM=y i386_defconfig-server:CONFIG_SATA_AHCI=y i386_defconfig-server:CONFIG_SATA_AHCI_PLATFORM=y x86_64_defconfig:CONFIG_SATA_AHCI=y x86_64_defconfig-desktop:CONFIG_SATA_AHCI=y x86_64_defconfig-desktop:CONFIG_SATA_AHCI_PLATFORM=y x86_64_defconfig-server:CONFIG_SATA_AHCI=y x86_64_defconfig-server:CONFIG_SATA_AHCI_PLATFORM=y (If any were modular, they be set to 'm')
