Subject: Linux-Admin Digest #38
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Thu, 8 Sep 94 13:14:20 EDT

Linux-Admin Digest #38, Volume #2                 Thu, 8 Sep 94 13:14:20 EDT

Contents:
  Re: CU sudo version 1.3.1 released (Scott Denham)
  Re: XFree86 NOTEBOOK-LCD Xconfig Problem (Sebastian W. Bunka)
  Re: Which is better: tar->gzip or gzip->tar? (Kai Petzke)
  Re: CU sudo version 1.3.1 released (Jeff Wang)
  Minicom question (Brian Curti Harvell)
  Re: [Q] Substitute for 'mail' (Kai Petzke)
  Re: LINUX on a PowerPC??? (Kai Petzke)
  Re: INGRES on Linux: help... (Kai Petzke)
  Re: [ALERT] Password problem with Linux// (Alec Muffett)
  Re: NFS fs read-only when mounted read-write (Ben Pressnall)
  Re: Help! Cannot boot from anywhere!! (Nicola Pedrozzi)
  Re: Kernel panic: VFS: Unable to mount root fs (Soenke Voss)
  XFree86 NOTEBOOK-LCD Xconfig Problem (NISCHELWITZER Alexander Kurt)
  Help! Cannot boot from anywhere!! (Steve Kneizys)
  Re: NFS fs read-only when mounted read-write (Ben Pressnall)
  Re: Setting up term for everyone on system. (David Kastrup)
  Re: XFree86 NOTEBOOK-LCD Xconfig Problem (NISCHELWITZER Alexander Kurt)

----------------------------------------------------------------------------

From: [email-masked] (Scott Denham)
Crossposted-To: comp.unix.admin,comp.unix.aix,comp.sys.convex,comp.sys.hp.hpux,comp.sgi.admin,comp.sys.next.sysadmin,comp.unix.osf.osf1,comp.sys.sun.admin,comp.unix.ultrix
Subject: Re: CU sudo version 1.3.1 released
Date: 7 Sep 1994 19:50:48 GMT

Todd C Miller ([email-masked]) wrote:
: Version 1.3.1 of the CU version of sudo has been released.  Sudo is a
: program that allows a system administrator to give limited root
: access to users and logs copiously.  Version 1.3.1 is based on The Root
: Group's sudo 1.1 and is covered under the GNU Copyleft.

: The differences between 1.3 and 1.3.1 consist mostly of bug fixes,
: minor featur additions, portability changes, and code reorganization.
: See the CHANGES file for all the gory details.

:   Todd C. Miller    Sysadmin--University of Colorado    [email-masked]

I've been trying to install sudo.v1.3 under AIX 3.2.5, and come up with the
externals: 

__crypt
__encrypt
__setkey

unresolved from the link. These appear to be lower level routines called
out of the crypt entry in /lib/libc.a/shr.o

None of the guru's around here seem to have an answer beyond vague mutterings
that it has something to do with the non-exportability of des encryption...
Is this right? If so I'm surprised it wasn't mentioned in the install docs
and wonder if instead there's just another library someplace that needs to
be pulled in to resolve these...

Since Todd's off on a "much needed vacation" until later this month and
I'm kinda pressed for time pending a "much unneeded business trip", I
hoped somebody might know the answer to this one...

   Scott S. Denham  
   Programming Supervisor
   Western Geophysical
   713.963.2628
   [email-masked]

------------------------------

From: [email-masked] (Sebastian W. Bunka)
Subject: Re: XFree86 NOTEBOOK-LCD Xconfig Problem
Date: 8 Sep 1994 13:10:12 GMT
Reply-To: [email-masked]

NISCHELWITZER Alexander Kurt ([email-masked]) wrote:

: Hello,

: I have problems with the installation of
: XFree86. My Xconfig file doens't work
: drivers are there, and I also
: don't know which monitor I should select for
: my Dual Scan LCD Display (640x480x256), and
: which clock rate does a LCD Display have?

