Linux-Misc Digest #796, Volume #19                Fri, 9 Apr 99 23:13:12 EDT

Contents:
  X-CD-Roast Problem (Steve)
  Re: utility for reading wtmp (Lew Pitcher)
  X session dies whenever I save a GIF in GIMP? (D. J. Birchall)
  Re: Why Linux still isn't my standard boot-up OS, or what are the Linux-equivalents 
for these Windoze programs? (Jeremy Crabtree)
  Re: Ghostscript - Do I need it if RH5.2 already prints (Jeremy Nickolet)
  Re: VMWARE -- why isn't it the rage topic of discussion? (Jerry Gardner)
  Re: Running as root? (Robert Heller)
  harddisk keep busy (digger)
  Re: free computer13 ("opus007")
  Re: Why Linux still isn't my standard boot-up OS, or what are the Linux-equivalents 
for these Windoze programs? (Mike Mckinney)
  Re: LS120 or ZIP ( both parallel port )? (Jeremy Nickolet)

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

From: Steve <[EMAIL PROTECTED]>
Subject: X-CD-Roast Problem
Date: Sat, 10 Apr 1999 00:37:08 +0000

Hi,

I' new to Linux, but things seem to be going OK so far. :-)

I have a question regarding X-CDRoast, which is as follows:

I can read a CD (both Data and Audio), and store the resulting image in
my HD.

However, after writing the CD (which takes some time, and the 'Record'
LED flashes, so I assume that something is being written to the disk) I
get an error message to the effect that 'Some error occured'. This
message is displayed only when the 'fixating disk' operation is
happening. The writing phase then stops, and I now have five extra
coasters.

Any help would be appreciated. There doen't seem to be any mention of
this problem in the readme and help files, but then this software seems
to be implemented with only SCSI drives in mind.

My System:

AMD K6-2 300MHz,
64MBytes Ram
2 times 5 GB hard drives (Primary master, Secondary master)
1 32X CD-ROM (secondary slave)
1 6X CD-ROM-RW (Phillips 3610) (primary slave)

SuSE 6.0 (and I downloaded the correct binary from the X-CDRoast site).

I have recompiled the kernel with SCSI emulation enabled etc, and like I
say, I can read and store CD images.

Any ideas? Or is this a genuine bug that I should report to the author?

Thanks in advance

Steve


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

From: Lew Pitcher <[EMAIL PROTECTED]>
Subject: Re: utility for reading wtmp
Date: Fri, 09 Apr 1999 22:19:03 -0400

Clinton Carr wrote:
> 
> Is there a utility that can list entries in the .../wtmp file? I wish to
> audit previous logins.
> 
> Thanks,

man last

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

From: [EMAIL PROTECTED] (D. J. Birchall)
Crossposted-To: comp.os.linux.x,comp.graphics.misc
Subject: X session dies whenever I save a GIF in GIMP?
Date: 9 Apr 1999 14:55:22 GMT
Reply-To: [EMAIL PROTECTED]

This one's a bit weird.

I've got Red Hat 5.2, XFree86 (3.3.3.1), Blackbox (0.50.4) and 
GIMP (1.0.1) on my laptop.  Everything has worked fine for
motnhs.

A few minutes ago, I had a bunch of applications going (Netscape,
GQview, numerous GNOME terminals, and GIMP with a bunch of files
open).  My X session died, and I found myself back at the XDM
prompt.  Not a big deal; it happens occasionally when I try to do
too many things at once...

So I logged back in, started GIMP up, opened a GIF, flipped it
to RGB, scaled it, flipped it back to indexed, went to save it,
and wham-o, there I am back at XDM.  Tried again - same deal.

The images *are* getting saved properly - but immediately 
thereafter, my X session is dying.

Anybody seen this before?  Know what'd cause it?  Know how to
fix it?  I'm guessing that there might be a config file or lock
file that GIMP's seeing that it doesn't want to see, or isn't
seeing that it wants to see...

-Dan

-- 
Daniel Birchall, VP - Technology, Digital Facilities Management.
[EMAIL PROTECTED] is no longer a real address for me,
since a bunch of illiterates spammed it! :)  My username is djb.
http://www.scream.org/maisha/ is the Unofficial Maisha Fan Site.

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

From: [EMAIL PROTECTED] (Jeremy Crabtree)
Crossposted-To: alt.os.linux,comp.os.linux.help,linux.redhat.misc
Subject: Re: Why Linux still isn't my standard boot-up OS, or what are the 
Linux-equivalents for these Windoze programs?
Date: 10 Apr 1999 00:23:39 GMT
Reply-To: [EMAIL PROTECTED]

[EMAIL PROTECTED] allegedly wrote:
>In article <[EMAIL PROTECTED]>,
>  Michael Powe <[EMAIL PROTECTED]> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>>     Linux> A good and easy to use offline news-reader like Forte
>>     Linux> Agent, which is able to decode binaries with a single click
>>     Linux> of the mouse, sorting headers on subject, and launcing
>>     Linux> binaries with one click.
>>
>> Gnus/Emacs.  Learn to use the keyboard, it's much faster than the
>> mouse.
>>
>
>Oh please..... That may be true for some of us, but not everyone is so good
>with the keyboard. There is a reason the mouse is so popular. People are more
>productive with it. Yes, I can type faster than most people so I use the
>keyboard over the mouse frequently. But GUI programs are usually easier to use
>than text based ones.

I have one argument for the power of the CLI

find . -name Makefile | awk '{print "mv " $1 " " $1 ".bak \; sed s/\\\"INCROOT \
= \/usr\/X11R6\/include\\\"/\\\"INCROOT = \/usr\/X11R6\/include\/X11\\\"/g \<" \
$1 ".bak > " $1}'

I can't do that from a GUI.

That said, GUIs have their uses.

-- 
"Being myself a remarkably stupid fellow, I have had to unteach myself 
 the difficulties, and now beg to present to my fellow fools the parts
 that are not hard" --Silvanus P. Thompson, from "Calculus Made Easy."

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

From: Jeremy Nickolet <[EMAIL PROTECTED]>
Subject: Re: Ghostscript - Do I need it if RH5.2 already prints
Date: Sat, 10 Apr 1999 02:47:54 GMT

Jeff Peterson wrote:

> I just installed RH5.2 and was having problems setting up my Okidata 6e.
> I finally figured out that I needed to configure it for a HPLaserJet 4.
> While searching for answers, I came upon Ghostscript.
>
> My question is:
>
> Since RH 5.2 is currently able to print (did a postscript test), will
> adding Ghostscript help at all or improve the printing capability?
>
> Thanks
>
> ------------------  Posted via SearchLinux  ------------------
>                   http://www.searchlinux.com

It is probably already installed and being used.

Jeremy


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

From: [EMAIL PROTECTED] (Jerry Gardner)
Subject: Re: VMWARE -- why isn't it the rage topic of discussion?
Date: 10 Apr 1999 02:09:32 GMT

On Sun, 04 Apr 1999 19:12:25 -0500, Richard Steiner wrote:
>
>It's a neat concept, but I weaned myself from Windows long ago.
>
>-- 
>   -Rich Steiner  >>>--->  [EMAIL PROTECTED]  >>>---> Bloomington, MN
>    OS/2 + Linux (Slackware+RedHat+SuSE) + FreeBSD + Solaris + BeOS +
>    WinNT4 + Win95 + PC/GEOS + MacOS + Executor = PC Hobbyist Heaven!
     ^^^^^^   ^^^^^

Don't these two statements conflict? (I think I'd put WinNT4 and Win95
in the PC Hobbyist Hell category myself...)



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

From: Robert Heller <[EMAIL PROTECTED]>
Subject: Re: Running as root?
Date: Sat, 10 Apr 1999 02:49:39 GMT

  [EMAIL PROTECTED] (Frank Goodwyn),
  In a message on 9 Apr 1999 05:49:05 -0500, wrote :

