Linux-Misc Digest #414, Volume #20               Sun, 30 May 99 12:13:12 EDT

Contents:
  Re: Offline newsreader for Linux (Jan Panteltje)
  Re: telnet in as root? ("John Burton")
  Who is this NEWS guy? ("Michael Schmeing")
  Re: make dep - What is "as" ??? ("D. Vrabel")
  Re: In defence of UNIX man pages (Robert Hull)
  Re: Offline newsreader for Linux (Bruce Stephens)
  Re: root , adduser , password ? ("Erik Akkermans")
  Re: Linux: now or never (NoSpam)
  Re: XWindows Server ("adam howard")
  Re: telnet in as root? ("George Georgakis")
  Re: Linux: now or never (Nero)

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

From: [EMAIL PROTECTED] (Jan Panteltje)
Subject: Re: Offline newsreader for Linux
Date: Sun, 30 May 99 14:42:38 GMT

>> I've just started using leafnode to make my machine into a little private
>> mail server.  Then read them at your leisure using slrn (or whatever you
>> prefer).
>
>newsserver, you mean!
>
>One should tell Steve: Under Linux you don't need an offline reader
>(infact they don't exist). You set up your own newsserver with INN
>or leafnode.
>
That is not true.
I wrote NewsFleX, although it is not free, it is a very good off line news
reader for Linux.
The predecessor to NewsFleX, xagent that is free (written in C) is at sunsite.
So, why bother with all those difficult programs if you can have it all, with
a decent GUI running under X, automatic dial in etc.
But of cause you can, if you are into not using X, use something simple.
NewsFleX can be found at http://www.panteltje.demon.nl.
There are also some more programs there.
So, before you say something like 'does not exist', please make a more deep
study of Linux (and Unix) first, then you will probably find, that in this
operating system, there is VERY little that 'does not exist'.
So, hopefully that enhanced your expertise in the field somewhat.
J.


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

From: "John Burton" <[EMAIL PROTECTED]>
Crossposted-To: 
alt.os.linux,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.questions
Subject: Re: telnet in as root?
Date: Sun, 30 May 1999 14:55:19 +0100

Well you're right of course. I retract what I said, there _is_ a security
risk.

Is there a way to disable logins to a linux machine completly from the
ppp networking while allowing them from the network card.

George Georgakis wrote in message <01beaaa3$52a52b60$0101a8c0@george>...
>Do *either* of those systems have Net access? If so, then you *do* have a
>security risk.
>
>George
>
>John Burton <[EMAIL PROTECTED]> wrote in article
><7irebn$bj1$[EMAIL PROTECTED]>...
>>
>> It's not always a security risk. I've got two computers in my house on
>> their own network so there is no risk and it's appriate to be able
>> to do the easiest thing.
>>
>>
>>



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

From: "Michael Schmeing" <[EMAIL PROTECTED]>
Subject: Who is this NEWS guy?
Date: 30 May 1999 10:45:15 +0200

Hi,
can anyone answer that question? Today I got over 500 new articles and
by far the most (I did not count them but it must be way over 80%)
have someone called NEWS as author. Who is this guy?

If it stays like this I would like the answer as an email or I might
miss it.

Curious for the answer,
Michael
-- 
Michael Schmeing, Artillerieweg 46, D-26129 Oldenburg
e-mail: [EMAIL PROTECTED] 
www: http://www.Informatik.Uni-Oldenburg.DE/~michae2

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

From: "D. Vrabel" <[EMAIL PROTECTED]>
Subject: Re: make dep - What is "as" ???
Date: Sun, 30 May 1999 15:02:22 +0100

On Sun, 30 May 1999, Paul wrote:

> Hi everybody,
> 
> I have a problem with  make dep. When I type make dep it returns :
> gcc :  installaton problem, cannot exec 'as' :  No such file or
> directory
> make: *** [scripts/mkdep] Error 1
as is the assembler.  It's part of the binutils package.

David Vrabel


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

From: Robert Hull <[EMAIL PROTECTED]>
Subject: Re: In defence of UNIX man pages
Date: Wed, 19 May 1999 01:24:57 +0100

In article <[EMAIL PROTECTED]>, Johan Kullstam
<[EMAIL PROTECTED]> writes
>Robert Hull <[EMAIL PROTECTED]> writes:
>
>> Now to get back to the subject of man pages - they are not meant to be a
>> substitute for your Chemical Engineering manual, but a *technical*
>> manual about IT. In that context, I repeat that a good *technical*
>> manual will leave the examples to the User's Guide
>
>fine.  however i seem to be lacking in user-guide pages.
>
>$ user ls
>bash: user: command not found.
>
>if you are going to insist on segregating out examples from the man
>pages, let's at least find them a better home for them than /dev/null.
>
There *is* a better home for them, as you probably already know. Instead
of trying to score points with non-existent commands, try the ones that
*do* exist such as info

[Robert@thehulls Robert]$ info ls

File: fileutils.info,  Node: ls invocation,  Next: dir invocation,  Up:
Directory listing

`ls': List directory contents
=============================

   The `ls' program lists information about files (of any type,
including directories).  Options and file arguments can be intermixed
arbitrarily, as usual.

   For non-option command-line arguments that are directories, by