: Which of the Monitor Types in the ConfigX86
: is for LCD Panels, and exists there a
: Xconfig.sample for notebooks?
: My hardware is:
:       i485DX2 notebook
:       LCD DualScan[ Display CCFT 9.5inch
:       Vesa Local Bus System
:       Cirrus Logic Graphic Card CL-GD 6440
:               internal 640x480x256
:               external 1280x1024x16
:               1MB
I don't have the solution for YOUR card, but propably you'd like to try
the Xconfig from our Notebook - an Olivetti Philos 33 with (standard?)
vga (it's something like a WD90??? chip inside). I'm running only the
XF86-VGA16 server ! and it works only with 640x480x16.
==============Oli33 Xconfig========================
#
# some nice paths, to avoid conflicts with other X-servers
#
RGBPath         "/usr/X386/lib/X11/rgb"
#
FontPath        "/usr/X386/lib/X11/fonts/misc/"
# NoTrapSignals
# Xqueue
Keyboard
  AutoRepeat 500 5
  ServerNumLock
ps/2            "/dev/mouse"
#
# The 16-colour VGA driver
#
VGA16
  Virtual       640 480
  Viewport      0 0 
  Modes         "640x480" 
  Chipset       "generic"
  Clocks 28.322 36
# **********************************************************************
# Database of video modes
# **********************************************************************
ModeDB
#
# name        clock   horizontal timing     vertical timing      flags
"640x480"     28.322  640  680  720  864    480  488  491  521
"800x600"     36      800  840  912  1024   600  600  602  625
===================end of Xconfig=======================

: Thanks for your help,
You're wellcome

:               Nischi
Cheers, Sebastian
--

email:                   [ [email-masked] ]
voice:                   FAX:
+43-1-71155260           +43-1-7149110
Location: earth, europe, austria, vienna  Inst. of Bacteriology  Vet.Univ.

------------------------------

From: [email-masked] (Kai Petzke)
Subject: Re: Which is better: tar->gzip or gzip->tar?
Date: 8 Sep 94 13:15:33 GMT

[email-masked] (Delemar ) writes:

>       It's more critical than that: tar is a "block device" archiver, that
>means it use N blocks for each file archived with a block size of Nx512 bytes
>(default N=20). Suppose you have 100 small files of 512 bytes, each of them will
>require one 20x512 bytes long block, 1000kb for them all to be compare with
>100x512 = 50kb. 

This is wrong.  Tar writes blocks of 20 x 512 bytes (unless you override
it with options), but it does not pad files to 20 x 512 byte blocks.  It
pads files only to 512 byte blocks.  The maximum, that you loose on one
file in an tar archive thus is 511 byte and another 512 byte for the header
block.

However, the archive as a whole is padded to 20x512 byte blocks.  So the
uncompressed size of tar files is always a multiple of 10240 bytes.

Kai
-- 
Kai Petzke                      | How fast can computers get?
Technical University of Berlin  |
Berlin, Germany                 | Sol 9, of course, on Star Trek.
[email-masked]   |

------------------------------

From: [email-masked] (Jeff Wang)
Crossposted-To: comp.unix.admin,comp.unix.aix,comp.sys.hp.hpux
Subject: Re: CU sudo version 1.3.1 released
Date: 8 Sep 94 13:08:04 GMT
Reply-To: [email-masked]

[email-masked] (Ron Morley) writes:
 )> Scott Denham ([email-masked]) wrote:
( > : Todd C Miller ([email-masked]) wrote:
 )> : : Version 1.3.1 of the CU version of sudo has been released.  Sudo is a
( > : : program that allows a system administrator to give limited root
 )> : : access to users and logs copiously.  Version 1.3.1 is based on The Root
( > : : Group's sudo 1.1 and is covered under the GNU Copyleft.
 )> 
( > : : The differences between 1.3 and 1.3.1 consist mostly of bug fixes,
 )> : : minor featur additions, portability changes, and code reorganization.
( > : : See the CHANGES file for all the gory details.
 )> 
( > <stuff about aix compile problem deleted>
 )> Where is this source available at?  I just ran an archie search and
( > only found references to sudo v1.2.

ftp.cs.colorado.edu:
pub/sysadmin/utilities/cu-sudo.v1.3.1.tar.Z
pub/sysadmin/utilities/cu-sudo.v1.3.1pl1.tar.Z
pub/sysadmin/utilities/cu-sudo.v1.3.1pl2.tar.Z

The 'cu-sudo.v1.3.1pl2.tar.Z' appears to be the latest and greatest.

-- 
 #====}==) #===(==}  #====}==) #===(==}  {==)===# (=={====#  {==)===# (=={====#
>> Jeff Wang      [email-masked]  Geophysical/Geological Applications  <<
>> Chevron Petroleum Technology Company  Phone : (504) 592-6162               <<
>> 935 Gravier Street, Room 1006         Fax   : (504) 592-7106               <<
>> New Orleans, Louisiana 70112          Valeo,vales. Die dulci fruimini!! :) <<

------------------------------

From: [email-masked] (Brian Curti Harvell)
Subject: Minicom question
Date: 7 Sep 1994 16:01:37 -0400

Hi I have a quick question about minicom. I have Slackware 2.0 dist and when
trying to use minicom as non root it says that I don't have access to the 
config file. Now the man page says you can have a file minicom.users with
who is allowed to use it but I can't seem to get it right or not in the
right place. Could someone help me.
Brian

------------------------------

From: [email-masked] (Kai Petzke)
Subject: Re: [Q] Substitute for 'mail'
Date: 8 Sep 94 13:19:43 GMT

[email-masked] (Jonathan Bradshaw) writes:

>Yes, I know about deliver and procmail -- and am using procmail myself for
>the MDA from sendmail but I just installed INN and it uses 'mail' to send
>status messages. There must be something I can install that will make this
>work.

Several people have reported success by linking /bin/mail to elm.  If
elm is called from a pipe, not from a terminal, it pretty much behaves
like mail.

Kai
-- 
Kai Petzke                      | How fast can computers get?
Technical University of Berlin  |
Berlin, Germany                 | Sol 9, of course, on Star Trek.
[email-masked]   |

------------------------------

From: [email-masked] (Kai Petzke)
Subject: Re: LINUX on a PowerPC???
Date: 8 Sep 94 13:20:53 GMT

[email-masked] (Joe Rach) writes:

>  I heard that there was a beta port of Linux for the new Apple PowerPCs.
>Is there any truth to this? I thought GNU was boycotting Apple.

Linux is not GNU.  Any Linux developper is free to port the code to
Apple's computer.  It is only, that the FSF won't do it.

PowerPC is not Apple.  PowerPC is a chip desigened by a few major
companies, like IBM and Motorola.

There is indeed a project to port Linux to the Power PC.  Latest time I
heard about it, it was still very ALPHA.  See the PROJECTS FAQ, which
is posted to comp.os.linux.announce regularly.

Kai
-- 
Kai Petzke                      | How fast can computers get?
Technical University of Berlin  |
Berlin, Germany                 | Sol 9, of course, on Star Trek.
[email-masked]   |

------------------------------

From: [email-masked] (Kai Petzke)
Subject: Re: INGRES on Linux: help...
Date: 8 Sep 94 13:25:18 GMT

[email-masked] (Ti Co Nuong) writes:

>Hi everyone,
>  Could you please help me with this: I have used "lha" along with
>  the INGRES software version 04.94 downloaded from tsx-11.mit.edu.
>  I follow exactly the procedures; it creates all the subdir. as specified.
>  But inside some of the dir., there are nothing.  For example, inside ./bin
>  there are suppose some executable file such as createdb, copydb...

You have to make them yourself.  cd to the source/newconf directory, and
type make; make install.

Kai
-- 
Kai Petzke                      | How fast can computers get?
Technical University of Berlin  |
Berlin, Germany                 | Sol 9, of course, on Star Trek.
[email-masked]   |

------------------------------

From: [email-masked] (Alec Muffett)
Subject: Re: [ALERT] Password problem with Linux//
Date: 8 Sep 1994 13:41:59 GMT
Reply-To: [email-masked]

<sigh> - roll out std.answer #47revB  8-)

Go check out "Crack" and "CrackLib".

- the former is a retroactive password cracker, and the latter is a
library routine that can be wired into "passwd" type programs, so that
a user's attempts to select a new password may proactively screened for
safety.

                - alec
--
Alec Muffett
Sun Microsystems 
European Network Security Group
(speaking for himself, not his employers)

---- 8< ----
Host: cert.org
Last Updated Thu Sep  1 19:18:22 GB-Eire 1994

    Location: pub/tools
      DIRECTORY rwxrwxr-x    512       Jun 25 1992    crack
      DIRECTORY rwxrwxr-x    512       Jul 15 1993    cracklib
    Location: pub/tools/crack
      FILE      rw-rw-r--    61387     Jun 25 1992    crack_4.1-shar1
      FILE      rw-rw-r--    57857     Jun 25 1992    crack_4.1-shar2
      FILE      rw-rw-r--    40085     Jun 25 1992    crack_4.1-shar3
      FILE      rw-rw-r--    57056     Jun 25 1992    crack_4.1-shar4
      FILE      rw-rw-r--    33153     Jun 25 1992    crack_4.1-shar5
      FILE      rw-rw-r--    256000    Jun 25 1992    crack_4.1-tar
      FILE      rw-rw-r--    105219    Jun 25 1992    crack_4.1-tar.Z
    Location: pub/tools/cracklib
      FILE      rw-rw-r--    90112     Jul 15 1993    cracklib25_small.tar
      FILE      rw-rw-r--    34436     Jul 15 1993    cracklib25_small.tar.Z
---- 8< ----

------------------------------

From: [email-masked] (Ben Pressnall)
Subject: Re: NFS fs read-only when mounted read-write
Date: Wed, 7 Sep 1994 19:59:54 GMT

In article <[email-masked]> [email-masked] (Paul McRae) writes:
>From: [email-masked] (Paul McRae)
>Subject: NFS fs read-only when mounted read-write
>Date: 26 Aug 1994 02:15:43 GMT

>We have two Linux systems (1.1.18), one exports a directory (/nfs) as
>(rw).  The other mounts it in /etc/fstab as (rw).  However, on the 
>client system, files cannot be written to the remotely mounted 
>directory and there is an error message 'file system is read-only'.

>Can anyone help me with this?

>Please respond via e-mail.

>Thanks,

>--Paul

>-- 
>--------------------------------------------------------------------------
>  Paul McRae                      "Keep things as simple as possible,      
>  [email-masked]            but not simpler." -- Albert Einstein   
>  London, Ontario, CANADA                                                 

------------------------------

From: [email-masked] (Nicola Pedrozzi)
Subject: Re: Help! Cannot boot from anywhere!!
Date: Thu, 8 Sep 1994 11:32:12 GMT

In article <[email-masked]>, [email-masked] (Steve Kneizys) writes:
|> 
|> Hello!  Help!!!
|> 
|> I have Linuz running 1.0.8 just fine, slackware 1.2 install, fine and
|> dandy.  But I wanted to test the 1.1.45 Kernel, so I compiled and
|> ran into a snag on re-boot.  So I decided to reboot from SLACKWARE
|> 1.2 with the boot command:
|> 
|> mount root=/dev/hda1
|> 
|> and it seemed to go okay, it asked for the ROOT disk and read some,
|> the locked up after the 'root mounted' message.  This was with the
|> SCSINET boot image, which worked okay for the original install and
|> current hardware of IDE disk (330 Meg) and 3c579 NIC.  
|> 
|> I tried to boot with slackware 2.0 SCSINET and NET boot images, using
|> both the COLOR and TTY disks (I have 1.44 floppies) but it hangs at the
|> same place again.
|> 
|> Any ideas?
|> 
|> Thanks so very very much!  
|> 
|> Steve...
|> 
|> P.S.  Once I get in I have the old kernel to tell LILO to boot from
|> so I'll be fine :)

Hi Steve,
Did you try booting from the boot disk without saying 'mount ...' ?
Just hit enter at the first prompt in such a way to have the color disk 
as / (root) filesystem.

I hope this help
Ciao Nicky

------------------------------

From: [email-masked] (Soenke Voss)
Subject: Re: Kernel panic: VFS: Unable to mount root fs
Date: Thu, 8 Sep 1994 11:19:53 GMT

In article <[email-masked]>, [email-masked] (Ari Lampinen) writes:
> 
> I need to ask your help again in this embarrassing booting problem of mine.
> Here is a more detailed description of it.
> 
> -ari   ;-(
> 
> 
> 
> The Pentium machine has a 1 GB SCSI disk that was partitioned as:
> 1) MS-DOS (C disk)   123 MB                   /dev/sda1
> 2) MS_DOS (D disk)   150 MB                   /dev/sda5
> 3) Linux tmp         200 MB                   /dev/sda6
> 4) Linux root        500 MB                   /dev/sda7
> 5) Linux swap         30 MB                   /dev/sda8
> 
> 
> The original DOS partitioning (123/880) was done by the PC distributor.
> 
> The DOS D disk was never used and was obviously not properly configured
> from the view of DOS because it prevented installation of some DOS software.
> So I removed the logical drive D (DOS FDISK showed the EXT partition size
> was 880 MB and the D disk held 150 MB). After this little oparation
> the DOS problems disappeared but linux does not boot at all.
> 
> 
> The boot msg when booting with LILO: linux root=/dev/sda<n>, where n=3-8:
> 
> ....
> Partition check:
> sda: sda1 sda2 < >
> MINIX-fs: unable to read superblock
> EXT-fs: unable to read superblock
> XIA-fs: read super_block failed (inode.c 74)
> MSDOS bread failed
> Kernel panic: VFS: Unable to mount root fs on 08:0n   (n=3-8)
> 
> 
> The boot msg when booting with LILO: linux root=/dev/sda2
> 
> ....
> Partition check:
> sda: sda1 sda2 < >
> (MS-DOS FS Rel. 12 .......)
> (...)
> Kernel panic: ....
> 
> 
> The boot msg when booting with LILO: linux root=/dev/sda1
> 
> ...
> VFS: Mounted root (msdos filesystem) readonly
> (nothing happened after this)
> 
> 

