Thomas Hood wrote:
iface eth0 inet static
address 172.17.207.12
gateway 172.17.207.1
netmask 255.255.255.0
I'll assume that interface eth0 is configured using the "ifup" command.
Add this line to the "iface eth0" stanza in /etc/network/interfaces
dns-nameservers 172.17.207.1 172.17.207
Is it written down anywhere what postrm purge is supposed to do?
Presumably remove some set of files, but what criteria should be used to
choose which?
The policy document is not much help; s6.8 says when it is called, but
not what it actually needs to do. I can't find more detail, though of
"Miriam Ruiz" <[EMAIL PROTECTED]> writes:
> Maybe there should also be a clasification of packages according to
> how bad would a bug be in them for the whole system, so that patches
> in those could be more carefully reviewed.
Perhaps uploads could come with the diff against the last version (or
BALLABIO GERARDO <[EMAIL PROTECTED]> writes:
> if I understand correctly, the problem was that openssl used some
> segment of uninitialized memory as a source of entropy, and the
> offending patch cleared it.
This is not correct. Clearing tmpbuf before reading /dev/urandom is
harmless. The broke
charset=us-ascii
> Content-Transfer-Encoding: 7bit
> Message-ID: <[EMAIL PROTECTED]>
> Date: Sun, 19 Feb 2006 11:01:56 +
> From: Richard Kettlewell <[EMAIL PROTECTED]>
> X-Face:
> h[Hh-7npe<
> F<\{jehn7.KrO{!7=:(@J~]<.[{>v9!1Z&W?r\c.!4DXH5PW
Gunnar Wolf <[EMAIL PROTECTED]> writes:
> Richard Kettlewell dijo [Fri, Jun 10, 2005 at 03:42:01PM +0100]:
>> I think it doesn't go far enough.
>>
>> mv sbin/* bin
>> rmdir sbin
>> ln -s bin sbin
>>
>> ...and the problem goes away
Miles Bader <[EMAIL PROTECTED]> writes:
> astronut <[EMAIL PROTECTED]> writes:
>> I agree. The type of user who is likely to be using the ifconfig
>> command on a regular basis is the type of user who probably already
>> has sbin in their path. (Power user, sysadmin's nonprivleged
>> account, etc.
Bernd Eckenfels <[EMAIL PROTECTED]> writes:
> The problem here is that ifconfig must be in sbin by FHS and by history
> (would break too many scripts). So moving is not an option. I can however
> put a symlink in /bin, however I am not sure how other DDs think about it,
> as this will set a bad pre
Jakob Lell <[EMAIL PROTECTED]> writes:
> many shell scripts use tempfiles like /tmp/tempfile.$$. This creates
> insecure tempfile vulnerabilities. One commonly used fix for this problem
> is to use set -e or/and set -C in the shell script. This makes the whole
> script fail if one command fails or
I use debmirror to maintain a local Debian archive, off
ftp.uk.debian.org and www.mirror.ac.uk. I get errors regarding the
following files:
dists/potato/main/source/games/xdigger_1.0.10-1.diff.gz
dists/potato/main/source/games/xdigger_1.0.10-1.dsc
dists/potato/main/source/games/xdigger_1.0.
Adrian Bunk <[EMAIL PROTECTED]> writes:
> If you start asking you will likely find more than thousand packages
> where someone will have a good reason for an update of the package
> in Debian 3.0. If only every 10th of these updates introduces a new
> bug (IMHO a conservative estimation) these pack
Panu A Kalliokoski <[EMAIL PROTECTED]> writes:
> Richard Kettlewell wrote:
>> I think you've answered your own question; it _can_ known which
>> soname to use, and to discover it, it should check the version of
>> the compiler.
>
> I'm not sure whe
Panu Kalliokoski <[EMAIL PROTECTED]> writes:
> Steve Langasek wrote:
>> [...compiler ABI is part of library ABI...]
> You're right; I'm just more worried about the more practical point
> that if a library, when being built, cannot know which SONAME it
> should install itself under (it would involve
[EMAIL PROTECTED] (Martin v. Loewis) writes:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>> My concern is that locally compiled apps built against C++
>> libraries other than libstdc++ will silently stop working on
>> upgrade. This is certainly not the most important issue facing us
>> in the tr
Matthew Wilcox <[EMAIL PROTECTED]> writes:
> * Add a Conflict with the non-`c' version of the package.
So it will be impossible to have both the old and new library packages
on the system simultaneously. That's broken.
>Why don't we just change the sonames?
>
>Because upstream choos
Craig Dickson <[EMAIL PROTECTED]> writes:
> Richard Kettlewell wrote:
>> Even if you don't care about weird platforms, "x > -1" is a
>> ridiculously obscure test in this context; to achieve the same
>> effect it would be much clearer to make x unsign
Richard Kettlewell writes:
> Jonathan Walther <[EMAIL PROTECTED]> writes:
> [...]
> > +
> > + /* follow any symlinks to the mailbox */
> > + memset(folder_path, 0, sizeof folder_path);
> > + if (lstat (lf->folder_path, &st) != -1 &&
Radovan Garabik <[EMAIL PROTECTED]> writes:
> Jean-Marc Chaton wrote:
>> - Almost all French users (and I think I can extrapolate: all the
>> users who need to read messages with non-ascii chars) need to set
>> up a '/etc/locale.gen' to see them correctly for example with
>> mutt, and that e
Ari Makela <[EMAIL PROTECTED]> writes:
> If you take a look at even just European languages you can see that
> most of them cannot be written with a-zA-Z. Actually, I think only
> English can.
It can't here, if you want to refer to the local currency in the
conventional way.
--
http://www.green
At http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79821 you will
find a discussion between the X maintainer and me.
It turns out that although he had received notification that the
updated package had been installed, ftp.debian.org did not reflect
this.
ttfn/rjk
at home and at work, and hope one day to be
able to contribute some more of my time to it. But I don't have the
time at present.)
--
Richard Kettlewell, ElectricMail Ltd
phone: +44 1223 501333 fax: +44 1223 501444
[EMAIL PROTECTED]
I've had these messages before, and followed the instructions for
stating that I no longer maintain the packages in question. But they
still keep appearing.
Can somebody *please* sort this out, and tell me that they have done
so?
(Both packages are, AFAIK, utterly obsolete and should not exist a
o remind people once again that
the svgalib packages could do with a new maintainer, as I currently do
not have time to do further work on them.
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
1. Does anyone want to take over the job of maintaining these
packages?
2. How badly do we need an aout-svgalib package? Are linuxsdoom &c
available in ELF?
Package: aout-svgalib
Package: svgalib1-bin
Package: svgalib1
Package: svgalib1-dev
ttfn/rjk
so it should be the same
colour independent of letter case.
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
started.
netstd_nfs or netstd_misc may be a sensible place to do this.
(It's not clear to me that this is a bug in precisely one package.)
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
ll my packages out soon, honest.. l-)
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
eded to be setgid mail into a separate
executable.)
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
Package: manpages
Version: 1.11-4
SEE ALSO
open(2), dup2(2), F_DUPFD(2), F_GETFD(2), F_GETFL(2),
F_GETLK(2), socket(2).
but:
[EMAIL PROTECTED]:richard$ man F_GETLK
No manual entry for F_GETLK
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED
Package: manpages
Version: 1.11-4
ERRORS
EBADF filedes is bad.
ENOENT File does not exist.
EACCESS, EFAULT, ENOMEM and ENAMETOOLONG are also possible.
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http
contents of the ... pairs.
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
ash table is full or action is \fIFIND\fP and the \fIitem\fP cannot be find
in the hash table.
.SH BUGS
-END
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
compression library - runtime
chiark:richard$
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
ired/X=both-problems (Status,Err: uppercase=bad)
||/ NameVersionDescription
+++-===-==-
ii ncurses3.0 1.9.9e-1 Video terminal manipulation: shared librarie
--
Richard Kettlewell [EM
>/etc/passwd has
>majordom:*:30:30:majordomo:/var/majordomo:/bin/sh
>
>The group should be `majordom', not `majordomo'.
All else aside, the correct passwd line is:
majordom:*/usr/lib/majordomo:/bin/sh
There should be no such directory as /var/majordomo; it certainly
doesn't appear in the
> dpkg-source.1
-rw-r--r-- 1 root root 6283 Aug 24 19:19
/usr/man/man1/dpkg-source.1.gz
[EMAIL PROTECTED]:richard$ man dpkg-shlibdeps
No manual entry for dpkg-shlibdeps
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
of the
screen; and occasionally it even ends up in the right place.
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
e
421-aftpd: User [EMAIL PROTECTED] is not allowed for service ftp on muskogee.
421 aftpd: aborted
ftp>
(again, this serves to illustrate the point, even if it didn't
actually work fully.)
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
Package: manpages
Version: 1.11-4
According to `man 2 acct':
SEE ALSO
acct(5)
But:
[EMAIL PROTECTED]:richard$ man 5 acct
No manual entry for acct in section 5
[EMAIL PROTECTED]:richard$
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROT
ly it should behave sensibly in the absence of
/etc/papersize (or depend on a package which is known to provide it,
though I think this is not as good an option). Secondly the postinst
script ignores any errors that occur; it should include `set -e' so
that errors are never ignored.
--
Richard
Package: bind
Version: 4.9.3-P1-3
`dig' really belongs in the `dnsutils' package, not the `bind'
package; just because one is not running a local name server does not
imply that one doens't want to use `dig' to look things up.
--
Richard Kettlewell [EMAIL PRO
Package: doc-debian
Version: 1.0-3
In /usr/doc/debian/bug-reporting.txt.gz:
HOW TO REPORT A BUG IN DEBIAN
Send mail to [EMAIL PROTECTED], as described below.
However, according to:
http://www.cl.cam.ac.uk/users/iwj10/debian
[EMAIL PROTECTED] writes:
>>> echo $HOME/Mailbox >$HOME/.forward
>
>Richard Kettlewell:
>>This is a bad idea if the home directory is NFS-mounted from a remote
>>system; IME file locking under NFS is very easy to get wrong. (Not
>>that all mailers get lock
even on local file systems...)
Additionally, a system might well have different backup or quota
policies for mail and ordinary user data, which is a good reason to
keep them separate.
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
I can't see the need to compress
things using compress either, as gzip produces smaller output, runs on
pretty much everything and is free.
--
Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.elmail.co.uk/staff/richard/
a revision number is a good indicator of Debian
specific packages anyway.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
Ian Jackson wrote:
>Note that < means less-than-or-equal-to in this context.
Could dpkg also support using <= for this meaning please? (Or does it
already?) Having to write < to mean <= is far from optimal; I think
it's something we should aim to get away from at some
wever, I haven't tried to build Debian packages in that sort of
environment, so there may be gotchas I'm missing.
A tool which could adjust permissions and ownership of the contents of
a tar file shouldn't be hard to write; you'd still have to get the tar
file ba
me
>people are going to try that, I guess.
Actually I think it would be a good thing if we could support Debian
entirely over UMSDOS - being able to run Linux without having to mess
around repartitioning hard discs is going to make a lot of people a
lot more willing to try it.
--
Richard Ket
However:
[EMAIL PROTECTED]:richard$ ls -l | head -1
total 19792
Broken pipe
[EMAIL PROTECTED]:richard$
Bill Mitchell writes:
>
>PACKAGE: dpkg
>VERSION: 1.0.7
>
>Script started on Mon Dec 18 21:19:37 1995
>root:work# dpkg --info less*deb | head -1
> old debian package, version 0.939000.
>Broken p
e conditions in it that can fail to
>remove some of the guts of links -- these will prevent the directory
>from being removed until the directory has been cleaned up
>(e.g. mount it as an msdos file system, then use rm -rf).
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
run
>and they may need bash.
...and can I just mention the Curses extension to perl here?
I believe under ELF it would actually be dynamically loaded are
therefore not drag libncurses into perl unless you actually used it,
but it's so wonderful I think it deserves a mention l-)
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
yms'. The PATH environment variable
was invented for a good reason...
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
ly the system
administrator is likely to want to use it - ordinary users might well
want to compile up a kernel and modules, for example.
This has been reported as various bugs before...
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
Bruce Perens writes:
>I was talking about moving initrunlvl to /etc, not /var/log .
Oops.
>Regarding the location of the rc[0-6].d directories, slackware,
>redhat, caldera, etc. all put them in /etc/rc.d/rc[0-6].d . I don't
>have to change their locations, but it seems to make more sense for
>us
>>I can make symbolic links in /etc/rc.d that point back out to where
>>the directories are instead of moving the directories. I was of the
>>impression that real SysV worked the other way, but I can satisfy
>>everyone.
>
>I agree with Ian. Pleas don't do this. Adding alternative paths to
>the s
en thinking about using a named pipe so that
>it will work with a read-only root. You can't change run-levels if
>you can't write this file.
Isn't it just as likely that /var/log will be on a mounted filesystem?
(In fact /var is a separate filesystem on mine.)
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
d be good.
>That way we would just change the name of the symlink from
>not-released-1.0 to release-1.0, while the actual directory would be the
>same.
This seems to be one of the more important things.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
an/debian-stable -> /debian/.hidden/debian-tree2 # changed from tree1
> /debian/debian-0.93 -> /debian/.hidden/debian-tree1 # might be deleted
> /debian/debian-1.1 -> /debian/.hidden/debian-tree2
>
>And no re-mirroring need occur.
My comments about this remain as above. My suggestion provides the
required functionality without creating `hidden' directories.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
ight place for a stable version
without having to think about it. If people actually want to live on
the bleeding edge, it shouldn't actually be any effort to do so - just
hard to do by accident.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
ing through symlinks you'd have to
read a README which would also warn you about installing unreleased
software.
This idea went down quite well when discussed off-line last night -
what does anyone else think?
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
ersion which just
asks `do you want to install the development tools' and such
questions. But I think there may need to be a level between this and
the current dselect as well.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
A friends system recently installed with Debian just booted in 80x50
and set the font incorrectly, resulting in an unreadable screen.
(Only the top half of each character was displayed.)
This bug has been reported at least twice before, and apparently has
yet to be fixed.
The fix is to edit /etc/
Package: smail
Version: 3.1.29.1-13
There are no aliasinclude and forwardinclude directors in Debian's
smail. This stops one from doing mailing lists.
/usr/doc/smail-admin-guide/* provides examples.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
/usr/include/tcl/default.h
/usr/include/tcl/ks_names.h
tclX
/usr/include
/usr/include/tcl
/usr/include/tcl/tclExtend.h
/usr/include/tcl/tcl++.h
(tcl=7.3-4; tk=3.6-4; tclX=7.3b-5; all a.out versions)
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
Andrew Howell writes:
>Bill Mitchell writes:
>>Dx -- dunno. Didn't take note when I had it open. I grepped
>>/var/log/messages for a bogomips figure, but that's apparently
>>no longer part of the startup. As I recall under earlier kernels,
>>it was low -- perhaps 6.something. Better than the 3
If that happens it's a bug in adduser, which is what chooses the
uid/gid pair, not Majordomo.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
nly response was the suggestion that it could be allocated on the
fly, so I did that.
To my knowledge there's no strict requirement that Majordomo use the
same uid/gid on every machine.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
>'majordom' is UID 102
[...discussion deleted...]
I discussed this with Ian J. last night and there's a possibility it's
a bug (or at least an infelicity ;-) in dpkg.
Majordomo 1.93-2 will (a) get it right and (b) should fix any broken
installation of 1.93-1 that may be aroun
g owned by user 101 to be owned by majordomo.
Is there a group with gid 101 on your system?
What is the gid of the majordom group on your system?
This needs some experimentation.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
Package: bind
Version: 4.9.3-BETA24-1
The postrm script doesn't remove the named.boot file when you run dpkg
--purge on the package.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
Steve Greenland writes:
>[/etc/profile suggestion]
>> if [ -f $HOME/$ARCH-linux ]; then
>> PATH=$HOME/$ARCH-linux:$PATH
>> else
>> mkdir $HOME/bin 2>/dev/null
>> PATH=$HOME/bin:$PATH
>> fi
>>
>
>I don't think /etc/profile should be creating directories in my home
>directory.
Ag
te this
program.)
(These are not the only ways of using the script; its precise
behaviour can be quite finely tuned both by the configuration file and
from the command line, if necessary.)
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
Ian Jackson has asked me to post this message to debian-devel;
apparently the UK academic network is having routing problems the
practical effect of which is that mail between *.ac.uk and other parts
of the world is not currently getting through.
This means no messages to debian-devel, among other
Bill Hogan writes:
>Packages: devel/source, base/modules
Versions?
>Problem: base/modules installs genksyms as `/usr/bin/genksyms',
> kernel Makefile[?] looks for `/sbin/genksyms'.
Wasn't this reported ages ago? I can't find anything in the bug
report logs, however.
genksyms ought to
her that's too expensive for
>him, in his situation. Don't make the decision for him and expect him
>to like it.
Agreed.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
>> * what if the user has processes running? Or a print
>> job queued? Or mail queued?
>
>Life is too short to worry about this.
Actually I should have written `kill any processes the user owns'
without opening that point to discussion since leaving them running
ha
possible to delete everything from the home
directory except a .forward file.
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
re I
upload it.
Thanks for taking the time to have a look at it!
--
Richard Kettlewell [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
79 matches
Mail list logo
