>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
mode 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]
liminating bashisms causes
inconvenient divergence from upstream. But that divergence can be
limited to this short patch per offending script:
1c1
< #!/bin/sh
---
> #!/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]
people
> could be working on instead.
Well, we know how time consuming it can 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 d
the
"POSIX-only" rule laid down in 10.4.
See #267142 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
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". Tro
s_msg() would have to be added.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ure to see how much 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_success_msg() { echo "$@"; }
> 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 [EM
sv-rc 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 &qu
item: Grep the postinst files 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]
.
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]
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 c
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]
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
her in complex ways and the
scripts and data 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]
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
and bring
> interfaces 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]
ths versus eighteen months. I hope 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 su
uldn't 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&qu
tinue to participate 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 sub
ld 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]
s to have access to
an archive 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]
g01078.html
http://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
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 alwa
t with "grave". That is, if the package
isn't unusable 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.
scripts at once
> and letting each call its dependencies. This would 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. (T
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]
available for use by other, non-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 sub
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 [EM
> 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 [EM
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 bot
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]
eading posts on this topic. My webmain
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]
ht place to put 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]
he gets 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]
alsa-base package. It would include 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-imag
s nothing
else 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
le Debian release.
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
at needs to be fixed, though. Another 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 PROTECT
chine's 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]
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
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? C
illing to make use of
such a feature, though.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
7379. This feature is also needed so that maintainer
scripts can change runlevel configuration iff they haven't
been changed by the user.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
needing some devious guerilla techniques to thwart the
> packages starting.
apt-get install sysv-rc-conf.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
orm of this question is how does one deal with
> missing dependencies when using dpkg and not apt.
One downloads the missing packages and dpkg --install's them.
BTW have you tried module-assistant?
--
Thomas Hood
n purge too, so I suggest
you simply override lintian and linda.
[*] (or do the file-rc equivalent, which happens automatically
if file-rc is installed because you use update-rc.d)
--
Thomas Hood
dit page" button on the
> page.
Inspired by A.S.'s comment I've just sorted the proposals
into four groups, though not exactly the ones he defined.
--
Thomas Hood
nstead use a program
> called 'pmount' (policy mount) that allows normal users to mount
> removable devices without an /etc/fstab entries.
All sounds good.
Have you heard that mount's upstream is looking for someone to adopt mount
(and the rest of util-linux)? Interested?
--
Thomas Hood
question was bug #267142 "debian-policy:
Sections 10.4 and 6.1 are inconsistent (Posix doesn't say what you
think it says)".
Please follow up to debian-policy.
--
Thomas Hood
an we at least assume that "test"
will be grandfathered, and consequently that "-a" and "-o" should be
avoided?
--
Thomas Hood
o be added to
our blacklist files /etc/hotplug/blacklist.d/alsa-base and
/etc/discover.d/alsa-base.
--
Thomas Hood
ew values. If x and y have
configuration utilities xcfg and ycfg then z should insofar as possible
use xcfg and ycfg to make changes to x's and y's configurations.
--
Thomas Hood
Ian Murdock wrote:
> I will add this support to discover2 as well, since it currently
> suffers from the same problem as discover1 with respect to blacklisting
> modules.
Thanks. We will release a new version of alsa-base very shortly that
makes use of this feature.
--
Thomas Hood
ve tried a few times,
> and wound up with scripts in ppp, dhcp, and network - all modelled
> similiar to the DHCP state management.
I have also had to deal with this when I made the resolvconf package: I
had to write different hook scripts for each of the DHCP clients, pppd
and ifupdown. It took a long time to debug them all.
--
Thomas Hood
these issues to write to
#255195 and support my request to create a debian-net mailing list.
--
Thomas Hood
On Wed, 2004-10-13 at 21:53, Joshua Kwan wrote:
> Well, no. Now discover1 (as yet unreleased) has support for an
> /etc/discover.d dir where you can have something akin to
> /etc/hotplug/blacklist.d/alsa-base. Of course, once that discover1 upload
> is made, the bug goes to the ALSA maintainers.
>
t;up" scripts if
pppd reconnects.
I can see why, in the case of PPP interfaces, that might be desired. I am
not sure that we should implement it, though. It would depart from the
way ifupdown "up" and "down" scripts have worked in the past for other
interfaces.
--
Thomas Hood
On Wed, 2004-10-13 at 10:57, Petter Reinholdtsen wrote:
> [Thomas Hood]
> Isn't this only a problem with discover1? I thought discover (v2) had
> a mechanism to detect if OSS or ALSA was used.
If there is such a mechanism then it isn't working.
> It is probably better to
ages should Conflict with discover and discover1.
--
Thomas Hood
On Tue, 2004-10-12 at 23:28, Robert Collins wrote:
> Does it hook into ppp to handle persistent ppp connections? (i.e. adsl).
I am not sure what you mean.
The new ifupdown uses pppd's updetach option. Run with this option,
pppd only exits after it has made a connection. Since ifup runs "up"
co
ddressed in the experimental
version of ifupdown.
--
Thomas Hood
On Tue, 12 Oct 2004 14:30:14 +0200, Robert Collins wrote:
> Thats quite different - I'd love for this to be consolidated and
> addressed though.
The experimental version of ifupdown addresses this to some extent. The
if-up.d scripts are run only after the PPP interface is created.
Is there a version of run-parts out there that runs all the
scripts in a directory in parallel? I have been writing
such a thing but I want to make sure that I am not reinventing
the wheel.
--
Thomas Hood
On Tue, 2003-10-21 at 05:12, Russell Coker wrote:
> Hmm, maybe we could make it the rule that anything with number 99 can return
> before it's finished initialising?
If the point here is to "speed up boot" then I think it would suffice
to move the rc symlinks for those "leaf" services to somethin
the system so that it knows which pairs of initscripts
to serialize, and (2) changing initscripts so that they are able to
wait until prerequisite services have become available. There are
other possibilities, too ...
--
Thomas Hood <[EMAIL PROTECTED]>
* Package name: waproamd
Version : 0.3b
Upstream Author : [EMAIL PROTECTED] (Lennart Poettering)
* URL :
http://www.stud.uni-hamburg.de/~lennart/projects/waproamd/
* License : GPL v.2
Description : wireless network roaming daemon
Waproamd makes a specifie
On Wed, 2003-10-08 at 21:25, Daniel Ruoso wrote:
> I think this should be clearly discussed.
Just to prevent any confusion I'll just point out that
the rant you quoted was authored by Eray Ozkural.
--
Thomas Hood <[EMAIL PROTECTED]>
ing them.
It doesn't sound to me as if one works _with_ him on util-linux.
--
Thomas Hood <[EMAIL PROTECTED]>
e incomplete. If there are newer versions
of any of these floating around that aren't available via the
link above then I would appreciate someone sending me a URL.
For DR ch.10 I have been consulting chapters 3 and 8 of the
Debian Network Administrator's Manual by Duncan C Thomson a
Manoj wrote:
> > I would be interested in knowing how you set it up equivalent
> > to cardctl scheme allows me to set up pcmcia networks.
cardmgr's system of configuring things dependently upon
"scheme,socket,instance,hwaddr" is quite powerful but it is
possible to configure interfaces dependentl
hing to do.
My own preference is to disable everything in /etc/pcmcia/network.opts
and set things up so that hotplug does ifup and ifup configures the
interface in the standard way. Then I can use dns-nameservers lines
for PCMCIA network interfaces too.
--
Thomas Hood <[EMAIL PROTECTED]>
sons. Its if-down.d companion would be something
like:
#!/bin/sh
[ "$DNS_DOMAINNAMES" ] || exit 0
resolvconf -d 000${IFACE}-extra
--
Thomas Hood <[EMAIL PROTECTED]>
l consider letting
resolvconf migrate into sarge by closing #209265 with a 1.0
release.
--
Thomas Hood <[EMAIL PROTECTED]>
A's dependencies
is ambiguous between denoting the packages that depend on A and
the packages upon which A depends. I don't see how
A's depended-on packages
is any clearer. Actually it seems worse to me. I suggest using
packages upon which A depends
and
packages that depend on A
wherever the ambiguity matters.
--
Thomas Hood <[EMAIL PROTECTED]>
tly configured version dpkg will pass a null
> argument; older versions of dpkg may pass (including the
> angle brackets) in this case. Even older ones do not pass a second
> argument at all, under any circumstances.
--
Thomas Hood <[EMAIL PROTECTED]>
On Sat, 2003-09-06 at 19:33, Colin Watson wrote:
> The pre-depended-on
> package doesn't have to be configured; it merely has to have been
> configured at some point in the past. Thus, pre-depended-on packages
> have to be prepared to be functional in the most common case of being
> unpacked but no
So it seems that the sarge_rc_policy requirement is additional to
policy and is intended to deal with a shortcoming in dpkg. Please
correct me if I am wrong.
--
Thomas Hood
Or am I missing something?
--
Thomas Hood
ar/run/pckg/ .
--
Thomas Hood
?
I know of no prohibition against executable scripts in /var/run.
Why should there be such a prohibition? Unless an answer to this
turns up, go ahead and use /var/run .
--
Thomas Hood
maintainer (AJT) has
given permission.
If you would like to do us the favor of testing it before Thursday
then you can get it from:
deb http://debian.zugschlus.de/debian/zgpool/main/ifupdown/ /
deb-src http://debian.zugschlus.de/debian/zgpool/main/ifupdown/ /
--
Thomas Hood
e purposes of section
7.4 of the developer's reference "Dealing with inactive and/or
unreachable maintainers".
--
Thomas Hood
tags 156161 wontfix
thanks
On Mon, 2003-08-25 at 17:43, Goswin von Brederlow wrote:
> The existence of starts scripts alone is sufficient to get the right
> behaviour:
>
> old level | new level | affect
> --+---+
> | | no change (if it runs don't kill i
On Mon, 2003-08-25 at 16:24, Henrique de Moraes Holschuh wrote:
> It is up to the administrator to understand that this will break upgrades
> in weird ways if a service absolutely HAS to be restarted, since that
> restart will simply not happen.
Yes, restart will not happen if the current runlevel
a service but
invoke-rc.d interprets the absence of the stop symlink as
permission to start the service. This can't be called a bug
because the invoke-rc.d(8) passage above is ambiguous.
--
Thomas Hood
mlinks)
states. I have downgraded #156161 to a wish that the rc system
be specified in this way.
Can we agree that this a good idea? If not, I would be interested
to know where the problems lie.
--
Thomas Hood
If a utility was written to make
it more convenient to disable and enable a service, as discussed
above, then one could add a "manual" state (no symlinks) to
the "disabled" (all K symlinks) and "enabled" (not all K symlinks)
states.
Is this a good idea? If not, I would be interested to know where
the problems lie.
--
Thomas Hood
ant to run the latest version. Unless one side
gives in, this seems like adequate grounds for a fork.
--
Thomas Hood
ed
in debian-legal and that is the best place to continue the
discussion if you really can't let the subject drop.
--
Thomas Hood
/
(I built the new [u]mount programs by copying Debian's MCONFIG file
out of the Debian util-linux-2.11z source dir and running
"./configure" and "make".)
Please let me know whether or not you have any problems.
--
Thomas Hood
Package: wnpp
Version: unavailable; reported 2003-07-27
Severity: wishlist
* Package name: resolvconf
Version : 0.31
Upstream Author : Thomas Hood <[EMAIL PROTECTED]>
* URL : http://alioth.debian.org/projects/update-resolv
* License : GPL
Descr
On Sun, 2003-07-27 at 12:44, Colin Watson wrote:
> I tested this before posting. No, -e is a little more forgiving than
> that, as stated in bash(1):
>
> -e Exit immediately if a simple command (see SHELL
> GRAMMAR above) exits with a non-zero status.
On Fri, 2003-07-25 at 11:21, Manoj Srivastava wrote:
> On 25 Jul 2003 09:20:20 +0200, Thomas Hood <[EMAIL PROTECTED]> said:
> > Conffiles are different in one respect, which that is that they can
> > be locally modified. When a conffile is to be overwritten and it
> >
On Fri, 2003-07-25 at 11:20, Colin Watson wrote:
> On Fri, Jul 25, 2003 at 10:04:26AM +0100, David Pashley wrote:
> > Probably the biggest unicode problem I have noticed is with man and/or
> > less where it can't display dashes correctly. At least it doesn't seem
> > to work out of the box.
>
> In
On Fri, 2003-07-25 at 11:19, Manoj Srivastava wrote:
> Not really. Why do we need this overly micromanaging rule in
> policy? As long as it understood that user data is not to be deleted,
> why can't I put user data in /var/lib// if I so desire, as long
> as I take care to not rm -rf that
Re:
1. dpkg -L
2. conffiles belonging to the package
3. configuration files other than conffiles belonging to the package
4. package's log output, cached compiled versions of conffiles, etc.
5. user data created using the package
On Fri, 2003-07-25 at 09:01, Manoj Srivastava wrote:
> > Here is my
101 - 200 of 254 matches
Mail list logo
