Bug#638341: initscripts: Boot fails: Permission denied (Read-only file system)

2011-11-16 Thread Kingsley G. Morse Jr.
Hi Roger,

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?

Thanks,
Kingsley




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org




Bug#638341: initscripts: Boot fails: Permission denied (Read-only file system)

2011-11-16 Thread Roger Leigh
On Thu, Aug 18, 2011 at 11:04:12AM -0700, Kingsley G. Morse Jr. wrote:
> Package: initscripts
> Version: 2.88dsf-13.11

> 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
> 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.

> How the scripts lost execute permission is a
> mystery.

Checking the actual .deb files, the init scripts in question
are all installed with executable permissions.  This doesn't
look like a defect in the initscripts package itself.  (If this
was the case, there would also have been rather more bug reports.)

Have you been able to identify the cause of the problem in the
interim?  Without some further detail, it's rather difficult to
reproduce, and I would tend to think that it was due to something
happening on your system rather than a bug in initscripts.


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.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#638341: initscripts: Boot fails: Permission denied (Read-only file system)

2011-09-21 Thread Thomas PIERSON
Hi,

I just upgrade initscripts package to the new version '2.88dsf-13.11' too.
I reboot my system and all seem to be OK. I checked the script you
talking about and it have correct permissions.

I try the same upgrade on an other testing system and it seem to be OK
too. So, I could not reproduce this bug and maybe inisctripts package is
not the source of your issue.
But I just done some tests and I am not the maintainer of this package.

Best regards,
Thomas PIERSON


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental'),
(1, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initscripts depends on:
ii  coreutils   8.5-1
ii  debianutils 4.0.2
ii  libc6   2.13-18
ii  lsb-base3.2-28
ii  mount   2.19.1-5
ii  sysv-rc 2.88dsf-13.11
ii  sysvinit-utils  2.88dsf-13.11

Versions of packages initscripts recommends:
ii  e2fsprogs  1.42~WIP-2011-07-02-1
ii  psmisc 22.13-1

initscripts suggests no packages.

-- no debconf information



signature.asc
Description: OpenPGP digital signature


Bug#638341: initscripts: Boot fails: Permission denied (Read-only file system)

2011-08-18 Thread Kingsley G. Morse Jr.
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  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 

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  debianutils4.0.2 Miscellaneous utilities specific t
ii  libc6  2.13-16   Embedded GNU C Library: Shared lib
ii  lsb-base   3.2-27Linux Standard Base 3.2 init scrip
ii  mount  2.19.1-5  Tools for mounting and manipulatin
ii  sysv-rc2.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



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org