Re: man dpkg

1996-06-15 Thread Richard Lovison
On Sat, 15 Jun 1996, Mark Phillips wrote: > Is it true that there is not manual entry for dpkg or dselect?! In manpages 1.11-4 there is an entry for dpkg which may be of help. The installation manual for Debian included some info on dselect and if you have access to the web, Debian's homepage (h

Re: sysklogd problems

1996-06-13 Thread Richard Lovison
On Wed, 12 Jun 1996, Richard Lovison wrote: > I just discovered that my system logging utilities stopped functioning two > days ago after I did some upgrades. I attempted to reinstall sysklogd > 1.3-6 but received the following error message: > > warning: /etc/init.d/sysklog

sysklogd problems

1996-06-13 Thread Richard Lovison
I just discovered that my system logging utilities stopped functioning two days ago after I did some upgrades. I attempted to reinstall sysklogd 1.3-6 but received the following error message: warning: /etc/init.d/sysklogd doesn't exist during rc.d setup. Error processing sysklogd I don't reca

Re: printing .lj files

1996-06-08 Thread Richard Lovison
On Fri, 7 Jun 1996, Carlos Carvalho wrote: > Richard Lovison ([EMAIL PROTECTED]) wrote on 7 June 1996 18:35: > >Does anyone know how to prevent a blank page from being printed at the > >end of the print job when printing a .lj file created using dvilj? > >Couldn't f

printing .lj files

1996-06-07 Thread Richard Lovison
Does anyone know how to prevent a blank page from being printed at the end of the print job when printing a .lj file created using dvilj? Couldn't find anything in the lpr or dvilj manpage. Any help would be appreciated. Thanks in advance.---Richard

sysklogd upgrade

1996-06-06 Thread Richard Lovison
I recently upgraded from syslogd 1.3-2 to sysklogd 1.3-6 manually using dpkg. When I started dselect I was informed that syslogd and sysklogd were in conflict, the configuration files for syslogd were still on the system. I proceeded to purge syslogd but was informed I couldn't because it was a re

Re: modprobe messages about module net-pf: what are they?

1996-06-04 Thread Richard Lovison
On Tue, 4 Jun 1996, Yves Arrouye wrote: > Since 1.99, I get messages like: > > Jun 4 00:03:50 marin modprobe: Can't locate module net-pf-4 > Jun 4 00:03:52 marin modprobe: Can't locate module net-pf-5 > > in my daemon.log. Do you know what they mean? Net-pf-3 refers to the AX.25 network pr

Re: Debian 1.1 man & more

1996-06-04 Thread Richard Lovison
On Mon, 3 Jun 1996, Amos Shapira wrote: > I never went all the way about this, but I allways had the suspicion that > Slackware's "more" is actually "less" renamed. Could you check this? > (maybe try "more -V"?) > I dug up my old Slackware 2.0.1 distribution on cdrom and discovered that the /u

Re: Debian 1.1 man & more

1996-06-03 Thread Richard Lovison
On Sun, 2 Jun 1996, Austin Donnelly wrote: > Those systems maybe format the manpage to a temporary file, then > use more to view that file. Debian's man put the formatted output > through a pipe directly to the pager, for speed. > > Note that you can also do: > > $ export MANOPT='-Pless'

Appreciation! :)

1996-06-02 Thread Richard Lovison
. Hopefully in the near future I'll be able to contribute and give something back. --------- Richard Lovison [EMAIL PROTECTED] ***

Re: Debian 1.1 man & more

1996-06-02 Thread Richard Lovison
On Sat, 1 Jun 1996, Guy Maor wrote: > On Sat, 1 Jun 1996, Richard Lovison wrote: > > > While using man to read a manpage I am not able to scroll backwards a page > > by using "b" or "^B". > > more can't go backwards on unseekable files, like pi

Debian 1.1 man & more

1996-06-02 Thread Richard Lovison
While using man to read a manpage I am not able to scroll backwards a page by using "b" or "^B". Has anyone else experienced this? My current version of man is 2.3.10-11. If I just use "more" to read a text file, everything works fine. Richard

daemon.log

1996-06-01 Thread Richard Lovison
Hello all, I am new to this list as well as to the Debian distribution. I installed Debian 1.1 a couple of weeks ago and so far I'm very pleased with the system. :) I am receiving the following message in my /var/log/daemon.log whenever I use DIP to connect to my provider via SLIRP: modprobe: