Linux-Setup Digest #269, Volume #20              Fri, 22 Dec 00 02:13:06 EST

Contents:
  Re: What I've learned in the last few days... ([EMAIL PROTECTED])
  Re: BackSpace Keycode trouble (Ron House)
  X server problems with Linux on IBM 300PL (Werner)
  root fs not mounted (Mark)
  Re: X server problems with Linux on IBM 300PL (moonie;))
  Re: Kernel Compile Issues ([EMAIL PROTECTED])
  Re: Resize NTFS without Administrator Privs to Install RedHat -- Please  Help (Mark 
Post)
  APC BackUPS and cable (Henry_Barta)
  Can't start gnome-session (Help) (Dean Salvadore)
  Re: root fs not mounted ([EMAIL PROTECTED])
  Re: root fs not mounted ([EMAIL PROTECTED])
  Login ("Zayin Krige")
  Re: Setting up diskless booting linux clients ("Dan White")
  Re: Kernel bug... or Hardware bug ? ... Help ("John Mazza")

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

From: [EMAIL PROTECTED]
Subject: Re: What I've learned in the last few days...
Date: Fri, 22 Dec 2000 00:20:54 GMT

In article <91gidh$cv7$[EMAIL PROTECTED]>,
  [EMAIL PROTECTED] wrote:
>
>
> > 6) SanDisk USB Imagemate (SDDR-31) compact flash memory reader setup
> is no
> > easy task if you rely on the existing documentation. I did
everything
> just
> > like the docs said, but it just didn't mount. The problem stemmed
from
> the
> > fact that USB storage devices are accessed through SCSI /dev's.  The
> system
> > will never see /dev/sda1 as a valid block device if the SCSI disk
> module is
> > failing to load. Actually if the drivers are in place the whole
> process of
> > putting the reader online is very painless, yet it took me three
days
> to
> > figure that out :)
> >
> > This is only the beginning of my oddessy(sic). I will try and post
> other
> > things I come across as I fing them.
> >
>
> I am also trying to get this working but can not seem to mount the
card.
> The reader seems to be fine and shows under /proc/scsi/scsi and
> /proc/bus/usb/devices (with usb-storage associated). My mount attempts
> get rejected with you must specifiy the filesystem type (auto doesn't
> work). So what is the file system type???

To answer my own question, it turns out that my problem was that i was
trying to mount /dev/sda when I should have been trying to mount
/dev/sda1. The file system type is now autodetected and seems to be
vfat!


Sent via Deja.com
http://www.deja.com/

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

From: Ron House <[EMAIL PROTECTED]>
Crossposted-To: comp.windows.x
Subject: Re: BackSpace Keycode trouble
Date: Fri, 22 Dec 2000 01:00:36 +0000

Thomas Dickey wrote:
> 
> In comp.os.linux.setup Ron House <[EMAIL PROTECTED]> wrote:
> > I have just upgraded my Linux system to RedHat 6.2, using their standard
> > upgrade program, but unfortunately since then, one key code (BackSpace)
> > doesn't work properly. (It did before.) I want the backspace key to
> > delete backwards, and the del key to delete forwards, but both keys are
> > deleting forwards.
> 
> see the app-defaults file for XTerm

A bit vague, but okay... Well, I notice that the new file has a line:

<Key>Delete:    string(0x1b) string("[3~")

but according to xev, no Delete codes are being sent by the X server.
Also, both the old and new file contain nothing about the BackSpace key,
so why is that now not working? Finally, xev, as I understand it, is a
free-standing program, not part of XTerm, so why is that program now
reporting that both Del and BackSpace return BackSpace codes?

-- 
Ron House     [EMAIL PROTECTED]
              http://www.sci.usq.edu.au/staff/house

A rose grows in the Earth's good soil.

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

From: Werner <[EMAIL PROTECTED]>
Subject: X server problems with Linux on IBM 300PL
Date: Fri, 22 Dec 2000 02:24:07 GMT