FG> In article <[EMAIL PROTECTED]>, 
FG> [EMAIL PROTECTED] says...
FG> >
FG> ...
FG> 
FG> >Stop running as root!  That is what su is for!  It is trivial to set
FG> >up a user account for your self (and another for testing untrusted
FG> >software).
FG> >
FG> Pardon a newbie question, but how do you do this?  Or how do you find 
FG> out?  I have been running as root because, trivial or not, I'm not sure 
FG> how to do anything else.
FG> 
FG> FG
FG> 
FG>       

Many distributions include a script 'adduser'  or 'useradd', which does
all of the work.  (RedHat has one.) OR you can do it by hand.  The
minimum set of steps are:

1) edit /etc/passwd (and /etc/group, see below under 'gid').  Add a line like:

username:*:uid:gid:Full Name:homedir:shell

Where:

   'username' is the desired *unique* username (8 characters)
   'uid' is the *unique* user id number.  Generally highest number + 1
   'gid' is the group id.  In general a gid of 100 is good.  Look in
         /etc/group for defined groups.  Normal users should be in the
         'users' group (100), or in some group of users that you create
         for them.  Eg. if you have a batch of kids and don't want to
         get their 'grubby' paws on Mom and Dads file, add a line to 
         /etc/group like this:

         kids::200:mom,dad

         And use a gid of 200 for the kids' accounts.  Same idea for
         other 'classes' (groups) of users. (mom and dad are in group 100,
         are here given access to group 200 -- this allows mom and dad to
         spy on^H^H^H^H^H^Hmonitor the kids' files.)

   'Full Name' The users full name.  You can add various GECOS fields if
         you must: office number, phone number, etc.  On a home box this
         is probably silly.

   'homedir' The user's home directory, eg /home/username or
         /home/groupname/username or whatever you like, depending on
         disks and so on (eg, you can put the kids on their on disk 
         partition: /kiddisk/username or put a group of programmers on
         their own disk: /foobarProjectDisk/username, etc.)

   'shell' is the shell the user will get.  /bin/bash, /bin/csh,
           /bin/sh, /bin/tcsh, /bin/ksh, /bin/zsh.  If you don't like
           the user, you can give them /bin/true as a shell, which
           blocks them from logging in. (This is useful is the user in
           question is using the disk space via NFS or Samba (i.e. the
           kids on their old WinBox on the house LAN via 'Map Network
           Drive' and you don't want them finding 'telnet' and logging
           in and poking around where you don't want them).)


2) Once you have edited /etc/passwd, create the user's password (as root):

# passwd username


You will be asked for a password and asked to repeat the password.  

3) Then create the home directory:

# mkdir ~username
# chown username.group ~username

4) Now you might want put in some useful start up files: a .login or
..profile, a .cshrc or .tcshrc or .bashrc or whatever.  .Xdefaults,
..xinitrc or .xsession, .fvwmrc and so on. You don't need *any* of these
-- if the user is knowledable, they can make their own to suit
themselves. If this is not a login account (shell == /bin/true), then
certainly don't bother.

That is basicly it.  Oh, you may or may not want to have fun with
quotas, but that is a whole 'nother can of worms.






          
-- 
                                     \/
Robert Heller                        ||InterNet:   [EMAIL PROTECTED]
http://vis-www.cs.umass.edu/~heller  ||            [EMAIL PROTECTED]
http://www.deepsoft.com              /\FidoNet:    1:321/153

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

From: digger <[EMAIL PROTECTED]>
Crossposted-To: como.os.linux.help
Subject: harddisk keep busy
Date: Fri, 09 Apr 1999 21:02:54 -0500


==============C90EB4EAAA7ED0F8DA846F5A
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit

Hello,

my harddisk is keeping busy. the light of harddisk flash every 4
seconds, even after i logged out. it is annoying. i want to know what's
going on? here is the result of
$ ps aux
USER       PID %CPU %MEM  SIZE   RSS TTY STAT START   TIME COMMAND
bin        238  0.0  0.4   752   276  ?  S    20:41   0:00 portmap
daemon     277  0.0  0.4   784   284  ?  S    20:41   0:00 /usr/sbin/atd

