Linux-Advocacy Digest #664, Volume #26           Wed, 24 May 00 13:13:04 EDT

Contents:
  Re: Why only Microsoft should be allowed to create software ("Erik Funkenbusch")
  Re: Would a M$ Voluntary Split Save It? (Chris Wenham)
  Re: Need ideas for university funded project for linux (Dowe Keller)
  Re: W2K BSOD's documented *not* to be hardware (Was: lack of goals. ("Erik 
Funkenbusch")
  Re: Linux vs. Solaris Intel (R.E.Ballard ( Rex Ballard ))
  Re: how to enter a bug report against linux? (ggq15$[EMAIL PROTECTED])
  Re: how to enter a bug report against linux? (John Hasler)
  Re: Fun with Brain Dead Printers. (julien mills)
  Re: Font deuglification ?? (Bob Tennent)
  Re: Linux fails - again (Leslie Mikesell)
  Re: Fun with Brain Dead Printers. (Joe Pfeiffer)
  Re: how to enter a bug report against linux? (Leslie Mikesell)
  Re: Tholen invoked - Thread now dead (was Re: Would a M$ Voluntary Split Save It?) 
("Joe Malloy")
  Re: Windows by Day, Linux by Night (Streamer)
  Re: Fun with Brain Dead Printers. (JEDIDIAH)

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

From: "Erik Funkenbusch" <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.ms-windows.nt.advocacy,comp.os.os2.advocacy,comp.sys.mac.advocacy
Subject: Re: Why only Microsoft should be allowed to create software
Date: Wed, 24 May 2000 11:18:46 -0500

Marty <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> > Hmm.. interesting.  Windows requires a different version of himem.sys
than
> > the DOS version.  That means you are replacing windows distribution
files
> > with OS/2 versions in order to make it work, which is not what was
claimed
> > (that retail unmodified Windows 3.1 ran in a VDM).
>
> Himem.sys was a part of DOS, not Win3.1.  Try again.

Yes, it is.  But Windows shipped a different version, and when you install
Windows, it changes your config.sys to point to the version in the windows
directory.

Try again.




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

Crossposted-To: 
comp.os.os2.advocacy,comp.os.ms-windows.nt.advocacy,comp.sys.mac.advocacy
Subject: Re: Would a M$ Voluntary Split Save It?
From: Chris Wenham <[EMAIL PROTECTED]>
Date: Wed, 24 May 2000 16:11:46 GMT

josco <[EMAIL PROTECTED]> writes:

> I propose when they MS is split into an OS and Apps company that many of
> those who argued for MS will proclaim that MS won. MS always indented to
> be split into two companies, each with its own monopoly. 

 If you strike them down they will become more powerful than you can
 possibly imagine.

Regards,

Obi Wan Kenobi

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

From: [EMAIL PROTECTED] (Dowe Keller)
Crossposted-To: 
comp.os.linux,comp.os.linux.development,comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Need ideas for university funded project for linux
Date: 24 May 2000 09:28:00 -0700

On 23 May 2000 13:07:01 GMT, David T. Blake <[EMAIL PROTECTED]> wrote:
>David Steuber <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] (David T. Blake) writes:
>
>> ' Section 3b) (on modifications to QT)
>> ' When modifications to the Software are released under this
>> ' license, a non-exclusive royalty-free right is granted to the
>> ' initial developer of the Software to distribute your modification.
>> 
>> The right is non-exlusive.  That means everyone can get that right.  I 
>> think TrollTech is just trying to prevent forking of the Qt library
>> here.
>
>No, they are ensuring they can continue a revenue stream based
>on contributions from outside the company. They will take your
>modification and include it in QT Pro.
>
>> As I said previously, if you don't like the Qt license, you can
>> create your own library. There is no one to stop you. You can
>> also use one of the other available libraries.
>
>I was not arguing I should create a library. I was not arguing
>against QTs right to use whatever license they like. I was
>arguing that people should think twice before referring to QT
>licensing as substantially free or "open source". The right to
>fork is absent, the right not to have your contributions included
>in proprietary works (such as QT Pro) is gone, and QT gets a copy
>of EVERYTHING that even links to their code, even if it is not
>publicly available. 