default `ls' lists the contents of directories, not recursively, and
omitting files with names beginning with `.'.  For other non-option
arguments, by default `ls' lists just the file name.  If no non-option
arguments are specified, `ls' lists the contents of the current
directory.

   By default, the output is sorted alphabetically.  If standard output
is a terminal, the output is in columns (sorted vertically); otherwise,
they are listed one per line.

   Because `ls' is such a fundamental program, it has accumulated many
options over the years.  They are described in the subsections below;
within each section, options are listed alphabetically (ignoring case).
The division of options into the subsections is not absolute, since some
options affect more than one aspect of `ls''s operation.

   The `-g' option is accepted but ignored, for compatibility with
Unix.  Also see *Note Common options::.

* Menu:

* Which files are listed::
* What information is listed::
* Sorting the output::
* General output formatting::
* Formatting the file names::

File: fileutils.info,  Node: Which files are listed,  Next: What
information is listed,  Up: ls invocation

Which files are listed
======================

   These options determine which files `ls' lists information for.  By
default, any files and the contents of any directories on the command
line are shown.

`-a'
`--all'
     List all files in directories, including files that start with `.'.

`-A'
`--almost-all'
     List all files in directories except for `.' and `..'.

`-B'
`--ignore-backups'
     Do not list files that end with `~', unless they are given on the
     command line.

`-d'
`--directory'
     List just the names of directories, as with other types of files,
     rather than listing their contents.

`-I'
`--ignore'
     Do not list files whose names match the shell pattern (not regular
     expression) PATTERN unless they are given on the command line.  As
     in the shell, an initial `.' in a file name does not match a
     wildcard at the start of PATTERN.

`-L'
`--dereference'
     In a long listing, show file information (e.g., times and
     permissions) for the referents of symbolic links rather than for
     the symbolic links themselves.

`-R'
`--recursive'
     List the contents of all directories recursively.

File: fileutils.info,  Node: What information is listed,  Next: Sorting
the output,  Prev: Which files are listed,  Up: ls invocation

What information is listed
==========================

   These options affect the information that `ls' displays.  By
default, only file names are shown.

`-D'
`--dired'
     With the long listing (`-l') format, print an additional line after
     the main output:

          //DIRED// BEG1 END1 BEG2 END2 ...

     The BEGN and ENDN are unsigned integers which record the byte
     position of the beginning and end of each file name in the output.
     This makes it easy for Emacs to find the names, even when they
     contain unusual characters such as space or newline, without fancy
     searching.

     If directories are being listed recursively (`-R'), output a
     similar line after each subdirectory:
          //SUBDIRED// BEG1 END1 ...

`-G'
`--no-group'
     Inhibit display of group information in a long format directory
     listing.  (This is the default in some non-GNU versions of `ls',
     so we provide this option for compatibility.)

