From Moray.Henderson at ict-software.org Thu Nov 15 14:53:18 2012 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Thu, 15 Nov 2012 14:53:18 +0000 Subject: list-harddrives/parted Message-ID: <001701cdc340$f425e5a0$dc71b0e0$@Henderson@ict-software.org> Quick one (hopefully): can Anaconda's parted module (as used by list-harddrives, for example) distinguish between fixed and removable storage? There's got to be a better way of filtering out the DVD and USB sticks than saying list-harddrives | grep -v "sr" Moray. "To err is human; to purr, feline." From tibbs at math.uh.edu Thu Nov 15 14:58:45 2012 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Thu, 15 Nov 2012 08:58:45 -0600 Subject: list-harddrives/parted In-Reply-To: <001701cdc340$f425e5a0$dc71b0e0$@Henderson@ict-software.org> (Moray Henderson's message of "Thu, 15 Nov 2012 14:53:18 +0000") References: <001701cdc340$f425e5a0$dc71b0e0$@Henderson@ict-software.org> Message-ID: >>>>> "MH" == Moray Henderson writes: MH> Quick one (hopefully): can Anaconda's parted module (as used by MH> list-harddrives, for example) distinguish between fixed and MH> removable storage? To get all of the non-removable disks, I just do: for file in /sys/block/sd*; do rem=$(cat $file/removable) if [[ $rem == 0 ]]; then hds="$hds $(basename $file)" fi done Of course if you have some storage setup that presents disks with some name other than sd* then you'll have to adjust that. - J< From rangsan.au at gmail.com Wed Nov 21 15:25:26 2012 From: rangsan.au at gmail.com (Rangsan A) Date: Wed, 21 Nov 2012 22:25:26 +0700 Subject: kickstart boot option to rule the Network card name to eth0 Message-ID: Hi Kickstart Expertise, How can I use udev rules to manage the nic naming at the first time anaconda start asking for the nic that will be use for load the OS image. I use ksdevice= at the boot option. and it is detected as "eth4" while the os is install. Is there any way to rename it to "eth0" ? For the SLES, they has kernel boot option udev.rule="mac=00:1a:64:bd:13:86,name=eth0". Is there any equivalent option for REDHAT ? Thank you in advance. Regards, Rangsan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimi at sngx.net Wed Nov 21 15:53:42 2012 From: jimi at sngx.net (James Cammarata) Date: Wed, 21 Nov 2012 09:53:42 -0600 Subject: kickstart boot option to rule the Network card name to eth0 In-Reply-To: References: Message-ID: On Wed, Nov 21, 2012 at 9:25 AM, Rangsan A wrote: > Hi Kickstart Expertise, > > How can I use udev rules to manage the nic naming at the first time anaconda > start asking for the nic that will be use for load the OS image. > > I use ksdevice= at the boot option. and it is detected as > "eth4" while the os is install. Is there any way to rename it to "eth0" ? > > For the SLES, they has kernel boot option > udev.rule="mac=00:1a:64:bd:13:86,name=eth0". Is there any equivalent option > for REDHAT ? Add biosdevname=0 to your boot options and things will revert to the old naming scheme. From jwells at rackspace.com Wed Nov 21 16:20:15 2012 From: jwells at rackspace.com (Jeff Wells) Date: Wed, 21 Nov 2012 16:20:15 +0000 Subject: kickstart boot option to rule the Network card name to eth0 In-Reply-To: Message-ID: On 11/21/12 9:53 AM, "James Cammarata" wrote: >On Wed, Nov 21, 2012 at 9:25 AM, Rangsan A wrote: >> Hi Kickstart Expertise, >> >> How can I use udev rules to manage the nic naming at the first time >>anaconda >> start asking for the nic that will be use for load the OS image. >> >> I use ksdevice= at the boot option. and it is detected as >> "eth4" while the os is install. Is there any way to rename it to >>"eth0" ? >> >> For the SLES, they has kernel boot option >> udev.rule="mac=00:1a:64:bd:13:86,name=eth0". Is there any equivalent >>option >> for REDHAT ? > >Add biosdevname=0 to your boot options and things will revert to the >old naming scheme. biosdevname=0 will keep the naming scheme eth* instead of em* but will not address the NIC swapping. > >_______________________________________________ >Kickstart-list mailing list >Kickstart-list at redhat.com >https://www.redhat.com/mailman/listinfo/kickstart-list From rangsan.au at gmail.com Wed Nov 21 17:50:35 2012 From: rangsan.au at gmail.com (Rangsan A) Date: Thu, 22 Nov 2012 00:50:35 +0700 Subject: kickstart boot option to rule the Network card name to eth0 Message-ID: I'm not sure how the anaconda order and naming NIC at this step (boot process) between the order of loading modules or the order of PCI bus as seen by BIOS post code? On Thu, Nov 22, 2012 at 12:00 AM, wrote: > > ---------- Forwarded message ---------- > From: Jeff Wells > To: Discussion list about Kickstart > Cc: > Date: Wed, 21 Nov 2012 16:20:15 +0000 > Subject: Re: kickstart boot option to rule the Network card name to eth0 > > > On 11/21/12 9:53 AM, "James Cammarata" wrote: > > >On Wed, Nov 21, 2012 at 9:25 AM, Rangsan A wrote: > >> Hi Kickstart Expertise, > >> > >> How can I use udev rules to manage the nic naming at the first time > >>anaconda > >> start asking for the nic that will be use for load the OS image. > >> > >> I use ksdevice= at the boot option. and it is detected as > >> "eth4" while the os is install. Is there any way to rename it to > >>"eth0" ? > >> > >> For the SLES, they has kernel boot option > >> udev.rule="mac=00:1a:64:bd:13:86,name=eth0". Is there any equivalent > >>option > >> for REDHAT ? > > > >Add biosdevname=0 to your boot options and things will revert to the > >old naming scheme. > > biosdevname=0 will keep the naming scheme eth* instead of em* but will not > address the NIC swapping. > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: