On Fri, 24 Jul 2009, Petter Reinholdtsen wrote:
> The system clock is set from the hardware clock by the kernel without
> timezone information, and later in the boot by the hwclock*.sh scripts
You know, given that the only reason to have hwclock around nowadays is to
apply timezone information to
On Fri, 24 Jul 2009, Petter Reinholdtsen wrote:
> I guess we could extend init/runlevel to track this information.
> Would have to extend /dev/initctl protocol and make runlevel suid
> root, I guess. Do init know about the previous runlevel? If not, it
> would have to be extended to have this inf
Package: initscripts
Version: 2.86.ds1-66
Severity: normal
Let me question some stuff:
--- /etc/init.d/bootlogd.dpkg-dist 2009-07-15 00:40:37.0 +0200
+++ /etc/init.d/bootlogd2009-06-30 18:52:53.0 +0200
@@ -12,12 +11,12 @@
### END INIT INFO
PATH=/sbin:/bin # No rem
severity 444276 minor
thanks
[Guillaume]
> So If you have an idea to fix it (without change my BIOS time...)...
Nope, I do not.
The system clock is set from the hardware clock by the kernel without
timezone information, and later in the boot by the hwclock*.sh scripts
with timezone information.
Processing commands for cont...@bugs.debian.org:
> severity 444276 minor
Bug #444276 [initscripts] initscripts: mount /lib/init/rw /proc and /sys with
bad hours
Severity set to 'minor' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug trackin
Is this still a problem with user-mode-linux with the latest version
of sysvinit-utils (version 2.86.ds1-66)? It contain some fixes to
bootlogd.
Happy hacking,
--
Petter Reinholdtsen
___
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.aliot
Your message dated Fri, 24 Jul 2009 22:30:50 +0200
with message-id <20090724203050.ga15...@login1.uio.no>
and subject line Re: Bug#522211: initscripts: System doesn't boot when serial
console and bootlogd enabled
has caused the Debian Bug report #522211,
regarding initscripts: System doesn't boot
[Marco Túlio Gontijo e Silva]
> /etc/inittab:
>
> # The "id" field MUST be the same as the last
> # characters of the device (after "tty").
> (...)
> # Example how to put a getty on a serial line (for a terminal)
> #
> #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
>
> Shouldn't this be S0 instea
Your message dated Fri, 24 Jul 2009 20:06:06 +0200
with message-id <20090724180606.go8...@login2.uio.no>
and subject line Re: sysvinit: Running 'halt' twice within one second results
in system not halting
has caused the Debian Bug report #148819,
regarding sysvinit: Running 'halt' twice within on
Your message dated Fri, 24 Jul 2009 19:52:40 +0200
with message-id <20090724175240.gm8...@login2.uio.no>
and subject line Re: Init Run Level Change Problem
has caused the Debian Bug report #413443,
regarding Init Run Level Change Problem
to be marked as done.
This means that you claim that the pr
Your message dated Fri, 24 Jul 2009 19:56:16 +0200
with message-id <20090724175616.gn8...@login2.uio.no>
and subject line Re: sysvinit: with CONCURRENCY=shell in /etc/default/rcS,
bootlogd don't send boot messages also on console
has caused the Debian Bug report #532904,
regarding sysvinit: with
This patch will activate a warning when such configuration is used.
It could be a good start to get rid of it. Eventualy, I believe we
should detect such calls before doing any changes, and reject the
update-rc.d call.
Index: debian/sysv-rc/sbin/update-rc.d
===
Processing commands for cont...@bugs.debian.org:
> reassign 265801 sysvinit-utils
Bug #265801 [sysvinit] [BOOTLOGD] bootlogd stops too early
Bug reassigned from package 'sysvinit' to 'sysvinit-utils'.
Bug #265801 [sysvinit-utils] [BOOTLOGD] bootlogd stops too early
Ignoring request to alter found
Your message dated Fri, 24 Jul 2009 19:21:51 +0200
with message-id <20090724172151.gj8...@login2.uio.no>
and subject line Re: Bug#510078: add a Short-Description to /etc/init.d/ script
has caused the Debian Bug report #510078,
regarding add a Short-Description to /etc/init.d/ script
to be marked a
tags 375183 - patch
thanks
The provided patch is incomplete. If the documented behaviour of
invoke-rc.d regarding /usr/sbin/policy-rc.d should change, the
documentation need to change too.
Happy hacking,
--
Petter Reinholdtsen
___
Pkg-sysvinit-deve
Processing commands for cont...@bugs.debian.org:
> tags 375183 - patch
Bug #375183 [sysv-rc] invoke-rc.d: Uses hardcoded path to policy-rc.d
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Package: sysv-rc
Version: 2.80-1
Severity: important
I've discovered what I believe is misuse of the sysvinit boot system.
The nslu2-utils package calls update-rc.d like this (see #507545):
update-rc.d zleds start 99 S 1 2 3 4 5 . stop 5 0 1 2 3 4 5 6 .
This inserts both start and stop symlink
FYI: The status of the sysvinit source package
in Debian's testing distribution has changed.
Previous version: 2.86.ds1-63
Current version: 2.86.ds1-65
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you wil
Processing commands for cont...@bugs.debian.org:
> tags 537394 - patch
Bug #537394 [initscripts] initscripts: /etc/rcS.d/S46mountnfs-bootclean.sh
accidently delete vde2 pid files and mgmt files in /var/run/vde2/
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you ne
tags 537394 - patch
thanks
Do not see the patch, so I remove the patch flag.
[Alan Guo]
> For /etc/rcS.d/S12mountall-bootclean.sh cleans /tmp , /var/lock and
> /var/run, I think it is not nessary
> /etc/rcS.d/S46mountnfs-bootclean.sh cleanning /tmp, /var/lock,
> /var/run once again, so I report t
[Petter Reinholdtsen]
> Here is a wild guess. Does it help to apply the patch provided in
> bug #492796?
The patch was part of todays upload of 2.86.ds1-66. Please let me
know if it solve this issue or not.
Happy hacking,
--
Petter Reinholdtsen
__
[Petter Reinholdtsen]
> I believe runlevel uses /var/run/*tmp, and guess its content is bogus.
> Any idea what could mess up the utmp/wtmp files?
It is calling setutent()/getutent() to find the runlevel information,
and this reads /var/run/utmp to get the current status. No idea what
could mess u
[Petter Reinholdtsen]
> Started on this.
I've now done processing all the patches, dropping the ones that are
part of the new upstream tarball. These are the ones left:
% ls debian/patches/
00list 46_pidof_symlinkman.dpatch
94_fstab-decode.dpatch
10_doc_manuals.dpatch
[Petter Reinholdtsen]
> I suspect a good way to do it might be to disable all patches in
> 00list, and then re-introduce the ones we still need.
Started on this.
Wrote a small script to make it easier to handle patches now in the
upstream tarball. Here is a copy in case others got time to help.
Package: sysvinit
Version: 2.86.ds1-65
Severity: minor
/etc/inittab:
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
(...)
# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
Shouldn't this be S0
Your message dated Fri, 24 Jul 2009 09:18:29 +
with message-id
and subject line Bug#492796: fixed in sysvinit 2.86.ds1-66
has caused the Debian Bug report #492796,
regarding /sbin/bootlogd: findpty() fails to fail
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Fri, 24 Jul 2009 09:18:29 +
with message-id
and subject line Bug#531198: fixed in sysvinit 2.86.ds1-66
has caused the Debian Bug report #531198,
regarding initscripts: bootlogd should be stopped after all init scripts
to be marked as done.
This means that you claim that th
Your message dated Fri, 24 Jul 2009 09:18:29 +
with message-id
and subject line Bug#536574: fixed in sysvinit 2.86.ds1-66
has caused the Debian Bug report #536574,
regarding shutdown: missing argument to accton
to be marked as done.
This means that you claim that the problem has been dealt w
Accepted:
initscripts_2.86.ds1-66_i386.deb
to pool/main/s/sysvinit/initscripts_2.86.ds1-66_i386.deb
sysv-rc_2.86.ds1-66_all.deb
to pool/main/s/sysvinit/sysv-rc_2.86.ds1-66_all.deb
sysvinit-utils_2.86.ds1-66_i386.deb
to pool/main/s/sysvinit/sysvinit-utils_2.86.ds1-66_i386.deb
sysvinit_2.86.ds
After uploading the current svn version to unstable, I finally found
the courage to upgrade to the new 2.87dsf upstream tarball. It is
imported into svn now.
I did not yet find time to go through all the patches in
debian/patches/, to disable the ones now inclued in the upstream
tarball. I hope
sysvinit_2.86.ds1-66_i386.changes uploaded successfully to localhost
along with the files:
sysvinit_2.86.ds1-66.dsc
sysvinit_2.86.ds1-66.diff.gz
sysvinit_2.86.ds1-66_i386.deb
sysvinit-utils_2.86.ds1-66_i386.deb
initscripts_2.86.ds1-66_i386.deb
sysv-rc_2.86.ds1-66_all.deb
Greetings,
31 matches
Mail list logo