`-i'
`--inode'
     Print the inode number (also called the file serial number and
     index number) of each file to the left of the file name.  (This
     number uniquely identifies each file within a particular
     filesystem.)

`-l'
`--format=long'
`--format=verbose'
     In addition to the name of each file, print the file type,
     permissions, number of hard links, owner name, group name, size in
     bytes, and timestamp (by default, the modification time).  For
     files with a time more than six months old or more than one hour
     into the future, the timestamp contains the year instead of the
     time of day.

     For each directory that is listed, preface the files with a line
     `total BLOCKS', where BLOCKS is the total disk space used by all
     files in that directory.  By default, 1024-byte blocks are used;
     if the environment variable `POSIXLY_CORRECT' is set, 512-byte
     blocks are used (unless the `-k' option is given).  The BLOCKS
     computed counts each hard link separately; this is arguably a
     deficiency.

     The permissions listed are similar to symbolic mode specifications
     (*note Symbolic Modes::.).  But `ls' combines multiple bits into
     the third character of each set of permissions as follows:
    `s'
          If the setuid or setgid bit and the corresponding executable
          bit are both set.

    `S'
          If the setuid or setgid bit is set but the corresponding
          executable bit is not set.

    `t'
          If the sticky bit and the other-executable bit are both set.

    `T'
          If the sticky bit is set but the other-executable bit is not
          set.

    `x'
          If the executable bit is set and none of the above apply.

    `-'
          Otherwise.

`-o'
     Produce long format directory listings, but don't display group
     information.  It is equivalent to using `--format=long' with
     `--no-group' .  This option is provided for compatibility with
     other versions of `ls'.

`-s'
`--size'
     Print the size of each file in 1024-byte blocks to the left of the
     file name.  If the environment variable `POSIXLY_CORRECT' is set,
     512-byte blocks are used instead, unless the `-k' option is given
     (*note General output formatting::.).

     For files that are NFS-mounted from an HP-UX system to a BSD
     system, this option reports sizes that are half the correct
     values.  On HP-UX systems, it reports sizes that are twice the
     correct values for files that are NFS-mounted from BSD systems.
     This is due to a flaw in HP-UX; it also affects the HP-UX `ls'
     program.

File: fileutils.info,  Node: Sorting the output,  Next: General output
formatting,  Prev: What information is listed,  Up: ls invocation

