All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <russell@coker.com.au>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: at last: info regarding boot problems on multiple partitions
Date: Thu, 9 Sep 2004 18:30:59 +0100	[thread overview]
Message-ID: <20040909173059.GB10046@lkcl.net> (raw)
In-Reply-To: <200409100233.47416.russell@coker.com.au>

On Fri, Sep 10, 2004 at 02:33:47AM +1000, Russell Coker wrote:
> On Thu, 9 Sep 2004 08:49, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > FINALLY i got a useable system when i encountered a boot problem
> > [well, i got a console login].
> >
> > the issue is that partitions fail to be mounted.
> >
> > i had noticed over a period of time that programs like pump and dhclient
> > and some others would stop partitions from being unmounted during
> > shutdown.
> >
> > [remember i have /boot, /, /usr, /var and /home]
> >
> > for some reason, this also caused the partitions to fail to MOUNT on
> > startup.
> 
> I've seen a very similar problem, but it was intermittent and didn't occur 
> enough to let me debug it.  

 yes, it is intermittent (being dependent on a program not terminating,
 thereby keeping /usr from being unmounted), and also cyclic.

 cyclic as in you run into the problem through a shutdown, then
 start up, then have to power down again to clear the problem,
 and your system is fine, but on shutdown it happens again.


 it's a pain, and i _think_ it's down to the banning of initrc_t
 from writing to /etc.

 i note that there's an audit message to attempt a touch on a file
 somewhere in /etc.

 if that causes a change in behaviour in one of the early boot-up
 scripts...



> I'm not certain that I saw the same problem but 
> the result of file systems not being mounted was similar.
 
 yes.

> I would be very interested in any further information you may find on this.

 will keep looking.

 l.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2004-09-09 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 22:49 at last: info regarding boot problems on multiple partitions Luke Kenneth Casson Leighton
2004-09-09 12:22 ` Stephen Smalley
2004-09-09 13:10   ` Luke Kenneth Casson Leighton
2004-09-09 16:33 ` Russell Coker
2004-09-09 17:30   ` Luke Kenneth Casson Leighton [this message]
2004-09-09 17:35   ` Luke Kenneth Casson Leighton
2004-09-09 18:38   ` Luke Kenneth Casson Leighton
2004-09-09 23:43     ` Luke Kenneth Casson Leighton
2004-09-11 16:20       ` Russell Coker

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=20040909173059.GB10046@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    /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.