I am afraid that what you have done is that you deleted your linux partitions.
DOS disk DOESN'T recognise any non-dos 'partition' inside a 'extended partition', which it itself calls 'extended DOS partition'.
Modifying logical drives inside a extended partition with DOS fdisk leads to the
deletion of all non-dos 'partitions' inside.
The only chance to recover applies only if you have a printout of linux fdisk of
the original partitioning, including start and end cylinders of all partitions.
The you can repartition the drive from a linux boot floppy with linux fdisk by using exactly the same values.
Otherwise I am afraid your data are lost. I would be sorry for that.

Regards,
  Soenke

===========================================================================
Soenke Voss                                            Faculty of Economics
UNIX system administrator                    Department of Computer Science
                                                    University of Bielefeld
                                                          P.O. Box 10 01 31
                                                            33501 Bielefeld
[email-masked]                                      Germany
===========================================================================

------------------------------

From: [email-masked] (NISCHELWITZER Alexander Kurt)
Subject: XFree86 NOTEBOOK-LCD Xconfig Problem
Date: 8 Sep 1994 11:37:42 GMT

Hello,

I have problems with the installation of
XFree86. My Xconfig file doens't work
correct with my hardware and I didn't
found anything in XFree86-HOWTO which 
could solve this problem.

I have no CL6440 (SVGA-file) in the
ConfigX86 program only lower CL (CIRRUS LOGIC)
drivers are there, and I also
don't know which monitor I should select for
my Dual Scan LCD Display (640x480x256), and
which clock rate does a LCD Display have?

