: DELAYLOGIN=no
No-login mode always: rm -f /etc/nologin ; : /etc/nologin
Anyone see any problems with this scheme? Any better ideas?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
: DELAYLOGIN=yes
No-login mode never: rm -f /var/lib/initscripts/nologin ; DELAYLOGIN=no
No-login mode always: touch /var/lib/initscripts/nologin ; DELAYLOGIN=no
Anyone see any problems with this scheme? Any better ideas?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL
packages into bastions of untended bugs.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
... insulting.
This is not a fair characterization of what the introduction of
a two-maintainer rule would be doing. No one should be insulted
by general rule changes designed to make Debian work better.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
this idea.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
mood then
I'd suggest that those who are promoting team maintainance are trying
to gain power while evading responsibility.
Well, you do suggest it here. And what you suggest makes no sense, so
let's not rule out the possibility that you are in fact paranoid.
--
Thomas Hood
--
To UNSUBSCRIBE
and admins who
have to ensure that writable space is shoved under /var/run by
the time any of the H tries to write there.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Gabor Gombas wrote:
... I'd like to have a check for /run (or /lib/run or whatever)
being empty at the end of the boot process
The new mountvirtfs prints such warnings for all the virtual
filesystems.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Tmpfs memory can be swapped out, so is this even a hypothetical
problem?
Maybe it isn't on Linux. I wasn't aware tmpfs could be swapped out.
That still leaves the question of just which features we want to require
from our non-Linux kernels for basic operation, I guess.
Yes, I don't
would be an
appropriate claim if Manoj had said it looked okay.
Agreed. Fortunately, I didn't claim that.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
only for those very
few purposes for which /var/run cannot be used. If there are worries
about abuse then I would suggest the addition of a sentence to Policy
forbidding such abuse.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
-write and programs must not use /run before the
cleaning has been completed; it would probably be easier to drop the
cleanliness-at-boot guarantee and let programs clean out their own
stale files.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
So, has anyone tested the new packages?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, but at the top level.
Here's another possible argument:
Putting R in /lib spoils the otherwise read-only
character of that directory.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Anthony Towns wrote:
Developers have been known not to be completely familiar with policy,
but it's admins and upstream programmers that I'm particularly
thinking of.
I don't see any problems arising from rampant /run use by _admins_.
They are always free to do what they want with their
Any other defenders of /lib/run? Of /run?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
find /lib/run uglier than /run. ;)
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
, but it does involve some work.
There is a new upstream release candidate out now (1.0.11rc1) and I would
like to take the opportunity to go through the process with the new
volunteer.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
with INIT_VERBOSE=yes kernel parameter. Is the boot more verbose?
Any glitches in any of the messages?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 17 Jun 2005 10:07:10 +0200
Source: tpctl
Binary: tpctl
Architecture: source i386
Version: 4.17-2
Distribution: unstable
Urgency: low
Maintainer: Debian tpctl maintainers [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
The ALSA packaging team needs help. We really need someone with expertise
in programming for the ALSA library. If you are able to help us, please
contact us at [EMAIL PROTECTED]
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
I seek co-maintainers for:
mwavem
thinkpad, tpctl
resolvconf
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to solicit opinions.
Please reply to [EMAIL PROTECTED], not to the list.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to be reworked?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the latter eliminates the need
for the former.
I am cc:ing this to debian-devel in order to solicit opinions.
Please reply to [EMAIL PROTECTED], not to the list.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
if 'localhost.localdomain' is included on the
127.0.0.1 line in /etc/hosts.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
That did it, unloaded the snd-intel8x0 and 8x0m and then reloaded i810_audio
and things worked again.
i810_audio is an OSS module, not an ALSA module. You fixed sound by switching
from ALSA to OSS.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
properly whether
/etc/hosts contains
127.0.0.1 localhost.localdomain localhost
or
127.0.0.1 localhost
especially considering the fact that the sarge installer writes
/etc/hosts with the former.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
. For backward compatibility that behavior should
probably be preserved.
When a final decision has been made about how hot plug blacklisting
will be implemented in the future, please file a bug report against
alsa-base explaining what changes need to be made, if any.
--
Thomas Hood
--
To UNSUBSCRIBE
files which might
appropriately be kept in a subdirectory of /run/.
/etc/nologin
/etc/mtab
/etc/network/run/ifstate
/etc/resolvconf/run/*
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Andreas Metzler wrote:
Thomas Hood [EMAIL PROTECTED] wrote:
[command -v]
It is not even useful as a which(1) replacement. Whereas which
prints the pathname of the first executable file on the PATH,
command -v prints the pathname of the first executable file on the
PATH _or_ the pathname
Marco d'Itri wrote:
Andreas Metzler wrote:
Thomas Hood wrote:
Is there anything else which dash supports but posh does not?
command -v
Which is the well known which(1) replacement, and basically mandatory
in a sane Debian shell. I keep wondering why people bother with posh.
command -v
updates.
To change it know is just silly political correctness.
I think that the kernel packaging team members should be able to do
their work without being insulted.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
of a shell feature whose use we should
not be discouraging. That's why it is proposed that local be
added (alongside echo -n) as an exception to the POSIX-only rule
expressed in 10.4. (Both bash and dash support local.) If you
agree then it would be helpful to mention this in #294962.
--
Thomas
be to replace '-a' with
'] [' in the offending scripts.
I support the idea of requiring #!/bin/sh scripts to be runnable on
posh.
I don't.
So the idea is doomed and there is no more need to discuss it.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
---
#!/bin/bash
If test -a, test -o and local are no longer considered
illegal bashisms then there won't be much need for this.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
can't be greater than the maximum. And I know that the maximum
is larger than 343.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thomas Hood [EMAIL PROTECTED] wrote:
I would appreciate it if someone would create the potash shell,
consisting of posh modified to implement test -a, test -o and
local. Debian would probably run on that well enough for it to
be used as /bin/sh, and it could become the de facto testbed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 31 Jul 2005 16:00:00 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.33
Distribution: unstable
Urgency: medium
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
for a long discussion of the POSIX-only rule.
I support the idea of requiring #!/bin/sh scripts to be runnable on
posh. Unfortunately not everyone is prepared to go along with it
(e.g., #309415).
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 21 Jul 2005 09:37:01 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.32
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
I have a couple of initscripts that print progress messages and I do
not want to be too hasty in eliminating them so I am thinking of
doing the following for now:
...
if [ -r /lib/lsb/init-functions ] ; then
. /lib/lsb/init-functions
print_warning_msg() { log_warning_msg $* ; }
that holding the control key down would allow
me to roll forward in order to move the viewport forward and thus
INCREASE the text size, as if I was getting closer to the text.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 20 Jul 2005 11:00:00 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.31
Distribution: unstable
Urgency: medium
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
() would have to be added.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the maintainer scripts can be simplified
on the basis of the assumption that the previous version is sarge
or later.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
$@; }
log_warning_msg() { echo $@; }
fi
Perhaps an idea for you too?
The package is only 20 kbytes installed. Let's just start Depending on it.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
and leave the Conflicting up to the latter.
The salty dog and I have been discussing runlevel editors in
general and bum in particular. I think that the next release
of bum will be rather good. :)
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 15 Jun 2005 11:18:18 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.30
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
in order to obtain the
factory default sequence numbers and implement a restore
factory default sequence numbers feature. See my last comment
in #183460.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sun, 10 Jul 2005 01:57:54 -0400, Nathanael Nerode wrote:
I suggested Debian IV
Are release numbers really needed? Why not do away with them altogether?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Nigel Jones wrote:
On 10/07/05, Thomas Hood [EMAIL PROTECTED] wrote:
Are release numbers really needed? Why not do away with them altogether?
you mean, just stick with code names?
That wouldn't exactly work, Debian's apt/dpkg basicly relies on
release numbers, how else can it easily
.
Among numbers, integers describe this order most clearly. :)
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian releases as minor ones. Every release is
major.
If Debian simply _must_ have decimal points in its release numbers then
I'd suggest replacing the 'r' in update version numbers with '.'. Thus
9.1 would be the number of the first etch update.
--
Thomas Hood
--
To UNSUBSCRIBE, email
have been split off into a separate Arch: all package.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 14 Jun 2005 20:00:00 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.29
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
Package: wnpp
Severity: normal
I request assistance with maintaining the mwavem package.
I own a ThinkPad 600 with an Mwave modem inside and I use this
to test the mwavem packages that I prepare. However, I do not use
the machine on a daily basis. If possible I would like help from
someone who
that the DPL will get
involved in this debate and steer it toward a firm decision.
To begin with we can all go back and review:
http://wiki.debian.net/index.cgi?ReleaseProposals
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
up and down.
http://people.redhat.com/dcbw/NetworkManager/
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
be
enough time to adjust to it before the release. Then the release was
delayed for a couple of years; meanwhile the maintainers of dhcp and dhcp3
have been busy with other things.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 20 May 2005 17:00:00 +0200
Source: mwavem
Binary: mwavem
Architecture: source i386
Version: 2.0-1
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
in the Debian project despite its
dysfunctional organisation;
2. push for changes to the organisation;
3. participate in another project instead.
(There are other possibilities, of course.)
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
be better if we simply made rc capture initscripts'
standard output (and exit status) and formatted it in such a way that
bootup messages were prettier.
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 17 Apr 2005 02:30:56 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.28
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
that wholly conforms to the DFSG, robustly interpreted.
Another goal is to encourage authors to license works compatible with the
DFSG, robustly interpreted.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Apparently Gentoo is using simpleinit. Anyone know what the
other distros are using?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 1 Apr 2005 16:16:21 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.27
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
be very hard to
implement efficiently.
I missed the beginning of this conversation. I hope it has been said that
the first thing we should do is investigate the several dependency-base
init systems that are already out there. (There are earlier threads about
this.)
--
Thomas Hood
by everyone (if the bug only affects some users) then the
bug is not grave.
If the bug is unreproducible then it can't be the case that the package is
unusable to everyone. So I'd say that a downgrade is justified.
Of course, I may be misinterpreting the severity tags.
--
Thomas Hood
On Fri, 2005-04-01 at 22:22 +0200, Frank Küster wrote:
(bugs in maintainer scripts are a policy violation)
I don't recall policy saying that maintainer scripts must be entirely
bug free.
Obviously they _should_ be bug free, but bugs in maintainer scripts
aren't always RC.
--
Thomas Hood
://lists.debian.org/debian-devel/2004/06/msg01445.html
http://lists.debian.org/debian-devel/2003/11/msg01695.html
http://lists.debian.org/debian-devel/2003/09/msg01359.html
http://lists.debian.org/debian-devel/2003/01/msg01898.html
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 26 Mar 2005 18:07:18 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.6.4-4.12exp4
Distribution: experimental
Urgency: low
Maintainer: Anthony Towns [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 9 Mar 2005 21:00:45 +0100
Source: thinkpad
Binary: thinkpad-source thinkpad-base
Architecture: source i386
Version: 5.8-4
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood
-LSB packages.
* Update README.Debian.
Should Debian initscripts use lsb init-functions?
It would probably be best if this were decided at the project level.
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Does anyone use the libasound2-plugins package? If so, how?
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Thu, 24 Mar 2005 08:50:16 +0100, Marc Haber wrote:
Is it as easy to participate with Ubuntu as it is with Debian?
In some respects it is easier. For one thing you can become a maintainer
there without going through an NM ordeal.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL
http://people.ubuntu.com/~scott/patches/
Thanks, that is very useful.
I see that Ubuntu has done a lot of work to make initscripts send output
through lsb printing functions. Are there any plans for Debian to adopt
these changes?
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 17 Mar 2005 20:00:00 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.6.4-4.12exp3
Distribution: experimental
Urgency: low
Maintainer: Anthony Towns [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 13 Mar 2005 18:10:44 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.6.4-4.12exp2
Distribution: experimental
Urgency: low
Maintainer: Anthony Towns [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL
On Thu, 10 Mar 2005 22:00:15 +0100, Thomas Hood wrote:
Here is another idea. We create a new binary package
sound-system-chooser which contains blacklists for both OSS and ALSA and
provides a debconf interface that the administrator can use to disable
either or both of the sound systems
I am interested in this subject.
http://panopticon.csustan.edu/thood/readonly-root.html
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
the blacklists because more
than one of them can be installed at once.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
interface apparently doesn't support In-Reply-To headers.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
in Debian that provides the same functionality.
laptop-net also contains a configuration file switching mechanism. I
believe that Chris Hanson (laptop-net's author) was once thinking of
repackaging this separately from laptop-net.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
files that would blacklist ALSA
modules, just as alsa-base blacklists OSS modules. These packages would
Conflict with each other and 2.6 kernel-image packages would Depend on
their disjunction.
An alternative is to drop ALSA modules from the 2.6 kernel-image packages.
--
Thomas Hood
the (currently nonexistent) oss package
which blacklists ALSA modules.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
Actually, this isn't true for 2.6 kernels. By default, discover
loads ALSA modules into 2.6 kernels.
The alsa-base/alsa-utils duo still has its uses, though, even if
you are running 2.6.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
option
would be to put the alsa modules in separate packages, just like pcmcia
modules.
There already exist separate alsa modules packages. Currently we only
build them for 2.4 kernels, though.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 19 Feb 2005 14:54:42 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.6.4-4.12exp1
Distribution: experimental
Urgency: low
Maintainer: Anthony Towns [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 3 Mar 2005 19:05:05 +0100
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.6.4-4.12
Distribution: unstable
Urgency: low
Maintainer: Anthony Towns [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 12 Sep 2004 14:46:29 +0200
Source: ifupdown
Binary: ifupdown
Architecture: source i386
Version: 0.6.4-4.11
Distribution: unstable
Urgency: low
Maintainer: Anthony Towns [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 29 Jan 2005 23:26:30 +0100
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.26
Distribution: unstable
Urgency: medium
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 8 Feb 2005 11:09:15 +0100
Source: tpctl
Binary: tpctl
Architecture: source i386
Version: 4.17-1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
On Sat, 2005-02-12 at 18:59 -0600, David Moreno Garza wrote:
On Sat, 2005-02-12 at 22:52 +0100, Thomas Hood wrote:
It would be nice if the page indicated which of the binary packages is new.
The binary column indicates those created within the source package.
Every source package
permanently
connected network adapter, or, if it does not have one of those,
127.0.1.1.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sat, 12 Feb 2005 01:20:13 +0100, Anibal Monsalve Salazar wrote:
Any input is welcome.
It would be nice if the page indicated which of the binary packages is new.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 21 Jan 2005 17:46:14 +0100
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.25
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 7 Jan 2005 18:00:00 +0100
Source: thinkpad
Binary: thinkpad-source thinkpad-base
Architecture: source i386
Version: 5.8-3
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 5 Dec 2004 22:02:21 +0100
Source: tpctl
Binary: tpctl
Architecture: source i386
Version: 4.16-1
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED]
Description
101 - 200 of 350 matches
Mail list logo