I agree about the right to fork, but several free software licenses
(the X-Windows, and BSD licenses come to mind) allow people to make
proprietary software incorporating thier code (IIRC this is exactly
what Sun did, and BSDI does).  If I'm off track i.e. your talking
about something different, please clarify.

-- 
dowe                                            [EMAIL PROTECTED]
---
A formal parsing algorithm should not always be used.
                -- D. Gries

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

From: "Erik Funkenbusch" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.advocacy,comp.os.ms-windows.nt.advocacy
Subject: Re: W2K BSOD's documented *not* to be hardware (Was: lack of goals.
Date: Wed, 24 May 2000 11:26:04 -0500

Leslie Mikesell <[EMAIL PROTECTED]> wrote in message
news:8ggssi$19ke$[EMAIL PROTECTED]...
> >It is an application problem.  An application needs to have
> >the authority to open and close registry keys.  In the case
> >above, the system's memory is being used up because of an
> >infinite number of requests are being created.  The application
> >is doing this, and therefore, it is the application that
> >is causing the problem.  If the application were written to
> >properly handle the opening and closing of keys, there would
> >be no problems.
>
> Reasonable operating systems provide a method to limit the
> resources consumed by any application to a point where it
> cannot crash the system.

Unless said reasonable system has a bug which allows it to.  This is a bug.
The OS shouldn't allocate more resources than it can handle and should fail
the call before getting to that point.  Many OS's have bugs that allow
things which aren't supposed to happen, NT is not alone in that.

> If you look at the history of unix and the reasons resource
> limits were added, you will see that win2k needs them for
> the same reasons that were well known long ago.

Win2k has limits, They simply aren't easily user adjustable.





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

From: R.E.Ballard ( Rex Ballard ) <[EMAIL PROTECTED]>
Subject: Re: Linux vs. Solaris Intel
Date: Wed, 24 May 2000 16:08:12 GMT

In article <[EMAIL PROTECTED]>,
  2:1 <[EMAIL PROTECTED]> wrote:
> Can anyone comment on linux vs. solaris intel?
>
> I've only used it from a users point of view (such as now),
> and have noticed a few things (like the X server seem a bit slow)
> but they don't really say much.
>
> Can anyone do a better comparison?

Solaris 86 is Sun's attempt to get a foot into the PC market.
It is one of several commercial grade products, including SCO
UNIX and Lynx which are based on more traditional BSD and
AT&T kernels.

The advantages are that the BSD/AT&T kernels have been pretty stable,
and have been field-tested in a number of "Battleground" situations.

Solaris has two drawbacks, both of which have nothing to do with
the technical merits.

First, Solaris is a proprietary operating system licensed by Sun.
Sun competes with other UNIX vendors such as IBM, HP, and DEC/Compaq
which aren't too keen on turning Sun into another "Microsoft".  This
is the same problem that plagues IBM's OS/2, SCO's UNIX, and UnixWare.
Linux gives all UNIX vendors the opportinity to capitalize on the
market generated and created by Linux.

Second, Solaris for Intel is the "second string" product, intended
as more of a prototyping tool for developers who wish to develop
applications for Sun servers, but need a prototyping system that
works on Laptops and Desktop PCs.  Solaris for Intel isn't really
treated like a strategic product.  Most of the Solaris/Sparc
applications have not been ported to Intel.  Intel device support
isn't as broad.  And third party support for Solaris/Intel is not
significant.

Some companies, like IBM are agressively supporting Linux on all
product lines from their Handhelds to their System 390 mainframes.
Others like Sun and HP are making their RISC versions of UNIX
source code compatible with Linux.  In some cases, the Linux and
UNIX implementations can even run common binaries.

