JP Pozzi | 21 May 2013 19:00
Picon

Bug#709217: initscripts: checkfs.sh abend on BTRFS filesystem

Package: initscripts
Version: 2.88dsf-41
Severity: normal

Dear Maintainer,

I get a message at system startup as "fsck" is incorrect for btrfs file-systems
:

Log of fsck -C -R -A -a
Tue May 21 18:32:07 2013

fsck from util-linux 2.20.1
Unknown option: -a
usage: btrfs [--help] [--version] <group> [<group>...] <command> [<args>]
BOOTB: clean, 720/65536 files, 168362/262135 blocks (check in 4 mounts)
STOCKAGE: clean, 218/1048576 files, 2179291/4194304 blocks
VARLOG: clean, 6205/65536 files, 35419/262144 blocks
AMANDA_HOLD: clean, 12/1048576 files, 109842/4194304 blocks
Unknown option: -a
usage: btrfs [--help] [--version] <group> [<group>...] <command> [<args>]
fsck died with exit status 129

Tue May 21 18:32:08 2013
----------------

I upgrade to unstable yesterday, no problems before.

Regards

(Continue reading)

Roger Leigh | 19 May 2013 17:47

update-rc.d: Removal of start and stop actions

Hi,

With the release of wheezy, all systems should be using dependency-
based booting.  This makes the provision of static sequence ordering
pointless, but the update-rc.d interface still allows sequence
numbers to be passed for its start, stop and defaults actions.  They
just get ignored when using insserv, but they still need providing
unless you are using defaults with no options (which is recommended).

I'm planning on merging these two patches:
http://anonscm.debian.org/gitweb/?p=users/rleigh/sysvinit.git;a=commitdiff;h=3ed24526866d93e28ae3a501b131d5efe002f11a
http://anonscm.debian.org/gitweb/?p=users/rleigh/sysvinit.git;a=commitdiff;h=48daa9d5c8e28f8669e5b85cd369605c8254232c

These do the following:
- remove all support for non-dependency-based boot; in practice, this
  code hasn't been used for a couple of stable releases, since we always
  used the insserv code.
- remove support for start and stop; the options still exist, but they
  just invoke the "defaults" action.  This was already the case with
  insserv, but it's now explicit.
- the update-rc.d(8) manpage is updated to remove all the legacy
  documentation and examples.  This should make it clear what's
  currently supported, and it greatly simplifies the interface.

None of this should affect anyone since in practice there will be no
noticable difference other than the addition of a warning if the start
or stop actions are used.  I'm just bringing it up in case this will
cause anyone problems--in which case shout now before it's changed!

Following this change, I'd like to have debhelper and lintian warn
(Continue reading)

Harald Dunkel | 19 May 2013 16:13
Picon
Favicon

Bug#708934: how to avoid all mounts for LXC systems?

Package: initscripts
Version: 2.88dsf-41
Severity: wishlist

For LXC systems all mounts are supposed to happen _before_
init is run. Every mount tried by one of the run level scripts
creates a "permission denied" error message.

Below is a sample boot session showing startup and shutdown
of a LXC system (CONCURRENCY=none).

The problem is that I cannot disable the "unwanted" scripts
performing the mount, because I would loose other initialization
steps as well.

It would be very nice if the run level scripts doing mount/\
umount could be streamlined to support LXC systems.

Many thanx
Harri

-------------------------------------------------------------------
# lxc-start -n wheezy
INIT: version 2.88 booting
 <at>  <at>  <at>  /etc/rcS.d/S01checkroot-bootclean.sh start
Cleaning up temporary files... /tmp /lib/init/rw /run /run/lock /run/shm.
 <at>  <at>  <at>  /etc/rcS.d/S01mountkernfs.sh start
mount: permission denied
mount: permission denied
 <at>  <at>  <at>  /etc/rcS.d/S01mtab.sh start
(Continue reading)

Roger Leigh | 18 May 2013 22:33

Stable update for sysvinit

Hi,

It was pointed out that #694252 was preventing some upgrades from lenny
due to preventing the enabling of dependency-based boot.  The following
one line change corrects this:

diff --git a/debian/changelog b/debian/changelog
index 437a296..459c770 100644
--- a/debian/changelog
+++ b/debian/changelog
 <at>  <at>  -1,3 +1,13  <at>  <at> 
