Your message dated Tue, 20 Sep 2005 18:26:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line S02 symlink is not obsolete
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at bugs) by bugs.debian.org; 12 Sep 2005 23:26:16 +0000
>From [EMAIL PROTECTED] Mon Sep 12 16:26:16 2005
Return-path: <[EMAIL PROTECTED]>
Received: from miranda.se.axis.com [193.13.178.8]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EExgm-0006pT-00; Mon, 12 Sep 2005 16:26:16 -0700
Received: from lassie.se.axis.com (lassie.se.axis.com [193.13.178.6])
by miranda.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id
j8CNPhoX029982
for <[EMAIL PROTECTED]>; Tue, 13 Sep 2005 01:25:43 +0200
Received: from localhost (lassie.se.axis.com [193.13.178.6])
by lassie.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id
j8CNPgQ1005661
for <[EMAIL PROTECTED]>; Tue, 13 Sep 2005 01:25:43 +0200
Date: Tue, 13 Sep 2005 01:25:42 +0200 (CEST)
From: Cristian Ionescu-Idbohrn <[EMAIL PROTECTED]>
Reply-To: Cristian Ionescu-Idbohrn <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: initscripts: mountvirtfs and /etc/default/tmpfs
Message-ID: <[EMAIL PROTECTED]>
X-Sucks: micro$oft
X-User-Tracking: sucks
X-To-Spammers: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: initscripts
Version: 2.86.ds1-1.1
Severity: normal
1. I see these symlinks:
/etc/rcS.d/S02mountvirtfs -> ../init.d/mountvirtfs*
/etc/rcS.d/S36mountvirtfs -> ../init.d/mountvirtfs*
It seems only S36 should exist. There's some code in:
,---- [ /var/lib/dpkg/info/initscripts.postinst ]
| # Defaults for 2.85-16 and up for mountvirtfs levels changed,
| # so remove the existing startup links if we upgraded from
| # an older version.
| #
| case "$oldver" in
| 2.85-1[0-5])
| update-rc.d -f mountvirtfs remove >/dev/null 2>&1 ||:
| ;;
| esac
`----
doing some cleanup, but that happens only for _some_ initscripts
versions. I supose I missed just those $oldver, so I'm stuck with
the S02 symblink. I guess it's safe to manually remove that. Maybe
a more aggresive cleanup is required.
2. I found this line:
,---- [ /etc/default/tmpfs ]
| TMPFS_SIZE=$(expr 32 \* 1024 \* 1024)
`----
which causes this:
/etc/default/tmpfs: line 5: expr: command not found
at boot. I guess that happens because /usr/bin/expr lives on a not
yet mounted partition.
Using this instead:
,----
| TMPFS_SIZE=$((32 * 1024 * 1024))
`----
works better (no errors), but I think it's considered bash-ism and
should be avoided. Is there any other way to do it?
Cheers,
Cristian
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.72
Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968)
Versions of packages initscripts depends on:
ii coreutils 5.2.1-2.1 The GNU core utilities
ii dpkg 1.13.11 package maintenance system for Deb
ii e2fsprogs 1.38-2 ext2 file system utilities and lib
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii util-linux 2.12p-7 Miscellaneous system utilities
initscripts recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 327925-done) by bugs.debian.org; 20 Sep 2005 16:27:39 +0000
>From [EMAIL PROTECTED] Tue Sep 20 09:27:39 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mailservice.tudelft.nl [130.161.131.5]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EHky3-0005Xi-00; Tue, 20 Sep 2005 09:27:39 -0700
Received: from localhost (localhost [127.0.0.1])
by rav.antivirus (Postfix) with ESMTP id 4021B223071
for <[EMAIL PROTECTED]>; Tue, 20 Sep 2005 18:27:07 +0200 (CEST)
Received: from aglu.demon.nl (x082.decis.nl [130.161.177.82])
by mx0.tudelft.nl (Postfix) with ESMTP id 7B5E0223111
for <[EMAIL PROTECTED]>; Tue, 20 Sep 2005 18:27:06 +0200 (CEST)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
by aglu.demon.nl (Postfix) with ESMTP id 15A2C3FF4F
for <[EMAIL PROTECTED]>; Tue, 20 Sep 2005 18:26:32 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 20 Sep 2005 18:26:31 +0200
From: Thomas Hood <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050912)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: S02 symlink is not obsolete
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at tudelft.nl
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Cristian Ionescu-Idbohrn wrote:
> 1. I see these symlinks:
>
> /etc/rcS.d/S02mountvirtfs -> ../init.d/mountvirtfs*
> /etc/rcS.d/S36mountvirtfs -> ../init.d/mountvirtfs*
>
> It seems only S36 should exist.
Why do you conclude that, when initscripts.postinst contains:
updatercd mountvirtfs start 2 S . start 36 S .
The initscript _is_ supposed to run at both S02 and S36.
At one point it ran only at S02 but an extra S symlink was added at
S36, just after S36discover. The changelog entry for version 2.85-16
includes:
* Run mountvirtfs again at S36 so that it mounts /proc/bus/usb in
case usb was loaded as a module (closes: #249031)
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