The good news for developers is that they can implement for Linux
on a cheap PC, and very quickly port to Solaris and other core
systems.  Ironically, Linux developers have been more effective
at using "Unix" tools than Sun has been, primarily because of
Sun's commitement to Java based technologies.  Ironically,
Sun's lack of support for Java for Linux (Linux was often several
months behind NT) resulted in less support for Java within the
Linux user community (actually more support for other technologies).

Since Linux lacket the really fine Java tools, development efforts
for Linux often focused around Perl/TK, Python, and TCL, which had
better support for Fork() based implementations.

> -Ed

--
Rex Ballard - Open Source Advocate, Internet
I/T Architect, MIS Director
http://www.open4success.com
Linux - 60 million satisfied users worldwide
and growing at over 1%/week!


Sent via Deja.com http://www.deja.com/
Before you buy.

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

From: ggq15$[EMAIL PROTECTED]
Crossposted-To: comp.os.linux.misc
Subject: Re: how to enter a bug report against linux?
Date: 24 May 2000 08:23:01 -0700

In article <8ggq15$1650$[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
 
> The openness of Linux is a plus in this area,
>but the lack of a central and official repository for bug tracking
>and status is a big minus.
>
>  Les Mikesell
 
we dont need no freek'ng central bug tracking for linux kernel. if
you have a problem, search the web or ask Alan Cox or post a question
on a linux news group (there are tones of 'em).

This is Linux, this is aint no stupied windows. If you do not like
it, go stick to your crappy windoz and leave us alone, we are
coding kernel stuff here, not some bloody user program.

bug tacking and testing crap system aint never gona be pushed down
our throats, get over it, I agree with Peter, this is how it always 
was and always will. This is the Linux way.

got a problem, send email to Alan. This is our bug tracking system. period.

 


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

From: John Hasler <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: how to enter a bug report against linux?
Date: Wed, 24 May 2000 12:42:12 GMT

Peter writes:
> Report an interesting bug, and it'll be fixed in a jiffy.

Known bugs are not interesting.  It's hard to find out if a bug is known.

>  Boring bugs indeed will be forgotten.

And then reported again by people who are not aware that they are known.

> I believe that's known.

If there was a kernel BTS you could easily know for sure.

> I believe that's known.  I've seen several threads go past on the scsi
> problem in 2.3.99 and above.  Doug's working on it.  Ask him!

And waste his time with something you believe that he may already know
about?  I expect I would just get a testy reply telling me not to send in
bugs with out researching them first.

I wrote:
> ...was a kernel BTS I'd research the problem there and either test any
> fix...

Peter writes:
> EH? Why don't you mail the maintainer?

Anyone who imagines that he has found a new kernel bug should email a
maintainer?  How are the maintainers to get any work done?

> That's debian practice too!

Filing a bug via the Debian BTS does email the maintainer.  Emailing a
Debian maintainer without checking the BTS first will often get you
directed to the BTS.

> As you know, you might get Alan's interest on that one too.

what makes you think I know any such thing?

> Make sure at least Doug knows about it.

If there was a kernel BTS I could do so in a few minutes.  I'm not willing
to root about in an email archive, though: sound isn't that important to
me.  And I won't risk irritating the maintainer by being the 130th one to
report a known bug.

Besides, I don't know who 'Doug' is or why you assume that I know that this
bug should go to him.
-- 
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI




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

From: julien mills <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: Fun with Brain Dead Printers.
Date: Wed, 24 May 2000 12:20:46 -0400
Reply-To: [EMAIL PROTECTED]

Svend Garnaes wrote:
> 
> Johan Kullstam wrote:
> 
> > you will want to make a printer driver that inserts printer cursor
> > positioning commands (like \r) in the appropriate places.
> >
> > unix text files have end-of-line marker LF. for terminals or printers
> > LF means line feed, but leave the cursor in the same column.  to get
> > back to the start of the line, you need a carriage return CR.
> > termcap and cooked mode does this for terminals.  surely there is a
> > method that works for printers.
> 
> In RedHat Linux you would use printtool to set the 'Fix Staircase'
> option for the printer. It results in the file textonly.cfg in the
> printer's spool directory containing the line CRLFTRANS=1, which
> does the trick.

You could pipe your print jobs through a sed script which added a 
CTRL-M (carriage return) to the end of each line.  I belive this
is the traditional solution.

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

From: [EMAIL PROTECTED] (Bob Tennent)
Subject: Re: Font deuglification ??
Date: 24 May 2000 16:17:34 GMT
Reply-To: [EMAIL PROTECTED]

On Thu, 25 May 2000 01:45:21 +1000, Steve Budak wrote:
 >Howdy, I can't seem to find the howto for font deuglification in RedHat
 >Linux 6.2

http://www.linuxdoc.org/HOWTO/mini/FDU.html

Bob T.

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

From: [EMAIL PROTECTED] (Leslie Mikesell)
Subject: Re: Linux fails - again
Date: 24 May 2000 11:23:04 -0500

In article <8gfqoc$gm5$[EMAIL PROTECTED]>,
Sam E. Trenholme <[EMAIL PROTECTED]> wrote:
>>Odd that you don't just add the NFS patches, or run the VALinux
>>kernel that includes them, or use amanda, or pipe the tar
>>copies over rsh/ssh. 
>
>Where do you get the NFS patches?  Sorry to interupt this newsgroup with a
>request for useful information.

I got tired of tracking them down for every kernel release and matching
the patches to the kernel and utilities, so I just run the
VALinux distribution on servers that need NFS. There are
iso images as well as SRPMS and a normal distribution directory
under:
ftp://ftp.valinux.com/pub/software/VALinux/6.2.1/

There are directions for doing it the hard way at
ftp://ftp.valinux.com/pub/support/hjl/knfsd/README.nfs

I suspect you could drop the VAlinux kernel and knfs utilities
into a different distribution (at least RH) or do an
upgrade against a RedHat system, but I have always done a
clean install. 

>I personally prefer logical disk partition names ("hda" makes a lot more
>sense than "c0t0d0s2"),

Hda makes sense because it specifies a particular location. Sda
does not, because it is mapped at boot time in the order the
devices are detected.  Adding or removing a SCSI drive can
change the names of all the others where they would stay fixed
in the cntndnsn scheme.

  Les Mikesell
   [EMAIL PROTECTED]

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

From: Joe Pfeiffer <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: Fun with Brain Dead Printers.
Date: 24 May 2000 10:19:20 -0600

Nothing brain dead about it -- but why are you jumping to the
conclusion that your printer is somehow unique in doing this, and that
this particular wheel has yet to be invented?

Get any of the standard sets of printer filters and configure it to
fix stairstepping.  If you're running RedHat you can just check a box
in the printer configuration from the control panel (and I assume
there is something equally simple in the other distributions).

ASCII doesn't specify a character to be used as the end-of-line
character.  I'd guess that the Record Separator character would have
been a good choice (though I'd have to find some more complete
documentation on the intent of the control characters to be anywhere
near sure), but neither MS-DOS nor Unix used it; MS-DOS confused line
separation with device control and uses a CR-LF pair; Unix picked a LF
(and calls it newline).
-- 
Joseph J. Pfeiffer, Jr., Ph.D.       Phone -- (505) 646-1605
Department of Computer Science       FAX   -- (505) 646-1002
New Mexico State University          http://www.cs.nmsu.edu/~pfeiffer
VL 2000 Homepage:  http://www.cs.orst.edu/~burnett/vl2000/

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

From: [EMAIL PROTECTED] (Leslie Mikesell)
Crossposted-To: comp.os.linux.misc
Subject: Re: how to enter a bug report against linux?
Date: 24 May 2000 11:41:47 -0500

In article <[EMAIL PROTECTED]>,
Full Name <[EMAIL PROTECTED]> wrote:
>
>Any serious administrator who reads this thread would have to discard
>Linux as a bad joke.

Except that it is better than the alternatives that go through
some of the right motions.

>The more I read the more I believe Linux advocates are nothing more
>than children who have found a new toy to play with.

You have been wrong about a lot of other things.  What's one more?

 Les Mikesell
   [EMAIL PROTECTED] 


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

From: "Joe Malloy" <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.os2.advocacy,comp.os.ms-windows.nt.advocacy,comp.sys.mac.advocacy
Subject: Re: Tholen invoked - Thread now dead (was Re: Would a M$ Voluntary Split Save 
It?)
Date: Wed, 24 May 2000 12:45:35 -0400

The Tholen tholens:

> > We sic Tholen onto you.
>
> Who is "we"?

The *real* question is how sic [sic!] is Tholen?
--

"USB, idiot, stands for Universal Serial Bus. There is no power on the
output socket of any USB port I have ever seen" - Bob Germer



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

From: Streamer <[EMAIL PROTECTED]>
Subject: Re: Windows by Day, Linux by Night
Date: Wed, 24 May 2000 11:19:38 -0500

Nathaniel Jay Lee wrote:

> 2:1 wrote:
> >
> > Erik Funkenbusch wrote:
> > >
> > > mlw <[EMAIL PROTECTED]> wrote in message
> > > news:[EMAIL PROTECTED]...
> > > > > Simone Paddock
> > > > > O'Reilly & Associates
> > > > > [EMAIL PROTECTED]
> > > > > www.oreilly.com
> > > >
> > > > So what is the point of this? This is the "LINUX" advocacy group, not a
> > > > Windows group. If you want to attract Windows users to read the book, go
> > > > to the windows advocacy groups. The notion that we who use Linux and
> > > > feel comfortable with it, simply need a Windows 9x in a nutshell book is
> > > > insane. I know Windows, I have used every version of MS Windows ever
> > > > made, and I mean that!! Go away, troll.
> > >
> > > Did you even read the article?  The article is written FOR Linux users (as
> > > is the book).
> >
> > I was a 'doze user long before i was a UNIX user. Ever since I first saw
> > UNIX (this was when I was a kid, and before i had heard of linux) I
> > perfered it. A few years ago, when I found a linux distro in a shop
> > (hey, long downloads cost over here) I installed it and never went back
> > (except for games). I'm sure that there are many linux users who had
> > much more experience with windows before installing linux (like me), and
> > therefore won't be interested in a book telling us how to use something
> > we dislike.
> >
> > -Ed
> >
> > --
> > Did you know that the reason that windows steam up in cold weather is
> > because
> > of all the fish in the atmosphere?
> >         -The Hackenthorpe Book Of Lies
>
> It looks like everyone missed the point of the original post.  If you
> had read the article, you would have seen that this book is aimed at
> those of us who are forced to use Windows for various reasons, but
> prefer Linux when we can use it.

You missed reading between the lines.  This book, as stated in the original post,
was written for Windows Users (any Windows users...not just people forced to use
Windows as you're trying to state).  To paraphrase, apparently the book didn't
sell well, so this is just another idea by O'reilley's marketing to help
stimulate sales of the book.....by trying to trick us into thinking this book was
written for Linux/Any other OS user.  Apparently the books sales are so flat that
they would even try a promotion for the first 1000 people just to see if they
could get more people buying the book.

================
My opinions are not my employers.



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

From: [EMAIL PROTECTED] (JEDIDIAH)
Crossposted-To: comp.os.linux.hardware
Subject: Re: Fun with Brain Dead Printers.
Date: Wed, 24 May 2000 16:58:12 GMT

On 24 May 2000 10:19:20 -0600, Joe Pfeiffer <[EMAIL PROTECTED]> wrote:
>Nothing brain dead about it -- but why are you jumping to the
>conclusion that your printer is somehow unique in doing this, and that
>this particular wheel has yet to be invented?

        Actually, there are commands in PCL3 to change this sort of behaivor.

[deletia]

        So, it's not like all printer manufacturers are completely oblivious
        to end of line issues...

-- 

    In what language does 'open' mean 'execute the evil contents of'    |||
    a document?      --Les Mikesell                                    / | \
    
                                      Need sane PPP docs? Try 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.advocacy) 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-Advocacy Digest
******************************

Reply via email to