From: Alastair Scobie <ascobie-5WhEfG1TI8k@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Alastair Scobie <ascobie-5WhEfG1TI8k@public.gmane.org>
Subject: Dracut and root filesystem UUIDs
Date: Fri, 13 Jan 2012 11:55:13 +0000 [thread overview]
Message-ID: <4F101BA1.5000903@ed.ac.uk> (raw)
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
--
Alastair Scobie
Head of Computing, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh, Scotland, EH8 9AB
Mail: ascobie-5WhEfG1TI8k@public.gmane.org Voice: 0131 650 5178
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
next reply other threads:[~2012-01-13 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 11:55 Alastair Scobie [this message]
[not found] ` <4F101BA1.5000903-5WhEfG1TI8k@public.gmane.org>
2012-01-13 14:06 ` Dracut and root filesystem UUIDs Harald Hoyer
[not found] ` <4F103A61.1070907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-13 14:09 ` Harald Hoyer
[not found] ` <4F103B21.80206-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-13 14:24 ` Alastair Scobie
[not found] ` <4F103EB1.9000209-5WhEfG1TI8k@public.gmane.org>
2012-01-13 15:08 ` Harald Hoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F101BA1.5000903@ed.ac.uk \
--to=ascobie-5whefg1ti8k@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox