At 02:09 PM 18/05/97 -0500, Guy Maor wrote:
>This might be because the + entry is not at the end? (5634, 8734) I
>plan to release a new passwd package today which fixes this.
I'm pretty sure I tried putting +:: in both /etc/passwd and /etc/shadow
- still no success there I think.
--
Karl Ferg
> "Kevin" == Kevin Dalley <[EMAIL PROTECTED]> writes:
Kevin> "Karl M. Hegbloom" <[EMAIL PROTECTED]> writes:
>> Q: Is anyone using `autoconf`? I wonder if it's worth learning
>> to use, and what people use it for. (I've barely glanced over
>> the manuals for it, so far.)
Karl Ferguson <[EMAIL PROTECTED]> writes:
> At 02:09 PM 18/05/97 -0500, Guy Maor wrote:
> >This might be because the + entry is not at the end? (5634, 8734) I
> >plan to release a new passwd package today which fixes this.
>
> I'm pretty sure I tried putting +:: in both /etc/passwd and /etc/s
And dont forget debmake's debsums command to check the integrity of a
package build with debmake.
On Tue, 13 May 1997, Jim Pick wrote:
>
> > Hi,
> >
> > I was asking over Linux-ISP about doing cleanup after breakins and got
> > many "use tripwire" answers, and one which says that RPM has a veri
At 10:07 PM 18/05/97 -0500, Guy Maor wrote:
>But is the last line in the file?
Certainly is. I just saw someone post on a 'login' bug that they couldn't
log in as anyone except for root because of the passwd file being mode 600
- this isn't the case for me.
the daemon.log reports this:
May 19 1
Is there a web page or other document that explains what our strategy
for libc6 is? I'm not talking about random comments on the list, I
mean something nailed down that I can refer to...
In particular, I've got a few issues to work out.
1) libgdbm -- libc6 includes libdb, and therefore gd
-BEGIN PGP SIGNED MESSAGE-
Karl M. Hegbloom <[EMAIL PROTECTED]> writes:
> Since the output from cron jobs is mailed anyhow, as it should be, I
> think that all cron scripts should report in as they are run, and
> that this should be made a standard. Here's why.
If you've ever administer
> 2. I installed shadowing as it suggested - started installing packages
> merrily. I also installed and configured NIS - however, I cannot log in
> any in my personal account - though I can finger anyone without trouble. I
> deinstalled shadow by doing a shadowconfig off and that still didn't fi
On May 19, Mark W. Eichin wrote
> Is there a web page or other document that explains what our strategy
> for libc6 is? I'm not talking about random comments on the list, I
> mean something nailed down that I can refer to...
yes, we need that !
> 1) libgdbm -- libc6 includes libdb, and the
Nicolás Lichtmaier <[EMAIL PROTECTED]> writes:
> Be prepared to receive lots of messages saying things like "unix is for
> real men that can look manpages set their own prompts" and "we shouldn't
> make any decision about the system's look and feel, the sysadm should"...
> The kind of decisions
In article <[EMAIL PROTECTED]>,
Andy Mortimer <[EMAIL PROTECTED]> writes:
> There has just been a long list of bugs against packages using `bashisms'
> in their scripts, and I can certainly remember this issue coming up
> before. But I don't know about anyone else, but I certainly have no
I would imagine that the sensible approach would be to script only with
features found in both ash and bash. This would also make you ksh
safe if someone were to propigate the susV stupidity of installing ksh
as sh.
Costa
From: [EMAIL PROTECTED] (Mark Baker)
Subject: Re: list of bashisms
Andy Mortimer <[EMAIL PROTECTED]> writes:
> > There has just been a long list of bugs against packages using `bashisms'
> > in their scripts, and I can certainly remember this issue coming up
> > before. But I don't know about anyone else, but I certainly have no idea
> > what features are availabl
> IIRC libgdbm is no longer developed, because even the author saw that
> libdb was better, and that there was no reason for double work.
Nice theory; however, db can't read gdbm files, nor does it provide
the gnu-specific version of the interface... so the existing gdbm
will be needed provided
> If we want to be friendly to newbies, we can write an X configurator
> like RedHat; but I don't think that's what we want.
I've heard rumors of this, but not seen it -- how does it differ from
XF86Setup (not xf86config, which is probably what the debian
old-timers think of, but the new tk-based
I initialy reported this problem as a RFE for the kernel-package,
but Manoj (and I tend to agree) thinks it should be discussed here first.
My point was the kernel package should also install the .config file used
to build the kernel for further reference (as getting the exact config t
On 18 May 1997, John Goerzen wrote:
> > Be prepared to receive lots of messages saying things like "unix is for
> > real men that can look manpages set their own prompts" and "we shouldn't
> > make any decision about the system's look and feel, the sysadm should"...
> > The kind of decisions tha
> So I say: PS1="[\\u] \\h:\\w\\$ " =D
Too long. But better than nothing.
--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble?
e-mail to [EMAIL PROTECTED] .
On May 19, Christoph Lameter wrote
> > So I say: PS1="[\\u] \\h:\\w\\$ " =D
>
> Too long. But better than nothing.
PS="[EMAIL PROTECTED]:\\w\\$ " ?
2 charaters shorter... :-)
regards, andreas
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
On Mon, 12 May 1997, Lars Wirzenius wrote:
> At least the following have been pointed out as problems with
> the current (source) packaging scheme. I'm not commenting
> on what the proper solution to each problem is, and I wish
> no-one else would, either, just so that we could, for once,
> avoid
Karl M. Hegbloom:
> Since the output from cron jobs is mailed anyhow, as it should be, I
> think that all cron scripts should report in as they are run, and that
> this should be made a standard. Here's why.
I think what we need is a more intelligent run-parts, for use with the cron
jobs, that ex
Too long when displayed. Not too long when specified.
Wit the hostname and the current directory I already run into more than 80
characters at times.
On Mon, 19 May 1997, Andreas Jellinghaus wrote:
>On May 19, Christoph Lameter wrote
>> > So I say: PS1="[\\u] \\h:\\w\\$ " =D
>>
>> Too lon
Hi all!
Friday evening my HD crashed as full suprise for me. Fortunatly, My /home
was not on the broken disk, but in any case my computer rather unusable
until I get a replacement HD (And a backup device - I guess you don't
believe how useful it is until...).
However, I'm busy with my studies fo
Hi,
My 2 cents: I think I agree with Vincent Renardias ; the
kernel configuration file really belongs in /boot. However, I do not
feel comfortable taking unilateral decisions about something as
touchy as /boot (some people require thin root partitions).
Are there any objection
On Mon, 19 May 1997, Christoph Lameter wrote:
> > So I say: PS1="[\\u] \\h:\\w\\$ " =D
> Too long. But better than nothing.
It isn't too long...!
[nick] newton:~/src/deb/lftp-0.11.1$
[nick] newton:~/src/deb/lftp-0.11.1$
[nick] newton:~/src/deb/lftp-0.11.1$ ls
Or the other version:
[E
On May 19, Manoj Srivastava wrote
> My 2 cents: I think I agree with Vincent Renardias ; the
> kernel configuration file really belongs in /boot. However, I do not
> feel comfortable taking unilateral decisions about something as
> touchy as /boot (some people require thin root partitions)
26 matches
Mail list logo