One of our leading NT admins at my company finally decided to give Linux a try. So he 
started to install Redhat 6.2 on IBM 300PL P2/350 with a S3 Trio built onto the MB.
Today he called me that he can't get the X server running. So I tried it but I was not 
able
to get it working either. 
It's important that I get it running since we have a lot of these PCs and since our NT 
admins
are finally willing to give it a try. Currently we have over 300 AIX servers, several 
Sharks 
and S80s, but unfortunatelly there is a tendency to use more and more NT. 
But if the introduction of Linux goes well, we might even consider to use Linux on 
Mainframes 
together with AIX (5L) servers.

So if anyone of you had any luck then please send me your email address and a copy of 
your
XF86Config file.

Thanks
Werner

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

From: Mark <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.misc,redhat.general,redhat.config
Subject: root fs not mounted
Date: Thu, 21 Dec 2000 21:50:20 -0600

Hey,

I am unable to boot up my redhat 6.2 machine after little use.  When I
try to boot it, I get the
following error message.

request_module [block_major_3]:  Root fs not mounted
VFS: Cannot open root device 03:06
kernel panic: VFS: unable to mount root fs on 03:06

In the short time that I have had the machine, I did not make any boot
or rescue disks. So I
learned that lesson pretty quick.  I even tried to install redhat 7 on
the machine, but the install
process failed on the same root fs problem.  I am new to linux and don't
even know where to
really began to try to resolve this problem.  Could the hard drive have
already died on me?
Any help would be great.

thanks,
mark


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

From: moonie;) <[EMAIL PROTECTED]>
Subject: Re: X server problems with Linux on IBM 300PL
Date: Fri, 22 Dec 2000 00:02:55 -0500

On Thu, 21 Dec 2000, Werner wrote:
>One of our leading NT admins at my company finally decided to give Linux a try. So he 
>started to install Redhat 6.2 on IBM 300PL P2/350 with a S3 Trio built onto the MB.
>Today he called me that he can't get the X server running. So I tried it but I was 
>not able
>to get it working either. 
>It's important that I get it running since we have a lot of these PCs and since our 
>NT admins
>are finally willing to give it a try. Currently we have over 300 AIX servers, several 
>Sharks 
>and S80s, but unfortunatelly there is a tendency to use more and more NT. 
>But if the introduction of Linux goes well, we might even consider to use Linux on 
>Mainframes 
>together with AIX (5L) servers.
>
>So if anyone of you had any luck then please send me your email address and a copy of 
>your
>XF86Config file.
>
>Thanks
>Werner

I can't help you with that problem other than to suggest the latest XFree86
server.  I will ask however, why do you want X on a server?
--
moonie ;)

Registered Linux User #175104
   (Registered at: http://counter.li.org)

KDE2
Kernel 2.4.0-test5
XFree86 4.0 Nvidia .94 drivers
RAID 0 Striped
Test-Pilots-R-Us ;)
ICQ #83003404
AIM mooniesdl3
MSN [EMAIL PROTECTED]




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

From: [EMAIL PROTECTED]
Subject: Re: Kernel Compile Issues
Date: Fri, 22 Dec 2000 05:03:59 GMT

Hope you did a 'make dep' before make zImage or bzImage.

In article <91t3dn$4ne$[EMAIL PROTECTED]>,
  [EMAIL PROTECTED] wrote:
> I'm trying to compile a 2.2.14 kernel on an ARM
> device, and am running into a problem.
>
> When I do 'make zImage', it goes a little and
> fails.  The last part of the log is:
>
> ------------------------------------------------
>
>         Considering target file `dummy'.
>         File `dummy' does not exist.
>         Finished prerequisites of target file
> `dummy'.
>         Must remake target `dummy'.
> *** 2.2 kernels no longer build correctly with
> old versions of binutils.
> Got a SIGCHLD; 2 unreaped children.
> Putting child 0x02070440 (dummy) PID 1692 on the
> chain.
> Live child 0x02070440 (dummy) PID 1692
> Reaping winning child 0x02070440 PID 1692
> *** Please upgrade your binutils to 2.9.5.
> Got a SIGCHLD; 2 unreaped children.
> Live child 0x02070440 (dummy) PID 1693
> Reaping winning child 0x02070440 PID 1693
> Live child 0x02070440 (dummy) PID 1694
> Got a SIGCHLD; 1 unreaped children.
> Reaping losing child 0x02070440 PID 1694
> make: *** [dummy] Error 1
> Removing child 0x02070440 PID 1694  from chain.
>
> ------------------------------------------------
>
> The biggest thing that stands out to me is the
> binutils 2.9.5 bit, but I'm running 2.9.5.0.31-3.
>
> Any help would be greatly appreciated, since this
> is driving me nuts!
>
> Thanks,
> Bill
>
> Sent via Deja.com
> http://www.deja.com/
>