digger     710  0.0  0.8  1276   508   1 S    20:45   0:00 -bash
digger    1635  0.0  0.7   856   488   1 R    20:58   0:00 ps aux
qmaild     366  0.0  0.5   800   344  ?  S    20:41   0:00 tcpserver -v
-c40 -u8
qmaill     327  0.0  0.4   736   288  ?  S    20:41   0:00 cyclog -s
1000000 /va
qmaill     343  0.0  0.3   720   228  ?  S    20:41   0:00 accustamp
qmaill     344  0.0  0.4   736   288  ?  S    20:41   0:00 cyclog -s
1000000 /va
qmaill     346  0.0  0.3   720   228  ?  S    20:41   0:00 accustamp
qmail
qmaill     364  0.0  0.3   720   220  ?  S    20:41   0:00 accustamp
qmaill     365  0.0  0.4   736   288  ?  S    20:41   0:00 cyclog -s
1000000 /va
qmailq     349  0.0  0.4   736   292  ?  S    20:41   0:00 qmail-clean
qmailr     348  0.0  0.4   736   280  ?  S    20:41   0:00 qmail-rspawn
qmails     328  0.0  0.5   780   332  ?  S    20:41   0:00 qmail-send
root         1  0.4  0.6   764   388  ?  S    20:40   0:04 init
root         2  0.0  0.0     0     0  ?  SW   20:40   0:00 (kflushd)
root         3  0.0  0.0     0     0  ?  SW   20:40   0:00 (kpiod)
root         4  0.0  0.0     0     0  ?  SW   20:40   0:00 (kswapd)
root       107  0.0  0.4   736   312  ?  S    20:41   0:00 kerneld
root       252  0.0  0.6   812   420  ?  S    20:41   0:00 syslogd
root       263  0.0  1.0  1080   652  ?  S    20:41   0:00 klogd
qmails     328  0.0  0.5   780   332  ?  S    20:41   0:00 qmail-send
root         1  0.4  0.6   764   388  ?  S    20:40   0:04 init
root         2  0.0  0.0     0     0  ?  SW   20:40   0:00 (kflushd)
root         3  0.0  0.0     0     0  ?  SW   20:40   0:00 (kpiod)
root         4  0.0  0.0     0     0  ?  SW   20:40   0:00 (kswapd)
root       107  0.0  0.4   736   312  ?  S    20:41   0:00 kerneld
root       252  0.0  0.6   812   420  ?  S    20:41   0:00 syslogd
root       263  0.0  1.0  1080   652  ?  S    20:41   0:00 klogd
root       291  0.0  0.7   852   448  ?  S    20:41   0:00 crond
root       305  0.0  0.5   776   368  ?  S    20:41   0:00 inetd
root       326  0.0  0.3   724   252  ?  S    20:41   0:00 supervise
/var/lock/q
root       342  0.0  0.3   724   252  ?  S    20:41   0:00 supervise
/var/lock/q
root       347  0.0  0.4   736   280  ?  S    20:41   0:00 qmail-lspawn
# Using
root       363  0.0  0.3   724   252  ?  S    20:41   0:00 supervise
/var/lock/q
root       380  0.0  0.3   744   252  ?  S    20:41   0:00 gpm -t ps/2
root       404  0.0  0.4   724   296   2 S    20:41   0:00
/sbin/mingetty tty2
root       405  0.0  0.4   724   296   3 S    20:41   0:00
/sbin/mingetty tty3
root       406  0.0  0.4   724   296   4 S    20:41   0:00
/sbin/mingetty tty4
root       407  0.0  0.4   724   296   5 S    20:41   0:00
/sbin/mingetty tty5
root       408  0.0  0.4   724   296   6 S    20:41   0:00
/sbin/mingetty tty6
root       410  0.0  0.2   720   140  ?  S    20:41   0:00 update
(bdflush)
root       660  0.0  0.5  1492   372   1 S    20:44   0:00 login --
digger
root      1634  0.0  0.3   724   252  ?  S    20:58   0:00 supervise
/var/lock/q

sorry for such a long list.

i am using redhat 5.2 with kernel 2.2.5. any advice is appreciated.