Sorting the output
==================

   These options change the order in which `ls' sorts the information
it outputs.  By default, sorting is done by character code (e.g., ASCII
order).

`-c'
`--time=ctime'
`--time=status'
     Sort according to the status change time (the `ctime' in the
     inode).  If the long listing format (`-l') is being used, print the
     status change time instead of the modification time.

`-f'
     Primarily, like `-U'--do not sort; list the files in whatever
     order they are stored in the directory.  But also enable `-a' (list
     all files) and disable `-l', `--color', and `-s' (if they were
     specified before the `-f').

`-r'
`--reverse'
     Reverse whatever the sorting method is--e.g., list files in reverse
     alphabetical order, youngest first, smallest first, or whatever.

`-S'
`--sort=size'
     Sort by file size, largest first.

`-t'
`--sort=time'
     Sort by modification time (the `mtime' in the inode), newest first.

`-u'
`--time=atime'
`--time=access'
`--time=use'
     Sort by access time (the `atime' in the inode).  If the long
     listing format is being used, print the last access time.

`-U'
`--sort=none'
     Do not sort; list the files in whatever order they are stored in
     the directory.  (Do not do any of the other unrelated things that
     `-f' does.)  This is especially useful when listing very large
     directories, since not doing any sorting can be noticeably faster.

`-X'
`--sort=extension'
     Sort directory contents alphabetically by file extension
     (characters after the last `.'); files with no extension are
     sorted first.

File: fileutils.info,  Node: General output formatting,  Next:
Formatting the file names,  Prev: Sorting the output,  Up: ls invocation

General output formatting
=========================

   These options affect the appearance of the overall output.

`-1'
`--format=single-column'
     List one file per line.  This is the default for `ls' when standard
     output is not a terminal.

`-C'
`--format=vertical'
     List files in columns, sorted vertically.  This is the default for
     `ls' if standard output is a terminal.  It is always the default
     for the `dir' and `d' programs.

`--color [=WHEN]'
     Specify whether to use color for distinguishing file types.  WHEN
     may be omitted, or one of:
        * none Do not use color at all.  This is the default.

        * auto Only use color if standard output is a terminal.

        * always Always use color.  Specifying `--color' and no WHEN is
     equivalent to `--color=always'.

`-F'
`--classify'
     Append a character to each file name indicating the file type.
     Also, for regular files that are executable, append `*'.  The file
     type indicators are `/' for directories, `@' for symbolic links,
     `|' for FIFOs, `=' for sockets, and nothing for regular files.

`--full-time'
     List times in full, rather than using the standard abbreviation
     heuristics.  The format is the same as `date''s default; it's not
     possible to change this, but you can extract out the date string
     with `cut' and then pass the result to `date -d'.  *Note `date'
     invocation: (sh-utils)date invocation.

     This is most useful because the time output includes the seconds.
     (Unix filesystems store file timestamps only to the nearest
     second, so this option shows all the information there is.)  For
     example, this can help when you have a Makefile that is not
     regenerating files properly.

`-k'
`--kilobytes'
     If file sizes are being listed, print them in kilobytes.  This
     overrides the environment variable `POSIXLY_CORRECT'.

`-m'
`--format=commas'
     List files horizontally, with as many as will fit on each line,
     separated by `, ' (a comma and a space).

`-n'
`--numeric-uid-gid'
     List the numeric UID and GID instead of the names.

`-p'
     Append a character to each file name indicating the file type.
     This is like `-F', except that executables are not marked.

`-x FORMAT'
`--format=across'
`--format=horizontal'
     List the files in columns, sorted horizontally.

`-T COLS'
`--tabsize=COLS'
     Assume that each tabstop is COLS columns wide.  The default is 8.
     `ls' uses tabs where possible in the output, for efficiency.  If
     COLS is zero, do not use tabs at all.

`-w'
`--width=COLS'
     Assume the screen is COLS columns wide.  The default is taken from
     the terminal settings if possible; otherwise the environment
     variable `COLUMNS' is used if it is set; otherwise the default is
     80.

File: fileutils.info,  Node: Formatting the file names,  Prev: General
output formatting,  Up: ls invocation

Formatting the file names
=========================

   These options change how file names themselves are printed.

`-b'
`--escape'
     Quote nongraphic characters in file names using alphabetic and
     octal backslash sequences like those used in C.

`-N'
`--literal'
     Do not quote file names.

`-q'
`--hide-control-chars'
     Print question marks instead of nongraphic characters in file
     names.  This is the default.

`-Q'
`--quote-name'
     Enclose file names in double quotes and quote nongraphic
     characters as in C.


-- 
Robert                    Talking to yourself - first sign of madness
                          Answering yourself back - first sign of schizophrenia
                          I go one better: If I don't like the answer ...
                          I put it to a majority vote

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

From: Bruce Stephens <[EMAIL PROTECTED]>
Subject: Re: Offline newsreader for Linux
Date: 30 May 1999 15:53:23 +0100

"Gero H. Marten" <[EMAIL PROTECTED]> writes:

> newsserver, you mean!
> 
> One should tell Steve: Under Linux you don't need an offline reader
> (infact they don't exist).  You set up your own newsserver with INN
> or leafnode.

Offline readers do exist.  Gnus, for example.

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

From: "Erik Akkermans" <[EMAIL PROTECTED]>
Subject: Re: root , adduser , password ?
Date: Sun, 30 May 1999 16:15:50 +0200


[EMAIL PROTECTED] heeft geschreven in bericht
<7ipoe4$ln1$[EMAIL PROTECTED]>...
>Hello,
>
>Up till now I've always logged in as root. Using Slakware (1996/7 ? )
>Apparently some aps. don't like this ?
>In particular I'm trying elm (emailer), since Netscape4.5 is painfully
slow.
>It seems that elm should not be run as root ?
>The original 'install.txt', writes about logging in as other than root;
>and gives an example. But my prompt sequence for adduser never
>asks for password !!
>Also where do I access the name-password pair. Or at least be
>able to remove the 'dud' users that I've added ?

As superuser (root):

To add a user <username>:
  adduser <username>

To enter password:
  passwd <username>

To delete <username>:
  userdel <username>

Regards, Erik



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

From: NoSpam <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,uk.comp.os.linux
Subject: Re: Linux: now or never
Date: Sun, 30 May 1999 15:06:19 +0000

Nero quotes 240+ lines needlessly just to add:
> 240 lines snipped]
> You Suck. :)

Methinks you need to learn to snip before you type!
-- 
               "IR35: New Labour, Old Habits!"
I still remember the last Labour government; electricity strikes,
bread strikes, "Closed Shops", the three day week, rubbish piled 
high in the streets, dead bodies waiting months to be buried...

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

From: "adam howard" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.redhat,linux.redhat.misc,msn.computingcentral.os.linux
Subject: Re: XWindows Server
Date: Sun, 30 May 1999 09:23:07 -0500

> There is a shareware product called X-Win32.  It works great.  The only
> limitation is that only one session per sub-net can run at a time, and
only
> for two hours at a time.  Once you pay, the limitations are lifted.

This one is available from starnet.com, i believe.

There is another X server not time limited available from
www.microimages.com






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

From: "George Georgakis" <linuxstart.com@geegee>
Subject: Re: telnet in as root?
Crossposted-To: 
alt.os.linux,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.questions
Date: Sun, 30 May 1999 13:44:57 GMT

Do *either* of those systems have Net access? If so, then you *do* have a
security risk.

George
===========================================================================
I never reply by email as a) I don't give out my real email address freely,
and b) it stops other NG users from reading the solutions to problems
If necessary, however, I can be contacted thru linuxstart.com@geegee. 
(Swap "geegee" and "linuxstart.com").
===========================================================================

John Burton <[EMAIL PROTECTED]> wrote in article
<7irebn$bj1$[EMAIL PROTECTED]>...
> 
> It's not always a security risk. I've got two computers in my house on
> their own network so there is no risk and it's appriate to be able
> to do the easiest thing.
> 
> 
> 

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

From: Nero <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,uk.comp.os.linux
Subject: Re: Linux: now or never
Date: Sun, 30 May 1999 22:22:41 +0800
Reply-To: [EMAIL PROTECTED]

Gilles Pelletier wrote:
> 
> Reinier Post <[EMAIL PROTECTED]> �crivait/wrote:
> 
> >[EMAIL PROTECTED] ( (Gilles Pelletier)) wrote:
> >
> >>I installed Gnome 6.1 last weekend. Everything went well until the
> >>menu driven installation refused to install the server (driver?) for
> >>my Mach32 video card. I then had to go to the prompt.
> >
> >At the prompt, as root, type 'yast', and you're back in the automatic
> >installation seat.
> 
> Oh, great! My video card problem is fixed, but I could get my CF
> keyboard back with your precious advice. The process is even more
> automatic than in DOS, where you have to write a line in config.sys
> and two in autoexec.bat. (The CF keyboard wasn't available on the
> first steps of installation, I believe.)
> 
> But... oups! CTRL + ALT don't work, only Alt Gr. And oups again,
> capitals letters ������ , save �, aren't available. Hum... I still
> prefer to write three lines in DOS.
> 
> >>So, I figured out that a beginner would be much better of building his
> >>system manually. You know, mkdir /dev, /mnt, /cdrom, whatever...
> >
> >SuSE has 4.5 gig of software and you want to install and configure it
> >manually?
> 
> No. Not the software, just the monitor, mouse, keyboard, etc. ; create
> users, delete users, create shadow passwords;. and mount, umount, etc.
> 
> There's a utility called "amd" which is supposed to simplify the
> process of mounting -- unmounting. Do you know what it does? This is
> really a pain! In DOS, I simply insert the disquette, type "d" (which
> is doskey for "DIR /O/P/S") then enter. For the following disquettes,
> I use the up arrow instead of "d".
> 
> Better yet, if I want to find a file, I do:
> "ou foobar" instead of "d"
> ("o�" is french for "where" and is doskey for "DIR %1 /O/P/S"
> 
> "tr www.foobar.com" makes a traceroute with date and time,
> Etc.
> 
> Now, I certainly won't pretend that you can do as much with DOSKEY and
> batch files as with shell scripts, but it's more than enough for the
> casual user; it's fairly easy to use and you don't have to roam in
> HOWTOs and FAQs to learn to write them. Any book for beginners can
> teach you to write a batch file. Of course, batch files seem to be
> outmoded. People use Windows "as it is."
> 
> >>Once the kernel is installed, Emacs could be opened with instructions
> >>in a top window and the prompt or the file to edit at the bottom.
> >
> >Once the kernel is installed, you need to install Emacs.  'Manually'?
> >
> >>Instructions could be formatted in HTML so that if you were installing
> >>a second IDE drive from a CD, you wouldn't have to find your way
> >>through SCSI installation from ftp. You'd read just what you need.
> >
> >How does the HTML file know what it is you need?
> 
> It doesn't. That's why the links are there: if you need it, you click
> it. Otherwise, you read the basics.
> 
> >>Autoinstalling Linux is like putting a nice body around a Ferrari's
> >>mechanics and giving the keys to John Doe saying "You just press the
> >>gas pedal and it moves forward."
> >
> >I don't know about you, but if I ever buy a Ferrari (which is
> >purely hypothetical) I'll be buying a car, ready for use; not a DIY
> >Ferrari assembly kit.
> 
> That's pretty much what Linux is. You can "assemble it" so that it
> asks you before overwriting a file. You can even set up a recycle bin.
> But no distribution will explain how to do these things while you're
> installing. You've got to search through piles and heaps of
> documentation, which most newcomers from theWindows world, complaining
> about its inadequacies and still unable to write a batch file, won't
> do.
> 
> Loosing a few files is one of the many reasons they're back to
> Windows. I'd bet that there are more copies of Linux gathering dust on
> the bottom shelves that being installed on numerous computers. That's
> why I'm saying that Linux is going nowhere as an OS for the general
> public. For now, it's only child's play and big hoopla.
> 
> Exemples:
> 
> A few months ago, here in Quebec, a journalist named Dumais, attempted
> a switch to Linux. All the community was around, helping him to get
> over every hurdle, just as the Linux community is supposed to do...
> and even quite a bit more.
> 
> The guy was reporting daily on his progress and finally got his system
> up and running (in 16 bit colors!) in "only" 4 days... after somebody
> went to his place to fix things. Then, nothing: a few "I'll be back"
> in December and he vanished in the haze. Don't ask about him, he's
> just gone. And it's Linux hoopla all over again.
> 
> Another dunce, you'll say? No so long ago, Linux-Quebec was sporting a
> link in its section "Linux dans les �coles" about Trois-Soleils school
> in Laval. A few old boxes had been networked to a Pentium 166 and
> provided access to the internet with Netscape. The system was
> certainly honed to perfection, as it was installed by Jacques G�linas
> of Linuxconf fame.
> 
> Quite a few months later, I called the school to ask how come not a
> single page had been added since the installation. The director told
> me that a few pieces of wire had apparently been borrowed (not
> computers!) and the network was put down. Gelinas wrote me that his
> son wasn't at this school anymore and that he had other concerns. The
> only link to an operating Linux system was eventually taken off the
> Linux-Quebec page on "schools". And it's Linux hoopla all over again.
> 
> I don't know how many small networks operate on NT in schools, but my
> nieces' school has a network and since there's no ballyhoo, my bet is
> that it's operating on NT. I guess there must be a few dozen of
> schools using NT in Quebec, but no one talks about it. It's the way to
> go, it's just normal.
> 
> For sure, M$ is now investing big money in the public librairies
> system in Canada, just as in the US.
> See: http://www.ledevoir.com/liv/1999a/gate010499.html
> (French text.)
> In Canada, the federal and provincial governments rely almost
> exclusively on M$ software. Quebec Liquor Board, amongst others, has
> switched from OS2 to NT.
> 
> Every day an immense installfest goes on for M$: all over the world,
> thousands of new cheap internet computers are sold or given away with
> a subscrition to internet services with only Windows on board.
> 
> McGill University, where Gopher was born, now gives its first courses
> on NT. This way, I was told, students get to learn something they can
> use in their everyday life.
> 
> Etc.
> 
> Of course, when someone like me makes a follow-up on Linux's success
> stories and takes a peek at M$ little exponential leaps in the real
> non-linux world, he's necessarily qualified as a M$ sycophant. People
> prefer evangelist Eric Raymond's Cathedral of the Bizarre gospel.
> 
> Though I wouldn't mind getting my economic and politic vision of the
> networked society from a programmer, it just so  happens that the most
> down to earth paper I've read so far is by economist Nathan Newman,
> who was a doctorate Berkely student at the time of the writing.
> See: From MSWord to MSWorld: How Microsoft is Building a Global
> Monopoly   http://www.netaction.org/msoft/world/
> 
> No bright new concept here, no scholarly erudition, just plain talk,
> the real M$ story. And what you learn mainly, is that when M$ can't
> beat the enemy in a face to face confrontation, as is the case for
> Linux, it undermines its defences.
> 
> As Linux is beginning to nibble away at the servers' market, Gates and
> Allen are still enlarging their users base and selling a hell of a lot
> of shares to get a large number of investors interested in M$ future.
> They invest the money in technologies (satellites, cables, databases)
> that might very well end up being just a little bit more M$ friendly
> than Linux friendly. We're not only talking about "Frontpage
> extensions" here... and look at the success they had with this silly
> thing!
> 
> For now, with its "750 million users in five years" (Raymond, a very
> conservative man, scaled down his estimate from 830 millions) Linux is
> doing great... while being M$' single greatest ally in its struggle
> against the DoJ. (One can only wonder and ponder at the miraculous
> coincidence of this... impending rise of Linux!)
> 
> But when DoJ trial ends, Windows 2000 will be out. Or rather, Windows
> 2000 will be out when DoJ trial ends. ; )  For a while, it might be
> exempt from certain "security breaches" that send user information
> back to M$ and of back doors that allow M$ technicians to peek at a
> system. (Who knows, it might even crash a wee bit less ;-)
> If Linux is not really more user friendly or, I'd say, "user
> comprehensible" (in the sense that a nice graphical interface just
> won't do), it will be the beginning of the end.
> 
> >Reinier Post (satisfied SuSE 6.1 user)
> 
> When I was in Holland, the administrator of the "Vliegen Bos" near
> Amsterdam liked to take me apart -- probably because I was more of his
> age than the rest of the campers -- to teach me about the common sense
> of the Dutch people (without exception, of course). It went from not
> wasting expensive and scarce police respourses on enforcing laws on
> marijuana, to living near one's work and using a bicycle to get to
> it... and, of course, the obligation to keep the key in the back
> wheel's lock when you rode (so it couldn't get lost, at least during
> the ride : )
> 
> I really hope he was right and that, as an experienced Linux user,
> you'll put some energy in making Linux more "user comprehensible" NOW.
> As you know, not much ever happens in the way of mobilisation during
> summer, and next September, it might be too late. It's now or never.
> 
> GP
You Suck. :)

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


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