Sent via Deja.com
http://www.deja.com/

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

From: [EMAIL PROTECTED] (Mark Post)
Crossposted-To: comp.os.linux.misc,linux.redhat.install
Subject: Re: Resize NTFS without Administrator Privs to Install RedHat -- Please  Help
Date: Fri, 22 Dec 2000 05:19:52 GMT

On Thu, 21 Dec 2000 17:57:54 +0100, David Vidal Rodriguez
<[EMAIL PROTECTED]> wrote:

-snip-
>From within Linux (supposing that that partition is
>mounted on /nt) you can rewrite the file without modifying any of the NTFS'
>structures (which is the really dangerous thing when writing) like this:
>dd if=/dev/myLinuxPartition of=/nt/bsect.lin bs=512 conv=notrunc count=1

And just what do you think this does, if not 'modify any of the NTFS
structures' ?
I've done exactly this, and got away with it a few times.  On the other
occasion, I had a minimally corrupted NTFS file system that needed to be
diskchecked when I rebooted NT, and I stopped doing it.

>If you don't like having rw access to NTFS, mount it readonly, but let ntfs.o
>with read/write support, and remount it rw only when you update the file. It is
>somehow tricky, but it works!
Not all the time, which is why the read-write support is listed as being
_very_ experimental.  If you want to do this, it would be just as easy, and
a lot safer, to write the 512-byte bootsector to a floppy, and then copy
that onto the c: drive after rebooting Windows NT.

Mark Post

Postmodern Consulting
Information Technology and Systems Management Consulting
To send me email, replace 'nospam' with 'home'.

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

From: Henry_Barta <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: APC BackUPS and cable
Date: 22 Dec 2000 05:20:19 GMT

    I've got one of those home made cables that use a couple of
    4.7K resistors to simulate one of the cables that APC sells
    for this unit. I had this working correctly (several Linux
    installs ago. Might have been Debian 1.? ;) on this system but
    the current version of 'apcupsd' that comes with Debian (3.2.6)
    has far more cable options than I can remember. It still includes
    a readme (README.cable) that describes this cable, but does
    not indicate (that I can figure out, anyhow) what cable type
    should be chosen in the apcupsd.conf file.  I've tried several
    types, but the daemon does not recognize when I pull the plug
    on the UPS. It'll still get me through the minor dips that are
    common, but I would like something that will shut down the
    computer during an extended outage.

    Any suggestions on the right cable type or how to better test
    this would be most welcomed.

    thanks,
    hank

-- 
Hank Barta                            White Oak Software Inc.
[EMAIL PROTECTED]                   Predictable Systems by Design.(tm)
                Beautiful Sunny Winfield, Illinois

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

From: Dean Salvadore <[EMAIL PROTECTED]>
Subject: Can't start gnome-session (Help)
Date: Fri, 22 Dec 2000 06:06:11 GMT

Hello,

I am running X116.4 bur cannot get gnome-session to run. It complains;
"undefined symbol: _IceTransNolisten
What does that mean? I assume it is a library thing but which one?

Thanks, Happy Holidays
-- 
"You don't have to wait for good things to happen...
"You are a good thing that is happening!"
Dean Salvadore
[EMAIL PROTECTED]

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

From: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.misc,redhat.general,redhat.config
Subject: Re: root fs not mounted
Date: Fri, 22 Dec 2000 06:19:03 GMT

Hi,
I'm also having the same problem with a slackware.2.0.35 that I built
yesterday. Can someone please throw some light on this problem.

Thanks in advance.

Cheers,
C.G.Senthilkumar.

In article <[EMAIL PROTECTED]>,
  Mark <[EMAIL PROTECTED]> wrote:
