Your message dated Wed, 16 Nov 2011 23:47:19 +0000
with message-id <20111116234719.go30...@codelibre.net>
and subject line Re: Bug#638341: initscripts: Boot fails: Permission denied
(Read-only file system)
has caused the Debian Bug report #638341,
regarding initscripts: Boot fails: Permission denied (Read-only file system)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
638341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-13.11
Severity: critical
Justification: breaks the whole system
The initscripts package normally does a fine job
of orchestrating many diverse and important
resources.
The main reason I'm writing is that after
upgrading and re-booting, many, many errors
appeared on the system console, including
Permission denied
Read-only file system
unable to open pidfile
module <you name it> not found
/etc/init.d/rc: line 150: /etc/rcS.d/S10checkroot.sh Permission denied
If I recall correctly, I also saw errors something like
hostname: Unknown host (none)
As you might imagine, the computer made Charlie
Sheen look stable.
I rebooted the computer with a live CD, either
Puppy Linux or System Rescue CD, chrooted to the
hard drive, and saw that several init scripts lacked
permission to be executed.
I listed them with
$ ls -l $(dpkg -L initscripts | egrep "init.d" | egrep sh)
and saw lines like
-rw-r--r-- 1 root root 9398 Jul 13 14:11 /etc/init.d/checkroot.sh
So I did a
$ chmod 755 <init script name>
on the init scripts that needed permission to
execute, and rebooted.
It seemed to work.
The bad news?
How the scripts lost execute permission is a
mystery.
I hope this humble bug report helps others,
Kingsley
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initscripts depends on:
ii coreutils 8.5-1 GNU core utilities
ii debianutils 4.0.2 Miscellaneous utilities specific t
ii libc6 2.13-16 Embedded GNU C Library: Shared lib
ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip
ii mount 2.19.1-5 Tools for mounting and manipulatin
ii sysv-rc 2.88dsf-13.11 System-V-like runlevel change mech
ii sysvinit-utils 2.88dsf-13.11 System-V-like utilities
Versions of packages initscripts recommends:
ii e2fsprogs 1.42~WIP-2011-07-02-1 ext2/ext3/ext4 file system utiliti
ii psmisc 22.14-1 utilities that use the proc file s
initscripts suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Nov 16, 2011 at 02:51:36PM -0800, Kingsley G. Morse Jr. wrote:
> Thank you for your conscientious follow up.
>
> You very reasonably asked if I identified how the
> scripts lost execute permission.
>
> Unfortunately, I have not.
>
> I agree that since no similar bug reports have
> been forthcoming, the problem seems to have been
> limited to my system.
>
> Do you agree that this bug report should be closed?
I'll close it now. Please do reopen it or file a new one if you
do find this occurs again or you have any further information.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
--- End Message ---