digger


==============C90EB4EAAA7ED0F8DA846F5A
Content-Type: text/html; charset=gb2312
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>

<pre>Hello,</pre>
my harddisk is keeping busy. the light of harddisk flash every 4 seconds,
even after i logged out. it is annoying. i want to know what's going on?
here is the result of
<br>$ ps aux
<br>USER&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PID %CPU %MEM&nbsp; SIZE&nbsp;&nbsp;
RSS TTY STAT START&nbsp;&nbsp; TIME COMMAND
<br>bin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 238&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
752&nbsp;&nbsp; 276&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 portmap
<br>daemon&nbsp;&nbsp;&nbsp;&nbsp; 277&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
784&nbsp;&nbsp; 284&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 /usr/sbin/atd
<br>digger&nbsp;&nbsp;&nbsp;&nbsp; 710&nbsp; 0.0&nbsp; 0.8&nbsp; 1276&nbsp;&nbsp;
508&nbsp;&nbsp; 1 S&nbsp;&nbsp;&nbsp; 20:45&nbsp;&nbsp; 0:00 -bash
<br>digger&nbsp;&nbsp;&nbsp; 1635&nbsp; 0.0&nbsp; 0.7&nbsp;&nbsp; 856&nbsp;&nbsp;
488&nbsp;&nbsp; 1 R&nbsp;&nbsp;&nbsp; 20:58&nbsp;&nbsp; 0:00 ps aux
<br>qmaild&nbsp;&nbsp;&nbsp;&nbsp; 366&nbsp; 0.0&nbsp; 0.5&nbsp;&nbsp;
800&nbsp;&nbsp; 344&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 tcpserver -v -c40 -u8
<br>qmaill&nbsp;&nbsp;&nbsp;&nbsp; 327&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 288&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 cyclog -s 1000000 /va
<br>qmaill&nbsp;&nbsp;&nbsp;&nbsp; 343&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
720&nbsp;&nbsp; 228&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 accustamp
<br>qmaill&nbsp;&nbsp;&nbsp;&nbsp; 344&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 288&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 cyclog -s 1000000 /va
<br>qmaill&nbsp;&nbsp;&nbsp;&nbsp; 346&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
720&nbsp;&nbsp; 228&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 accustamp qmail
<br>qmaill&nbsp;&nbsp;&nbsp;&nbsp; 364&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
720&nbsp;&nbsp; 220&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 accustamp
<br>qmaill&nbsp;&nbsp;&nbsp;&nbsp; 365&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 288&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 cyclog -s 1000000 /va
<br>qmailq&nbsp;&nbsp;&nbsp;&nbsp; 349&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 292&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 qmail-clean
<br>qmailr&nbsp;&nbsp;&nbsp;&nbsp; 348&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 280&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 qmail-rspawn
<br>qmails&nbsp;&nbsp;&nbsp;&nbsp; 328&nbsp; 0.0&nbsp; 0.5&nbsp;&nbsp;
780&nbsp;&nbsp; 332&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 qmail-send
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp; 0.4&nbsp;
0.6&nbsp;&nbsp; 764&nbsp;&nbsp; 388&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:40&nbsp;&nbsp;
0:04 init
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp; 0.0&nbsp;
0.0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp; ?&nbsp; SW&nbsp;&nbsp;
20:40&nbsp;&nbsp; 0:00 (kflushd)
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3&nbsp; 0.0&nbsp;
0.0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp; ?&nbsp; SW&nbsp;&nbsp;
20:40&nbsp;&nbsp; 0:00 (kpiod)
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4&nbsp; 0.0&nbsp;
0.0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp; ?&nbsp; SW&nbsp;&nbsp;
20:40&nbsp;&nbsp; 0:00 (kswapd)
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 107&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 312&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 kerneld
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 252&nbsp; 0.0&nbsp; 0.6&nbsp;&nbsp;
812&nbsp;&nbsp; 420&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 syslogd
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 263&nbsp; 0.0&nbsp; 1.0&nbsp;
1080&nbsp;&nbsp; 652&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 klogd
<br>qmails&nbsp;&nbsp;&nbsp;&nbsp; 328&nbsp; 0.0&nbsp; 0.5&nbsp;&nbsp;
780&nbsp;&nbsp; 332&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 qmail-send
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp; 0.4&nbsp;
0.6&nbsp;&nbsp; 764&nbsp;&nbsp; 388&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:40&nbsp;&nbsp;
0:04 init
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp; 0.0&nbsp;
0.0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp; ?&nbsp; SW&nbsp;&nbsp;
20:40&nbsp;&nbsp; 0:00 (kflushd)
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3&nbsp; 0.0&nbsp;
0.0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp; ?&nbsp; SW&nbsp;&nbsp;
20:40&nbsp;&nbsp; 0:00 (kpiod)
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4&nbsp; 0.0&nbsp;
0.0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp; ?&nbsp; SW&nbsp;&nbsp;
20:40&nbsp;&nbsp; 0:00 (kswapd)
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 107&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 312&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 kerneld
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 252&nbsp; 0.0&nbsp; 0.6&nbsp;&nbsp;
812&nbsp;&nbsp; 420&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 syslogd
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 263&nbsp; 0.0&nbsp; 1.0&nbsp;
1080&nbsp;&nbsp; 652&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 klogd
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 291&nbsp; 0.0&nbsp; 0.7&nbsp;&nbsp;
852&nbsp;&nbsp; 448&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 crond
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 305&nbsp; 0.0&nbsp; 0.5&nbsp;&nbsp;
776&nbsp;&nbsp; 368&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 inetd
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 326&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
724&nbsp;&nbsp; 252&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 supervise /var/lock/q
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 342&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
724&nbsp;&nbsp; 252&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 supervise /var/lock/q
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 347&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
736&nbsp;&nbsp; 280&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 qmail-lspawn # Using
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 363&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
724&nbsp;&nbsp; 252&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 supervise /var/lock/q
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 380&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
744&nbsp;&nbsp; 252&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 gpm -t ps/2
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 404&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
724&nbsp;&nbsp; 296&nbsp;&nbsp; 2 S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 /sbin/mingetty tty2
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 405&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
724&nbsp;&nbsp; 296&nbsp;&nbsp; 3 S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 /sbin/mingetty tty3
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 406&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
724&nbsp;&nbsp; 296&nbsp;&nbsp; 4 S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 /sbin/mingetty tty4
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 407&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
724&nbsp;&nbsp; 296&nbsp;&nbsp; 5 S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 /sbin/mingetty tty5
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 408&nbsp; 0.0&nbsp; 0.4&nbsp;&nbsp;
724&nbsp;&nbsp; 296&nbsp;&nbsp; 6 S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 /sbin/mingetty tty6
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 410&nbsp; 0.0&nbsp; 0.2&nbsp;&nbsp;
720&nbsp;&nbsp; 140&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:41&nbsp;&nbsp;
0:00 update (bdflush)
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 660&nbsp; 0.0&nbsp; 0.5&nbsp;
1492&nbsp;&nbsp; 372&nbsp;&nbsp; 1 S&nbsp;&nbsp;&nbsp; 20:44&nbsp;&nbsp;
0:00 login -- digger
<br>root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1634&nbsp; 0.0&nbsp; 0.3&nbsp;&nbsp;
724&nbsp;&nbsp; 252&nbsp; ?&nbsp; S&nbsp;&nbsp;&nbsp; 20:58&nbsp;&nbsp;
0:00 supervise /var/lock/q
<p>sorry for such a long list.
<p>i am using redhat 5.2 with kernel 2.2.5. any advice is appreciated.
<p>digger
<br>&nbsp;</html>

