"Susan G. Kleinmann":
> Wishing to see the colored version of dselect, I tried this from a
> color xterm:
>
> # export TERM=linux
> # dselect
"linux" is, of course, the wrong terminal type. For color xterm's, the
correct type is "xterm-color". (dselect doesn't seem to be using colors
in the main
Lars Wirzenius wrote:
> "someone else who is now trying to hide her identity wrote:":
> > Wishing to see the colored version of dselect, I tried this from a
> > color xterm:
> >
> > # export TERM=linux
> > # dselect
>
> "linux" is, of course, the wrong terminal type. For color xterm's, the
> corr
Uploaded to master.debian.org.
This is the author's own response to the mount/umount security issues, and so
should replace the previous 2.5k-1 release which incorporated unofficial
patches.
Bruce, would you like to respond to the recent inquiry about Debian's
vulnerability status with regard to
Package: netstd
Version: 2.06-1
A bug currently making the rounds on the bugtraq mailing list:
The resolver library appears to allow the environment variable
RESOLV_HOST_CONF to be used to specify a pathname for an alternate
host.conf. It also has the unfortunate behavior of printing the text
o
[snipped]
> Urgency: Low
^^^
Where a security fix is involved, shouldn't the urgency be a little bit
higher than "low"? (especially where the problem affects many systems.)
-BEGIN PGP SIGNED MESSAGE-
Date: 16 Aug 96 13:58 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Michael Meskes <[EMAIL PROTECTED]>
Source: metamail
Version: 2.7-6
Binary: metamail
Architecture: i386 source
Description:
metamail: An implementation of MIME.
Changes:
met
You (Rob Browning) wrote:
> Hmm, I often use newgrp when I'm about to do a set of actions where I
> want to make sure all the new files get a particular group. For
> example, say I'm building a package in my home directory and I want
> all the files created to be group src because I'm likely to mo
You (Michael Meskes) wrote:
> > M> 1) Should we change the login package to be shadow aware? Or should
> > shadow
> I talked to Guy (login maintainer) about this problem a while ago and treid
> to persuade him to use ths shadow login as standard (it works without the
> shadow file, too). But he pr
You (Richard Kaszeta) wrote:
> Quick question (which may show some of my ignorance of the current
> linux shadow stuff):
>
> Will inclusion of the 'shadow' package as default interfere with the
> use of NIS passwd/group entries? Our installation is fairly dependent
> on NIS.
NIS and shadow don't
-BEGIN PGP SIGNED MESSAGE-
Date: 19 Aug 96 09:34 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Michael Meskes <[EMAIL PROTECTED]>
Source: sudo
Version: 1.4.5-1
Binary: sudo
Architecture: i386 source
Description:
sudo: Provides limited super user privileges to specific
On Thu, 8 Aug 1996, Warwick HARVEY wrote:
>metafontThe TeX Metafont program
>dvilj, dvipsProvided by dviljk, dvipsk (? - iwj)
These came up due to a misunderstanding of the guidelines.
They are no longer needed and I will remove them when I update the TeX
related package
Michael Alan Dorman writes ("New source format and related issues..."):
...
> I've looked at the docs, I've examined hello and dpkg, and I'll be
> damned if I can find any information that would allow me to actually
> reproduce the files that were uploaded to master, and assuming that
> dpkg was in
Hi,
> I think it should be enough to check for the string `slip' in /proc/modules
> and the string `sl?:' in /proc/net/dev. Is this correct?
sl?: will only be in /proc/net/devif you have any serial line in xSLIBy mode
(alsattach or dip running). If there ius no serial/pty line in linemode,
there
Package: perl
Version: 5.003-2
This package contains some documents in a Perl-specific documentation
format called `pod'. These files are installed in /usr/lib/perl5, eg
/usr/lib/perl5/POSIX.pod oor /usr/lib/perl5/pod/perlop.pod.
They should be somewhere in /usr/doc, or (since they're distribute
> A quick workaround is to change envarok() in telnetd/state.c as
> appended. My guess is that only telnetd needs to be changed for now,
> as neither rlogin nor rsh (if I remember correctly) allow the client
> to pass in environment variables.
Is this environment variable sourced for SUID/SGID pr
>
> I'd like to contribute some packages, but I'd like to ask some
> questions first:
>
> 1. One of these packages is the replacement of `libX11.so'. Do I have to make
> whole alternative version of appropriate standard X package or is there some
> way to make small "one-file-replacement" packag
Many of the latex package's files contain these lines (these
particular copied from preload.dc in latex_2e-7.deb):
%% IMPORTANT NOTICE:
%% You are not allowed to distribute this file.
%% For distribution of the original source see
%% the copyright notice in the file preload.dtx .
I see nothing in
Latex_2e-7 keeps a set of preload files in both /etc and
/usr/lib/texmf/tex/latex/config, both identical filesets. One of
these should be eliminated.
--
Richard W Kaszeta Graduate Student/Sysadmin
[EMAIL PROTECTED] University of MN, ME Dept
http://www.
Package: man
Version: 2.3.10-13
I get this error when mandb is trying to process the xjewel.1x manpage:
[EMAIL PROTECTED] ~log>man xjewel
Reformatting xjewel(1), please wait...
input in flex scanner failed
[EMAIL PROTECTED] ~log>mandb -d
...
ult_src: File /usr/X11R6/man/man1/xjewel.1x
input in fl
You (Bernd Eckenfels) wrote:
> > A quick workaround is to change envarok() in telnetd/state.c as
> > appended. My guess is that only telnetd needs to be changed for now,
> > as neither rlogin nor rsh (if I remember correctly) allow the client
> > to pass in environment variables.
>
> Is this envi
20 matches
Mail list logo
