Linux-Misc Digest #227, Volume #24 Fri, 21 Apr 00 18:13:06 EDT
Contents:
Re: Linux is Hard to Use: part 3 (Robie Basak)
Re: Problems with Login - Need help (Robie Basak)
Re: Two questions at startup: xtab and xfs (Robie Basak)
SOLVED (Gerald Pollack)
DBF Databases for Linux? (Matt Friedman)
Re: Bell Sympatico HSE (Matt Friedman)
Sharing modem in linux box for data/fax/dun with rest of LAN (Jeff Gerard)
Knews (=?iso-8859-1?Q?Beno=EEt?= Smith)
Re: Does anybody know a gzip-compressor in hardware ? (Jonathan Stowe)
Re: RPM problem (=?iso-8859-1?Q?Beno=EEt?= Smith)
PCMCIA modem: "Sorry, the modem is busy." (Rudd)
VFS messages spamming (Alastair Neil)
Re: Linux is Hard to Use: part 3 (Eric Y. Chang)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Robie Basak)
Subject: Re: Linux is Hard to Use: part 3
Reply-To: [EMAIL PROTECTED]
Date: 21 Apr 2000 21:10:19 GMT
On 21 Apr 2000 16:50:08 GMT, Eric Y. Chang said:
> Linux is Hard to Use: Part 3
>
>Linux new user (NU) installation usage profile.
>Expert comments are marked EX.
>
>
>NU: I have heard a lot about Linux recently. It just seems like the
>hottest thing around. I am going to install it on my machine. Can
>it coexist with Windows 98? I don't want to give that up until I am
>sure that Linux is working for me. What distribution should I use,
>and how should I prepare my machine?
>
>EX: You could try RedHat. Also, it is recommended that you purchase
>a new hard disk. It is very likely that you have one hard disk, and
>Windows is stored on one large partition taking up the whole disk,
>and you will have to repartition the disk. There is a utility called
>FIPS which you can use for this purpose, but it is risky. Are you
>willing to risk your Windows data for a couple hundred dollars?
>
>NU: No way! I can afford a new hard drive if it means that my
>Windows data will be safe.
>
>EX: OK, then, good luck!
>
>(several days later)
>
>NU: I've got a problem. Linux has destroyed Windows. I tried to
>install to the second hard disk and now the computer just generates
>010101010101010101010101010101010101010101010101010101010...
>forever when it tries to boot. Also, I cannot boot Windows.
Eh? Redhat doesn't destroy Windows, even 5.2 doesn't.
>EX: Oh yes, the old lilo
>010101010101010101010101010101010101010101010101010101010... bug.
>You did make a boot disk? Why did you want to go back to Windows
>anyway?
No such thing; if you want to critisize, try finding a real problem.
>NU: Yes, I do have a boot disk, but I need to use Windows and it
>is gone. Also, the reason that I need to use Windows is that Linux
>will not do everything I need it to.
>
>EX: Oh yes it will! What do you need? Games, office productivity
>tools, graphics software, etc., just surf the web, and you will
>find hundreds of applications for Linux.
>
>NU: I need the video chip number. Autoprobe failed, and the
>XFree86 configurator failed. I need a windowing system for some
>applications. Windows can find out what video chip I have, but
>Linux cannot. Do you have a www site for that?
BEFORE installing Linux, people should check out the compatibility.
Surely that is fairly obvious; when I installed it for the first
time (I was once a Microsoft sheep), I read through the Redhat
docs and did this.
>EX: No, I can't think of one off hand. If you cannot boot
>Windows, you could try opening the case and reading the chip
>number.
>
>(several days later)
>
>NU: I could not find the video card. I think that video is
>integrated into the motherboard. Why can Windows find it and
>Linux cannot?
>
>EX: That is caused by an old bug in Xconfigurator. It still
>has not been fixed, but it has been reported. One wild guess:
>Look for a chip with many pins that says SiS on the back, and
>record the 4 digits after the SiS. This should help.
>
>There is something that I should warn you about at this moment.
>You will be tempted to return to Windows soon. And, you will
>probably try to do something in a hurry, perhaps rashly. The
>typical new user at this point will try to reinstall either
>Windows or Linux, losing all kinds of data and configuration
>time. This is complained about a lot on the 'net. Do not
>rush back to windows. Fix the problems in your lilo
>configuration file, and Windows will probably boot again.
>Then, calm down, and take things slowly. You are asking for
>Windows back, and the quick answer is to do fdisk /mbr, but
>that is not what you really want. You want a dual boot
>Windows/Linux system with Windows on the first hard drive and
>Linux on the second.
>
>(several days later)
>
>NU: You were right. I paniced, and messed everything up. I
>tried fdisk /mbr, and it did not work. It probably is not
>supported anymore. Since it did not work, I tried to
>reinstall Linux in a more conservative way. I opted for a
>"Workstation" installation...
>
>EX: Oh no! You can't do that! If you do that, you will
>never be able to go back to Windows. The old "Workstation"
>installation mode is too dangerous and it is old. You must
>have an old CD-ROM.
>
>NU: But it says nothing about not being able to go back to
>Windows. I only found that out later when the Workstation
>mode wrote two ext2 partitions over my first hard disk. The
>manual does not say anything about this.
>
>EX: Well, it should, and you should know better. This is a
>typical new user profile.
>
>NU: It gets worse. I tried to re-install Windows. It did
>not work. There is a strange error. fdisk will not remove
>the first partition since there is a second one. And it will
>not remove the second one because there is a logical
>partition in it. And, it will not remove the logical
>partition, because it says that there is none.
Well, the Windows fdisk (if you mean the Windows fdisk) is
useless; even the old DOS one was better. Microsoft seems
to have dumbed it down to have a nice, friendly UI. Is it
so hard to boot of a Linux boot disk and run that fdisk?
>EX: This is a well known bug in Windows.
>
>NU: That information does not help me now! Why didn't it
>warn me before I tried installing?
>
>EX: A warning would not have helped. You were screwed from
>the very beginning, and the installation process toyed with
>your emotions until you had no choice but to mess up in
>exactly this way. The authors of the installation program
>should have forseen this and tailored the installation
>process to suggest a different path.
>
>NU: Well, that doesn't help either! How can I get Windows
>back?
>
>EX: You will have to get rid of those two partitions.
>Unfortunately, this is not easy. I checked linuxnewbie.org,
>www.redhat.com archives, FAQ, etc., and there was no info on
>it. Someone on the newsgroups said that this is an FAQ and
>you can check http://sunsite.auc.dk/linux-newbie/FAQ.htm.
>Unfortunately, that link is dead. But here is how to do it.
>Go to the store and buy a copy of Partition Magic...
Really? Ask here and many would answer.
>NU: I don't want to buy anything else! Will this be
>guaranteed to work, or will it be like the second hard disk
>that I bought that "guaranteed" that I would not lose any
>Windows data.
>
>EX: Calm down. You probably didn't lose anything important
>anyway. There is a way to do it with Linux fdisk. Just run
>fdisk from Linux and restore these partitions.
Exactly.
>(several days later)
>
>NU: I tried what you suggested, and it didn't work. fdisk
>will not work on a root partition that is currently being
>used by the running system. Also, I have to do this in those
>hard-to-read text consoles.
Use a proper boot disk; I always recommend www.toms.net/rb -
EX is giving bad advice. And you can always remount it read-only.
>EX: Oh yeah, that's right. I forgot. I never had to do this.
>You will have to go through the install all over again, and set
>the partition types of the first hard disk to DOS 16 FAT. Then,
>you should be able to reinstall Windows. Of course, you'll lose
>all your data, but you did back it up, didn't you?
>
>NU: How about the video? I tried your suggestion, and there
>was a chip that said SiS on it. The number did not quite match
>the one in the selection box, so I chose the nearest one, and it
>did not work. The screen came up, but at very low resolution.
>The font was huge and unusable.
>
>EX: Oh yes, the old low resolution bug! That is strange.
>Nobody wants low resolution, but you still seem to get it if
>something went wrong.
>
>NU: What went wrong?
>
>EX: I don't know. This is a well known problem. Lets check the
>XFree86 Installation HOWTO. Oops, nothing in here. How about the
>www.XFree86.org site. Oops, there's nothing in here either.
>Hmmmmm, this is strange, I seem to recall that this is a very
>common bug. How about www.redhat.com. Ahh yes, searching the
>archives finds a whold bunch of hits. Hey, wait a second! Most
>of these links are dead. Here we go, here is one that works.
>Yes, someone is reporting the problem once again, and there is
>someone named Manuel (presumably a support person) saying that you
>should bypass autoprobing and select 800x600 directly.
>
>NU: I already tried that. It didn't work.
>
>EX: Well, I guess that I am kind of out of ideas. Maybe I should
>post the query on comp.os.linux.misc. Somebody should have seen
>this problem before.
This problem with driver support has only come about recently (since
Windows 95, IMO). Before that, there were standards for everything.
Modems connected to the COM port if they were external, or emulated an
appropriate UART if internal. They all used the AT command set
(fortunately that has hung on).
Printers either used the Epson or HP command set. Graphics cards had
the VGA standard, and the VESA SVGA was going to be the next new
thing.
Sound cards were all Adlib/Creative SB/GUS compatible. All games
worked with appropriate VESA drivers; WP 5.1 had support for many,
many printers.
Then Windows 95 came along (and to a lesser extent 3.0/3.1/3.11),
allowing every hardware manufacturer to write their own command sets
and protocols and a software driver; so there was no competing for
standards, Microsoft just made the appropriate software standards.
3D cards were invented in this phase, so they never had a standard
command set (the software standards were Direct3D, and later OpenGL
thanks to Carmack).
Video cards no longer have to support VESA, just have Windows drivers.
The software modem was born. Now every piece of hardware has different
drivers. When complaining about Windows crashing all the time,
Microsoft blames it on incompetent/incompatible drivers.
Installing Windows is a right pain (and I have to do it often). I have
various different hardware (quite a well kitted-out PC). This adds up
to about 6 or 7 different driver disks; one for the mouse, one for the
printer, one for the TV card, one for the video card, one for the
modem(!), one for the sound card and one for the monitor(!). I've
probably missed one or two more.
This means that it takes longer to install and set up Windows, then
Linux (one disc for them all). I have had a computer on which Windows
produces a BSOD complaining about the IDE controller before the
install has even finished, because the motherboard driver(!) hasn't
been loaded yet. (Linux handles it fine, though).
Switching from Windows to Linux is difficult; now almost solely for
hardware compatibility problems. But the main reason for this is that
hardware manufacturers have been reluctant to release specs.
Now that they are starting to come round, quite often someone will
find problems and the answer is 'upgrade'.
If you were a Windows person, you wouldn't buy the hardware unless it
was compatible with Windows. Surely the same follows for Linux? You
can't really complain to Linux if it doesn't have support, complain to
your hardware manufacturers! If you have problems with your video card
in Windows, surely you complain to the manufacturer, not Microsoft! If
your hardware manufacturer is not interested, take your business
elsewhere!
Admittedly, though, people are stuck because of this; the only
solution is to:
1) Buy new hardware. This isn't so bad; it'll probably cost as much as
your next Windows upgrade, which you won't be doing anyway (see
later).
2) Wait. Use Windows, but when upgrading new hardware, make sure it's
compatible with Linux (even if you don't use it yet). When all your
hardware is compatible, switch.
I switched to Linux about a year ago; I know it well now. The last
three times I tried to use Windows, I managed to crash it within 10
minutes. The only reason I was using Windows was to export the last of
my data over (even the Word install program crashed!). I can tell you
that it is worth it, equivalents of everything you actually need are
available, and it's faster.
I use my computer a lot; it's often doing 3 or 4 things at the same
time. Finding that I have to reboot to do a 5th and having to do the
other 4 things all over again, or wait is something that I'd rather do
without.
And as for Windows 2000 not having to reboot/not crashing/being fast?
We all fell for that in Windows 95, Windows 98 (to a lesser extent),
Windows NT 3.51, Windows NT 4? Even if it is true, for the amount I'd
spend on a Windows 2000 server and IIS making it 1.5 times faster than
GNU/Linux/Apache (not that I believe it is), I could have 3 computers
running GNU/Linux/Apache on a DNS RR.
Plus, bugs get fixed faster. Plus, you can get help easily (not just a
'then don't DO that' answer). Plus, it's way, way, WAY more
configurable.
(rant mode off)
Robie.
--
------------------------------
From: [EMAIL PROTECTED] (Robie Basak)
Subject: Re: Problems with Login - Need help
Reply-To: [EMAIL PROTECTED]
Date: 21 Apr 2000 21:13:32 GMT
On Fri, 21 Apr 2000 16:30:14 GMT, Matthew Rudderham said:
>Hi,
>I just started running linux about a week ago, and love it.
>I am running Linux Mandrake 7.0 on a Pentium III - 450, 128mb RAM.
>I've run into a problem with my login though. When a user logs in the Bash
>shell which is default doesn't seem to beoperating properly. After the
>user logging in enters their password, the following line is displayed:
>/bin/bash: dircolors: command not found
>When the user tried for example to execute /bin/ls or another command the
>following is displayed:
>/bin/bash: dircolors: command not found
>/bin/bash: id: command not found
>/bin/bash: tty: command not found
>(Note running ls from an directory other than /bin will not do anything
>(bad command returned) so I assume paths are not being set).
>This only happens with accounts I've setup, and not the root account.
>Onlogin with root I do get one error:
>grep - command not found
Strange. Try typing 'alias' and see what comes up.
>I try executing grep after login completes, and it executed okay.
>
>On another note, I was wondering where the login scripts are stored for
>each user? Thanks for the help.
/etc/profile is executed first, then ~/.bash_profile, which also
sources ~/.bashrc. You can't set up an individual, uneditable login
script a la NT unless you do a switch statement in /etc/profile.
Robie.
--
------------------------------
From: [EMAIL PROTECTED] (Robie Basak)
Subject: Re: Two questions at startup: xtab and xfs
Reply-To: [EMAIL PROTECTED]
Date: 21 Apr 2000 21:17:44 GMT
On Wed, 19 Apr 2000 16:00:46 -0900, David Rabanus said:
>Hi folks,
>
>When I start up my Compaq Presario 1215 with RedHat 6.0 and kernel
>2.2.5-15 I always get this section of messages dealing with "xtab":
>
>[snip]
>
>What do they mean? Can I ignore them?
If you don't know what nfs is, you don't need it; type:
chkconfig --list
as root (I think it's in /usr/sbin) and check that anything
mentioning nfs is off for levels 3 and 5.
Switch one off typing:
chkconfig --level 35 name_here off
Sorry, I'm not sure about xfs (you don't want to switch it off, though).
Robie.
--
------------------------------
From: Gerald Pollack <[EMAIL PROTECTED]>
Subject: SOLVED
Date: Fri, 21 Apr 2000 21:26:36 GMT
Mandrake's automatic configuration apparently didn't set things up=20
correctly. I downloaded sndconfig from a redhat mirror, ran that, and=20
that fixed it. I think that the problem was a missing alias in=20
/etc/conf.modules:
alias sound-slot-0 es1370
(another possible component of the problem: apparently this card uses=20
es1370, not 1371).
------------------------------
From: Matt Friedman <"mwf"@total.net(remove-to-reply)>
Subject: DBF Databases for Linux?
Date: Fri, 21 Apr 2000 17:23:22 -0400
Are there any databases for Linux that use the DBF file format? Are
there any that have X GUIs, or that can have an X [or KDE] Gui
bolted-on?
I work over three platforms [Linux/Mac./Win], and I'd like to use my DBF
files on each.
MF
------------------------------
From: Matt Friedman <"mwf"@total.net(remove-to-reply)>
Subject: Re: Bell Sympatico HSE
Date: Fri, 21 Apr 2000 17:26:34 -0400
Robert J Carter wrote:
> You're right - I do have the grandfathered connection - except that I
> get 2.5 mbps. And it's beginning to sound like it's something I'm
> gonna want to hold on to :-)
Oh yeah... All you have to do is never move. :-)
MF
------------------------------
From: Jeff Gerard <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.setup
Subject: Sharing modem in linux box for data/fax/dun with rest of LAN
Date: Fri, 21 Apr 2000 21:30:02 GMT
Hi...I'm trying to do something that should theoretically work with what
I've tried thus far.
My setup is as follows:
RH6.2 on one box with 2 nics. 1 nic plugged into cable modem other
connected to 2nd PC which is a windows98 SE machine.
I have a working modem in the linux box that I would like to be able to
access using the windows box. I have tried a couple of programs but with
no luck (mdmpoold and NPComm which can be found easily on freshmeat.net
by searching for them)
The idea behind this setup is that mdmpoold runs on linux as a modem
server, redirecting traffic to the modem and the NPcomm program runs on
the windows machine creating a virtual com port that redirects modem
traffic to the modem server on the networked linux box running mdmpoold.
I have spent many hours playing around with this with no luck.
I have also trying playing around with my firewall rules to make sure
that traffic is not being rerouted to the external ip. I do have access
to internet from both machines via the cable modem so my firewall rules
appear to be working correctly.
If anybody knows of a different way to do what I am trying to do or knows
how to get this combination working, PLEASE let me know!!
Thanks in advance....
--
Jeff Gerard
[EMAIL PROTECTED]
**Remove NOSPAM to reply**
------------------------------
From: =?iso-8859-1?Q?Beno=EEt?= Smith <[EMAIL PROTECTED]>
Subject: Knews
Date: Fri, 21 Apr 2000 23:28:25 -0100
Greetings,
I have just installed Knews, and I am trying to launch it: the window
appears, but I only get the message "Connected to server; reading active
file..." (.newsrc-<myNewsServer> ?). And it never ends up with it !
Please could someone give me an explanation for this ? Thanks in advance
for any answer.
--
Beno�t Smith
Just A Rhyme Without A Reason
------------------------------
From: Jonathan Stowe <[EMAIL PROTECTED]>
Crossposted-To:
comp.sys.ibm.pc.hardware.chips,comp.compression,de.comp.os.unix.linux.hardware,comp.lang.perl.misc
Subject: Re: Does anybody know a gzip-compressor in hardware ?
Date: 21 Apr 2000 19:26:45 +0100
Reply-To: Jonathan Stowe <[EMAIL PROTECTED]>
In comp.lang.perl.misc J Alan Jackson <[EMAIL PROTECTED]> wrote:
> Andreas Vierengel wrote:
>>
>> Thanks again for the answers.
>>
>> I'm definetely stuck with gzip, since another compression algorithm is not
>> supported by the client program and we have no control over this programs :-(
>>
>
> A thought....
> GZip has a variety of compression levels.
>
I'm still unclear as to what this has to do with Perl - if a hardware
solution is what is required then a high level programming language is not
going to help. If you want to do compression with Perl then you can use
Compress::ZLib. Once the specification for your hardware is available I am
sure we would be delighted to have the public interface so someone can
create a module that can use it. Until that time it has nothing to do with
Perl.
/J\
--
No jokes, no taunting--That kid's got bosoms! Somebody get me a wet
towel! C'mere you butterball.
--
fortune oscar homer
------------------------------
From: =?iso-8859-1?Q?Beno=EEt?= Smith <[EMAIL PROTECTED]>
Subject: Re: RPM problem
Date: Fri, 21 Apr 2000 23:32:10 -0100
Dave Brown wrote:
>
> In article <[EMAIL PROTECTED]>, Beno�t Smith wrote:
> >I recently tried to install some RPM packages, but I only received the
> >irritating "failed dependancies" message followed by a list of
> >supposedly missing libraries. Then I was surprised by seeing that most
> >of the concerned libraries ARE present in my system (in the directories:
> >/lib, /usr/lib, /usr/X11R6/lib) !!!
> >Could someone give me an explanation for this ? I am using the Slackware
> >7.0. distro.
>
> RPM only knows what's in the rpm database, not what's really installed.
> Since Slackware 7.0 doesn't use rpm for initial installation, there is
> no database for rpm to reference. (Which makes me wonder what good
> using rpm does on a "non-rpm" system...)
>
> Using "rpm -i --nodeps" will cause the software to be dumped out of
> the package onto the system, but no guarantees that anything will
> work. Dependent components may be on the system, but not where the
> packaged software expects them. And components of the packaged
> software may be installed in places where the "non-rpm" system
> can't find them.
>
> I've usually used "rpm2tgz" to get the components into a tarball so that
> I can see what's going to be put where.
>
> --
> Dave Brown Austin, TX
Thanks for all answers - especially this above. It's really too bad, I
tried the "--nodeps": not only the app didn't work, but I couldn' remove
it, because it was "not installed" !!! Now I have only to look for
"rpm2tgz"...
--
Beno�t Smith
Just A Rhyme Without A Reason
------------------------------
From: Rudd <[EMAIL PROTECTED]>
Subject: PCMCIA modem: "Sorry, the modem is busy."
Date: Fri, 21 Apr 2000 15:42:09 -0600
I'm running CorelLinux 1.0 on a Toshiba 4015CDS with a 3COM/Noteworthy
56k modem. I have compiled a new 2.2.14 kernel, along with 2.2.14
pcmcia modules (and updated pcmcia card services from source), and
everything appears to be working correctly, except that I get a "Sorry,
the modem is busy" message when I try to dial up or query the modem from
within kppp (The KDE GUI dial up). As I have no idea how to check
things manually from the command line (the manpages for pppd are a
little more complex than I'm ready for at the moment), I'm at a loss for
troubleshooting. The 'lsmod' and 'cardctl ident & status' commands (as
well as the daemon/kernel logs) don't appear to show any problems.
'cardctl status' even indicates that the modem is "ready."
The mystery, for me, is that when I run my default 2.2.12-kernel, along
with the Corel 2.2.12 pcmcia modules (as I'm doing right now), the
process is problem free (even though the daemon log indicates mismatch
between the card services, which has been upgraded, and the
2.2.12-pcmcia-modules, which have not). This raises the question of
what Corel might have done to their default pcmcia modules, or if some
kind of change needs to be made to the modem query script (I don't even
know where to find such a beast)??? The new, 2.2.14 pcmcia modules are
from the Debain "potato" release.
I'll be happy to provide any additional info, if that might be helpful.
Thanks in advance for any ideas.
--
Rudd Gates \ [EMAIL PROTECTED] \ Shut up and ski.
=====================Geek Code V. 3.12=======================
G! d s+:++ a- C++ UL+ P L+ E- W+ N++ o-- K- w+ O-- M- V- PS+
PE- Y PGP- t+ 5- X R tv b DI++ D G e* h---- r+++ y++++
=============================================================
------------------------------
From: Alastair Neil <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: VFS messages spamming
Date: Fri, 21 Apr 2000 21:56:56 GMT
Hi,
I'm running RH 6.2 on a Sony PCG-F340 laptop. My kernel ring buffer
keeps getting filled with apparently harmless messages from VFS:
...
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
VFS: Disk change detected on device ide1(22,0)
...
The device in question is the CD-ROM drive. I only receive these
messages if there is no disc in the drive. If I have a CD-ROM in the
drive - even if it is not mounted - no problems.
Anyone have any ideas how to fix this?
--
Those who are mentally and emotionally healthy are those who have
learned when to say yes, when to say no and when to say whoopee. -- W.S.
Krabill
Alastair Neil
------------------------------
From: [EMAIL PROTECTED] (Eric Y. Chang)
Subject: Re: Linux is Hard to Use: part 3
Date: 21 Apr 2000 22:04:18 GMT
Reply-To: [EMAIL PROTECTED]
Robie Basak ([EMAIL PROTECTED]) wrote:
: On 21 Apr 2000 16:50:08 GMT, Eric Y. Chang said:
...
: >forever when it tries to boot. Also, I cannot boot Windows.
: Eh? Redhat doesn't destroy Windows, even 5.2 doesn't.
: >EX: Oh yes, the old lilo
: >010101010101010101010101010101010101010101010101010101010... bug.
: >You did make a boot disk? Why did you want to go back to Windows
: >anyway?
: No such thing; if you want to critisize, try finding a real problem.
Actually, I have never personally witnessed this during an install,
but I have seen the results so many times that I believe that there
is something wrong. Apparently, the new user installs LILO, and
forgets about lilo -u, saving the MBR, etc. Then, upon rebooting
the computer, all the 01010101010... comes out. The CD-ROM is
incapable of booting Windows. And an improperly prepared boot
floppy cannot boot Windows either. Once lilo on the MBR fails, you
will have to restore the MBR. The humorous thing is that this is
almost always discovered when Linux fails to recognize either the
video card or the network, sending the helpless user running back
to Windows. Again, I have little experience with this, since I
do not dual boot.
Eric
------------------------------
** 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 (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
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-Misc Digest
******************************