==============C90EB4EAAA7ED0F8DA846F5A==


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

From: "opus007" <[EMAIL PROTECTED]>
Crossposted-To: 
comp.lang.basic.visual.misc,comp.lang.c,comp.lang.c++,comp.lang.java.programmer,comp.lang.javascript,comp.lang.perl.misc,comp.os.linux.advocacy,comp.os.linux.hardware,comp.os.linux.networking,comp.os.linux.setup,comp.os.os2.advocacy,com
Subject: Re: free computer13
Date: Sat, 10 Apr 1999 03:03:00 GMT

Something tells me that Michael Dell and his attorneys would be interested
in this post. Think I will forward it to Dell (my favorite computer company
:->) and let them take it from there.

And by the way idiot - Dell has been around for longer than 5 years!

I hate spam.

--
opus
"Laissez les bons temps rouler"


webmaster wrote in message <7eg4vn$bsp$[EMAIL PROTECTED]>...
>Free Computer at http://giveaways.arecool.net
>
>DELL IS GIVING AWAY 500 FREE PENTIUM 500 Computers to celebrate their 5th
>anniversary.
>
>Hurry and if you are one of the first 500 people you win a new computer!!!
>



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

From: [EMAIL PROTECTED] (Mike Mckinney)
Crossposted-To: alt.os.linux,comp.os.linux.help,linux.redhat.misc
Subject: Re: Why Linux still isn't my standard boot-up OS, or what are the 
Linux-equivalents for these Windoze programs?
Reply-To: [EMAIL PROTECTED]
Date: Sat, 10 Apr 1999 03:00:05 GMT

