Bug#1039246: istgt: ships sysv-init script without systemd unit
Package: istgt Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), istgt has been flagged by Lintian as shipping a sysv-init script without a corresponding systemd unit file. The default init system in Debian is systemd, and so far this worked because a transitional sysv-init-to-unit generator was shipped by systemd. This is in the process of being deprecated and will be removed by the time Trixie ships, so the remaining packages that ship init scripts without systemd units will stop working. There are various advantages to using native units, for example the legacy generator cannot tell the different between a oneshot service and a long running daemon. Also, sanboxing and security features become available for services. For more information, consult the systemd documentation: https://www.freedesktop.org/software/systemd/man/systemd.unit.html You can find the Lintian warning here: https://lintian.debian.org/sources/istgt In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Setting an environment variable for the init in FreeBSD
Hi all, in linux I can set a parameter in the kernel command line, like for example runitdir=somedir , and it will be added to init's environment. Will this work with a FreeBSD kernel? If not, is there a way to achieve the same result? Regards, Lorenzo
Re: List for discussing init system diversity (e.g. sysvinit & elogind)
Hello, Matthew Vernon, le mar. 16 oct. 2018 14:10:23 +0100, a ecrit: > I mentioned this on debian-devel already in the thread about Buster > maybe losing sysvinit support, but I thought it was worth flagging to > the HURD/BSD lists since it seems relevant to your interests :-) FYI, I have bounced most mails of the discussion on -bsd and -hurd. (basically I avoided the flaming mails). But thanks for thinking about it too :) Samuel
List for discussing init system diversity (e.g. sysvinit & elogind)
Hi, I mentioned this on debian-devel already in the thread about Buster maybe losing sysvinit support, but I thought it was worth flagging to the HURD/BSD lists since it seems relevant to your interests :-) There's a couple of posts in the archive of where the elogind for buster work is: http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/2018-October/thread.html And the mailman listinfo page (where you can subscribe and suchlike) is: http://www.chiark.greenend.org.uk/mailman/listinfo/debian-init-diversity [I've set follow-ups there; feel free to redirect to me if relevant] HTH, Matthew
Re: init
On Sat, Jun 25, 2016 at 07:09:35PM +0200, Christoph Egger wrote: > Hi! > > Jon Boden writes: > > What are your plans for the future of init on Debian GNU/kFreeBSD? Are you > > going to continue with sysvinit for the time being? > > > > For the upcoming release of ubuntuBSD I'm thinking about using BusyBox > > + OpenRC > > (https://blog.flameeyes.eu/2012/03/using-busybox-with-openrc). Do you > > think this is a good idea? Is there a particular reason you're staying > > with sysvinit? > > The OpenRC package on debian seems stalled. which means sysvinit is the > one solution that works without further work. There's really not much > more reason why we're still doing sysv. A working openrc package (even > from ubuntu) to test the system certainly would be welcome. Hi Christoph On Ubuntu the original sysvinit package has become unusable so for ubuntuBSD we need a large patch to restore it: https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-xenial/view/head:/sysvinit.diff What's wrong with the current openrc package? It worked fine in my tests. I also managed to make it work with BusyBox Init, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827733 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827718 -- Jon Boden ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS! http://www.ubuntubsd.org/ -- https://twitter.com/ubuntuBSD
Re: init
Hi! Jon Boden writes: > What are your plans for the future of init on Debian GNU/kFreeBSD? Are you > going to continue with sysvinit for the time being? > > For the upcoming release of ubuntuBSD I'm thinking about using BusyBox > + OpenRC > (https://blog.flameeyes.eu/2012/03/using-busybox-with-openrc). Do you > think this is a good idea? Is there a particular reason you're staying > with sysvinit? The OpenRC package on debian seems stalled. which means sysvinit is the one solution that works without further work. There's really not much more reason why we're still doing sysv. A working openrc package (even from ubuntu) to test the system certainly would be welcome. Christoph
Bug#827733: BusyBox Init + OpenRC
Package: busybox
Version: 1.22.0-19
Tags: patch
Hi
With the package added by this patch (busybox-openrc), BusyBox Init can be used
as PID 1 as a launcher for OpenRC (instead of SysV /sbin/init). This has the
potential for faster boot times (but I haven't measured it, see
https://blog.flameeyes.eu/2012/03/using-busybox-with-openrc).
I've only tested it on ubuntuBSD, but I think it should work fine on Debian
too. I've also added Linux and Hurd versions of inittab.
--
Jon Boden
ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS!
http://www.ubuntubsd.org/ -- https://twitter.com/ubuntuBSD
diff -Nur -x changelog ../debian/busybox-openrc.links debian/busybox-openrc.links
--- ../debian/busybox-openrc.links 1970-01-01 01:00:00.0 +0100
+++ debian/busybox-openrc.links 2016-06-20 13:47:35.911041000 +0200
@@ -0,0 +1,4 @@
+bin/busybox sbin/init
+bin/busybox sbin/halt
+bin/busybox sbin/reboot
+bin/busybox sbin/poweroff
diff -Nur -x changelog ../debian/control debian/control
--- ../debian/control 2015-08-07 23:39:01.0 +0200
+++ debian/control 2016-06-20 14:08:19.252858000 +0200
@@ -76,6 +76,23 @@
busybox-initramfs provides a simple stand alone shell that provides
only the basic utilities needed for the initramfs.
+Package: busybox-openrc
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}, busybox, openrc
+Conflicts: sysvinit (<< 2.88dsf-44), sysvinit-core, upstart [linux-any], systemd-sysv [linux-any]
+Section: admin
+Description: BusyBox init for OpenRC
+ BusyBox combines tiny versions of many common UNIX utilities into a single
+ small executable. It provides minimalist replacements for the most common
+ utilities you would usually find on your desktop system (i.e., ls, cp, mv,
+ mount, tar, etc.). The utilities in BusyBox generally have fewer options than
+ their full-featured GNU cousins; however, the options that are included
+ provide the expected functionality and behave very much like their GNU
+ counterparts.
+ .
+ busybox-openrc provides a minimalist implementation of /sbin/init, configured
+ for use with OpenRC.
+
Package: busybox-udeb
Package-Type: udeb
Architecture: any
diff -Nur -x changelog ../debian/inittab.hurd debian/inittab.hurd
--- ../debian/inittab.hurd 1970-01-01 01:00:00.0 +0100
+++ debian/inittab.hurd 2016-06-20 14:12:59.364964000 +0200
@@ -0,0 +1,28 @@
+# /etc/inittab: init(8) configuration.
+
+# Launch OpenRC for system initialization
+::sysinit:/sbin/openrc sysinit
+::wait:/sbin/openrc boot
+::wait:/sbin/openrc default
+
+# What to do when CTRL-ALT-DEL is pressed.
+::ctrlaltdel:/sbin/reboot
+
+# /sbin/getty invocations for the runlevels.
+#
+::respawn:/sbin/getty 38400 tty1
+::respawn:/sbin/getty 38400 tty2
+::respawn:/sbin/getty 38400 tty3
+::respawn:/sbin/getty 38400 tty4
+::respawn:/sbin/getty 38400 tty5
+::respawn:/sbin/getty 38400 tty6
+::respawn:/sbin/getty 38400 console
+
+# Example how to put a getty on a serial line (for a terminal)
+#
+#::respawn:/sbin/getty -L ttyS0 9600 vt100
+#::respawn:/sbin/getty -L ttyS1 9600 vt100
+
+# Example how to put a getty on a modem line.
+#
+#::respawn:/sbin/mgetty -x0 -s 57600 ttyS3
diff -Nur -x changelog ../debian/inittab.kfreebsd debian/inittab.kfreebsd
--- ../debian/inittab.kfreebsd 1970-01-01 01:00:00.0 +0100
+++ debian/inittab.kfreebsd 2016-06-20 14:13:02.382742000 +0200
@@ -0,0 +1,27 @@
+# /etc/inittab: init(8) configuration.
+
+# Launch OpenRC for system initialization
+::sysinit:/sbin/openrc sysinit
+::wait:/sbin/openrc boot
+::wait:/sbin/openrc default
+
+# What to do when CTRL-ALT-DEL is pressed.
+::ctrlaltdel:/sbin/reboot
+
+# /sbin/getty invocations for the runlevels.
+#
+::respawn:/sbin/getty 38400 ttyv0 xterm
+::respawn:/sbin/getty 38400 ttyv1 xterm
+::respawn:/sbin/getty 38400 ttyv2 xterm
+::respawn:/sbin/getty 38400 ttyv3 xterm
+::respawn:/sbin/getty 38400 ttyv4 xterm
+::respawn:/sbin/getty 38400 ttyv5 xterm
+
+# Example how to put a getty on a serial line (for a terminal)
+#
+#::respawn:/sbin/getty -L cuau0 9600 vt100
+#::respawn:/sbin/getty -L cuau1 9600 vt100
+
+# Example how to put a getty on a modem line.
+#
+#::respawn:/sbin/mgetty -x0 -s 57600 ttyd3
diff -Nur -x changelog ../debian/inittab.linux debian/inittab.linux
--- ../debian/inittab.linux 1970-01-01 01:00:00.0 +0100
+++ debian/inittab.linux 2016-06-20 14:13:05.623434000 +0200
@@ -0,0 +1,27 @@
+# /etc/inittab: init(8) configuration.
+
+# Launch OpenRC for system initialization
+::sysinit:/sbin/openrc sysinit
+::wait:/sbin/openrc boot
+::wait:/sbin/openrc default
+
+# What to do when CTRL-ALT-DEL is pressed.
+::ctrlaltdel:/sbin/reboot
+
+# /sbin/getty invocations for the runlevels.
+#
+::respawn:/sbin/getty 38400 tty1
+::respawn:/sbin/getty 38400 tty2
+::respawn:/sbin/getty 38400 tty3
+::respawn:/sbin/getty 38400 tty4
+::respawn:/sbin/getty 38400 tty5
+::respawn:/sbin/getty 38400 tty6
+
+# Example how to put a getty on a serial line (for a terminal)
+#
+#::respawn
Bug#827718: init: open /dev/console on GNU/kFreeBSD
Package: busybox
Version: 1.22.0-19
Tags: patch
FreeBSD kernel doesn't tell PID 1 the pathname of /dev/console through CONSOLE
environment variable like Linux does. Instead it expects PID 1 to always open
/dev/console.
This patch is tested on ubuntuBSD but I think it should work on Debian too (I
haven't tested the whole init yet, but I verified that with my patch it can
print to stdout).
I've also sent it to BusyBox bugzilla:
https://bugs.busybox.net/show_bug.cgi?id=9031
--
Jon Boden
ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS!
http://www.ubuntubsd.org/ -- https://twitter.com/ubuntuBSD
Index: busybox-1.22.0/init/init.c
===
--- busybox-1.22.0.orig/init/init.c
+++ busybox-1.22.0/init/init.c
@@ -277,11 +277,19 @@ static void console_init(void)
#ifdef VT_OPENQRY
int vtno;
#endif
- char *s;
+#if defined(__linux__)
+ char *s;
s = getenv("CONSOLE");
if (!s)
s = getenv("console");
+#elif defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
+ const char *s;
+ s = "/dev/console";
+#else
+#error "we don't know how to open the console on this system"
+#endif
+
if (s) {
int fd = open(s, O_RDWR | O_NONBLOCK | O_NOCTTY);
if (fd >= 0) {
init
Hi What are your plans for the future of init on Debian GNU/kFreeBSD? Are you going to continue with sysvinit for the time being? For the upcoming release of ubuntuBSD I'm thinking about using BusyBox + OpenRC (https://blog.flameeyes.eu/2012/03/using-busybox-with-openrc). Do you think this is a good idea? Is there a particular reason you're staying with sysvinit? -- Jon Boden ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS! http://www.ubuntubsd.org/ -- https://twitter.com/ubuntuBSD
Bug#795354: marked as done (freebsd-utils: init script fails on ZFS root)
Your message dated Thu, 13 Aug 2015 19:04:04 + with message-id and subject line Bug#795354: fixed in freebsd-utils 10.1~svn273304-1+kbsd8u1 has caused the Debian Bug report #795354, regarding freebsd-utils: init script fails on ZFS root 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.) -- 795354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freebsd-utils Version: 10.1~svn273304-1 Severity: normal Tags: pending Hi, The freebsd-utils init script can fail on first boot of a newly- installed system, trying to point /etc/mtab to /proc/mounts, in the case of a ZFS root that is read-only until after the zfs init script has run. sysvinit already handles /etc/mtab now, after making the rootfs writable, so we don't need to do this here. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: freebsd-utils Source-Version: 10.1~svn273304-1+kbsd8u1 We believe that the bug you reported is fixed in the latest version of freebsd-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steven Chamberlain (supplier of updated freebsd-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 26 Oct 2014 18:50:21 + Source: freebsd-utils Binary: freebsd-utils freebsd-utils-udeb kldutils kldutils-udeb kbdcontrol kbdcontrol-udeb vidcontrol freebsd-net-tools freebsd-net-tools-udeb freebsd-nfs-server freebsd-nfs-common geom freebsd-ppp devd devd-udeb ktrace pf powerd mkuzip Architecture: source Version: 10.1~svn273304-1+kbsd8u1 Distribution: jessie-kfreebsd Urgency: medium Maintainer: GNU/kFreeBSD Maintainers Changed-By: Steven Chamberlain Description: devd - device state change monitoring daemon devd-udeb - device state change monitoring daemon (udeb) freebsd-net-tools - FreeBSD networking tools freebsd-net-tools-udeb - FreeBSD networking tools (udeb) freebsd-nfs-common - NFS support files common to client and server freebsd-nfs-server - FreeBSD server utilities needed for NFS on GNU/kFreeBSD freebsd-ppp - FreeBSD Point-to-Point Protocol (PPP) userland daemon freebsd-utils - FreeBSD utilities needed for GNU/kFreeBSD freebsd-utils-udeb - FreeBSD utilities needed for GNU/kFreeBSD (udeb) geom - modular disk I/O request transformation framework kbdcontrol - command-line tool to change keyboard layout on GNU/kFreeBSD kbdcontrol-udeb - command-line tool to change keyboard layout on GNU/kFreeBSD (udeb) kldutils - tools for managing kFreeBSD modules kldutils-udeb - tools for managing kFreeBSD modules (udeb) ktrace - A kernel call tracer mkuzip - Disk image compression utility pf - The OpenBSD Packet Filter powerd - System utility for power control and energy saving vidcontrol - command-line tool to control the system console on GNU/kFreeBSD Closes: 795354 Changes: freebsd-utils (10.1~svn273304-1+kbsd8u1) jessie-kfreebsd; urgency=medium . * Don't set up /etc/mtab here; the root is still read-only at this point, and sysvinit already does this correctly. (Closes: #795354) * fstype_alias.diff: accept some Linux-style names for `mount -t` filesystem types: - ext2 for ext2fs - ext3 for ext3fs - ext4 for ext4fs - cifs for smbfs Checksums-Sha1: 74207f69f411159e20d4b555b1a510cb6e2c1458 3469 freebsd-utils_10.1~svn273304-1+kbsd8u1.dsc 3731a61fc5cc52c795f3b5204a489ad6d4f5c38d 80484 freebsd-utils_10.1~svn273304-1+kbsd8u1.debian.tar.xz Checksums-Sha256: fd5123fb729bee81dfe56aef6f37dad6da9acdfab2a6606eefc57d65442f5113 3469 freebsd-utils_10.1~svn273304-1+kbsd8u1.dsc ed0b3ddb1ed3c313a0373c13d1e7275d1e564f5c28c2226b26ea682036f2d9c3 80484 freebsd-utils_10.1~svn273304
Bug#795354: freebsd-utils: init script fails on ZFS root
Package: freebsd-utils Version: 10.1~svn273304-1 Severity: normal Tags: pending Hi, The freebsd-utils init script can fail on first boot of a newly- installed system, trying to point /etc/mtab to /proc/mounts, in the case of a ZFS root that is read-only until after the zfs init script has run. sysvinit already handles /etc/mtab now, after making the rootfs writable, so we don't need to do this here. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Propellor on kfreebsd (Re: how I wrote init by accident)
Hi, [I don't currently have an OpenID, so was unable to comment directly at http://joeyh.name/blog/entry/how_I_wrote_init_by_accident/ ] Propellor also just accidentally works on Debian GNU/kFreeBSD! In the same way as a Docker container, it can be used as the init for a jail: (some arguments to the jail command omitted for clarity) > root@kfreebsd-amd64:~# jail -c jid=2006 host.hostname=example.com > command=/usr/bin/propellor > if ! cabal build; then cabal configure; cabal build; fi > Building propellor-0.5.1... > Preprocessing executable 'propellor' for propellor-0.5.1... > Preprocessing library propellor-0.5.1... > In-place registering propellor-0.5.1... > Preprocessing executable 'config' for propellor-0.5.1... > ln -sf dist/build/config/config propellor > > > fatal: No remote repository specified. Please, specify either a URL or a > remote name from which new revisions should be fetched. > Git fetch ... failed > merge: origin/master - not something we can merge > running apache2 ... ok > overall ... ok I didn't have a Git master set up, but Apache is running; the FreeBSD jail command lets me spawn 'ps aux' inside it: > root@kfreebsd-amd64:~# jail -m jid=2006 command=/bin/ps aux > USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND > root 25807 0.0 0.0 10468 1396 ?R+ 02:57 0:00 /bin/ps aux > www-data 25797 0.0 0.0 362204 4996 ?S02:57 0:00 > /usr/sbin/apache2 -k start > www-data 25796 0.0 0.0 362204 4996 ?S02:57 0:00 > /usr/sbin/apache2 -k start > root 25793 0.0 0.0 73032 4084 ?Ss 02:57 0:00 > /usr/sbin/apache2 -k start Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5374236f.6000...@pyro.eu.org
Re: Init system for non-Linux ports
On 22/02/2014 03:32, Joel Lopes Da Silva wrote: > I don't really know much more than that, sorry. I'm not a FreeBSD > developer either. I'm just a guy who thinks launchd is a pretty awesome > init system, and who would love to see it more widely used. Well, our hands are pretty busy here. But if you want to help, you could talk to them about their plans for adopting launchd and tell us the results. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/53088ab0.4010...@debian.org
Re: Init system for non-Linux ports
On Friday, February 21, 2014, at 09:04 PM, Robert Millan wrote: > On 21/02/2014 19:09, Joel Lopes Da Silva wrote: > > Furthermore, if you Google some of these big names (launchd, OpenRC and > > systemd), narrowing down the search results to wiki.freebsd.org, it will > > be pretty clear that launchd seems to be only one that’s actually being > > worked on by FreeBSD developers: https://wiki.freebsd.org/launchd > > I couldn’t find any similar page for the other contenders on the FreeBSD > > wiki. > > > > Surely, using the same init system as the one that FreeBSD might use > > someday will be nice for maintaining the Debian GNU/kFreeBSD port in the > > long run. > > That's interesting to hear. Since we're forced to diverge from Debian > GNU/Linux > on this, it'd certainly be helpful if we could synergize with FreeBSD. > > I was silently hoping that FreeBSD might eventually adopt OpenRC if it gains > more traction. What do you know of FreeBSD project position regarding launchd? > > You mentioned some pointers to the wiki which can be used as speculation, but > has this matter actually been proposed/discussed? I don't really know much more than that, sorry. I'm not a FreeBSD developer either. I'm just a guy who thinks launchd is a pretty awesome init system, and who would love to see it more widely used. All I know about the FreeBSD launchd project is actually on that page of the wiki. To summarize it: - FreeBSD apparently sponsored a Google Summer of Code project to port launchd to FreeBSD a while ago; - this last December, someone named R Tyler Croy announced his intent to re-open this project to port launchd to FreeBSD: http://unethicalblogger.com/2013/12/03/scratchiest-neckbeard-freebsd-x200.html - it appears that he might actually be a FreeBSD developer since he has his own page with an @freebsd.org address in the FreeBSD wiki: https://wiki.freebsd.org/RTylerCroy - there's a fair amount of activity in the openlaunchd repository he opened in GitHub: https://github.com/rtyler/openlaunchd But again, I think it's pretty telling that searching for "OpenRC" in the FreeBSD wiki doesn't yield any results. I think your best bet to learn more about the effort is to try to get in touch with R Tyler. There's even a chat room on freenode for this project. Thanks for considering this! -- Joel Lopes Da Silva -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140222033230.ga15...@gmail.com
Re: Init system for non-Linux ports
On 21/02/2014 19:09, Joel Lopes Da Silva wrote: > Furthermore, if you Google some of these big names (launchd, OpenRC and > systemd), narrowing down the search results to wiki.freebsd.org, it will > be pretty clear that launchd seems to be only one that’s actually being > worked on by FreeBSD developers: https://wiki.freebsd.org/launchd > I couldn’t find any similar page for the other contenders on the FreeBSD > wiki. > > Surely, using the same init system as the one that FreeBSD might use > someday will be nice for maintaining the Debian GNU/kFreeBSD port in the > long run. That's interesting to hear. Since we're forced to diverge from Debian GNU/Linux on this, it'd certainly be helpful if we could synergize with FreeBSD. I was silently hoping that FreeBSD might eventually adopt OpenRC if it gains more traction. What do you know of FreeBSD project position regarding launchd? You mentioned some pointers to the wiki which can be used as speculation, but has this matter actually been proposed/discussed? -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5307bf67.1050...@debian.org
Re: Init system for non-Linux ports
Hi folks, I’m just a lambda user of Debian GNU/kFreeBSD, not a Debian Developer or Maintainer. But if I could give you guys my 2 cts, I’d encourage you to really consider launchd for this discussion. It’s a proven system, which has been in use for many years in what’s arguably one of the most widely used flavors of Unix-like OSes, since it powers every single Mac and iOS device out there. And fortunately it's all open source, under the Apache License Version 2.0. Furthermore, if you Google some of these big names (launchd, OpenRC and systemd), narrowing down the search results to wiki.freebsd.org, it will be pretty clear that launchd seems to be only one that’s actually being worked on by FreeBSD developers: https://wiki.freebsd.org/launchd I couldn’t find any similar page for the other contenders on the FreeBSD wiki. Surely, using the same init system as the one that FreeBSD might use someday will be nice for maintaining the Debian GNU/kFreeBSD port in the long run. Cheers, -- Joel Lopes Da Silva -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140221190903.gb10...@gmail.com
Re: default init on non-Linux platforms
Apparently sysvinit scripts must be retained anyway for a smooth migration to jessie; also for easy backporting of jessie packages to wheezy, and maybe other reasons. Non-Linux ports are likely to use those SysV init scripts, though we might invoke them from something other than sysvinit. I know some maintainers would like SysV init scripts to disappear, but the earliest I think that can happen for existing packages would be jessie+1. In that case, we should try to plan for a similar migration from jessie to jessie+1. It's difficult to predict so far ahead, but if it will be a migration to OpenRC, maybe jessie should try to have OpenRC already in place, so that it will be able to use jessie+1's runscripts when they appear and be able to shut down cleanly when SysV init scripts are gone. (I think Thomas was describing the same situation in the context of sid) Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5303f898.7070...@pyro.eu.org
Re: default init on non-Linux platforms
On Tue, Feb 18, 2014 at 05:26:05PM +0100, Christoph Egger wrote: > Hm so why was none of the ports list Cc-ed on this mail? There is > active discussion [0] between hurd and bsd people were we want to go > now. Likewise perhaps pkg-sysvinit-devel should be copied into all such discussions (copied here) -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140218165441.gc2...@bryant.redmars.org
Re: default init on non-Linux platforms
Hi! Ondřej Surý writes: > I don't really want to open another can of worms, but what's the opinion > of non-Linux ports maintainers on default init? Hm so why was none of the ports list Cc-ed on this mail? There is active discussion [0] between hurd and bsd people were we want to go now. > Or maybe I should turn it another way: > > If we have working OpenRC on kFreeBSD and GNU Hurd, can I do: > > Depends: systemd | openrc > > if I want to get rid of non-declarative init scripts in my daemon > packages? As others have said already, sysv init is hardly going away *for* *jessie* (if for upgrades alone). This positions seems to clearly be supported by systemd maintainers as well (I remember particularly discussing things along these lines with e.g. Michael Stapelberg at Debconf). Christoph [0] 52e82fac.2070...@pyro.eu.org and followups -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bny4ie02@anonymous.siccegge.de
Re: Init system for non-Linux ports
Hi, On Sat, Feb 15, 2014 at 02:47:14PM +, Robert Millan wrote: > On 14/02/2014 18:46, Steven Chamberlain wrote: > > Well, we have an announcement today from Canonical - AIUI Upstart will > > be discontinued after Ubuntu 14.04 LTS and they will switch to systemd: > > http://www.markshuttleworth.com/archives/1316 > > I'm not familiar with Ubuntu politics. Is everyone in line with that decision? About upstart as default, my understanding is that (i) defunding upstart development will likely make that question moot cause the Ubuntu community is very probably not interested in putting up the work now that everybody else switches, (ii) I saw statements from other technical board members before Mark's announcement that dropping upstart as default is likely, now that Debian is moving to systemd for the Linux ports. The more interesting question is whether upstart will be continued as a community project and/or supported as an alternative in Debian/Ubuntu. Not sure about that. Michael -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140217165630.ga30...@raptor.chemicalconnection.dyndns.org
Re: Init system for non-Linux ports
On 14/02/2014 18:46, Steven Chamberlain wrote: > Well, we have an announcement today from Canonical - AIUI Upstart will > be discontinued after Ubuntu 14.04 LTS and they will switch to systemd: > http://www.markshuttleworth.com/archives/1316 I'm not familiar with Ubuntu politics. Is everyone in line with that decision? -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52ff7df2.1040...@debian.org
Re: Init system for non-Linux ports
On 12/02/14 12:40, Steven Chamberlain wrote: > In particular I wonder what Ubuntu will do, and > if Upstart has a future at all. Well, we have an announcement today from Canonical - AIUI Upstart will be discontinued after Ubuntu 14.04 LTS and they will switch to systemd: http://www.markshuttleworth.com/archives/1316 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fe6490.8040...@pyro.eu.org
Re: Init system for non-Linux ports
On 12 February 2014 12:23, Robert Millan wrote: > On 12/02/2014 12:09, Steven Chamberlain wrote: >> There are a few reasons to keep sysvinit scripts maintained for jessie: >> 1. for smoother upgrades from wheezy >> 2. in order to backport jessie packages to wheezy >> 3. for non-Linux (or non-systemd) ports >> >> So ports are not the only reason. And yet all of the above points still >> apply to ports; we'd have to support sysvinit even if we went with >> something else. > > If we have to support it anyway, is it really worth spending effort on > Upstart/OpenRC for Jessie? > > IMHO it'd be safer to wait and see where things go. For example, are Upstart > developers serious about portability or was this just an experiment? Is > OpenRC going to be adopted by FreeBSD and/or other BSDs? > Yes, a few upstart upstream developers are interested in porting to kFreebsd, and later to Freebsd. If packages follow the current policy, there shouldn't be much additional work once upstart is supported on those platforms. Integration-wise, there will be needed to inspect and/or tweak a few jobs where things don't match up (e.g. udev <-> devd events). We didn't start on Hurd yet. In the best interest of Debian/kFreeBSD, it is probably best to stick with sysv-init as default for jessie, and have alternatives fully available by feature freeze such that a switch can be made for jessie+1. This is simply because no init alternatives exist on !Debian/Linux in squeeze already, and e.g. on Debian/Linux upstart/systemd already exist as working alternatives on squeeze systems. Out of all the open-source operating systems, i'm yet to see one that introduce new init and switch to it by default in a single upgrade. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhlughvwru+8cvawtrgzjj5_p_qboke_rreqtnp1m6onu...@mail.gmail.com
Re: Init system for non-Linux ports
On 12/02/14 13:18, Robert Millan wrote: > Or maybe backward compat? I hear some of the new init implementations > support SysV. SysV init scripts? I thought this was obvious, or maybe I misunderstand what you mean. *All* of the init systems that were discussed by the TC, even systemd (for now), can use existing SysV init scripts. This is important to know, because some (perhaps most) packages may not bother creating systemd unit files at all for jessie, and continue to fully maintain the SysV init scripts they already have. And adopting any new init system for jessie is made considerably easier by using the same init scripts as sysvinit. SysV init scripts can be overridden by creating a new runscript/job of the same name. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb7974.60...@pyro.eu.org
Re: Init system for non-Linux ports
On 12/02/2014 12:40, Steven Chamberlain wrote: > Although, come jessie+1, I wonder how upgrades will be handled, if > sysvinit scripts go away. Maybe Pre-Depends. Or maybe have written instructions to install the new init by hand, like we often do for kernels. Or maybe backward compat? I hear some of the new init implementations support SysV. I think having one or more replacements in good shape would be nice, but I doubt we'll be in trouble because of this. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb74a1.8070...@debian.org
Re: Init system for non-Linux ports
On 12/02/14 12:23, Robert Millan wrote: > If we have to support it anyway, is it really worth spending effort on > Upstart/OpenRC for Jessie? Right, sysvinit is a viable and easy option for jessie; having any other init systems working is a bonus. At least we know now that we need to concentrate on maintaining sysvinit scripts. Although, come jessie+1, I wonder how upgrades will be handled, if sysvinit scripts go away. Maybe it is preferable to have some new init system *already* in place, as default in jessie. But it's difficult to predict so far ahead. > IMHO it'd be safer to wait and see where things go. I agree, a lot could change now that GNU/Linux has chosen systemd, and we have plenty of time. In particular I wonder what Ubuntu will do, and if Upstart has a future at all. The still-ongoing GNOME/logind issue may have some impact on that. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb6bb7.5020...@pyro.eu.org
Re: Init system for non-Linux ports
On 12/02/2014 12:09, Steven Chamberlain wrote: > There are a few reasons to keep sysvinit scripts maintained for jessie: > 1. for smoother upgrades from wheezy > 2. in order to backport jessie packages to wheezy > 3. for non-Linux (or non-systemd) ports > > So ports are not the only reason. And yet all of the above points still > apply to ports; we'd have to support sysvinit even if we went with > something else. If we have to support it anyway, is it really worth spending effort on Upstart/OpenRC for Jessie? IMHO it'd be safer to wait and see where things go. For example, are Upstart developers serious about portability or was this just an experiment? Is OpenRC going to be adopted by FreeBSD and/or other BSDs? -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb67d2.4000...@debian.org
[Fwd: Re: Init system for non-Linux ports]
Forwarded Message From: Svante Signell To: debian-h...@lists.debian.org Subject: Re: Init system for non-Linux ports Date: Wed, 12 Feb 2014 13:02:45 +0100 On Wed, 2014-02-12 at 10:45 +, Robert Millan wrote: > On 29/01/2014 09:26, Petr Salinger wrote: > What is the current status of OpenRC? Is it usable? I fear that it is currently broken since one of the latest patches. Do you have a (scrappable) pre-installed image I can download, ala: http://people.debian.org/~sthibault/hurd-i386/ -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1392206649.10315.16.ca...@s1499.it.kth.se
Re: Init system for non-Linux ports
On 12/02/14 10:45, Robert Millan wrote: > I'm a bit afraid that even if sysvinit itself stays mostly fine, the scripts > written for > it could turn into a bunch of bitrot. There are a few reasons to keep sysvinit scripts maintained for jessie: 1. for smoother upgrades from wheezy 2. in order to backport jessie packages to wheezy 3. for non-Linux (or non-systemd) ports So ports are not the only reason. And yet all of the above points still apply to ports; we'd have to support sysvinit even if we went with something else. I don't think it matters much what we choose, but seems we'd want to make use of legacy sysvinit compatibility - write very few scripts in specific formats (e.g. OpenRC runscripts / Upstart jobs). We probably have right up until freeze to make a preference, and perhaps by then there will be more than one fully-working init system. GNU/Hurd porters already said they aim to maintain sysvinit scripts: https://lists.debian.org/debian-hurd/2014/01/msg00051.html And there are plenty of GNU/Linux users who will want to run systems without systemd. (individuals, derivatives, quite possibly Google). Thinking ahead, package maintainers won't have such need to support sysvinit for jessie+1 so that's when we'll really have problems. Having something like OpenRC or Upstart might allow to add/override broken init scripts with native/declarative ones. Perhaps by then we'll have new ways to convert init scripts or generate them from metalanguage; or built-in support for reading each others' formats. > And AFAICS we may be able to use Upstart some time in the future but this > doesn't seem > possible right now. We could initially ask the maintainer to apply Dmitri's patches and try to keep it building on kfreebsd. And just keep it around for people to play around with and possibly get it fully working. IIRC it runs, but will need early boot scripts re-writing, equivalent to /etc/rcS.d/ > What is the current status of OpenRC? Is it usable? Pretty good as I recall; it was very easy to test using jails. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb647f.3090...@pyro.eu.org
Re: [Fwd: Re: Init system for non-Linux ports]
On 12/02/14 12:04, Svante Signell wrote: > I fear that it is currently broken since one of the latest patches. Do > you have a (scrappable) pre-installed image I can download, ala: > http://people.debian.org/~sthibault/hurd-i386/ Yes, Aurelien Jarno has kindly made these: > http://blog.aurel32.net/153 > http://people.debian.org/~aurel32/qemu/ Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb63f3.1030...@pyro.eu.org
Re: Init system for non-Linux ports
On 29/01/2014 09:26, Petr Salinger wrote: >> 1. stay with sysvinit >> 2. switch to OpenRC unconditionally >> 3. switch to Upstart unconditionally >> 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC >> 5. further discussion >> >> Please rank the above putting your preferred option first, as per >> Debian's usual Condorcet voting system. This is totally non-binding, >> I'm most interested in hearing people's ideas, questions, or the reasons >> for their choices. > > I would add also > 6. switch to Upstart only if Linux uses it by default, otherwise stay with > sysvinit > > My preference is > > 6-5-1,2,4-3 We have less options now ;-) I'm a bit afraid that even if sysvinit itself stays mostly fine, the scripts written for it could turn into a bunch of bitrot. And AFAICS we may be able to use Upstart some time in the future but this doesn't seem possible right now. What is the current status of OpenRC? Is it usable? -- Robert Millan -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52fb50d4.1010...@debian.org
Re: [draft] Debian/Hurd porters position in the default init system debate
On 31/01/14 10:57, Justus Winter wrote: > 1. Up to this day, Debian/Hurd has never used the current default init > system (sysvinit) but has relied on its own init and rc system. We > are prepared to use a non-default init system in the future. This will become increasingly difficult when SysV init scripts stop being maintained... and in new packages perhaps not provided at all. > 3. We ask that the current sysvinit-compatible init scripts are left > in place, so that we can use sysvinit in the future. Some maintainers want to discontinue providing sysvinit scripts right away. Policy *may* require them to do so for jessie, but likely not for jessie+1. > 4. We acknowledge that there is a maintenance cost involved with > keeping the current init scripts. We will help maintain them as part > of our porting effort. I'd like for this work to be minimised by sharing across GNU/Hurd, kFreeBSD and even with GNU/Linux users who don't want to use the default init system. So, does this mean SysV init scripts are your preferred format? In which case it's not so important for the ports to choose the same init system, since anything can use these. But if for example you'd planned to maintain OpenRC-specific runscripts instead, that would be a reason for kFreeBSD to consider using OpenRC. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52eb9cd7.50...@pyro.eu.org
Re: Init system for non-Linux ports
I'm only a kFreeBSD user and don't have any official standing within the Debian project, but all the same my preferences are 614253 where 6. is the proposed alternative to switch to Upstart if Linux uses it, otherwise sysvinit. Jeff -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140129160233.gb12...@unpythonic.net
Re: Init system for non-Linux ports
Hi! Robert Millan writes: > [ 3 ] 1. stay with sysvinit > [ 3 ] 2. switch to OpenRC unconditionally > [ 3 ] 3. switch to Upstart unconditionally > [ 1 ] 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC > [ 2 ] 5. further discussion Petr Salinger writes: > I would add also > 6. switch to Upstart only if Linux uses it by default, otherwise stay with > sysvinit > > My preference is > > 6-5-1,2,4-3 I agree we should follow Linux *iff* doing so is feasible. Apart from that I haven't put enough time into details to really have a founded opinion there => (6=4) 5 (1=2=3) Robert Millan writes: > Btw is the tech-ctte going to force both ports to use the same option? This > might > have a significant effect on options 3 and 4, depending on the viability of > Upstart > on the Hurd (which I'm totally ignorant of). I'm the tech-ctte will even consider deciding anything for !linux without a really good reason. As long as we (the kfreebsd people) and the hurd people each find something that works for us we should be fine. The only thing from the tech-ctte / GR discussions that might affect us is, if the project decides to drop support for some init system. Christoph -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mwiff3ea@mitoraj.siccegge.de
Re: Init system for non-Linux ports
1. stay with sysvinit 2. switch to OpenRC unconditionally 3. switch to Upstart unconditionally 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC 5. further discussion Please rank the above putting your preferred option first, as per Debian's usual Condorcet voting system. This is totally non-binding, I'm most interested in hearing people's ideas, questions, or the reasons for their choices. I would add also 6. switch to Upstart only if Linux uses it by default, otherwise stay with sysvinit My preference is 6-5-1,2,4-3 Petr -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.lnx.2.00.1401291025160.15...@contest.felk.cvut.cz
Re: Init system for non-Linux ports
On 28/01/14 22:31, Steven Chamberlain wrote: > 1. stay with sysvinit I know that would be the least work, but I think we should take the opportunity to switch now to one of the modern init systems. Some package maintainers specifically expressed that they don't want to maintain SysV init scripts for much longer; any other init system at least gives them one alternate syntax. > 2. switch to OpenRC unconditionally > 3. switch to Upstart unconditionally > 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC > 5. further discussion My preferences at the moment would be: 2 4 1 3 5 I really appreciate the recent work toward porting libnih and Upstart, but unless Debian was *fully* behind it I don't think we'd gain much for the additional complexity. The event model seems a key difference to me. It sounds better suited to laptops, portable devices and hot-plugging, whereas for now I think the non-Linux ports still need the robustness and simplicity of a traditional dependency model, even if it lacks speed or some special features. OpenRC is *very* simple code, and BSD-licensed, which I think we could more easily extend to our needs. It works almost well enough already to boot GNU/kFreeBSD, and also inside BSD jails. I've read that it is built and somewhat usable on GNU/Hurd, though I don't know how much more work would be still needed (probably rewrite of the early rcS.d scripts). And whichever one is used for the jessie release, it maybe won't hurt to keep the other one around, built and available to play around with, but unsupported. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Re: Init system for non-Linux ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/01/2014 23:31, Steven Chamberlain wrote: > Here are the options I can think of - but let me know if you want > something not represented here: > > 1. stay with sysvinit > 2. switch to OpenRC unconditionally > 3. switch to Upstart unconditionally > 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC > 5. further discussion > > Please rank the above putting your preferred option first, as per > Debian's usual Condorcet voting system. This is totally non-binding, > I'm most interested in hearing people's ideas, questions, or the reasons > for their choices. [ 3 ] 1. stay with sysvinit [ 3 ] 2. switch to OpenRC unconditionally [ 3 ] 3. switch to Upstart unconditionally [ 1 ] 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC [ 2 ] 5. further discussion Btw is the tech-ctte going to force both ports to use the same option? This might have a significant effect on options 3 and 4, depending on the viability of Upstart on the Hurd (which I'm totally ignorant of). - -- Robert Millan -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLoNHAACgkQC19io6rUCv+gIwCeMIIt66QpJEE+EnmqvXJM0zvc rsYAn28O23lAlEkLtoVZAiw/OUj8xx43 =HCd6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e83470.4080...@debian.org
Re: Init system for non-Linux ports
Em 2014-01-28 20:31, Steven Chamberlain escreveu: Hi everyone, "What init system would we like to use by default on the non-Linux ports for jessie?" I hope this question is really as straightforward as it looks, and that we might come to some general agreement much more quickly than the tech-ctte bug! Here are the options I can think of - but let me know if you want something not represented here: 1. stay with sysvinit 2. switch to OpenRC unconditionally 3. switch to Upstart unconditionally 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC 5. further discussion Please rank the above putting your preferred option first, as per Debian's usual Condorcet voting system. This is totally non-binding, I'm most interested in hearing people's ideas, questions, or the reasons for their choices. Thanks! Regards, 4 or 1...a good idea would be openlaunchd...if Debian adopt openlaunchd, would be the first GNU distro to have the Apple init system. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b33a374cb9d9e9600f837d123f9c...@openmailbox.org
Init system for non-Linux ports
Hi everyone, "What init system would we like to use by default on the non-Linux ports for jessie?" I hope this question is really as straightforward as it looks, and that we might come to some general agreement much more quickly than the tech-ctte bug! Here are the options I can think of - but let me know if you want something not represented here: 1. stay with sysvinit 2. switch to OpenRC unconditionally 3. switch to Upstart unconditionally 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC 5. further discussion Please rank the above putting your preferred option first, as per Debian's usual Condorcet voting system. This is totally non-binding, I'm most interested in hearing people's ideas, questions, or the reasons for their choices. Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: OpenPGP digital signature
Re: Bug#727708: tech-ctte: Decide which init system to default to in Debian.
On 29/10/13 01:34, Steven Chamberlain wrote: > Actually quite amazing how painless that was, though I most certainly > don't expect it to be functional yet. I have tested it now. It's actually running and doing 'something'! And it is colourful. I'm testing it inside of a BSD jail currently. This is a remarkably easy environment for debugging. I can alternatively enter a fully working bash shall or prod in the jail's chroot directly. > # jail -J /var/run/jail/$JID.jid -c jid=$JID name=jail$JID > path=/srv/jail/$JID host.hostname=$HOSTNAME ip4.addr=$IP > command=/sbin/rc sysinit > >OpenRC 0.10.9429351 is starting up GNU/kFreeBSD 9.0-2-amd64-xenhvm (x86_64) > > mdconfig: ioctl(/dev/mdctl): Device or resource busy > /libexec/rc/sh/init.sh: 18: /libexec/rc/sh/init-common-post.sh: newfs: not > found > mount: /dev/md0 : Operation not permitted I think it was trying to create a FreeBSD-style ramdisk, which is probably not possible inside a jail. May need to skip whatever it is trying to do there, or pre-create a tmpfs inside the jail before I try to boot it. # jail -J /var/run/jail/$JID.jid -c jid=$JID name=jail$JID path=/srv/jail/$JID host.hostname=$HOSTNAME ip4.addr=$IP command=/sbin/rc boot > * Checking local filesystems ... > /libexec/rc/sh/runscript.sh: 90: /libexec/rc/sh/runscript.sh: fsck: not found > * Filesystems couldn't be fixed > >[ !! ] > * rc: Aborting! > * fsck: caught SIGTERM, aborting Indeed I do not have an fsck, since util-linux depends on initscripts depends on sysv-rc so it disappeared. This is unnecessary inside a jail anyway. That's as far as I got with this tonight, but just to let you know that OpenRC is somewhat alive on GNU/kFreeBSD. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/527055be.6090...@pyro.eu.org
Re: Bug#727708: tech-ctte: Decide which init system to default to in Debian.
Hi,
On Sun, 27 Oct 2013 02:47:56 +0800 Thomas Goirand wrote:
> Note that OpenRC already works on some (non-Debian) BSD platforms, and
> that it should be trivial to have it to build on kFreeBSD and Hurd,
And so I came up with the attached patch which gets it building on
GNU/kFreeBSD, and it passed whatever tests are run during build. I
actually chose Linux implementations for most things, which are really
provided by GNU libc or /proc.
Actually quite amazing how painless that was, though I most certainly
don't expect it to be functional yet. (For example, I expect it still
needs to know about linprocfs, linsysfs, tmpfs and maybe devfs).
I look forward to seeing OpenRC in the Debian archive. Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/etc/rc.conf.GNU-kFreeBSD b/etc/rc.conf.GNU-kFreeBSD
new file mode 100644
index 000..e138e3a
--- /dev/null
+++ b/etc/rc.conf.GNU-kFreeBSD
@@ -0,0 +1,12 @@
+##
+# GNU/kFreeBSD SPECIFIC OPTIONS
+
+# This is the subsystem type. Valid options on GNU/kFreeBSD:
+# ""- nothing special
+# "jail"- FreeBSD jails (not yet implemented)
+# If this is commented out, automatic detection will be used.
+#
+# This should be set to the value representing the environment this file is
+# PRESENTLY in, not the virtualization the environment is capable of.
+#rc_sys=""
+
diff --git a/mk/os-GNU-kFreeBSD.mk b/mk/os-GNU-kFreeBSD.mk
new file mode 100644
index 000..9fc9313
--- /dev/null
+++ b/mk/os-GNU-kFreeBSD.mk
@@ -0,0 +1,10 @@
+# Copyright (c) 2008 Roy Marples
+# Released under the 2-clause BSD license.
+
+# Generic definitions
+
+PKG_PREFIX?= /usr/local
+SFX= .BSD.in
+
+CPPFLAGS+= -D_BSD_SOURCE -D_XOPEN_SOURCE=700
+LIBDL= -Wl,-Bdynamic -ldl
diff --git a/mk/os.mk b/mk/os.mk
index 3e18962..6b2d428 100644
--- a/mk/os.mk
+++ b/mk/os.mk
@@ -3,7 +3,7 @@
# Generic definitions
-_OS_SH= uname -s
+_OS_SH= uname -s | tr '/' '-'
_OS:= $(shell ${_OS_SH})
OS?= ${_OS}
include ${MK}/os-${OS}.mk
diff --git a/src/librc/librc-daemon.c b/src/librc/librc-daemon.c
index 982da35..7a860c6 100644
--- a/src/librc/librc-daemon.c
+++ b/src/librc/librc-daemon.c
@@ -30,7 +30,7 @@
#include "librc.h"
-#if defined(__linux__)
+#if defined(__linux__) || defined (__GLIBC__)
static bool
pid_is_exec(pid_t pid, const char *exec)
{
diff --git a/src/rc/mountinfo.c b/src/rc/mountinfo.c
index eaace13..1006a0c 100644
--- a/src/rc/mountinfo.c
+++ b/src/rc/mountinfo.c
@@ -39,7 +39,7 @@
# include
# define statfs statvfs
# define F_FLAGS f_flag
-#elif defined (__linux__)
+#elif defined (__linux__) || defined (__GLIBC__)
# include
#endif
@@ -265,7 +265,7 @@ find_mounts(struct args *args)
return list;
}
-#elif defined (__linux__)
+#elif defined (__linux__) || defined (__GLIBC__)
static struct mntent *
getmntfile(const char *file)
{
diff --git a/src/rc/rc-logger.c b/src/rc/rc-logger.c
index 468225f..e8fb0ff 100644
--- a/src/rc/rc-logger.c
+++ b/src/rc/rc-logger.c
@@ -44,7 +44,7 @@
#include
#include
-#ifdef __linux__
+#if defined(__linux__) || defined(__GLIBC__)
# include
#elif defined(__NetBSD__) || defined(__OpenBSD__)
# include
diff --git a/src/rc/runscript.c b/src/rc/runscript.c
index e504e4a..f14db11 100644
--- a/src/rc/runscript.c
+++ b/src/rc/runscript.c
@@ -52,7 +52,7 @@
#include
#include
-#ifdef __linux__
+#if defined(__linux__) || defined(__GLIBC__)
# include
#elif defined(__NetBSD__) || defined(__OpenBSD__)
# include
Bug#721446: marked as done (nfsiod: Init script needs output formatting.)
Your message dated Wed, 02 Oct 2013 23:34:02 + with message-id and subject line Bug#721446: fixed in freebsd-utils 9.2-1 has caused the Debian Bug report #721446, regarding nfsiod: Init script needs output formatting. 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.) -- 721446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721446 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freebsd-nfs-common Version: 9.0+ds1-11~deb7u1 Severity: normal Tags: patch As nfsiod is started the executable emits some text. This upsets the message flow crafted by log_msg_*. The following patch silences that glitch. Regards, Mats Erik Andersson, DM --- etc/init.d/nfsiod.orig 2013-03-18 10:32:55.0 + +++ etc/init.d/nfsiod 2013-08-25 23:30:10.0 + @@ -43,7 +43,7 @@ start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \ - $DAEMON_ARGS \ + $DAEMON_ARGS > /dev/null \ || return 2 # Add code here, if necessary, that waits for the process to be ready # to handle requests from services started subsequently which depend --- End Message --- --- Begin Message --- Source: freebsd-utils Source-Version: 9.2-1 We believe that the bug you reported is fixed in the latest version of freebsd-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 721...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Millan (supplier of updated freebsd-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 03 Oct 2013 01:21:38 +0200 Source: freebsd-utils Binary: freebsd-utils freebsd-utils-udeb kldutils kldutils-udeb kbdcontrol kbdcontrol-udeb vidcontrol freebsd-net-tools freebsd-net-tools-udeb freebsd-nfs-server freebsd-nfs-common geom freebsd-geom freebsd-ppp devd devd-udeb ktrace pf powerd mkuzip Architecture: source kfreebsd-amd64 Version: 9.2-1 Distribution: unstable Urgency: low Maintainer: GNU/kFreeBSD Maintainers Changed-By: Robert Millan Description: devd - device state change monitoring daemon devd-udeb - device state change monitoring daemon (udeb) freebsd-geom - modular disk I/O request transformation framework (meta-package) freebsd-net-tools - FreeBSD networking tools freebsd-net-tools-udeb - FreeBSD networking tools (udeb) freebsd-nfs-common - NFS support files common to client and server freebsd-nfs-server - FreeBSD server utilities needed for NFS on GNU/kFreeBSD freebsd-ppp - FreeBSD Point-to-Point Protocol (PPP) userland daemon freebsd-utils - FreeBSD utilities needed for GNU/kFreeBSD freebsd-utils-udeb - FreeBSD utilities needed for GNU/kFreeBSD (udeb) geom - modular disk I/O request transformation framework kbdcontrol - command-line tool to change keyboard layout on GNU/kFreeBSD kbdcontrol-udeb - command-line tool to change keyboard layout on GNU/kFreeBSD (udeb) kldutils - tools for managing kFreeBSD modules kldutils-udeb - tools for managing kFreeBSD modules (udeb) ktrace - A kernel call tracer mkuzip - Disk image compression utility pf - The OpenBSD Packet Filter powerd - System utility for power control and energy saving vidcontrol - command-line tool to control the system console on GNU/kFreeBSD Closes: 721446 Changes: freebsd-utils (9.2-1) unstable; urgency=low . * New upstream release. - Refresh all patches. - Bump B-D on freebsd-glue and libcam-dev. . [ Robert Millan ] * Misc adjustments for freebsd-glue 0.1.0. * Reduce the patchset even further by using trimdomain, link_addr and link_ntoa from freebsd-glue. * Improve output formatting in nfsiod init script. Thanks Mats Erik Andersson. (Closes: #721446) Checksums-Sha1: a42147ca7931ea9b7671c7d9d50c220abc66475b 2783 freebsd-utils_9.2-1.dsc 347befa2db5c6203a8cd269256c9f22585134cb1 2134646 freebsd-utils_9.2.orig.tar.gz 89601ba497301d3269725b0d65e5201b897d8bbf 135070 freebsd-utils_9.2-1.debian.tar.gz 44313c2ae4da85fecfc5fe4541e3b801ac13018c 253476 freebsd-utils_9.2-1_kfreebsd-amd
Bug#721446: nfsiod: Init script needs output formatting.
Package: freebsd-nfs-common Version: 9.0+ds1-11~deb7u1 Severity: normal Tags: patch As nfsiod is started the executable emits some text. This upsets the message flow crafted by log_msg_*. The following patch silences that glitch. Regards, Mats Erik Andersson, DM --- etc/init.d/nfsiod.orig 2013-03-18 10:32:55.0 + +++ etc/init.d/nfsiod 2013-08-25 23:30:10.0 + @@ -43,7 +43,7 @@ start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \ - $DAEMON_ARGS \ + $DAEMON_ARGS > /dev/null \ || return 2 # Add code here, if necessary, that waits for the process to be ready # to handle requests from services started subsequently which depend
Bug#695679: marked as done (freebsd-utils: Init script fails in jail, breaks dist-upgrade)
Your message dated Sun, 30 Dec 2012 00:33:22 + with message-id and subject line Bug#695679: fixed in freebsd-utils 9.0+ds1-9 has caused the Debian Bug report #695679, regarding freebsd-utils: Init script fails in jail, breaks dist-upgrade 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.) -- 695679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freebsd-utils Version: 9.0+ds1-8 Severity: normal Dear Maintainer, I am running Debian GNU/kFreeBSD jailed on a native FreeBSD 9 machine. Trying to dist-upgrade from squeeze to wheezy I get this: Setting up freebsd-utils (9.0+ds1-8) ... Installing new version of config file /etc/init.d/freebsd-utils ... [] Loading devfs rules...devfs ruleset: ioctl DEVFSIO_SUSE: Operation not permitted invoke-rc.d: initscript freebsd-utils, action "start" failed. dpkg: error processing freebsd-utils (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: freebsd-utils E: Sub-process /usr/bin/dpkg returned an error code (1) It's easy enough to work around this issue (exit 0 in the init script does the trick) but it's a little annoying and would be nice to have fixed. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-RELEASE-p3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages freebsd-utils depends on: ii libbsd0 0.4.2-1 ii libc0.1 2.13-37 ii libcam6 9.0+ds1-3 ii libgeom19.0+ds1-3 ii libjail19.0+ds1-3 ii libkiconv4 9.0+ds1-3 ii libkvm0 9.0+ds1-3 ii libsbuf69.0+ds1-3 ii libtirpc1 0.2.2-5 ii lsb-base4.1+Debian8 ii zlib1g 1:1.2.7.dfsg-13 freebsd-utils recommends no packages. Versions of packages freebsd-utils suggests: pn freebsd-hackedutils ii kbdcontrol 9.0+ds1-8 pn vidcontrol -- no debconf information --- End Message --- --- Begin Message --- Source: freebsd-utils Source-Version: 9.0+ds1-9 We believe that the bug you reported is fixed in the latest version of freebsd-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 695...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steven Chamberlain (supplier of updated freebsd-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 11 Dec 2012 20:28:30 + Source: freebsd-utils Binary: freebsd-utils freebsd-utils-udeb kldutils kldutils-udeb kbdcontrol kbdcontrol-udeb vidcontrol freebsd-net-tools freebsd-net-tools-udeb freebsd-nfs-server freebsd-nfs-common geom freebsd-geom freebsd-ppp devd devd-udeb ktrace pf powerd mkuzip Architecture: source kfreebsd-amd64 Version: 9.0+ds1-9 Distribution: unstable Urgency: low Maintainer: GNU/kFreeBSD Maintainers Changed-By: Steven Chamberlain Description: devd - device state change monitoring daemon devd-udeb - device state change monitoring daemon (udeb) freebsd-geom - modular disk I/O request transformation framework (meta-package) freebsd-net-tools - FreeBSD networking tools freebsd-net-tools-udeb - FreeBSD networking tools (udeb) freebsd-nfs-common - NFS support files common to client and server freebsd-nfs-server - FreeBSD server utilities needed for NFS on GNU/kFreeBSD freebsd-ppp - FreeBSD Point-to-Point Protocol (PPP) userland daemon freebsd-utils - FreeBSD utilities needed for GNU/kFreeBSD freebsd-utils-udeb - FreeBSD utilities needed for GNU/kFreeBSD (udeb) geom - modular disk I/O request transformation framework kbdcontrol - command-line tool to change keyboard layout on GNU/kFreeBSD kbdcontrol-udeb - command-line tool to change keyboard layout on GNU/kFreeBSD (udeb) kldutils - tools for managing kFreeBSD modules kldutils-udeb - tools for managing kFreeBSD modules (udeb) ktrace - A kernel call tracer mkuzip - Disk image compression utility pf - The
Processed: Re: Bug#695679: freebsd-utils: Init script fails in jail, breaks dist-upgrade
Processing control commands: > tags -1 + confirmed patch Bug #695679 [freebsd-utils] freebsd-utils: Init script fails in jail, breaks dist-upgrade Added tag(s) confirmed and patch. > severity -1 important Bug #695679 [freebsd-utils] freebsd-utils: Init script fails in jail, breaks dist-upgrade Severity set to 'important' from 'normal' -- 695679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b695679.135525925525611.transcr...@bugs.debian.org
Re: Bug#695679: freebsd-utils: Init script fails in jail, breaks dist-upgrade
Control: tags -1 + confirmed patch Control: severity -1 important On 11/12/12 16:20, Stefan Ott wrote: > Setting up freebsd-utils (9.0+ds1-8) ... > Installing new version of config file /etc/init.d/freebsd-utils ... > [] Loading devfs rules...devfs ruleset: ioctl DEVFSIO_SUSE: > Operation not permitted > invoke-rc.d: initscript freebsd-utils, action "start" failed. > dpkg: error processing freebsd-utils (--configure): > subprocess installed post-installation script returned error exit > status 1 > configured to not write apport reports > Errors were encountered while processing: > freebsd-utils > E: Sub-process /usr/bin/dpkg returned an error code (1) Hi! This is reproducible in jails on 'native' Debian GNU/kFreeBSD as well. I think it may be better if the initscript just warns if devfs seems unavailable, and exit with status 0; in a jail with default settings the rest of the initscript (e.g. mounting kernel filesystems) can't function anyway. With a change I just committed to SVN it now looks like this: # /etc/init.d/freebsd-utils start [] Loading devfs rules...devfs ruleset: ioctl DEVFSIO_SUSE: Operation not permitted (warning). # echo $? 0 Please review/test this change if you can: http://anonscm.debian.org/viewvc/glibc-bsd/trunk/freebsd-utils/debian/freebsd-utils.init?r1=3414&r2=4376&view=patch Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50c79d65.1090...@pyro.eu.org
Bug#695679: freebsd-utils: Init script fails in jail, breaks dist-upgrade
Package: freebsd-utils Version: 9.0+ds1-8 Severity: normal Dear Maintainer, I am running Debian GNU/kFreeBSD jailed on a native FreeBSD 9 machine. Trying to dist-upgrade from squeeze to wheezy I get this: Setting up freebsd-utils (9.0+ds1-8) ... Installing new version of config file /etc/init.d/freebsd-utils ... [] Loading devfs rules...devfs ruleset: ioctl DEVFSIO_SUSE: Operation not permitted invoke-rc.d: initscript freebsd-utils, action "start" failed. dpkg: error processing freebsd-utils (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: freebsd-utils E: Sub-process /usr/bin/dpkg returned an error code (1) It's easy enough to work around this issue (exit 0 in the init script does the trick) but it's a little annoying and would be nice to have fixed. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-RELEASE-p3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages freebsd-utils depends on: ii libbsd0 0.4.2-1 ii libc0.1 2.13-37 ii libcam6 9.0+ds1-3 ii libgeom19.0+ds1-3 ii libjail19.0+ds1-3 ii libkiconv4 9.0+ds1-3 ii libkvm0 9.0+ds1-3 ii libsbuf69.0+ds1-3 ii libtirpc1 0.2.2-5 ii lsb-base4.1+Debian8 ii zlib1g 1:1.2.7.dfsg-13 freebsd-utils recommends no packages. Versions of packages freebsd-utils suggests: pn freebsd-hackedutils ii kbdcontrol 9.0+ds1-8 pn vidcontrol -- no debconf information -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121211162017.31643.57530.report...@buzzer.ott.net
Bug#674582: marked as done (init script requires kldutils, but devd doesn't Depend on it)
Your message dated Fri, 25 May 2012 17:18:02 + with message-id and subject line Bug#674582: fixed in freebsd-utils 9.0+ds1-5 has caused the Debian Bug report #674582, regarding init script requires kldutils, but devd doesn't Depend on it 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.) -- 674582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: devd Version: 9.0+ds1-4 Severity: grave devd init script requires kldutils, but a dependency on this package is missing. This is currently breaking debootstrap when run against sid. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-i386 (i386) Kernel: kFreeBSD 8.1-1-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devd depends on: ii libbsd0 0.3.0-2 ii libc0.1 2.13-32 ii libgcc1 1:4.7.0-7 devd recommends no packages. devd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: freebsd-utils Source-Version: 9.0+ds1-5 We believe that the bug you reported is fixed in the latest version of freebsd-utils, which is due to be installed in the Debian FTP archive: devd-udeb_9.0+ds1-5_kfreebsd-amd64.udeb to main/f/freebsd-utils/devd-udeb_9.0+ds1-5_kfreebsd-amd64.udeb devd_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/devd_9.0+ds1-5_kfreebsd-amd64.deb freebsd-geom_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/freebsd-geom_9.0+ds1-5_kfreebsd-amd64.deb freebsd-net-tools-udeb_9.0+ds1-5_kfreebsd-amd64.udeb to main/f/freebsd-utils/freebsd-net-tools-udeb_9.0+ds1-5_kfreebsd-amd64.udeb freebsd-net-tools_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/freebsd-net-tools_9.0+ds1-5_kfreebsd-amd64.deb freebsd-nfs-common_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/freebsd-nfs-common_9.0+ds1-5_kfreebsd-amd64.deb freebsd-nfs-server_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/freebsd-nfs-server_9.0+ds1-5_kfreebsd-amd64.deb freebsd-ppp_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/freebsd-ppp_9.0+ds1-5_kfreebsd-amd64.deb freebsd-utils-udeb_9.0+ds1-5_kfreebsd-amd64.udeb to main/f/freebsd-utils/freebsd-utils-udeb_9.0+ds1-5_kfreebsd-amd64.udeb freebsd-utils_9.0+ds1-5.debian.tar.gz to main/f/freebsd-utils/freebsd-utils_9.0+ds1-5.debian.tar.gz freebsd-utils_9.0+ds1-5.dsc to main/f/freebsd-utils/freebsd-utils_9.0+ds1-5.dsc freebsd-utils_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/freebsd-utils_9.0+ds1-5_kfreebsd-amd64.deb geom_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/geom_9.0+ds1-5_kfreebsd-amd64.deb kbdcontrol-udeb_9.0+ds1-5_kfreebsd-amd64.udeb to main/f/freebsd-utils/kbdcontrol-udeb_9.0+ds1-5_kfreebsd-amd64.udeb kbdcontrol_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/kbdcontrol_9.0+ds1-5_kfreebsd-amd64.deb kldutils-udeb_9.0+ds1-5_kfreebsd-amd64.udeb to main/f/freebsd-utils/kldutils-udeb_9.0+ds1-5_kfreebsd-amd64.udeb kldutils_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/kldutils_9.0+ds1-5_kfreebsd-amd64.deb ktrace_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/ktrace_9.0+ds1-5_kfreebsd-amd64.deb mkuzip_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/mkuzip_9.0+ds1-5_kfreebsd-amd64.deb pf_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/pf_9.0+ds1-5_kfreebsd-amd64.deb powerd_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/powerd_9.0+ds1-5_kfreebsd-amd64.deb vidcontrol_9.0+ds1-5_kfreebsd-amd64.deb to main/f/freebsd-utils/vidcontrol_9.0+ds1-5_kfreebsd-amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Millan (supplier of updated freebsd-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 25 May 2012 18:54:45 +0200 Source: freebsd-utils Binary: freebsd-utils freebsd-utils-udeb kldutils kldutils-udeb kbdcontrol kbdcontrol-udeb vidcontrol freebsd-net-tools freebsd-net-tools-udeb freebsd-nfs-server freebsd-nfs-common
Bug#674582: init script requires kldutils, but devd doesn't Depend on it
Package: devd Version: 9.0+ds1-4 Severity: grave devd init script requires kldutils, but a dependency on this package is missing. This is currently breaking debootstrap when run against sid. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: kfreebsd-i386 (i386) Kernel: kFreeBSD 8.1-1-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devd depends on: ii libbsd0 0.3.0-2 ii libc0.1 2.13-32 ii libgcc1 1:4.7.0-7 devd recommends no packages. devd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525164434.82203.37723.reportbug@thorin
Bug#670412: marked as done (geli init script fails if /etc/default/geli is unconfigured)
Your message dated Tue, 08 May 2012 06:47:36 + with message-id and subject line Bug#670412: fixed in freebsd-utils 9.0+ds1-4 has caused the Debian Bug report #670412, regarding geli init script fails if /etc/default/geli is unconfigured 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.) -- 670412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: geom Version: 9.0+ds1-3 The geli init script fails if no geli devices are configured in /etc/fstab and /etc/default/geli. This prevented an upgrade of geom and freebsd-geom: [...] Setting up geom (9.0+ds1-3) ... Starting GELI subsystem...UNCONFIGURED. See /etc/default/geli ... failed! invoke-rc.d: initscript geli, action "start" failed. dpkg: error processing geom (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports dpkg: dependency problems prevent configuration of freebsd-geom: freebsd-geom depends on geom; however: Package geom is not configured yet. dpkg: error processing freebsd-geom (--configure): dependency problems - leaving unconfigured [...] As geom contains more than just geli it is imho wrong to print an error (warning is fine ofc), but it certainly is wrong to fail the init script. --- End Message --- --- Begin Message --- Source: freebsd-utils Source-Version: 9.0+ds1-4 We believe that the bug you reported is fixed in the latest version of freebsd-utils, which is due to be installed in the Debian FTP archive: devd-udeb_9.0+ds1-4_kfreebsd-i386.udeb to main/f/freebsd-utils/devd-udeb_9.0+ds1-4_kfreebsd-i386.udeb devd_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/devd_9.0+ds1-4_kfreebsd-i386.deb freebsd-geom_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-geom_9.0+ds1-4_kfreebsd-i386.deb freebsd-net-tools-udeb_9.0+ds1-4_kfreebsd-i386.udeb to main/f/freebsd-utils/freebsd-net-tools-udeb_9.0+ds1-4_kfreebsd-i386.udeb freebsd-net-tools_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-net-tools_9.0+ds1-4_kfreebsd-i386.deb freebsd-nfs-common_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-nfs-common_9.0+ds1-4_kfreebsd-i386.deb freebsd-nfs-server_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-nfs-server_9.0+ds1-4_kfreebsd-i386.deb freebsd-ppp_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-ppp_9.0+ds1-4_kfreebsd-i386.deb freebsd-utils-udeb_9.0+ds1-4_kfreebsd-i386.udeb to main/f/freebsd-utils/freebsd-utils-udeb_9.0+ds1-4_kfreebsd-i386.udeb freebsd-utils_9.0+ds1-4.debian.tar.gz to main/f/freebsd-utils/freebsd-utils_9.0+ds1-4.debian.tar.gz freebsd-utils_9.0+ds1-4.dsc to main/f/freebsd-utils/freebsd-utils_9.0+ds1-4.dsc freebsd-utils_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-utils_9.0+ds1-4_kfreebsd-i386.deb geom_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/geom_9.0+ds1-4_kfreebsd-i386.deb kbdcontrol-udeb_9.0+ds1-4_kfreebsd-i386.udeb to main/f/freebsd-utils/kbdcontrol-udeb_9.0+ds1-4_kfreebsd-i386.udeb kbdcontrol_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/kbdcontrol_9.0+ds1-4_kfreebsd-i386.deb kldutils-udeb_9.0+ds1-4_kfreebsd-i386.udeb to main/f/freebsd-utils/kldutils-udeb_9.0+ds1-4_kfreebsd-i386.udeb kldutils_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/kldutils_9.0+ds1-4_kfreebsd-i386.deb ktrace_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/ktrace_9.0+ds1-4_kfreebsd-i386.deb mkuzip_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/mkuzip_9.0+ds1-4_kfreebsd-i386.deb pf_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/pf_9.0+ds1-4_kfreebsd-i386.deb powerd_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/powerd_9.0+ds1-4_kfreebsd-i386.deb vidcontrol_9.0+ds1-4_kfreebsd-i386.deb to main/f/freebsd-utils/vidcontrol_9.0+ds1-4_kfreebsd-i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 670...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Robert Millan (supplier of updated freebsd-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 May 2012 23:5
Bug#670412: geli init script fails if /etc/default/geli is unconfigured
On 26/04/12 00:21, Steve Fouchet wrote: > It can be bypass if you initialise $geli_devices with any value in > /etc/default/geli. > ex : geli_devices="da75" > > then geli start and booting process/ packages configuration can continue. Thanks... that would work around this problem, yes. The package needed fixing though, otherwise it breaks the install/upgrade process, like for users who haven't created their geli devices yet. Or some users might want to install the geli tools but don't want to initialise any devices at boot time. I've committed a fix to SVN for the next upload of freebsd-utils which: * exits the initscript with status 0 -- that fixes the error seen during dpkg/apt-get; * shows this warning at startup, if no geli devices are configured: [warn] Starting GELI subsystem: not configured; see /etc/default/geli (warning). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f98951f.7080...@pyro.eu.org
Re: Bug#670412: geli init script fails if /etc/default/geli is unconfigured
On 26/04/12 00:21, Steve Fouchet wrote: > It can be bypass if you initialise $geli_devices with any value in > /etc/default/geli. > ex : geli_devices="da75" > > then geli start and booting process/ packages configuration can continue. Thanks... that would work around this problem, yes. The package needed fixing though, otherwise it breaks the install/upgrade process, like for users who haven't created their geli devices yet. Or some users might want to install the geli tools but don't want to initialise any devices at boot time. I've committed a fix to SVN for the next upload of freebsd-utils which: * exits the initscript with status 0 -- that fixes the error seen during dpkg/apt-get; * shows this warning at startup, if no geli devices are configured: [warn] Starting GELI subsystem: not configured; see /etc/default/geli (warning). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9894ee.8000...@pyro.eu.org
Re: Processed: Re: Bug#670412: geli init script fails if /etc/default/geli is unconfigured
It's due to a checks in geli init script.
line 108: if [ -z "${devices}" ];
It can be bypass if you initialise $geli_devices with any value in
/etc/default/geli.
ex : geli_devices="da75"
then geli start and booting process/ packages configuration can continue.
Hope it can help.
WakS
Le 25/04/2012 23:36, Debian Bug Tracking System a écrit :
Processing commands for cont...@bugs.debian.org:
tags 670412 + pending
Bug #670412 [geom] geli init script fails if /etc/default/geli is unconfigured
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f988711.9080...@gmail.com
Processed: Re: Bug#670412: geli init script fails if /etc/default/geli is unconfigured
Processing commands for cont...@bugs.debian.org: > tags 670412 + pending Bug #670412 [geom] geli init script fails if /etc/default/geli is unconfigured Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 670412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133538959532575.transcr...@bugs.debian.org
Re: Bug#670412: geli init script fails if /etc/default/geli is unconfigured
On 25/04/12 12:52, Stefan Bühler wrote: > Setting up geom (9.0+ds1-3) ... > Starting GELI subsystem...UNCONFIGURED. See /etc/default/geli ... failed! > invoke-rc.d: initscript geli, action "start" failed. > dpkg: error processing geom (--configure): > subprocess installed post-installation script returned error exit status 1 Hi, The initscript will need to return zero exit status in this case (Debian policy seems to allow that, despite contradictory LSB policy). But there is still a choice in how this can be displayed: 1. With existing log_failure_msg: Starting GELI subsystem... UNCONFIGURED. See /etc/default/geli ... failed! 2. With log_success_msg (with implicit log_end_msg 0 = 'ok') : Starting GELI subsystem... UNCONFIGURED. See /etc/default/geli. 3. With log_warning_msg (with implicit log_end_msg 255 = 'warning') : Starting GELI subsystem... UNCONFIGURED. See /etc/default/geli (warning). And if we get the fancy new lsb-base (4.1+Debian0+fancy1) in Wheezy, these would be preceded by [FAIL], [ ok ] or [warn] coloured red/green/yellow respectively. I think I prefer option 3, and also fixing the screaming capital letters. That seems the best way to communicate a not-quite-successful status, so the administrator is encouraged to either properly configure it or remove it. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f980bd5.9030...@pyro.eu.org
Bug#670412: geli init script fails if /etc/default/geli is unconfigured
Package: geom Version: 9.0+ds1-3 The geli init script fails if no geli devices are configured in /etc/fstab and /etc/default/geli. This prevented an upgrade of geom and freebsd-geom: [...] Setting up geom (9.0+ds1-3) ... Starting GELI subsystem...UNCONFIGURED. See /etc/default/geli ... failed! invoke-rc.d: initscript geli, action "start" failed. dpkg: error processing geom (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports dpkg: dependency problems prevent configuration of freebsd-geom: freebsd-geom depends on geom; however: Package geom is not configured yet. dpkg: error processing freebsd-geom (--configure): dependency problems - leaving unconfigured [...] As geom contains more than just geli it is imho wrong to print an error (warning is fine ofc), but it certainly is wrong to fail the init script. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f97e593.2050...@lighttpd.net
Bug#667477: Acknowledgement (libvirt: FTBFS[kfreebsd]: build-dependency on module-init-tools )
Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to debian-bsd@lists.debian.org (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Debian Libvirt Maintainers If you wish to submit further information on this problem, please send it to 667...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 667477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.667477.b.133353792219424@bugs.debian.org
Bug#667477: libvirt: FTBFS[kfreebsd]: build-dependency on module-init-tools
Package: src:libvirt Version: 0.9.11-1 Severity: serious Tags: sid wheezy User: debian-bsd@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-bsd@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: The following packages have unmet dependencies: module-init-tools : Depends: libkmod2 but it is not installable Depends: kmod but it is not installable module-init-tools recently became a arch:all package (it was linux-any before) so the Provides: by kfreebsd's kldutils is no longer able to satisfy the dependency on module-init-tools on the autobuilders. Please mark the build-dependency as linux-any. Regards Christoph If you have further questions please mail debian-bsd@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87iphfu4w1@hepworth.siccegge.de
kldutils provides module-init-tools
Helo I've noticed that kldutils now provides module-init-tools. Although I understand that their both functions at the end are the same, It appears to me that the debconf templated module-init-tools selection was really user friendly and simplified the administration of a box. I spent some time looking for any reference on this replacement (or mutex, in case) on this list and BT but I couldn't find any. Does anyone know something about this? Greetings, Dererk -- BOFH excuse #183: filesystem not big enough for Jumbo Kernel Patch signature.asc Description: OpenPGP digital signature
Bug#559344: marked as done (kldutils: bashism used in /etc/init.d/module-init-tools)
Your message dated Mon, 14 Dec 2009 21:49:58 + with message-id and subject line Bug#559344: fixed in freebsd-utils 8.0-2 has caused the Debian Bug report #559344, regarding kldutils: bashism used in /etc/init.d/module-init-tools 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.) -- 559344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kldutils Version: 8.0-1 Severity: normal When running with a default shell of dash and not bash, the /etc/init.d/module-init-tools script complains about not finding the bash builtin shopt: # /etc/init.d/module-init-tools start /etc/init.d/module-init-tools: 62: shopt: not found # Which is from this call: modules="`shopt -s nullglob ; cat /etc/modules /etc/modules.d/* \ | sed -e \"s/#.*//g\" -e \"/^\( \|\t\)*$/d\" `" -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 7.2-1-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kldutils depends on: ii freebsd-utils 7.2-9 FreeBSD utilities needed for GNU/k ii libbsd0 0.1.6-1utility functions from BSD systems ii libc0.1 2.10.2-2 GNU C Library: Shared libraries kldutils recommends no packages. kldutils suggests no packages. -- debconf information excluded -- debsums errors found: Your vendor has not defined Fcntl macro O_NOATIME, used at /usr/bin/debsums line 277. --- End Message --- --- Begin Message --- Source: freebsd-utils Source-Version: 8.0-2 We believe that the bug you reported is fixed in the latest version of freebsd-utils, which is due to be installed in the Debian FTP archive: freebsd-net-tools_8.0-2_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-net-tools_8.0-2_kfreebsd-i386.deb freebsd-utils-udeb_8.0-2_kfreebsd-i386.udeb to main/f/freebsd-utils/freebsd-utils-udeb_8.0-2_kfreebsd-i386.udeb freebsd-utils_8.0-2.diff.gz to main/f/freebsd-utils/freebsd-utils_8.0-2.diff.gz freebsd-utils_8.0-2.dsc to main/f/freebsd-utils/freebsd-utils_8.0-2.dsc freebsd-utils_8.0-2_kfreebsd-i386.deb to main/f/freebsd-utils/freebsd-utils_8.0-2_kfreebsd-i386.deb kbdcontrol_8.0-2_kfreebsd-i386.deb to main/f/freebsd-utils/kbdcontrol_8.0-2_kfreebsd-i386.deb kldutils-udeb_8.0-2_kfreebsd-i386.udeb to main/f/freebsd-utils/kldutils-udeb_8.0-2_kfreebsd-i386.udeb kldutils_8.0-2_kfreebsd-i386.deb to main/f/freebsd-utils/kldutils_8.0-2_kfreebsd-i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 559...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno (supplier of updated freebsd-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 14 Dec 2009 20:53:21 +0100 Source: freebsd-utils Binary: freebsd-utils freebsd-utils-udeb kldutils kldutils-udeb kbdcontrol freebsd-net-tools Architecture: source kfreebsd-i386 Version: 8.0-2 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno Changed-By: Aurelien Jarno Description: freebsd-net-tools - FreeBSD networking tools freebsd-utils - FreeBSD utilities needed for GNU/kFreeBSD freebsd-utils-udeb - FreeBSD utilities needed for GNU/kFreeBSD (udeb) kbdcontrol - command-line tool to change keyboard layout on GNU/kFreeBSD kldutils - tools for managing kFreeBSD modules kldutils-udeb - tools for managing kFreeBSD modules (udeb) Closes: 559344 560125 Changes: freebsd-utils (8.0-2) unstable; urgency=low . * freebsd-utils.init: fix quoting, and use a symbolic links instead of an hardlink (closes: #560125). * freebsd-utils: conflicts with module-init-tools (closes: #559344). Checksums-Sha1: 1bf9e96dd44fd5c264c0ef366e7abbe74c78b94f 1576 freebsd-utils_8.0-2.dsc 77818974546dfc0469fa6778457b44bdfa454f2e 53476 freebsd-utils_8.0-2.diff.gz 5b5197b79e76ec0f3bec51a997e29c7a606b0bb8 136726 freebsd-utils_8.0-2_kfreebsd-i386.deb 52a800faabb1eadfaf81e0dd2864375f0d8a5f92 11550 freebsd-utils-udeb_8.0-2_kfreebsd-i386.udeb 294a8f
Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
On Fri, 4 Dec 2009 14:43:52 +0100 (CET) Petr Salinger wrote: > It might be related to package name change in > > freebsd-utils (7.1-4) unstable; urgency=low > >* Rename module-init-tools to kldutils and net-tools to freebsd-net-tools, > as this is messing up the expectations of several services of equially > named binary coming from the same source package. > > -- Guillem Jover Mon, 13 Apr 2009 17:29:58 +0200 > > > Please run "dpkg -L kldutils", there should be only lines > > /etc/init.d > /etc/init.d/kldutils > > Please try also "dpkg -la | grep modules-init-tools", > there should be no such package. You might want to purge it. I wonder why it's not removed on upgrade. I can reproduce this by upgrading the lenny image from http://glibc-bsd.alioth.debian.org/install-cd/kfreebsd-i386/20090117/ (as mentioned in http://wiki.debian.org/Debian_GNU/kFreeBSD_FAQ), with apt-get and aptitude... and NOT switching to dependency based booting will not trigger a fault. With dependency based booting I have to purge module-init-tools to fully upgrade the system. Hanno -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
Hi, Rogério Brito writes: > On Dec 03 2009, Thorsten Glaser wrote: >> modules="$(cat /etc/modules /etc/modules.d/* 2>/dev/null | \ >> sed -e 's/#.*//g' -e '/^[ ]*$/d')" >> ^ ^-> space >> +> tab > > Are character classes (e.g., [[:blank:]]) understood by standard tools? GNU grep and GNU sed understand them. Thanks, Ludo’. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
On Dec 03 2009, Thorsten Glaser wrote:
> modules="$(cat /etc/modules /etc/modules.d/* 2>/dev/null | \
> sed -e 's/#.*//g' -e '/^[ ]*$/d')"
> ^ ^-> space
> +> tab
Are character classes (e.g., [[:blank:]]) understood by standard tools?
This way, things can be written without fear of whitespace being broken
and can be legible without needing to resort to things like saying "the
first character that you can't see is a tab and the second is a space".
Regards, Rogério Brito.
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
When running with a default shell of dash and not bash, the /etc/init.d/module-init-tools script complains about not finding the bash builtin shopt: # /etc/init.d/module-init-tools start /etc/init.d/module-init-tools: 62: shopt: not found # Which is from this call: modules="`shopt -s nullglob ; cat /etc/modules /etc/modules.d/* \ | sed -e \"s/#.*//g\" -e \"/^\( \|\t\)*$/d\" `" I have to say I don't really understand where you got this code. It has been fixed back in July, and is surely not in version 8.0-1. It might be related to package name change in freebsd-utils (7.1-4) unstable; urgency=low * Rename module-init-tools to kldutils and net-tools to freebsd-net-tools, as this is messing up the expectations of several services of equially named binary coming from the same source package. -- Guillem Jover Mon, 13 Apr 2009 17:29:58 +0200 Please run "dpkg -L kldutils", there should be only lines /etc/init.d /etc/init.d/kldutils Please try also "dpkg -la | grep modules-init-tools", there should be no such package. You might want to purge it. Petr -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
On Thu, Dec 03, 2009 at 08:58:49PM +0100, Hanno Hecker wrote: > Package: kldutils > Version: 8.0-1 > Severity: normal > > When running with a default shell of dash and not bash, the > /etc/init.d/module-init-tools script complains about not finding the bash > builtin shopt: > # /etc/init.d/module-init-tools start > /etc/init.d/module-init-tools: 62: shopt: not found > # > Which is from this call: > modules="`shopt -s nullglob ; cat /etc/modules /etc/modules.d/* \ > | sed -e \"s/#.*//g\" -e \"/^\( \|\t\)*$/d\" `" > I have to say I don't really understand where you got this code. It has been fixed back in July, and is surely not in version 8.0-1. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
On Thu, 3 Dec 2009 20:44:03 + (UTC) Thorsten Glaser wrote: > I propose: (untested at the moment though) > > modules="$(cat /etc/modules /etc/modules.d/* 2>/dev/null | \ > sed -e 's/#.*//g' -e '/^[ ]*$/d')" > ^ ^-> space > +> tab At least gnu sed, which we use, supports \t, so the 's/^[\t ]*$/d' is OK: $ bash -c "echo -e \"x\tx x\"" | sed -ne 's/[\t ]//g;l' xxx$ > >-- debsums errors found: > >Your vendor has not defined Fcntl macro O_NOATIME, used at /usr/bin/debsums > >line 277. > > WTF? Probably a bug in perl's Fcntl.pm, haven't looked further: $ perl -MFcntl=O_NOATIME -le 'print STDOUT O_NOATIME' Your vendor has not defined Fcntl macro O_NOATIME, used at -e line 1. Hanno -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
Hanno Hecker dixit: >modules="`shopt -s nullglob ; cat /etc/modules /etc/modules.d/* \ > | sed -e \"s/#.*//g\" -e \"/^\( \|\t\)*$/d\" `" This is even worse, as "...`..."..."...`..." (with or without inner quotes) is always wrong and not portable, however $(...) is guaranteed by POSIX which then is guaranteed by Policy 10.4. There is also an unescaped dollar sign that probably is removed by the shell, and I'm not too sure \t is expanded either. I propose: (untested at the moment though) modules="$(cat /etc/modules /etc/modules.d/* 2>/dev/null | \ sed -e 's/#.*//g' -e '/^[]*$/d')" ^ ^-> space +> tab >-- debsums errors found: >Your vendor has not defined Fcntl macro O_NOATIME, used at /usr/bin/debsums >line 277. WTF? //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C" -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559344: kldutils: bashism used in /etc/init.d/module-init-tools
Package: kldutils Version: 8.0-1 Severity: normal When running with a default shell of dash and not bash, the /etc/init.d/module-init-tools script complains about not finding the bash builtin shopt: # /etc/init.d/module-init-tools start /etc/init.d/module-init-tools: 62: shopt: not found # Which is from this call: modules="`shopt -s nullglob ; cat /etc/modules /etc/modules.d/* \ | sed -e \"s/#.*//g\" -e \"/^\( \|\t\)*$/d\" `" -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 7.2-1-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kldutils depends on: ii freebsd-utils 7.2-9 FreeBSD utilities needed for GNU/k ii libbsd0 0.1.6-1utility functions from BSD systems ii libc0.1 2.10.2-2 GNU C Library: Shared libraries kldutils recommends no packages. kldutils suggests no packages. -- debconf information excluded -- debsums errors found: Your vendor has not defined Fcntl macro O_NOATIME, used at /usr/bin/debsums line 277. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [patch] add GNU/kFreeBSD fstab and init
On 22/07/2009, Luca Favatella wrote: > On 22/07/2009, Otavio Salvador wrote: >> Hello, >> >> On Wed, Jul 22, 2009 at 2:26 PM, Luca Favatella >> wrote: >>> On 22/07/2009, Luca Favatella wrote: >>>> This patch adds GNU/kFreeBSD /etc/fstab and /sbin/init. >>>> Please carefully review it. > [...] >> Fine with me; the only thing I'd do different is to merge both >> changelog lines in a single one. > > Fixed in the attached version 2 of the patch. Committed to trunk. Thanks, Luca Favatella -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [patch] add GNU/kFreeBSD fstab and init
Hello, On Wed, Jul 22, 2009 at 2:26 PM, Luca Favatella wrote: > On 22/07/2009, Luca Favatella wrote: >> This patch adds GNU/kFreeBSD /etc/fstab and /sbin/init. >> Please carefully review it. > > Now the patch should be really attached. > Sorry for the noise. Fine with me; the only thing I'd do different is to merge both changelog lines in a single one. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [patch] add GNU/kFreeBSD fstab and init
On 22/07/2009, Otavio Salvador wrote: > Hello, > > On Wed, Jul 22, 2009 at 2:26 PM, Luca Favatella wrote: >> On 22/07/2009, Luca Favatella wrote: >>> This patch adds GNU/kFreeBSD /etc/fstab and /sbin/init. >>> Please carefully review it. [...] > Fine with me; the only thing I'd do different is to merge both > changelog lines in a single one. Fixed in the attached version 2 of the patch. Cheers, Luca Favatella Index: debian/changelog === --- debian/changelog (.../trunk/packages/rootskel) (revision 59603) +++ debian/changelog (.../branches/d-i/kfreebsd/packages/rootskel) (revision 59603) @@ -6,6 +6,7 @@ [ Luca Favatella ] * Generalize code splitting Linux specific stuff. * GNU/kFreeBSD does not need klibc and udev. + * Add GNU/kFreeBSD /etc/fstab and /sbin/init. [ Otavio Salvador ] * Unix socket support is built-in since long ago so we don't need to Index: src/etc/fstab-kfreebsd === --- src/etc/fstab-kfreebsd (.../trunk/packages/rootskel) (revision 0) +++ src/etc/fstab-kfreebsd (.../branches/d-i/kfreebsd/packages/rootskel) (revision 59603) @@ -0,0 +1 @@ +none /proc linprocfs defaults0 0 Index: src/sbin/init-kfreebsd === --- src/sbin/init-kfreebsd (.../trunk/packages/rootskel) (revision 0) +++ src/sbin/init-kfreebsd (.../branches/d-i/kfreebsd/packages/rootskel) (revision 59603) @@ -0,0 +1,24 @@ +#!/bin/sh +# Set up filesystem as root and pivot into it. + +export PATH=/sbin:/bin:/usr/sbin:/usr/bin +exec < /dev/console > /dev/console 2> /dev/console +export TERM=cons25 + +export BOOT_DEBUG=2 + +trap "echo \"Something wicked happened. Press enter for rescue shell.\" ; read NULL ; exec sh" 0 +set -e + +. /lib/debian-installer/init-debug +debugshell "just booted" + +echo "Setting up filesystem, please wait ..." +mount -o update,rw -t ufs /dev/md0 / +mount -t devfs devfs /dev/ +mount /proc +ln -s /var/run/log /dev/log + +# Close all open files on the initrd, and run busybox init. +debugshell "before init" +exec /usr/sbin/chroot . /bin/busybox init < /dev/console > /dev/console 2>&1 Property changes on: src/sbin/init-kfreebsd ___ Added: svn:executable + *
Re: [patch] add GNU/kFreeBSD fstab and init
On 22/07/2009, Luca Favatella wrote: > This patch adds GNU/kFreeBSD /etc/fstab and /sbin/init. > Please carefully review it. Now the patch should be really attached. Sorry for the noise. Index: debian/changelog === --- debian/changelog (.../trunk/packages/rootskel) (revision 59603) +++ debian/changelog (.../branches/d-i/kfreebsd/packages/rootskel) (revision 59603) @@ -6,6 +6,8 @@ [ Luca Favatella ] * Generalize code splitting Linux specific stuff. * GNU/kFreeBSD does not need klibc and udev. + * Add GNU/kFreeBSD /etc/fstab. + * Add GNU/kFreeBSD /sbin/init. [ Otavio Salvador ] * Unix socket support is built-in since long ago so we don't need to Index: src/etc/fstab-kfreebsd === --- src/etc/fstab-kfreebsd (.../trunk/packages/rootskel) (revision 0) +++ src/etc/fstab-kfreebsd (.../branches/d-i/kfreebsd/packages/rootskel) (revision 59603) @@ -0,0 +1 @@ +none /proc linprocfs defaults0 0 Index: src/sbin/init-kfreebsd === --- src/sbin/init-kfreebsd (.../trunk/packages/rootskel) (revision 0) +++ src/sbin/init-kfreebsd (.../branches/d-i/kfreebsd/packages/rootskel) (revision 59603) @@ -0,0 +1,24 @@ +#!/bin/sh +# Set up filesystem as root and pivot into it. + +export PATH=/sbin:/bin:/usr/sbin:/usr/bin +exec < /dev/console > /dev/console 2> /dev/console +export TERM=cons25 + +export BOOT_DEBUG=2 + +trap "echo \"Something wicked happened. Press enter for rescue shell.\" ; read NULL ; exec sh" 0 +set -e + +. /lib/debian-installer/init-debug +debugshell "just booted" + +echo "Setting up filesystem, please wait ..." +mount -o update,rw -t ufs /dev/md0 / +mount -t devfs devfs /dev/ +mount /proc +ln -s /var/run/log /dev/log + +# Close all open files on the initrd, and run busybox init. +debugshell "before init" +exec /usr/sbin/chroot . /bin/busybox init < /dev/console > /dev/console 2>&1 Property changes on: src/sbin/init-kfreebsd ___ Added: svn:executable + *
[patch] add GNU/kFreeBSD fstab and init
This patch adds GNU/kFreeBSD /etc/fstab and /sbin/init. Please carefully review it. I'm proposing both together because they are closely related. This patch should not affect GNU/Linux builds and has been in the kfreebsd d-i branch for a while. Cheers, Luca Favatella -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [LCFC] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
Hi, On Friday 01 May 2009 09:24:11 Christian Perrier wrote: > Quoting Justin B Rye (j...@edlug.org.uk): > > "Possible FreeBSD keyboards" are the keyboard-layouts that are > > available for FreeBSD (the things you switch between by using the > > command referred to in the previous line). FreeBSD apparently uses > > things like /usr/share/syscons/keymaps/finnish.iso.kbd - effectively > > a keymap file, but formatted quite differently from the ones I see > > in /usr/share/keymaps. > > We should probably do s/keyboard/keymap? Sorry for being this late. For some reason I saw your mails just now. I agree that keymap would be better option (as Petr also said in his reply to your BTS mail). Cheers, Edu ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/ -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [LCFC] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
Quoting Justin B Rye (j...@edlug.org.uk): > "Possible FreeBSD keyboards" are the keyboard-layouts that are > available for FreeBSD (the things you switch between by using the > command referred to in the previous line). FreeBSD apparently uses > things like /usr/share/syscons/keymaps/finnish.iso.kbd - effectively > a keymap file, but formatted quite differently from the ones I see > in /usr/share/keymaps. We should probably do s/keyboard/keymap? signature.asc Description: Digital signature
Re: [LCFC] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
Esko Arajärvi wrote: > Description: command-line tool to change FreeBSD keyboard layout > This package provides the original FreeBSD command to set keyboard layout > and > the FreeBSD possible > keyboards. > > The part "and the FreeBSD possible keyboards" is (to me) somewhat confusing. > Justin's patch from 2009-04-20 says "plus the possible FreeBSD keyboards.", > which seems to mean different thing. What actually is "FreeBSD possible > keyboard"? A keyboard which can be used with FreeBSD? A keyboard specially > designed for FreeBSD?" Keyboard model? Keyboard rules? My reshuffle was just based on the syntactic rule that when there's a modifying noun and a genuine adjective both modifying the same noun, the adjective comes first; it's "strange keyboard layouts", not "keyboard strange layouts". "Possible FreeBSD keyboards" are the keyboard-layouts that are available for FreeBSD (the things you switch between by using the command referred to in the previous line). FreeBSD apparently uses things like /usr/share/syscons/keymaps/finnish.iso.kbd - effectively a keymap file, but formatted quite differently from the ones I see in /usr/share/keymaps. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [LCFC] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
On Thursday 30 April 2009 08:37:38 Christian Perrier wrote:
> This is the last call for comments for the review of debconf
> templates for freebsd-utils.
>
> The reviewed templates will be sent on Saturday, May 02, 2009 to the
> package maintainer as a bug report and a mail will be sent to this list
> with "[BTS]" as a subject tag.
Package: kbdcontrol
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf
Description: command-line tool to change FreeBSD keyboard layout
This package provides the original FreeBSD command to set keyboard layout and
the FreeBSD possible
keyboards.
The part "and the FreeBSD possible keyboards" is (to me) somewhat confusing.
Justin's patch from 2009-04-20 says "plus the possible FreeBSD keyboards.",
which seems to mean different thing. What actually is "FreeBSD possible
keyboard"? A keyboard which can be used with FreeBSD? A keyboard specially
designed for FreeBSD?" Keyboard model? Keyboard rules?
Package: net-tools
Section: net
Priority: important
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}
Replaces: freebsd-utils (<< 5.4), freebsd-hackedutils (<= 6.1-1)
Description: FreeBSD networking tools
This package provides the FreeBSD tools needed to manage networking on
GNU/kFreeBSD.
This template has a double space after the word "provides"
###
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
[LCFC] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
This is the last call for comments for the review of debconf
templates for freebsd-utils.
The reviewed templates will be sent on Saturday, May 02, 2009 to the package
maintainer as a bug report and a mail will be sent to this list with
"[BTS]" as a subject tag.
--
Template: kbdcontrol/keymap
Type: select
Choices: ${choices}
Default: none
Description: Keymap:
Please choose the keyboard map.
.
If in doubt, don't choose any map. You can always come back to
this question with "dpkg-reconfigure kbdcontrol".
Template: module-init-tools/network
Type: multiselect
Choices: ${choices}
_Description: Network card drivers:
Please select drivers for this machine's network card(s). You may select more
than
one driver, or none at all, depending on the number of cards installed in the
machine.
.
You most likely don't need any, since default kernels currently include
built-in support for network cards. You can always come back to this question
later
with "dpkg-reconfigure module-init-tools".
Template: module-init-tools/sound
Type: multiselect
Choices: ${choices}
_Description: Sound card drivers:
Please select drivers for this machine's sound card(s). You may select more
than
one driver, or none at all, depending on the number of cards installed in the
machine.
.
If in doubt, leave this field empty. The "snd_probe" command may be used
later to identify the sound card(s). You can always come back to this question
with "dpkg-reconfigure module-init-tools".
Template: module-init-tools/other
Type: multiselect
Choices: ${choices}
_Description: Other modules:
Please select the modules needed to properly support this
machine's hardware.
.
If in doubt, leave this field empty. You can always come back to
this question with "dpkg-reconfigure module-init-tools".
Source: freebsd-utils
Section: utils
Priority: important
Maintainer: GNU/kFreeBSD Maintainers
Uploaders: Aurelien Jarno , Guillem Jover
Build-Depends: debhelper (>= 7), quilt, po-debconf, freebsd-buildutils,
libkvm-dev (>= 7.0), libbsd-dev (>= 0.0-1.2), libc0.1-dev (>= 2.7-13),
flex | flex-old, kfreebsd-kernel-headers (>= 0.31), libfreebsd-dev (>= 0.0-5),
libipx-dev, libkiconv-dev, libgeom-dev, libdevstat-dev, libsbuf-dev
# libkvm-dev: dmesg
# libgeom-dev : ccdconfig
# libfreebsd (>= 0.0-5): ifconfig
# libipx-dev: ifconfig
# libkiconv-dev: mount_*
# libc0.1-dev (>= 2.7-13): ifconfig
# libdevstat-dev: mdconfig
# libsbuf-dev: mdconfig
Standards-Version: 3.8.1
Package: freebsd-utils
Priority: required
Essential: yes
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}, ufsutils
Suggests: freebsd-hackedutils (>= 6.1-1)
Conflicts: inetutils-tools (<= 2:1.4.3+20051212-4)
Replaces: freebsd-hackedutils (<= 6.1-1)
Description: FreeBSD utilities needed for GNU/kFreeBSD
This package provides FreeBSD utilities needed for GNU/kFreeBSD.
Package: module-init-tools
Priority: important
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, kfreebsd-image
Replaces: kldutils (<< 6.0-2.really.5.4-0.6), freebsd-utils (<= 5.2.1-16),
freebsd-hackedutils (<= 6.1-1), kfreebsd-common (<< 6.1-6)
Description: tools for managing kFreeBSD modules
This package provides a set of programs for loading, inserting, and
removing kernel modules for kFreeBSD.
Package: kbdcontrol
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf
Description: command-line tool to change FreeBSD keyboard layout
This package provides the original FreeBSD command to set keyboard layout and
the FreeBSD possible
keyboards.
Package: net-tools
Section: net
Priority: important
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}
Replaces: freebsd-utils (<< 5.4), freebsd-hackedutils (<= 6.1-1)
Description: FreeBSD networking tools
This package provides the FreeBSD tools needed to manage networking on
GNU/kFreeBSD.
# FIXME:
# - add kdump
# - add jail
# - add ppp (ppp, pppctl, pppd)
# - add pf (pfctl + authpf + /etc stuff + init.d script)
# - add ipfw (???)
# - add devfs
signature.asc
Description: Digital signature
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
Marco d'Itri wrote: On Apr 22, Matthew Lockner wrote: What kind of crap am I looking for? Anything related to snd* modules for a start. properly. If we as users can't expect to be able to use this file anymore, it would be user-friendlier for the package upgrade to tell us so and state the correct alternative. It does, it's not my fault if you can't read and/or understand warnings. The insults aren't really necessary. If you're referring to: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. then that doesn't really tell me how to fix anything (move modprobe.conf into modprobe.d? Move the contents into their own files in modprobe.d?) The modprobe.conf manpage, which I'd consider a logical place to look for details, doesn't make any mention of this either. Incidentally, it also mentions a generate_modprobe.conf script that is no longer distributed with the package. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
Marco d'Itri wrote: On Apr 22, Matthew Lockner wrote: Since its postinst is my means of demonstrating the problem, then of course removing the package will prevent the problem from appearing, at least in this context. You can remove it and manually run modprobe. Anyway, I am quite sure that there is some crap in your /etc/modprobe.d/, double check everything. What kind of crap am I looking for? And be sure to delete /etc/modprobe.conf. My modprobe.conf still contains a line: install agpgart /sbin/modprobe radeon; /sbin/modprobe --ignore-install agpgart I don't recall precisely what that is there for, but somehow I remember it may have been needed to make hardware graphics acceleration work properly. If we as users can't expect to be able to use this file anymore, it would be user-friendlier for the package upgrade to tell us so and state the correct alternative. It is noteworthy that while I was obtaining the output you requested below, I had another hard lockup, and upon rebooting, there were similar problems during startup. The screen displayed the same kinds of warnings at points, and the OOM killer was stepping in at points to kill modprobe and its child processes. The warnings are harmless. I'll grant that the system still boots up, but the OOM-killer coming up in the process is something that is definitely not supposed to happen. I have a workaround for this personally, so for my part, I'm prepared to drop the matter - but based on this and other bug reports against this package, I find it likely there is an unresolved bug in play here. Left to your discretion, of course. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
On Apr 22, Matthew Lockner wrote: > What kind of crap am I looking for? Anything related to snd* modules for a start. > properly. If we as users can't expect to be able to use this file > anymore, it would be user-friendlier for the package upgrade to tell us > so and state the correct alternative. It does, it's not my fault if you can't read and/or understand warnings. -- ciao, Marco signature.asc Description: Digital signature
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
Marco d'Itri wrote:
On Apr 22, Matthew Lockner wrote:
The strongest evidence is that if I downgrade module-init-tools to the
prior version and hold the prior version and hold the package, the
problem goes away. I'd find the next most likely candidate to be
Not very compelling evidence.
This shows that your system was already broken:
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
If /etc/modprobe.conf was present, older releases ignored
/etc/modprobe.d/.
oss-compat's postinst script, but downgrading that package does nothing
if you still have the newest module-init-tools in place.
And what about removing oss-compat?
Since its postinst is my means of demonstrating the problem, then of
course removing the package will prevent the problem from appearing, at
least in this context.
It is noteworthy that while I was obtaining the output you requested
below, I had another hard lockup, and upon rebooting, there were similar
problems during startup. The screen displayed the same kinds of
warnings at points, and the OOM killer was stepping in at points to kill
modprobe and its child processes.
Please show the content of /etc/modprobe.d/oss-compat.conf.
Are you sure that the processes were related to oss-compat? Please find
out the exact command linux.
I meant "the exact command line" of the processes being run.
I got the blocks below from the output of ps. The first block was
gathered after dpkg-reconfigure oss-compat started spewing warnings; the
second block was gathered after a "killall modprobe sh" after running
ps. I had to run "killall modprobe sh" again to get rid of the mess,
but no more modprobe floods came in from that point. In my other
window, after each killall invocation, I get something like
/var/lib/dpkg/info/oss-compat.postinst: line 6: 5773
Terminated modprobe snd-seq-oss
I conclude that the postinst is hanging on the lines where it calls
modprobe, specifically for snd_seq_oss and snd_pcm_oss.
/usr/bin/perl -w /usr/sbin/dpkg-reconfigure oss-compat
/bin/sh /var/lib/dpkg/info/oss-compat.postinst configure 0.0.4+nmu3
modprobe snd_seq_oss
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --quiet snd_seq_midi
sh -c modprobe --ignore-install snd-seq && { modprobe --quiet
snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
modprobe --ignore-install snd_seq
sh -c /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet
snd-ioctl32 ; : ; }
/sbin/modprobe --ignore-install snd
/bin/sh /var/lib/dpkg/info/oss-compat.postinst configure 0.0.4+nmu3
modprobe snd_pcm_oss
sh -c modprobe --ignore-install snd-pcm && { modprobe --quiet
snd-pcm-oss ; : ;
modprobe --quiet snd_pcm_oss
sh -c modprobe --ignore-install snd-pcm && { modprobe --quiet
snd-pcm-oss ; : ;
modprobe --quiet snd_pcm_oss
sh -c modprobe --ignore-install snd-pcm && { modprobe --quiet
snd-pcm-oss ; : ;
modprobe --quiet snd_pcm_oss
sh -c modprobe --ignore-install snd-pcm && { modprobe --quiet
snd-pcm-oss ; : ;
modprobe --quiet snd_pcm_oss
sh -c modprobe --ignore-install snd-pcm && { modprobe --quiet
snd-pcm-oss ; : ;
modprobe --quiet snd_pcm_oss
sh -c modprobe --ignore-install snd-pcm && { modprobe --quiet
snd-pcm-oss ; : ;
modprobe --quiet snd_pcm_oss
sh -c modprobe --ignore-install snd-pcm && { modprobe --q
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
On Apr 22, Matthew Lockner wrote: > Since its postinst is my means of demonstrating the problem, then of > course removing the package will prevent the problem from appearing, at > least in this context. You can remove it and manually run modprobe. Anyway, I am quite sure that there is some crap in your /etc/modprobe.d/, double check everything. And be sure to delete /etc/modprobe.conf. > It is noteworthy that while I was obtaining the output you requested > below, I had another hard lockup, and upon rebooting, there were similar > problems during startup. The screen displayed the same kinds of > warnings at points, and the OOM killer was stepping in at points to kill > modprobe and its child processes. The warnings are harmless. -- ciao, Marco signature.asc Description: Digital signature
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
On Apr 22, Matthew Lockner wrote: > The strongest evidence is that if I downgrade module-init-tools to the > prior version and hold the prior version and hold the package, the > problem goes away. I'd find the next most likely candidate to be Not very compelling evidence. This shows that your system was already broken: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. If /etc/modprobe.conf was present, older releases ignored /etc/modprobe.d/. > oss-compat's postinst script, but downgrading that package does nothing > if you still have the newest module-init-tools in place. And what about removing oss-compat? >> Please show the content of /etc/modprobe.d/oss-compat.conf. >> Are you sure that the processes were related to oss-compat? Please find >> out the exact command linux. I meant "the exact command line" of the processes being run. -- ciao, Marco signature.asc Description: Digital signature
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
Marco d'Itri wrote:
On Apr 21, "Matthew J. Lockner" wrote:
I suspect this will be unreproducible since it hasn't been reported yet that
I definitely never experienced this on my system.
Anyway, I have no reason to believe this to be a m-i-t bug.
The strongest evidence is that if I downgrade module-init-tools to the
prior version and hold the prior version and hold the package, the
problem goes away. I'd find the next most likely candidate to be
oss-compat's postinst script, but downgrading that package does nothing
if you still have the newest module-init-tools in place.
Please show the content of /etc/modprobe.d/oss-compat.conf.
Are you sure that the processes were related to oss-compat? Please find
out the exact command linux.
install snd-pcm modprobe --ignore-install snd-pcm $CMDLINE_OPTS && {
modprobe --quiet snd-pcm-oss ; : ; }
install snd-mixer modprobe --ignore-install snd-mixer $CMDLINE_OPTS && {
modprobe --quiet snd-mixer-oss ; : ; }
install snd-seq modprobe --ignore-install snd-seq $CMDLINE_OPTS && {
modprobe --quiet snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
On Apr 21, "Matthew J. Lockner" wrote: > I suspect this will be unreproducible since it hasn't been reported yet that I definitely never experienced this on my system. Anyway, I have no reason to believe this to be a m-i-t bug. Please show the content of /etc/modprobe.d/oss-compat.conf. Are you sure that the processes were related to oss-compat? Please find out the exact command linux. -- ciao, Marco signature.asc Description: Digital signature
Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst
Package: module-init-tools Version: 3.7-pre9-1 Severity: important I recently did an "aptitude upgrade". I found that when the postinst of the oss-compat package was run during configuration of packages, I got a screenful of warnings, and found a long list of modprobe and "sh modprobe" processes running when inspecting the output of ps. At first I was just running "killall modprobe" to try to stop the madness, but found that something just kept spawning more modprobe processes. Eventually I found that "killall sh modprobe" will do the trick, if I'm fast about it. However, most of the times that I've tried tracking down or working around this problem, my system locks so hard that I have to kill X with Ctrl-Alt-Backspace, or even resort to the magic SysRq key, to get some response out of my system again. I suspect this will be unreproducible since it hasn't been reported yet that I can see, but it's a bad enough bug to bear mentioning at least. I'm likely going to try various combinations of package holds and downgrades until my system starts behaving again. What follows is a copy of the warnings I got from running "dpkg-reconfigure oss-compat". WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/isapnp, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/devfsd, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/display_class, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base-blacklist, it will be ignored in a future release. WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/isapnp, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/devfsd, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/display_class, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base-blacklist, it will be ignored in a future release. WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/isapnp, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/devfsd, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/display_class, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base-blacklist, it will be ignored in a future release. WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/isapnp, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/devfsd, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/display_class, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/pnp-hotplug, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base-blacklist, it will be ignored in a future release. /var/lib/dpkg/info/oss-compat.postinst: line 6: 24207 Terminated modprobe snd-seq-oss WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/isapnp, it will be ignored
Re: [RFR] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
Quoting Justin B Rye (j...@edlug.org.uk): > Christian Perrier wrote: > > Your review should be sent as an answer to this mail. > > I'm having trouble generating a patch here, since freebsd-utils > 7.1-5 in Sid doesn't have a module-init-tools.templates file. The > changelog for 7.1-4 says "Rename module-init-tools to kldutils"... > For now I'll just attach my modified versions. Thanks. That's probably caused by /me working on a version of the pacakge that was published before that change. Anyway, I don't think this dramatically changes the changes we're proposing and I think the maintainers will cope with all this..:) signature.asc Description: Digital signature
Re: [RFR] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
I'm having trouble generating a patch here, since freebsd-utils
7.1-5 in Sid doesn't have a module-init-tools.templates file. The
changelog for 7.1-4 says "Rename module-init-tools to kldutils"...
For now I'll just attach my modified versions.
> _Description: Network card drivers:
[...]
> - Note: You most likely don't need any, since default kernels currently
> include
> - builtin support for many NICs. You can always come back to this question
> later
> + You most likely don't need any, since default kernels currently include
> + built-in support for network cards. You can always come back to this
> question later
> with "dpkg-reconfigure module-init-tools".
The revised version avoids the jargonism NIC, but dropping the
qualifier "many" makes it sound as if it's talking about
CONFIG_NETDEVICES (required for a kernel to support NICs at all).
I'd put it back, or indeed make it "most network cards".
I'd also say "^the^ default kernels".
> Package: kbdcontrol
[...]
> -Description: Command line tool to change keyboard layout
> - Original FreeBSD command to set keyboard layout and the FreeBSD possible
> +Description: command-line tool to change FreeBSD keyboard layout
> + This package provides the original FreeBSD command to set keyboard layout
> and the FreeBSD possible
> keyboards.
"FreeBSD" is a modifying noun, which has to go after any adjectives,
and I think that "and" needs to be reinforced (to make it clear it's
"provides A + B", not "to set A + B"):
This package provides the original FreeBSD command to set keyboard layout,
plus the possible FreeBSD keyboards.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Template: module-init-tools/network
Type: multiselect
Choices: ${choices}
_Description: Network card drivers:
Please select drivers for this machine's network card(s). You may select more
than
one driver, or none at all, depending on the number of cards installed in the
machine.
.
You most likely don't need any, since the default kernels currently include
built-in support for most network cards. You can always come back to this
question later
with "dpkg-reconfigure module-init-tools".
Template: module-init-tools/sound
Type: multiselect
Choices: ${choices}
_Description: Sound card drivers:
Please select drivers for this machine's sound card(s). You may select more
than
one driver, or none at all, depending on the number of cards installed in the
machine.
.
If in doubt, leave this field empty. The "snd_probe" command may be used
later to identify the sound card(s). You can always come back to this question
with "dpkg-reconfigure module-init-tools".
Template: module-init-tools/other
Type: multiselect
Choices: ${choices}
_Description: Other modules:
Please select the modules needed to properly support this
machine's hardware.
.
If in doubt, leave this field empty. You can always come back to
this question with "dpkg-reconfigure module-init-tools".
Source: freebsd-utils
Section: utils
Priority: important
Maintainer: GNU/kFreeBSD Maintainers
Uploaders: Aurelien Jarno , Guillem Jover
Build-Depends: debhelper (>= 7), quilt, po-debconf, freebsd-buildutils,
libkvm-dev (>= 7.0), libbsd-dev (>= 0.0-1.2), libc0.1-dev (>= 2.7-13),
flex | flex-old, kfreebsd-kernel-headers (>= 0.31), libfreebsd-dev (>= 0.0-5),
libipx-dev, libkiconv-dev, libgeom-dev, libdevstat-dev, libsbuf-dev
# libkvm-dev: dmesg
# libgeom-dev : ccdconfig
# libfreebsd (>= 0.0-5): ifconfig
# libipx-dev: ifconfig
# libkiconv-dev: mount_*
# libc0.1-dev (>= 2.7-13): ifconfig
# libdevstat-dev: mdconfig
# libsbuf-dev: mdconfig
Standards-Version: 3.8.1
Package: freebsd-utils
Priority: required
Essential: yes
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}, ufsutils
Suggests: freebsd-hackedutils (>= 6.1-1)
Conflicts: inetutils-tools (<= 2:1.4.3+20051212-4)
Replaces: freebsd-hackedutils (<= 6.1-1)
Description: FreeBSD utilities needed for GNU/kFreeBSD
This package provides FreeBSD utilities needed for GNU/kFreeBSD.
Package: module-init-tools
Priority: important
Architecture: kfreebsd-i386 kfreebsd-amd64
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, kfreebsd-image
Replaces: kldutils (<< 6.0-2.really.5.4-0.6), freebsd-utils (<= 5.2.1-16),
freebsd-hackedutils (<= 6.1-1), kfreebsd-common (<< 6.1-6)
Description: tools for managing kFreeBSD modules
This package provides a set of programs for loading, inserting, and
removing kernel modules for kFreeBSD.
Package: kbdcontrol
Architecture: kfree
[RFR] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
Please find, for review, the debconf templates and packages descriptions for
the freebsd-utils source package.
This review will last from Sunday, April 19, 2009 to Wednesday, April 29, 2009.
Please send reviews as unified diffs (diff -u) against the original
files. Comments about your proposed changes will be appreciated.
Your review should be sent as an answer to this mail.
When appropriate, I will send intermediate requests for review, with
"[RFRn]" (n>=2) as a subject tag.
When we will reach a consensus, I send a "Last Chance For
Comments" mail with "[LCFC]" as a subject tag.
Finally, the reviewed templates will be sent to the package maintainer
as a bug report, and a mail will be sent to this list with "[BTS]" as
a subject tag.
Rationale:
--- freebsd-utils.old/debian/kbdcontrol.templates 2009-04-14
21:47:59.843981138 +0200
+++ freebsd-utils/debian/kbdcontrol.templates 2009-04-14 22:36:55.331982119
+0200
@@ -3,7 +3,7 @@
Choices: ${choices}
Default: none
Description: Keymap:
- You can choose a keymap in the list.
+ Please choose the keyboard map.
.
- Note: If you don't know, don't select any yet. You can always come back to
+ If in doubt, don't choose any map. You can always come back to
this question with "dpkg-reconfigure kbdcontrol".
Standardize to our usual recommendation (Please foo...).
As usual, also, we suggest dropping leading "Note:" stuffand also
use our standard formula here "If in doubt...".
--- freebsd-utils.old/debian/module-init-tools.templates2009-04-14
21:47:59.795981291 +0200
+++ freebsd-utils/debian/module-init-tools.templates2009-04-14
22:35:56.143982264 +0200
@@ -2,30 +2,30 @@
Type: multiselect
Choices: ${choices}
_Description: Network card drivers:
- Select the appropiate driver for your network cards. You may select more than
- one driver, or none at all, depending on the number of cards you have.
+ Please select drivers for this machine's network card(s). You may select more
than
+ one driver, or none at all, depending on the number of cards installed in the
machine.
.
- Note: You most likely don't need any, since default kernels currently include
- builtin support for many NICs. You can always come back to this question
later
+ You most likely don't need any, since default kernels currently include
+ built-in support for network cards. You can always come back to this question
later
with "dpkg-reconfigure module-init-tools".
About the same changes...
Template: module-init-tools/sound
Type: multiselect
Choices: ${choices}
_Description: Sound card drivers:
- Select the appropiate driver for your sound cards. You may select more than
- one driver, or none at all, depending on the number of cards you have.
+ Please select drivers for this machine's sound card(s). You may select more
than
+ one driver, or none at all, depending on the number of cards installed in the
machine.
.
- Note: If you don't know, don't select any yet. Later, you can use the
- snd_probe command to find it out. You can always come back to this question
+ If in doubt, leave this field empty. The "snd_probe" command may be used
+ later to identify the sound card(s). You can always come back to this question
with "dpkg-reconfigure module-init-tools".
Ditto.
Template: module-init-tools/other
Type: multiselect
Choices: ${choices}
_Description: Other modules:
- Below is a selection of modules that don't fall in either of the previous
- cathegories. Select those you find adequate.
+ Please select the modules needed to properly support this
+ machine's hardware.
.
- Note: If you don't know, don't select any yet. You can always come back to
+ If in doubt, leave this field empty. You can always come back to
this question with "dpkg-reconfigure module-init-tools".
And ditto.
--- freebsd-utils.old/debian/control2009-04-14 21:47:59.795981291 +0200
+++ freebsd-utils/debian/control2009-04-14 22:38:07.131982281 +0200
@@ -26,7 +26,7 @@
Conflicts: inetutils-tools (<= 2:1.4.3+20051212-4)
Replaces: freebsd-hackedutils (<= 6.1-1)
Description: FreeBSD utilities needed for GNU/kFreeBSD
- This package contains FreeBSD utilities needed for GNU/kFreeBSD.
+ This package provides FreeBSD utilities needed for GNU/kFreeBSD.
s/contains/provides (our standard recommendation, again).
Package: module-init-tools
Priority: important
@@ -35,14 +35,14 @@
Replaces: kldutils (<< 6.0-2.really.5.4-0.6), freebsd-utils (<= 5.2.1-16),
freebsd-hackedutils (<= 6.1-1), kfreebsd-common (<< 6.1-6)
Description: tools for managing kFreeBSD modules
- This package contains a set of programs for loading, inserting, and
+ This package provides a set of programs for loading, inserting, and
removing kernel modules for kFreeBSD.
Package: kbdcontrol
Ar
[ITR] templates://freebsd-utils/{kbdcontrol.templates,module-init-tools.te mplates}
Dear Debian maintainer, The Debian internationalisation team and the Debian English localisation team will soon begin the review of the debconf templates used in freebsd-utils. This review takes place for all packages that use debconf to interact with users and its aims are: - to improve the use of English in all debconf templates; - to make the wording of debconf templates more consistent; - to encourage more translations of templates. Even if your first language is English, this process is likely to help track down typos or errors, and improve consistency between the debconf templates of your package and that of other packages in the distribution. The process involves both debian-l10n-english contributors and Debian translators. The details of the process are given in http://wiki.debian.org/I18n/SmithDebconfReviewProcess. I will act as the coordinator of this activity for freebsd-utils. The first step of the process is to review the debconf source template file(s) of freebsd-utils. This review will start on Friday, April 17, 2009, or as soon as you acknowledge this mail with an agreement for us to carry out this process. All parts of the process will be carried out in close collaboration with you, and, unless you explicitely ask for it, no upload nor NMU will happen for freebsd-utils. If you approve this process, please let us know by replying to this mail. If some work in progress on your side would conflict with such a rewrite (such as adding or removing debconf templates), please say so, and we will defer the review to later in the development cycle. Thank you for your attention. -- signature.asc Description: Digital signature
Bug#523896: module-init-tools: Recent upgrade broke module auto-loading
Subject: module-init-tools: Recent upgrade broke module auto-loading Package: module-init-tools Version: 3.7-pre9-1 Severity: important After booting today, several essential modules were not loaded at bootup, giving me a barely functional system (no sound and no external drives). The missing modules were snd-ice1712 and sd-mod. Doing a manual modprobe loads the given modules without errors, and no other warnings than the umpteen messages about missing .conf extensions in /etc/modprobe.d. I have tried a reinstall of module-init-tools, udev and initramfs-tools, but that did not resolve the situation. If this is triggered by another package install, it must have been one of the packages that were installed on the 12th. I'll attach my dpkg log since the 11th, maybe someone with more knowledge than I can spot which package caused this. What is especially weird is that sd-mod is missing, while the usb-storage module does get loaded. From dmesg: [ 11.068300] usb-storage: device scan complete [ 11.068775] scsi 0:0:0:0: Direct-Access TOSHIBA MK1637GSX PQ: 0 ANSI: 2 CCS but the sd messages only appear after I perform a manual modprobe: [ 150.692889] Driver 'sd' needs updating - please use bus_type methods [...] [ 150.705723] sd 0:0:0:0: [sda] Attached SCSI disk Just today I also upgraded the kernel from 26-1 to 26-2, but both exhibit the same problem. I know that I can simply add the modules to /etc/modules and be done with it, but I'm more interested in finding out how this broke than papering over it with a workaround. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (800, 'testing'), (550, 'stable'), (101, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages module-init-tools depends on: ii libc6 2.9-4 GNU C Library: Shared libraries ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip module-init-tools recommends no packages. module-init-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug report: module-init-tools: depends upon sort and uniq, which are located in /usr
(please Cc me, I'm not on the list, just found it on gmane)
Petr Salinger dixit:
> Proper fix would be write "sort -u" using only /bin a /sbin binaries.
For this task, maybe a uniq-without-sort would be enough. Something like
this (at least works in mksh, maybe it's portable enough for /bin/sh):
--- module-init-tools.orig Wed May 16 19:05:53 2007
+++ module-init-tools Wed May 16 19:09:37 2007
@@ -27,12 +27,14 @@ do_start() {
for i in load stat unload ; do
which kld$i >/dev/null || exit 1
done
- modules="`shopt -s nullglob ; cat /etc/modules /etc/modules.d/* \
-| sed -e \"s/#.*//g\" -e \"/^\( \|\t\)*$/d\" | sort | uniq`"
-
- set -e
-
- for i in ${modules} ; do
+ mods=:
+ cat /etc/modules /etc/modules.d/* 2>/dev/null | \
+ sed -e 's/#.*$//g' -e '/^[ ]*$/d' | \
+ while read i; do
+ case $mods in
+ *:$i:*) continue ;;
+ esac
+ mods=$mods$i:
if ! kldstat -n $i >/dev/null 2>/dev/null ; then
echo "Loading $i ..."
kldload $i || true
I've just tried this and it works for me, maybe I didn't cover corner
cases, but it looks okay, and the autoconf texinfo manual (section
portable shell) tells me there is no additional quoting needed either.
Bonus: the bash-only “shopt” is gone as well!
HTH&HAND,
//mirabile
PS: If you got any other shell scripting tasks, feel free to come to me.
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence. -- Coywolf Qi Hunt
Re: Bug#424208: module-init-tools: use of /usr/bin/{sort,uniq} before /usr is mounted
On Tue, 15 May 2007, Marco d'Itri wrote: > On May 15, Thorsten Glaser <[EMAIL PROTECTED]> wrote: > > > Package: module-init-tools > > Version: 6.2-3 > > Why do I keep receiving bugs for a kfreebsd-i386 package which I do not > maintain? Because people are assigning it to the module-init-tools binary package instead of whatever the kfreebsd-i386 source package is called. [I don't even know what source package that is, actually.] Don Armstrong -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. -- Edmund Burke "Thoughts on the Cause of Present Discoontents" http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#424208: module-init-tools: use of /usr/bin/{sort,uniq} before /usr is mounted
Marco d'Itri dixit: >On May 15, Thorsten Glaser <[EMAIL PROTECTED]> wrote: > >> Package: module-init-tools >> Version: 6.2-3 > >Why do I keep receiving bugs for a kfreebsd-i386 package which I do not >maintain? No idea, in this case I suspect there are two different packages with the same name. (I thought they are either the same package, or have different names.) Me disculpe per favore, //mirabile -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#424208: module-init-tools: use of /usr/bin/{sort,uniq} before /usr is mounted
Marco d'Itri wrote: > On May 15, Thorsten Glaser <[EMAIL PROTECTED]> wrote: > >> Package: module-init-tools >> Version: 6.2-3 > > Why do I keep receiving bugs for a kfreebsd-i386 package which I do not > maintain? Because of this: X-Original-To: debian-bsd@lists.debian.org Received: from rietz.debian.org (rietz.debian.org [140.211.166.43]) by murphy.debian.org (Postfix) with ESMTP id 6F0BE359BC; Tue, 15 May 2007 16:48:24 -0500 (CDT) Received: from debbugs by rietz.debian.org with local (Exim 4.50) id 1Ho4jd-vQ-Eq; Tue, 15 May 2007 21:39:09 + Somebody/thing is assigning the debian-bsd list into the bug ;) Puzzled me for a while too Greets, Jeroen signature.asc Description: OpenPGP digital signature
Re: Bug#424208: module-init-tools: use of /usr/bin/{sort,uniq} before /usr is mounted
On May 15, Thorsten Glaser <[EMAIL PROTECTED]> wrote: > Package: module-init-tools > Version: 6.2-3 Why do I keep receiving bugs for a kfreebsd-i386 package which I do not maintain? -- ciao, Marco signature.asc Description: Digital signature
Re: Bug report: module-init-tools: depends upon sort and uniq, which are located in /usr
Le lundi 14 mai 2007 à 11:53 +0200, Petr Salinger a écrit : > > I tried to report it using reportbug, but it ended in Debian's official > > BTS as #423662 (so maybe this is another bug to report) and was almost > > instantly closed. Feel free to point me to the right place to report. > > Ohh, you just discovered bug in a package, that have compeletely different > content compared to Linux one (and is from different source package). Don't worry, I have more. ;-) > There is a small number of such kfreebsd specific packages, > this one belongs to them. > > Here is the report as generated by reportbug: > > Package: module-init-tools > > Version: 6.2-3 > > Severity: normal > > > > The initscript module-init-tools uses /usr/bin/sort and /usr/bin/uniq > > while /usr may not yet be mounted. Worst, it is the default with the > > current installation. > > As a workaround, just drop "| sort | uniq" from the initscript. > In the worst case, it will show confusing > "Not loading xxx (already loaded)". > > Proper fix would be write "sort -u" using only /bin a /sbin binaries. 1) I see how to do it just using awk, which is unluckily in /usr/bin also so doesn't solve anything. 2) It would be slightly more efficient, even if hardly noticeable to remove the call to uniq and only use "sort -u" 3) But as the next step in this script is to: if ! kldstat -n $i >/dev/null 2>/dev/null It should do no harm at all to remove completely the sort|uniq pair. > Any volunteer ? ;-) > > Petr -- Jérôme Warnier FLOSS Consultant http://beeznest.net
Re: Bug report: module-init-tools: depends upon sort and uniq, which are located in /usr
I tried to report it using reportbug, but it ended in Debian's official BTS as #423662 (so maybe this is another bug to report) and was almost instantly closed. Feel free to point me to the right place to report. Ohh, you just discovered bug in a package, that have compeletely different content compared to Linux one (and is from different source package). There is a small number of such kfreebsd specific packages, this one belongs to them. Here is the report as generated by reportbug: Package: module-init-tools Version: 6.2-3 Severity: normal The initscript module-init-tools uses /usr/bin/sort and /usr/bin/uniq while /usr may not yet be mounted. Worst, it is the default with the current installation. As a workaround, just drop "| sort | uniq" from the initscript. In the worst case, it will show confusing "Not loading xxx (already loaded)". Proper fix would be write "sort -u" using only /bin a /sbin binaries. Any volunteer ? ;-) Petr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug report: module-init-tools: depends upon sort and uniq, which are located in /usr
I tried to report it using reportbug, but it ended in Debian's official BTS as #423662 (so maybe this is another bug to report) and was almost instantly closed. Feel free to point me to the right place to report. Here is the report as generated by reportbug: Package: module-init-tools Version: 6.2-3 Severity: normal The initscript module-init-tools uses /usr/bin/sort and /usr/bin/uniq while /usr may not yet be mounted. Worst, it is the default with the current installation. Regards -- System Information: Debian Release: lenny/sid Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 6.2-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages module-init-tools depends on: ii debconf1.5.13Debian configuration management sy ii kfreebsd-image-6.2-1-486 [ 6.2-2 kernel of FreeBSD 6.2 image ii kfreebsd-image-6.2-1-686 [ 6.2-2 kernel of FreeBSD 6.2 image ii libbsd00.0-1.2+r1710 BSD compatibility library - shared ii libc0.12.5-7 GNU C Library: Shared libraries ii libfreebsd00.0-5 FreeBSD compatibility library - sh module-init-tools recommends no packages. -- debconf information: * module-init-tools/other: r128, unionfs * module-init-tools/sound: snd_cs4281, snd_es137x, snd_ess, snd_sb16, snd_sb8, snd_sbc (Creative Sound Blaster ISA and compatible) * module-init-tools/network: -- Jérôme Warnier FLOSS Consultant http://beeznest.net