+sysvinit (2.88dsf-41+wheezy1) stable-proposed-updates; urgency=low
+
+  [ Roger Leigh ]
+  * Correct the Breaks on bootchart to ensure that all broken
+    versions are removed on upgrade (Closes: #694252).  Break
+    bootchart << 0.10~svn407-4 to ensure that 0.10~svn407-3.3
+    and earlier are removed.
+
+ -- Roger Leigh <rleigh <at> debian.org>  Sat, 18 May 2013 21:19:44 +0100
+
 sysvinit (2.88dsf-41) unstable; urgency=low

   [ Roger Leigh ]:
diff --git a/debian/control b/debian/control
index ef089d0..0bfcf9e 100644
--- a/debian/control
+++ b/debian/control
 <at>  <at>  -116,7 +116,7  <at>  <at>  Breaks:
 # being a symlink #668616 and #668650
(Continue reading)

Michael Tokarev | 17 May 2013 07:03
Picon

Bug#686531: not only NFS

Control: retitle -1 checkroot-bootclean.sh fails on read-only root
Control: found -1 2.88dsf-41

The same happens when root is on local storage but still mounted
read-only.  And this happens with wheezy version too.

In /lib/init/bootclean.sh, clean_tmp, there's a check whenever
/tmp is world-writable - maybe it's a good idea to chmod it in
the real root (since it's read-only anyway!), and so whole thing
will just work.  Or maybe creatig /tmp/.tmpfs will do the trick.
For now I think I'll go for chmod 0755 /tmp.

After upgrading to wheezy I left with /lib/init/rw directory, and
that one too causes several ugly error messages and script failures
during bootup (this can be fixed simple by deleting the dir).

Thanks,

/mjt

Steve Langasek | 16 May 2013 05:20
Picon
Favicon

Bug#707007: Bug#707007: wishlist: bash_completion for /bin/service

Control: reassign -1 bash-completion

> It would be nice if "service <tab><tab><tab>" would show all acceptable
> names so that one doesn't have to remember if it was e.g.  "mysql" or
> "mysql-server".  I guess it's pretty easily done with bash_completion but
> I have no clue how such scripts are made.

There is already support for this in the core
/usr/share/bash-completion/bash_completion script.  And it works for me.

> Note that service(8) also supports upstart and systemd, so you have to
> take care of that when designing a completion function.

That's a good point; the current bash_completion only handles sysvinit
scripts.  Maybe it should be extended?  (But I'm not sure if that's on topic
for this bug report, or if a separate one should be filed.)

--

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek <at> ubuntu.com                                     vorlon <at> debian.org
Control: reassign -1 bash-completion

> It would be nice if "service <tab><tab><tab>" would show all acceptable
> names so that one doesn't have to remember if it was e.g.  "mysql" or
> "mysql-server".  I guess it's pretty easily done with bash_completion but
> I have no clue how such scripts are made.
(Continue reading)

Em DeEm | 9 May 2013 16:43
Picon

Bug#678260: startpar has a timeout value that lets boot messages get mixed

Package: sysvinit-utils
Version: 2.88dsf-41
Followup-For: Bug #678260
Tags: patch

Hi,

I also see mixed boot messages with startpar, especially on slow
embedded computers or on virtual machines. It seems that startpar
tries to print the messages of the last active process immediately. On
slow system, there is sometimes only one active process, which
startpar incorrectly considers as the last process overall. The
attached patch adds a better condition for this.

The patch solves the issue on my computer. Startpar is a fairly complex
program, hopefully the patch doesn't break other parts of it.

Cheers,
Em

-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

(Continue reading)

Carlo Stemberger | 7 May 2013 10:42
Picon
Gravatar

Bug#686991: Any news?

Hi,
I'd like to upgrade my SheevaPlug to Wheezy, but I found this bug report. What is the current situation?

Thank you!

Carlo
<div><div dir="ltr">Hi,<div>I'd like to upgrade my SheevaPlug to Wheezy, but I found this bug report. What is the current situation?</div>
<div><br></div>
<div>Thank you!</div>
<div><br></div>
<div>
Carlo</div>
</div></div>
Christian Hammers | 6 May 2013 21:42
Picon
Favicon

Bug#707007: wishlist: bash_completion for /bin/service

Package: sysvinit-utils
Version: 2.88dsf-41
Severity: wishlist

Hello

It would be nice if "service <tab><tab><tab>" would show all acceptable names 
so that one doesn't have to remember if it was e.g. "mysql" or "mysql-server".
I guess it's pretty easily done with bash_completion but I have no clue how
such scripts are made.

bye,

-christian-


-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sysvinit-utils depends on:
ii  libc6        2.13-38
ii  libselinux1  2.1.9-5

sysvinit-utils recommends no packages.

Versions of packages sysvinit-utils suggests:
pn  bootlogd  <none>
pn  sash      <none>

-- no debconf information

Laurent Vallar | 3 May 2013 11:23
Gravatar

Bug#706676: sysvinit: /sbin/init doesn't support LXC gracefull shutdown via lxc-shutdown

Package: sysvinit
Version: 2.88dsf-41
Severity: important

It seems that init doesn't handle properly SIGPWR inside LXC container,
even after applying a workarround found at :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695568#15

'lxc-shutdown -n <container>' halts gracefully a container but
container's /sbin/init process is left running after, so container
isn't stopped.

You have to do 'lxc-stop -n <container>' or a
'lxc-attach -n <container> -- /bin/kill -9 <init_pid>' to kill remaining
/sbin/init and stop container.

Regards.

-- System Information:
Debian Release: 7.0
  APT prefers wheezy
  APT policy: (990, 'wheezy'), (500, 'wheezy-updates'), (500, 'wheezy-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/dash

version of lxc:
ii  lxc             0.8.0~rc1-8+deb7

Versions of packages sysvinit depends on:
ii  debianutils     4.3.2
ii  initscripts     2.88dsf-41
ii  libc6           2.13-38
ii  libselinux1     2.1.9-5
ii  libsepol1       2.1.4-3
ii  sysv-rc         2.88dsf-41
ii  sysvinit-utils  2.88dsf-41

sysvinit recommends no packages.

sysvinit suggests no packages.

-- no debconf information

Debian Bug Tracking System | 1 May 2013 23:21
Picon

Processed: user release.debian.org <at> packages.debian.org, usertagging 694252, tagging 694252

Processing commands for control <at> bugs.debian.org:

> # Not going to be fixed for r0
> user release.debian.org <at> packages.debian.org
Setting user to release.debian.org <at> packages.debian.org (was adam <at> adam-barratt.org.uk).
> usertags 694252 + wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
> tags 694252 + wheezy-ignore
Bug #694252 [sysv-rc] sysv-rc: migration to dependency based boot order fails if bootchart from lenny is
still installed
Added tag(s) wheezy-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
--

-- 
694252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694252
Debian Bug Tracking System
Contact owner <at> bugs.debian.org with problems


Gmane