On Fri, 09 Apr 1999 13:41:08 GMT, [EMAIL PROTECTED] wrote:

>Oh please..... That may be true for some of us, but not everyone is so good
>with the keyboard. There is a reason the mouse is so popular. People are more
>productive with it. Yes, I can type faster than most people so I use the
>keyboard over the mouse frequently. But GUI programs are usually easier to use
>than text based ones.

        This is in fact not true at all. Actual factual studies that have proven
        that command line users can almost always be more productive than users
        who are using a GUI. GUI's are fine if you idea of productivity is
        searching through menus, filling in dialog boxes, and clicking on radio
        buttons, but think about this : I use the command line 95% of the time,
        but if need be I can make use of pretty much any GUI to get something
        done. You use a GUI at least 90% of the time, but could you get anything
        done if you had to use the command line ?

>It's unfortunate that many Unix are so arrogant and condescending to people
>who are used to Windows. Basically you are saying "Linux is better. Learn to
>do it our way." Yeah, and your types accuse Microsoft of heavy-handedness.
>Windows users use a wide variety of programs. They aren't going to give those
>up just and jump with Linux on their desktops just because Linux is purer or
>more stable. If it won't run their software or is confusing, they won't use
>it. No matter how much *you* say they don't need all that stuff.

It's not always a condescending attitude. Sometimes people who use Linux get
tired of hearing about how if it was just like Win* it would be so much
better. Better for who ? If you want to point & click, then stay with Win*,
because at least right now, Linux is not what you want, and contrary to what
a good many people think, they aren't doing anyone any favors by using Linux,
just like I wouldn't be doing anyone any favors using Win* .

-- 
[EMAIL PROTECTED]


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

From: Jeremy Nickolet <[EMAIL PROTECTED]>
Subject: Re: LS120 or ZIP ( both parallel port )?
Date: Sat, 10 Apr 1999 02:56:05 GMT

Jacek M. Holeczek wrote:

> Hi,
> I am considering buying either LS120 or ZIP drive. In any case it will
> be the parallel-port version ( in order to share/move data between some
> computers running Linux, some of them have no Internet access ). They both
> give about 100-120MB and cost also almost the same ( forget the disks, I
> won't need many ).
> Which one should I buy ? And why ?
> What is the reliability of data stored on their disks ? Is LS120 better
> then ZIP ?
> What is the effective ( not what the producer says ) transfer rate
> between such an external-parallel-port drive and the PC ? Which one is
> better and how much ?
> Thanks in advance,
> Jacek.

I use the parallel port Zip Drive and it is really quite good.  The newer
drivers have sped things up a fair amount and for me it works great for
occational storage and small backups.  I'm not sure if there is any support
for the new 250 MB Zip drives, but I image that it won't be long before there
are drivers for it.  The performance is supposed to be much improved as
well.  Might want to look into that as another alternative.

Jeremy


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


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

Reply via email to