Which of the Monitor Types in the ConfigX86
is for LCD Panels, and exists there a
Xconfig.sample for notebooks?

I have tested a lot of different controllers
and displays (with different colcks etc.)
but my linux system (1.0.9) always turned the display
black and didn't responde - so I had to reboot 
several times or I got execution errors from startx.

My hardware is:
        i485DX2 notebook
        LCD DualScan[ Display CCFT 9.5inch
        Vesa Local Bus System
        Cirrus Logic Graphic Card CL-GD 6440
                internal 640x480x256
                external 1280x1024x16
                1MB

Thanks for your help,

                Nischi

------------------------------

Subject: Help! Cannot boot from anywhere!!
From: [email-masked] (Steve Kneizys)
Date: 7 Sep 94 23:33:59 EST

Hello!  Help!!!

I have Linuz running 1.0.8 just fine, slackware 1.2 install, fine and
dandy.  But I wanted to test the 1.1.45 Kernel, so I compiled and
ran into a snag on re-boot.  So I decided to reboot from SLACKWARE
1.2 with the boot command:

mount root=/dev/hda1

and it seemed to go okay, it asked for the ROOT disk and read some,
the locked up after the 'root mounted' message.  This was with the
SCSINET boot image, which worked okay for the original install and
current hardware of IDE disk (330 Meg) and 3c579 NIC.  

I tried to boot with slackware 2.0 SCSINET and NET boot images, using
both the COLOR and TTY disks (I have 1.44 floppies) but it hangs at the
same place again.

Any ideas?

Thanks so very very much!  

Steve...

P.S.  Once I get in I have the old kernel to tell LILO to boot from
so I'll be fine :)

------------------------------

From: [email-masked] (Ben Pressnall)
Subject: Re: NFS fs read-only when mounted read-write
Date: Wed, 7 Sep 1994 20:23:11 GMT

In article <[email-masked]> [email-masked] (Paul McRae) writes:
>From: [email-masked] (Paul McRae)
>Subject: NFS fs read-only when mounted read-write
>Date: 26 Aug 1994 02:15:43 GMT

>We have two Linux systems (1.1.18), one exports a directory (/nfs) as
>(rw).  The other mounts it in /etc/fstab as (rw).  However, on the 
>client system, files cannot be written to the remotely mounted 
>directory and there is an error message 'file system is read-only'.

>Can anyone help me with this?

>Please respond via e-mail.

>Thanks,

>--Paul

>-- 
>--------------------------------------------------------------------------
>  Paul McRae                      "Keep things as simple as possible,      
>  [email-masked]            but not simpler." -- Albert Einstein   
>  London, Ontario, CANADA                                                 

You will have ot change the permissions for the files or directory you are 
accessing via NFS by using chmod.

          usr               group          world
         r  w  x            r  w  x          r  w  x
         |   |   |             |   |   |           |   |   |
         |   |   |             |   |   |           |   |   |
400--    |   |             |   |   |           |   |   |
200 -----    |             |   |   |           |   |   |
100---------              |   |   |           |   |   |
                                |   |   |           |   |   |
40-----------------------   |   |           |   |   |
20-------------------------     |           |   |   |
10-----------------------------            |   |   | 
                                                     |   |   |
4-----------------------------------------    |   |
2---------------------------------------------    |
1------------------------------------------------ 

hope this helps.

Ben

------------------------------

From: [email-masked] (David Kastrup)
Crossposted-To: comp.os.linux.help,comp.os.linux.misc
Subject: Re: Setting up term for everyone on system.
Date: 7 Sep 1994 20:28:44 GMT

[email-masked] (C.W. Southern) writes:

>I want to setup term on my Linux box so everyone on my system can
>use it.  Right now I have it setup for me only.  But I know that there
>is a way set it up so more then one user can share the socket to 
>connect to the remote machine.  Maybe run term as root... something 
>like that?  Can anyone help.

One rather cheap way is to to something like
tredir 2023 23
(you need not be root to do that)
Anyone wanting a remote login can then say
telnet your.machine 2023
-- 
 David Kastrup        [email-masked]          
 Tel: +49-241-72419 Fax: +49-241-79502
 Goethestr. 20, D-52064 Aachen

------------------------------

From: [email-masked] (NISCHELWITZER Alexander Kurt)
Subject: Re: XFree86 NOTEBOOK-LCD Xconfig Problem
Date: 8 Sep 1994 11:41:24 GMT

NISCHELWITZER Alexander Kurt ([email-masked]) wrote:

: Hello,

: I have problems with the installation of
: XFree86. My Xconfig file doens't work
: correct with my hardware and I didn't
: found anything in XFree86-HOWTO which 
: could solve this problem.

: I have no CL6440 (SVGA-file) in the
: ConfigX86 program only lower CL (CIRRUS LOGIC)
: drivers are there, and I also
: don't know which monitor I should select for
: my Dual Scan LCD Display (640x480x256), and
: which clock rate does a LCD Display have?

: Which of the Monitor Types in the ConfigX86
: is for LCD Panels, and exists there a
: Xconfig.sample for notebooks?

: I have tested a lot of different controllers
: and displays (with different colcks etc.)
: but my linux system (1.0.9) always turned the display
: black and didn't responde - so I had to reboot 
: several times or I got execution errors from startx.

: My hardware is:
:       i485DX2 notebook
:       LCD DualScan[ Display CCFT 9.5inch
:       Vesa Local Bus System
:       Cirrus Logic Graphic Card CL-GD 6440
:               internal 640x480x256
:               external 1280x1024x16
:               1MB

: Thanks for your help,

:               Nischi

------------------------------

** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [email-masked]

You can send mail to the entire list (and comp.os.linux.admin) via:

    Internet: [email-masked]

Linux may be obtained via one of these FTP sites:
    nic.funet.fi				pub/OS/Linux
    tsx-11.mit.edu				pub/linux
    sunsite.unc.edu				pub/Linux

End of Linux-Admin Digest
******************************