From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harald Hoyer Subject: Re: Dracut and root filesystem UUIDs Date: Fri, 13 Jan 2012 15:09:37 +0100 Message-ID: <4F103B21.80206@redhat.com> References: <4F101BA1.5000903@ed.ac.uk> <4F103A61.1070907@redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F103A61.1070907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Alastair Scobie Cc: "initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" On 13.01.2012 15:06, Harald Hoyer wrote: > On 13.01.2012 12:55, Alastair Scobie wrote: >> Apologies if this is the incorrect mailing list to discuss this issue.. >> >> Does anyone know if there is a way to configure dracut such that >> it will not attempt to mount USB mass-storage devices at boot time, >> but will still allow mounting of such devices once a system (in our >> case ScientifcLinux6) is fully booted? >> >> Why do we want to do this? We run several large teaching labs running >> SL6 desktops. We mount filesystems by UUID. We are concerned that our >> students could install a USB memory stick, at boot time, with a >> filesystem with the same UUID as the "official" root filesystem so >> fooling dracut into mounting a trojan filesystem. >> >> Thanks, in advance, for any ideas.. >> >> Alastair Scobie >> >> > > specifying "root=UUID= rd.shell=0" will do exactly what you want. Then you > also want to secure grub (or any other bootloader) with a password. Ah, sorry, only read half of it. You might want to blacklist the USB storage kernel driver then. "rd.driver.blacklist=usb-storage" or choose one of the by-path symlinks with e.g. "root=/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part1"