> Hey,
>
> I am unable to boot up my redhat 6.2 machine after little use.  When I
> try to boot it, I get the
> following error message.
>
> request_module [block_major_3]:  Root fs not mounted
> VFS: Cannot open root device 03:06
> kernel panic: VFS: unable to mount root fs on 03:06
>
> In the short time that I have had the machine, I did not make any boot
> or rescue disks. So I
> learned that lesson pretty quick.  I even tried to install redhat 7 on
> the machine, but the install
> process failed on the same root fs problem.  I am new to linux and
don't
> even know where to
> really began to try to resolve this problem.  Could the hard drive
have
> already died on me?
> Any help would be great.
>
> thanks,
> mark
>
>


Sent via Deja.com
http://www.deja.com/

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

From: [EMAIL PROTECTED]
Subject: Re: root fs not mounted
Date: Fri, 22 Dec 2000 06:24:01 GMT

hi,
I'm also facing the same problem with a slackeware2.0.35 kernek that I
compiled yesterday. Can someone please throw somw ligh on it.

Thanks,
C.G.Senthilkumar.

In article <[EMAIL PROTECTED]>,
  Mark <[EMAIL PROTECTED]> wrote:
> Hey,
>
> I am unable to boot up my redhat 6.2 machine after little use.  When I
> try to boot it, I get the
> following error message.
>
> request_module [block_major_3]:  Root fs not mounted
> VFS: Cannot open root device 03:06
> kernel panic: VFS: unable to mount root fs on 03:06
>
> In the short time that I have had the machine, I did not make any boot
> or rescue disks. So I
> learned that lesson pretty quick.  I even tried to install redhat 7 on
> the machine, but the install
> process failed on the same root fs problem.  I am new to linux and
don't
> even know where to
> really began to try to resolve this problem.  Could the hard drive
have
> already died on me?
> Any help would be great.
>
> thanks,
> mark
>
>


Sent via Deja.com
http://www.deja.com/

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

From: "Zayin Krige" <[EMAIL PROTECTED]>
Subject: Login
Date: Fri, 22 Dec 2000 08:40:33 +0200

is there anyway i van remove the login prompt from my tty's, but still
retain all networking functionality?


--
/*-------------------------------------------
Zayin Krige
[EMAIL PROTECTED]
www.redpoint.co.za
Redpoint Solutions (Pty) Ltd
Custom Software Solutions
==========================================*/



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

From: "Dan White" <[EMAIL PROTECTED]>
Subject: Re: Setting up diskless booting linux clients
Crossposted-To: comp.os.linux.questions,comp.os.linux.networking,comp.os.linux.help
Date: Fri, 22 Dec 2000 06:49:52 GMT

In article <[EMAIL PROTECTED]>, "John Von Essen"
<[EMAIL PROTECTED]> wrote:

> Now, other than what I said above, I dont know where to go next. If I
> try to boot the client, it grabs an IP, then hangs at the TFTP prompt. I

Unfortunately, PXE booting isn't as simple as it could be, but there is
a pxe package that can help you with it. See:

http://people.redhat.com/minter/tips/pxe-2md.html

- Dan White

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

From: "John Mazza" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Kernel bug... or Hardware bug ? ... Help
Date: Fri, 22 Dec 2000 06:52:16 GMT

I'd suspect hardware.

