From: Jeremy Jackson <jerj@coplanar.net>
To: Per Erik Stendahl <PerErik@onedial.se>
Cc: "'Linux Kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: Unmounting and ejecting the root fs on shutdown.
Date: Thu, 01 Mar 2001 16:01:48 -0500 [thread overview]
Message-ID: <3A9EB8BC.7E5D544D@coplanar.net> (raw)
In-Reply-To: <E44E649C7AA1D311B16D0008C73304460933B6@caspian.prebus.uppsala.se>
Per Erik Stendahl wrote:
>
> Nah, that looks too easy! ;-)
>
> > This might save everyone some pain:
> > from hdparm(8) man page (mine has some format
> > bugs, but you get the picture)
> >
> Is it true that the root fs is left mounted read-only? What is the
> rationale behind this? It seems to me that it would be better to
> completely unmount it and do whatever cleaning up is required (like
> cdrom_release()?). But I've been known to miss important issues before!
> :-)
>
> BTW, what would be the best way to determine which devices are cdrom
> devices? Looks like /proc/sys/dev/cdrom/info could be of use but what
> happens on a computer with more than one cdrom device?
>
Read about devfs option in 2.4 kernel. it puts only devices that exist
into /dev/cdroms/cdrom0, dev/cdroms/cdrom1, etc.
and if hdparm works (and it must since redhat's installer ejects it's
cd when rebooting) and you still are looking for a solution, well
no comment.
next prev parent reply other threads:[~2001-03-01 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 8:47 Unmounting and ejecting the root fs on shutdown Per Erik Stendahl
2001-03-01 21:01 ` Jeremy Jackson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-01 3:33 Jeremy Jackson
2001-02-28 18:07 David Balazic
2001-02-28 16:12 Per Erik Stendahl
2001-02-28 16:26 ` Mr. James W. Laferriere
2001-02-28 16:37 ` Miquel van Smoorenburg
2001-02-21 8:27 Per Erik Stendahl
2001-02-28 14:32 ` Mr. James W. Laferriere
2001-02-28 15:29 ` James A. Sutherland
2001-02-28 15:56 ` Mr. James W. Laferriere
2001-02-28 18:06 ` James A. Sutherland
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=3A9EB8BC.7E5D544D@coplanar.net \
--to=jerj@coplanar.net \
--cc=PerErik@onedial.se \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.