Linux-Development-Sys Digest #335, Volume #6 Wed, 27 Jan 99 04:14:02 EST
Contents:
Re: How can I build a Linux system from scratch - NO distribution? (Stefan Monnier)
Re: Modest next goal for Linux (James Youngman)
Re: Why I'm dumping Linux, going back to Windblows (Leslie Mikesell)
Re: Why I'm dumping Linux, going back to Windblows ([EMAIL PROTECTED])
Re: Modest next goal for Linux (Peter Steiner)
Re: Need help with XFree (Gordon Weast)
Re: Updating device driver from 2.0 -> 2.2... what's changed? (David Bukowski)
Re: Can I run a DOS Device Driver in an emulator ("Frank T. Lofaro")
xosview and 2.2.0 (Andreas Heiss)
Interesting compiler errors . . . (Nathan Paul Simons)
2.0.36 header bug (Conrad Sanderson)
Find a good free book? ("Malsi")
Re: Interesting compiler errors . . . (Nathan Paul Simons)
Updating device driver from 2.0 -> 2.2... what's changed? (Amish Dave)
Kernel 2.2.0 RPC timed out errors (Darrell Tangman)
Need Help, using NCR53C9x in ISA (Eric Wick)
Re: Modest next goal for Linux (jedi)
Re: Modest next goal for Linux (jedi)
----------------------------------------------------------------------------
From: Stefan Monnier
<[EMAIL PROTECTED]>
Subject: Re: How can I build a Linux system from scratch - NO distribution?
Date: 26 Jan 1999 13:48:24 -0500
>>>>> "Richard" == Richard Jones <[EMAIL PROTECTED]> writes:
> I don't think so. Things would be pretty bad
> if every time there was a slight routing problem
> between two nameservers on the Internet, one
> of the nameservers started returning negative
> responses to requests. The problem is that
There are two issues here:
If you're thinking of a real DNS server (serving some actual zone), it's
probably indeed undesirable to return "non existant host" in case of a
(temporary) routing problem. But for timeout reasons, it's better to return
*something*, so the RFC should provide for a "can't tell you right now" reply
so that the requesting host can immediately switch to another DNS server.
I don't know if such a reply is provided in the RFCs. If not, it's a bug in
the RFC.
Now for a named daemon that just serves as a local DNS cache, the difference
between "can't tell you right now" and "(non-authoritative)non existant host"
is probably minor enough to be preferable to the current situation where
the user has to repeatedly wait for endless timeouts.
So I stand by my claim: it qualifies as a bug AFAIC.
Stefan
------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy
Subject: Re: Modest next goal for Linux
Date: 25 Jan 1999 23:20:13 +0000
[EMAIL PROTECTED] (Liang-Shing Ng) writes:
> Is it possible to achieve my modest requirement of "guanranteed limited
> time response" in X window? i.e. When my Netscape started swapping, I
> want my cursor can still be responsive and move on to other windows and
> do some things.
hdparm -u
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
------------------------------
From: [EMAIL PROTECTED] (Leslie Mikesell)
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: 26 Jan 1999 23:24:26 -0600
In article <[EMAIL PROTECTED]>,
jedi <[EMAIL PROTECTED]> wrote:
>>
>>The average *disk* sold these days is larger than 2GB, after all, and
>>ext2fs supports partition sizes of on the order of 2TB, so limiting file
>>size to 2GB seems a mite unreasonable.
>
> It's a mild annoyance on the high end of things but isn't
> quite to a critical point yet. It's certainly a lame excuse
> to not deploy a non-trivial database on Linux.
A few minutes of video...
Les Mikesell
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: 26 Jan 1999 15:52:10 -0800
In article <78l27c$1cnk$[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
>
>>This point have been for me something I just could never understand
>>about the Unix world.
>It has more to do with having the same person write the manual that
>wrote the program than unix vs. anything else.
>
I think it has to do with the mentality of the programmer and the
environemnt they work in. nothing else. I've written a number of
programs, and written man pages for them, and always put examples at
the end.
>>to give a manual page for a command, that might contain n number of options,
>>yet a typical command might only use m of them at a time, where m << n,
>>yet, for the user to determine the correct m for each particular case,
>>they must read about each option, and then try to determine the subset
>>of them they need to compose to build the command.
>
>Who is going to decide what is 'typical'?
>
for a complicated command with many options, use your common sense and
put some examples to illustrate typical usages. if the programmer can
not decide what is a typical use of a program they wrote, then they
should not be programming.
>>For example, look at cpio man page. If the author of cpio have given
>>few examples showing how to use cpio to backup a tree on a file system,
>>and then how to restore the result back, and an example of how to do the
>>same moving one or more files, and such examples, then life will be so
>>much easier.
>
>What about the person who only uses cpio in -p mode to mirror
>to other directories?
>
great, write this one down also.
it takes only ONE line to show an example. disk space is sheap.
it does not hurt to show examples.
>>Iam to this day, could never understand why would the authors of man pages
>>refuse to show examples.
>
>There are too many possibilities to show them all and the author of the
>program wouldn't want to omit any. Remember, he just spent weeks
>adding an obscure function and now you want him to leave it out
>of the documentation because for you it isn't 'typical' usage.
>
weak arguments.
you are basically saying, if I can't show every possible example of how
a command can be used, then I am not going to show any.
I am saying, showing few examples is better than nothing.
if you need examples of what I am talking about, find a VMS system
and type 'help' and see what I mean.
On VMS, each command has examples included. some have one or two
examples, some have more. These examples speed the learning process
and leaves one feeling better about the system helping them to use
its commands.
>New functions are added as the need arises and they are added into the
>list of options. Should the fact that you don't happen to need one
>of those options today mean that it shouldn't be given equal space
>in the manual?
>
same bougus argument.
as I said, one or two lines is all it takes to show some examples
and explain them. how much time does it take for the programmer
to do that? 5 minutes per example? or instead have the user
spend 2 hours reading the man page trying to figure which option
they should use to do some common task?
>>may I am wrong on this, but I would really be interested in hearing from
>>others who wrote man pages, why did they not put some effort in putting
>>examples.
>
>I have always thought that every complex product should have two
>completely separate manuals.
fine. but untill someone does this, we are talking about what we have today.
man pages are easy to get to, and quick to read. and people are used
to them. no need to redesign the world. simply add few examples at the end.
Certainly a programmer who just finished a program could come up with
few examples of how to use their program.
it is such a trivial thing for the expert on the program to add after they
finished, and takes little time, and would have greate value to new users,
why is this resistence for the Unix programmer is something I stil do not
get.
kna
------------------------------
From: [EMAIL PROTECTED] (Peter Steiner)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: Modest next goal for Linux
Date: 26 Jan 1999 13:43:08 +0100
In article <78jbh0$aoi$[EMAIL PROTECTED]>, John De Hoog wrote:
>But what is this slowness I notice whenever trying to get a long list of
>files to display on Linux?
It seems to be stat(2). I have a directory with over 16000 files. Here
is a short comparison on 2.2.0-final:
(All data is cached so no HD access is needed)
...> time ls -lf |wc
0.06user 0.06system 0:00.15elapsed 78%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (74major+484minor)pagefaults 0swaps
16708 16708 401042
...> time ls |wc
0.56user 0.06system 0:00.66elapsed 93%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (75major+827minor)pagefaults 0swaps
16706 16706 401037
...> time ls -l |wc
1.10user 40.82system 0:42.51elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (92major+832minor)pagefaults 0swaps
16707 150356 1319879
...> ls
takes about 40 sec before starting to print anything, because it needs
stat() to determine what color to use.
Without stat it takes 0.06 sec to load the directory and 0.56 sec to
sort the listing. With stat it takes 40 sec lo load the directory and 1
sec to sort and output it (due to the longer format).
Ciao,
Peter
--
_ x ___
/ \_/_\_ /,--' [EMAIL PROTECTED] (Peter Steiner)
\/>'~~~~//
\_____/ signature V0.2 alpha
------------------------------
From: Gordon Weast <[EMAIL PROTECTED]>
Subject: Re: Need help with XFree
Date: Tue, 26 Jan 1999 16:55:47 -0500
One possibility is that everything is programmed correctly and you
are just seeing the default screen size. Try Ctrl-Alt-+ (the keypad
+ with Ctrl and Alt). If there are several screen sizes programmed
in, then this will cycle through them. For some reason the
tools put the lowest resolution first.
If this doesn't work, you have to try to reconfigure.
Gordon Weast
JP wrote:
>
> Loren Osborn wrote:
>
> > JP wrote:
> > >
> > > I am trying to run XFree with my TNT AGP card. I set the Xconf for Riva
> > > 128 and 4MB. I run XFree, and it displays at 320x320. Argh! How do I get
> > > larger desktop sizes, ala 1024x768?
> > > I'm a newbie, so please make any advice simple to understand =)
> > >
> > > --
> > > JP
> >
> > I'm not familiar with your video card (it might not be supported) but
> > have you tried to run XF86Setup? (having your video-card/monitor/mouse
> > manuals --if any-- nearby is useful.) Hope that helps....
> >
> > Loren
>
> How? Seriously, is this a program in Linux? I am using RedHat 5.2.
>
> --
> JP
> [EMAIL PROTECTED]
> Nolite te bastardes carborundorum
> __________________________________
>
> The mind and the sword are one-
> if the mind is right, the sword is right.
> __________________________________
------------------------------
From: David Bukowski <[EMAIL PROTECTED]>
Subject: Re: Updating device driver from 2.0 -> 2.2... what's changed?
Date: Tue, 26 Jan 1999 23:34:38 -0600
I've also noticed that the ide-scsi boot command has been taken out also.
I sorta need this for the system here to run the cdr. and still use the
cdrom as an IDE.
+1 to list of differences
On Tue, 26 Jan 1999, Amish Dave wrote:
> I've written several drivers for internal use (data collection, etc.)
> We've been using 2.0.30, but 2.2.0 has some features we really want/need.
> I haven't been paying much attention to the 2.1 series, so I'm now
> somewhat surprised at the large number of (admittedly mostly cosmetic)
> changes required to device driver source code to get it to compile.
> Is there a document analagous to Documentation/Changes intended to help
> kernel programmers get up to speed with 2.2? I haven't found such a
> beast in the Documentation directory, the Kernel Hacker's Guide, or via
> dejanews...
>
> Here's what I've noticed so far (to maybe help seed such a document):
>
> -> struct file_operations has changed - there is a flush() element
> introduced between open and release. The prototypes of many of these
> functions has also changed.
>
> -> #include <uaccess.h> to get user-space memory access functions.
>
> -> poll() instead of select(), and poll_table instead of select_table.
>
> -> copy_to_user/copy_from_user replaces memcpy_tofs/memcpy_fromfs
>
> -> bios32.h is deprecated, as is pcibios_find_device. Instead, use
> pci_find_device, which appears to be more than just a name change.
>
> -> ioremap instead of vremap, iounmap instead of vfree.
>
> -> a = get_user(b) changes to get_user(a, b)
>
> -> the {device}_read() and {device}_write() functions (struct file_operations)
> have new prototypes - no more struct inode *, but new parameter loff_t *ppos.
> What is this new parameter? I'm pretty sure I don't need to worry about it,
> since I haven't found (at least a char) device driver that does much with it.
>
> That's my quick list so far. It seems that to keep a driver compilable in
> both 2.0 and 2.2, I'm going to have to utilize a bunch of:
>
> #if LINUX_VERSION_CODE >= 0x020100
> #else
> #endif
>
> --
> Amish S. Dave University of Illinois at Chicago University of Chicago
> [EMAIL PROTECTED] medical student graduate student
>
>
>
===============================================================================
David B. Bukowski N9KPD
[EMAIL PROTECTED]
http://www.megsinet.net/davebb/
Computer stats:
OS: Slackware Linux 3.6 (kernel 2.0.36)
Computer: NEC Pentium 120 RAM: 80 Meg
Webmaster of Hamfesters Amateur Radio Club homepage:
http://www.megsinet/davebb/hamfesters.html
===============================================================================
------------------------------
From: "Frank T. Lofaro" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development,comp.os.linux.hardware,comp.os.linux.misc
Subject: Re: Can I run a DOS Device Driver in an emulator
Date: 27 Jan 1999 05:58:51 GMT
In comp.os.linux.development.system Gerard van der Sel <[EMAIL PROTECTED]> wrote:
>"Norm Dresner" <[EMAIL PROTECTED]> writes:
>#
># I have a special video card that needs to be initialized by a DOS device
># driver. There's nothing else available (unless you count windoze). (For
># the curious, it's a Targa+ overlay card.)
>#
># Once the initialization is done, I could throw DOS away and run CP/M-86
># (only joking).
>#
># I might be able to boot DOS, initialize the board, and then boot Linux, but
># that stinks, especially if I have to modify the settings.
>#
># Is there any way that I can call (perhaps hack up a DOS-style
># load-device-driver-from-the-command-line program) the driver from a DOS
># emulator in Linux to do the job.
>#
># All suggestions, hints, and even sympathy, gratefully accepted.
>#
># Norm D.
>#
>See the Linux <-> Windows HOWTO.
>You can initialise any card in Dos/Windows and then use a batch file to
>start Linux.
>In short:
>Copy LoadLin.exe and the kernel "vmlinuz" to your DOS/Windows
>enviroment.
>Make a batch file with the following contents:
>loadlin.exe vmlinuz root=<linux boot>
>for my system it is:
>e:\linux\loadlin.exe e:\linux\vmlinuz root=/dev/hdb8
>(I am using Red Hat 5.2, kernel 2.0.37)
>--
>Met vriendelijke groet,
Please READ the post you are replying to.
He does NOT want to boot DOS or Windoze!
Except from an emulation session inside Linux, if needed.
I know it would be best if he got hardware docs...
------------------------------
From: Andreas Heiss <[EMAIL PROTECTED]>
Subject: xosview and 2.2.0
Date: 27 Jan 1999 01:55:16 GMT
Hi folks,
I just installed 2.2.0 final.
When running xosview, I see strange network traffic all time.
The 'netmeter' doesn't work at all. Real network traffic isn't displayed.
I guess, the reason are the changes in the /proc.
But how can I fix it ? /proc backward compatibilty is enabled in the
kernel config.
Andreas
--
------------------------------
From: [EMAIL PROTECTED] (Nathan Paul Simons)
Subject: Interesting compiler errors . . .
Date: 27 Jan 1999 07:27:26 GMT
Reply-To: [EMAIL PROTECTED]
Lately, I have been getting some interesting compiler errors.
I feel justified in posting this to this group because most of the
software I am using is very developmental, and I wanted to see if anyone
else has been experiencing similar situations. The situation is this:
linux-2.2.0-pre9
glib-2.0.7
egcs-1.1.1
brand spankin' new 16.8 GB IBM IDE HDD
128 MB of RAM.
I only mention the RAM and HDD because I *think* they *might* be
part (if not all) of the problem. So what exactly is the problem?
I believe I am losing bits somewhere in my system. Either on the
hard drive, in the RAM or somewhere in between I have been getting
consistent problems (mainly when compiling) of data lossage and
munging. Take for example this message from egcs when compiling
gnome-core-0.99.3.2:
/usr/include/gtk/gtklist.h:99: parse error before character 0345
When I go to check gtklist.h on line 99, it looks perfectly normal.
I go back to gnome-core and start make again and it gets past it
with no problems. Occasionally, there will actually be something wrong
where it says it is, but this is usually an obvious munge of the code
(some weird character that should obviously not be where it is).
I am using a high level of optimization along with pentium pro
optimizations (and the compiler and all tools are all also similarly
optimized). I just don't know what is going on here, whether the
hard drive is losing data, the RAM is dropping bits or the compiler is
barfing for no apparent reason. Anyone with similar experiences?
------------------------------
From: [EMAIL PROTECTED] (Conrad Sanderson)
Subject: 2.0.36 header bug
Date: 27 Jan 1999 07:09:19 GMT
Something for Alan Cox who wants to make 2.0.37 ...
While compiling CD Paranoia III, I came across this oddity:
/usr/include/linux/cdrom.h:339: redefinition of `struct ccs_modesel_head'
struct ccs_modesel_head is defined in scsi/scsi.h
with this note:
/*
* standard mode-select header prepended to all mode-select commands
*
* moved here from cdrom.h -- kraxel
*/
Any reason why ccs_modesel_head is still in cdrom.h ?
------------------------------
From: "Malsi" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.development.apps
Subject: Find a good free book?
Date: Wed, 27 Jan 1999 08:35:45 +0100
Hello,
I am trying to find a very good book (free) available on the Internet (like
Thinking Java, for Java) about Linux : install, configure, superUser,
Networking, etc... Thank you...
Hicham
------------------------------
From: [EMAIL PROTECTED] (Nathan Paul Simons)
Subject: Re: Interesting compiler errors . . .
Date: 27 Jan 1999 07:32:13 GMT
Reply-To: [EMAIL PROTECTED]
In article <78mf4u$fe7$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Nathan Paul Simons) writes:
> glib-2.0.7
Oops, that's glibc-2.0.7.
------------------------------
From: [EMAIL PROTECTED] (Amish Dave)
Subject: Updating device driver from 2.0 -> 2.2... what's changed?
Date: Tue, 26 Jan 1999 23:21:16 GMT
I've written several drivers for internal use (data collection, etc.)
We've been using 2.0.30, but 2.2.0 has some features we really want/need.
I haven't been paying much attention to the 2.1 series, so I'm now
somewhat surprised at the large number of (admittedly mostly cosmetic)
changes required to device driver source code to get it to compile.
Is there a document analagous to Documentation/Changes intended to help
kernel programmers get up to speed with 2.2? I haven't found such a
beast in the Documentation directory, the Kernel Hacker's Guide, or via
dejanews...
Here's what I've noticed so far (to maybe help seed such a document):
-> struct file_operations has changed - there is a flush() element
introduced between open and release. The prototypes of many of these
functions has also changed.
-> #include <uaccess.h> to get user-space memory access functions.
-> poll() instead of select(), and poll_table instead of select_table.
-> copy_to_user/copy_from_user replaces memcpy_tofs/memcpy_fromfs
-> bios32.h is deprecated, as is pcibios_find_device. Instead, use
pci_find_device, which appears to be more than just a name change.
-> ioremap instead of vremap, iounmap instead of vfree.
-> a = get_user(b) changes to get_user(a, b)
-> the {device}_read() and {device}_write() functions (struct file_operations)
have new prototypes - no more struct inode *, but new parameter loff_t *ppos.
What is this new parameter? I'm pretty sure I don't need to worry about it,
since I haven't found (at least a char) device driver that does much with it.
That's my quick list so far. It seems that to keep a driver compilable in
both 2.0 and 2.2, I'm going to have to utilize a bunch of:
#if LINUX_VERSION_CODE >= 0x020100
#else
#endif
--
Amish S. Dave University of Illinois at Chicago University of Chicago
[EMAIL PROTECTED] medical student graduate student
------------------------------
From: Darrell Tangman <[EMAIL PROTECTED]>
Subject: Kernel 2.2.0 RPC timed out errors
Date: 27 Jan 1999 08:30:29 GMT
Trying to access a Motorola System V/88 box (fairly old); attempts to
mount a file system exported by the Motorola box hang for a while, then
die with an "RPC timed out" message. If I telnet to the Motorola box,
I get the "Login:" prompt, but no response to input from the keyboard
and eventually the connection times out. If I try to rlogin to the
Motorola box, I get an immediate session hang followed eventually by
an error something like "rcmd: risky: address already in use". (The
wording of this last is only approximate.)
I have updated to net-tools 1.49 and I *think* I've got everything
else up to the levels specified in /usr/src/linux/Documentation/-
Changes. The same hardware running 2.0.35 accesses the Motorola box
without problems, and running 2.2.0 it accesses our other systems
(AIX, ISC, SCO, DG/UX, Linux, and whatever DEC called UNIX on the
Alpha) without problems.
Strangely enough, I can rlogin from the Motorola box to the 2.2.0 Linux
box, and I can run xterm on the Motorola box and display it on XFree86
running on the 2.2.0 Linux box, so basic networking between the two
machines seems to be reasonably solid.
Can anyone suggest a good place to start looking for what might be
causing this? (My preferred solution is to junk the Motorola boxes,
which are becoming difficult to maintain, but I think I've been
outvoted.)
--
Darrell Tangman -- [EMAIL PROTECTED] -- Augusta, Georgia, USA
------------------------------
From: [EMAIL PROTECTED] (Eric Wick)
Subject: Need Help, using NCR53C9x in ISA
Date: 27 Jan 1999 08:30:49 GMT
Hello,
this Driver is in the Kernelsource since 2.1.132 or before. It can be compiled
f�r MCA-Structures, Amiga-Controllers, PowerMacs and Sparc. Who tell me the
Trick, to use this existing Driver in an Isa-Environment?
That could be no big job, cause the NCR53C80 finds the Chip and reports
"SCSI-Bus busy". I think there must be a connection between the 53c9x Driver
and the Isa-Environment, like the 53c80 does it.
Hope someone can give me Tips, i and other People want to use the 486DX2 from
ICL cause the Onboard-Controller works very well and fast under Dos and
Win.
ByeBye
Eric Wick
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (jedi)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: Modest next goal for Linux
Date: Tue, 26 Jan 1999 16:14:46 -0800
On 26 Jan 1999 04:07:56 -0800, David Fox <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] (jedi) writes:
>
>> On Tue, 26 Jan 1999 10:40:16 +0900, John De Hoog <[EMAIL PROTECTED]> wrote:
>> >jedi <[EMAIL PROTECTED]> wrote
>> >>>
>> >>>You're lucky you could find a scanner that works under Linux. Mine is not
>> >supported,
>> >>
>> >> If he didn't buy the first, cheapest, parallel port scanner
>> >> he could find, that likely explains why he had so little
>> >> trouble. Hardware that gets little respect within the
>> >> community is always going to be problematic.
>> >
>> >Are you saying the Nikon LS-2000 film scanner gets little respect within the
>> >community? I'd like to know what community you are talking about.
>>
>> The community of SANE backend driver writers apparently,
>> if you're having any trouble running it under Linux.
>
>That is a new and fancy film scanner. I haven't gotten up the time or
>the guts to actually obtain the device. I got technical specs from
>Nikon, but they don't seem to be LS-2000 specific. Are you sure it
>can't be driven with the LS-1000 drivers?
I don't know really. I presumed that that person that
was complaining about it's poor support options actually
had bad luck with the thing and at least gave situation
some non-trivial effort.
Although, I would tend to not expect more expensive hardware
to be well supported due to diminishing demand.
--
Herding Humans ~ Herding Cats
Neither will do a thing unless they really want to, or |||
is coerced to the point where it will scratch your eyes out / | \
as soon as your grip slips.
In search of sane PPP docs? Try http://penguin.lvcm.com
------------------------------
From: [EMAIL PROTECTED] (jedi)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: Modest next goal for Linux
Date: Tue, 26 Jan 1999 16:11:40 -0800
On Tue, 26 Jan 1999 07:18:00 GMT, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>In article <78jbh0$aoi$[EMAIL PROTECTED]>, "John De Hoog" <[EMAIL PROTECTED]> wrote:
>>But what is this slowness I notice whenever trying to get a long list of
>>files to display on Linux?
>
>Are you using colour ls? If so, things display much faster without colour, as
>it doesn't have to futz around determining what colour each file should be.
I use color ls without any noticable slowdown.
>
>Also, doing a directory listing on a FAT volume is pretty slow I've noticed. I
>try to avoid it when possible. :)
I also avoid FAT whenever possible. '-)
--
Herding Humans ~ Herding Cats
Neither will do a thing unless they really want to, or |||
is coerced to the point where it will scratch your eyes out / | \
as soon as your grip slips.
In search of sane PPP docs? Try http://penguin.lvcm.com
------------------------------
** 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.development.system) 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-Development-System Digest
******************************