Check to make sure the processor fans are working correctly (you wouldn't
believe how many of those I've seen die!).

Next check your RAM by swapping it out one module at a time, and make sure
the memory and system speeds are matched (i.e. don't use PC-100 RAM in on a
133 MHz FSB).  You may also want to look at the memory timing parameters in
the BIOS and maybe slow things down a bit.

Also make sure that your SCSI cables (if you're using SCSI) are up to snuff.
I've had major issues with low-quality SCSI cables marked "Ultra-160" that
were crap and required me to slow my drives down to 40 MB/s to work
properly.  These problems went away when better cables were used.  It may
also be possible that something on the motherboard is bad.

I'd suspect bad RAM first once I made sure there was no overheating in the
machine.  Intermittant crashes can be a real bear to troubleshoot, so you'll
need some patience.  Otherwise, you could just swap out the entire
processor/RAM/motherboard assembly with new parts.  You can get a decent
motherboard, PIII 750 processor, and 256 MB of ECC RAM for under $1,000.  It
may be cost-effective if it prevents downtime (users unable to do their
jobs) and the costly technician time (an IT guy making $40k a year costs
about 30-50 bucks an hour when you include benefits) that troubleshooting
would entail.

Good luck finding and squashing your bug.



<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hello there ...
> Here is my situation ... i am responsable for a linux file server
> running samba and nfs ... the first machine acting as server was
> a pentium 200 Mhz 32MB Ram IDE drive with kernel 2.2.14 (rh6.2) and
> samba 2.0.7 6.. it run for several months without any trouble ( 45 days
> uptime)...
> then due to load problems i decided to move the harddrive to
> a new box ( Pentim III 500 Mhz 128 Ram and VIA motherboard ) ...
> and then started my problems ... with no aperent reason the system
> started to crash ( OS hangup ) once in to days or even once a day, and
> due
> to the so often craches and reboots i started having problems with the
> filesystem ... i tried to fix it by upgrading to ( kernel 2.2.18 and
> samba 2.07)
> but with no luck ... i still got the some problem ....
> here is my logs ...
> .....
> Dec 18 10:41:21 netserver kernel: Unable to handle kernel paging request
> at virtual address 00200000
> Dec 18 10:41:21 netserver kernel: current->tss.cr3 = 02e4d000, %cr3 =
> 02e4d000
> Dec 18 10:41:21 netserver kernel: *pde = 00000000
> Dec 18 10:41:21 netserver kernel: Oops: 0000
> Dec 18 10:41:21 netserver kernel: CPU:    0
>
> ----
>
> Dec 12 09:28:43 netserver kernel: Unable to handle kernel paging request
> at virtual address 00100008
> Dec 12 09:28:43 netserver kernel: current->tss.cr3 = 04caf000, %cr3 =
> 04caf000
> Dec 12 09:28:43 netserver kernel: *pde = 00000000
> Dec 12 09:28:43 netserver kernel: Oops: 0000
> Dec 12 09:28:43 netserver kernel: CPU:    0
> Dec 12 09:28:43 netserver kernel: EIP:
> 0010:[update_vm_cache_conditional+138/340]
> Dec 12 09:28:43 netserver kernel: EFLAGS: 00010206
> Dec 12 09:28:43 netserver kernel: eax: 00000000   ebx: 00100000   ecx:
> c5524cc0   edx: 00100000
> Dec 12 09:28:43 netserver kernel: esi: 00000000   edi: c7fc0000   ebp:
> 00001000   esp: c3689e9c
> Dec 12 09:28:43 netserver kernel: ds: 0018   es: 0018   ss: 0018
> Dec 12 09:28:43 netserver kernel: Process smbd (pid: 2561, process nr:
> 78, stackpage=c3689000)
> Dec 12 09:28:43 netserver kernel: Stack: 00001000 c1189000 00100000
> 0c5524cc c013db9a c5524cc0 00001000 c1189000
> Dec 12 09:28:43 netserver kernel:        00001000 0811b729 c03ba840
> ffffffea c5524d0c 0000ffc3 c1425140 c1425140
> Dec 12 09:28:43 netserver kernel:        c1425140 00000000 00000000
> c3689f08 00000000 00000000 c7e6aa00 00001000
> Dec 12 09:28:43 netserver kernel: Call Trace:
> [ext2_file_write+1066/1588] [free_wait+99/108] [do_select+509/532]
> [sys_write+219/256] [ext2_file_write+0/1588] [system_call+52/56]
> Dec 12 09:28:43 netserver kernel: Code: 39 4b 08 75 e1 8b 4c 24 20 39 4b
> 0c 75 d8 ff 43 14 b8 02 00
>
> ----
>
> Dec 12 14:55:06 netserver kernel: Unable to handle kernel paging request
> at virtual address 00100008
> Dec 12 14:55:06 netserver kernel: current->tss.cr3 = 01518000, %cr3 =
> 01518000
> Dec 12 14:55:06 netserver kernel: *pde = 00000000
> Dec 12 14:55:06 netserver kernel: Oops: 0000
> Dec 12 14:55:06 netserver kernel: CPU:    0
> Dec 12 14:55:06 netserver kernel: EIP:
> 0010:[update_vm_cache_conditional+138/340]
> Dec 12 14:55:06 netserver kernel: EFLAGS: 00010206
> Dec 12 14:55:06 netserver kernel: eax: 00000000   ebx: 00100000   ecx:
> c798a880   edx: 00100000
> Dec 12 14:55:06 netserver kernel: esi: 00000000   edi: c7fc0000   ebp:
> 00001000   esp: c2a37e9c
> Dec 12 14:55:06 netserver kernel: ds: 0018   es: 0018   ss: 0018
> Dec 12 14:55:06 netserver kernel: Process smbd (pid: 5384, process nr:
> 79, stackpage=c2a37000)
> Dec 12 14:55:06 netserver kernel: Stack: 01a45000 c5fcb000 00100000
> 0c798a88 c013db9a c798a880 01a45000 c5fcb000
> Dec 12 14:55:08 netserver kernel:        00001000 0811f729 c6518a40
> ffffffea c798a8cc 0000ffc3 c54a1d20 c54a1d20
> Dec 12 14:55:08 netserver kernel:        c54a1d20 01a40000 00000000
> c2a37f08 00000000 00000000 c7e6aa00 00005000
> Dec 12 14:55:08 netserver kernel: Call Trace:
> [ext2_file_write+1066/1588] [write_intr+259/292] [write_intr+0/292]
> [ide_intr+227/304] [write_intr+0/292] [handle_IRQ_event+54/108]
> [sys_write+219/256]
> Dec 12 14:55:08 netserver kernel:        [ext2_file_write+0/1588]
> [system_call+52/56]
> Dec 12 14:55:08 netserver kernel: Code: 39 4b 08 75 e1 8b 4c 24 20 39 4b
> 0c 75 d8 ff 43 14 b8 02 00
> Dec 12 14:56:05 netserver kernel: Unable to handle kernel paging request
> at virtual address 00100008
> Dec 12 14:56:05 netserver kernel: current->tss.cr3 = 01518000, %cr3 =
> 01518000
> Dec 12 14:56:05 netserver kernel: *pde = 00000000
> Dec 12 14:56:05 netserver kernel: Oops: 0000
> Dec 12 14:56:05 netserver kernel: CPU:    0
> Dec 12 14:56:05 netserver kernel: EIP:
> 0010:[update_vm_cache_conditional+138/340]
> Dec 12 14:56:05 netserver kernel: EFLAGS: 00010206
> Dec 12 14:56:05 netserver kernel: eax: 00000000   ebx: 00100000   ecx:
> c798a220   edx: 00100000
> Dec 12 14:56:05 netserver kernel: esi: 00000000   edi: c7fc0000   ebp:
> 00001000   esp: c2a37e9c
> Dec 12 14:56:05 netserver kernel: ds: 0018   es: 0018   ss: 0018
> Dec 12 14:56:05 netserver kernel: Process smbd (pid: 5395, process nr:
> 79, stackpage=c2a37000)
> Dec 12 14:56:05 netserver kernel: Stack: 01aab000 c1051000 00100000
> 0c798a22 c013db9a c798a220 01aab000 c1051000
> Dec 12 14:56:05 netserver kernel:        00001000 08125729 c393f780
> ffffffea c798a26c 0000ffc3 c1052060 c1052060
> Dec 12 14:56:05 netserver kernel:        c1052060 01aa0000 00000000
> c2a37f08 00000000 00000000 c7e6aa00 0000b000
> Dec 12 14:56:05 netserver kernel: Call Trace:
> [ext2_file_write+1066/1588] [free_wait+99/108] [do_select+509/532]
> [sys_recv+30/36] [sys_write+219/256] [ext2_file_write+0/1588]
> [system_call+52/56]
> Dec 12 14:56:05 netserver kernel: Code: 39 4b 08 75 e1 8b 4c 24 20 39 4b
> 0c 75 d8 ff 43 14 b8 02 00
>



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


** 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 PROTECTED]

You can send mail to the entire list by posting to comp.os.linux.setup.

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

End of Linux-Setup Digest
******************************

Reply via email to