Linux-Misc Digest #357, Volume #18 Sat, 26 Dec 98 14:13:11 EST
Contents:
Multiple SCSI controllers, drive letter changing (Jack Ryan)
Re: Infringement of the GPL ([EMAIL PROTECTED])
Argh, MP3 player does not work! (Igor)
Re: Printing problems with Epson Stylus Color 640 ("Michael J. Saletnik")
Re: Does Linux support plug & play (Sid Kurias)
Re: Anti-Linux FUD ([EMAIL PROTECTED])
Re: Does Linux support plug & play (Ian Briggs)
Re: Changing CD ROMs ([EMAIL PROTECTED])
Re: Which book for newbie? (Jerry Lynn Kreps)
Re: Anti-Linux FUD (Jeremy Crabtree)
Re: Anti-Linux FUD (Jeff Read)
----------------------------------------------------------------------------
From: Jack Ryan <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.hardware
Subject: Multiple SCSI controllers, drive letter changing
Date: Sat, 26 Dec 1998 10:52:56 -0600
Hello,
I have built a *hot* linux box. But it has now got a problem with which
I hope someone can help me :)
I installed a ICP vortex SCSI controller and a NCR83xxx SCSI controller
both are pci, ide is off.
When I did the installation the only drive connected was a Ultra2 SCSI
on the ICP vortext.
The install went fine, assigning the drive id *sda*.
I then connected a cdrom, and 5 Jaz drives to the NCR controller.
The linux letter now on the *boot* drive moved from *sda* to *sdf*
I then disconnected all the drives on the NCR controller, rebooted and
got going again.
I then edit lilo.conf to change the device all reference from *sda* to
*sdf*. I also changes the *fstab* file in the same way. I ran
/sbin/lilo.
Thinking I was homefree I smiled and rebooted. It got further but I
think it's failing on trying to mount the swap.
Any help, would be appreciated, I'm up and going again, just with the
one Ultra2 drive.
Is there a way to tell linux to use the ICP controller as controller
zero and the NCR controller as controller 1, then the machine would keep
the letttering straight.
Thanks
Jack
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Infringement of the GPL
Date: Sat, 26 Dec 1998 16:06:16 GMT
Jerry Lynn Kreps writes:
> You're assuming that they made a valid improvement. They did not. They
> merely substituted one group for another. The efficacy remaind
> unchanged.
Then you should have no difficulty competing with them selling your
original design.
> Even if they had "improved" the effectiveness of the compound they were,
> like I was, standing on the shoulders of those who had gone before.
As does anyone who ever does anything.
> And don't give me that complaint that such and attitude toward spinoffs
> of publicly funded research would dry up research.
what 'attitude'? The only attitude I've seen so far is anger and
hostility.
> It was the taxpayers bucks that paid for it to begin with. Many of these
> "improvements" were learned by researchers but squirreled away while they
> were being paid out of public funds. Not honest enough to give true
> value for what they were paid for they are seduced by dreams of wealth,
> luxury and early retirement at other peoples expense by their thefts.
Good arguments against government funding of research.
> Taking money for someone elses work...
A statement which presumes that one can own intellectual work. This would
seem to contradict your statements above.
> ...is stealing from them,...
No. Stealing is depriving someone of property of which he had possession
before the theft. If A gives B a copy of A's work and B gives a copy of
that copy to C, A remains in possession of everything he was in possession
of before B made the 'unauthorized' copy.
> ...or denying them their right to allow others to benefit without
> monetary loss.
I can make no sense of this statement.
> He lost his rights to his own code and they now own it.
I wrote:
> Wrong.
> Think not? Just acquire their "prorpriatary" code and use it in your own
> software and see if they leave you alone.
They own the copyright on their code. He owns the copyright on his code.
They created a derivative work: one which contains both their work and his.
Either author may block copying of such a work. He chose not to do so (he
could change his mind at any time). This does not cause him to lose any of
his rights to his code.
--
John Hasler This posting is in the public domain.
[EMAIL PROTECTED] Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisconsin Do not send email advertisements to this address.
------------------------------
Date: Sat, 26 Dec 1998 10:07:46 -0600
From: [EMAIL PROTECTED] (Igor)
Subject: Argh, MP3 player does not work!
Reply-To: [EMAIL PROTECTED]
Something is strange with my system...
I am tyring to get it to play MP3 music. I downloaded xamp and xaudio.
Both give me troubles, when I try to play music all I hear is white
noise. Any suggestions why?
I have linux 2.0.35, a PAS16 card with SB emulation, Pentium 90 CPU,
and 64 megs of RAM.
At this moment, I am at a total loss. Any help will be appreciated.
============================================================================
char*p="char*p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
\=/, _-===-_-====-_-===-_-==========-_-====-_
| @___oo ( )_
/\ /\ / (___,,,}_--= )
) /^\) ^\/ _) =__ Anything is good and useful if )
) /^\/ _) (_ )
) _ / / _) ( it's made of chocolate. )
/\ )/\/ || | )_) (_ )
< > |(,,) )__) ( http://www.algebra.com/~ichudov )
|| / \)___)\ (_ _)
| \____( )___) )___ -==-_____-=====-_____-=====-___==
\______(_______;;; __;;;
------------------------------
From: "Michael J. Saletnik" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.questions
Subject: Re: Printing problems with Epson Stylus Color 640
Date: 26 Dec 1998 11:07:48 -0500
"Michael J. Saletnik" <[EMAIL PROTECTED]> writes:
> So to just print from the command line:
> gs @stc600ih.upp myFile.ps
And the sentence I forgot to write:
There are other modifications to printfilters, (ie, a uniprint entry
in printerdb), but overall those changes allow me to simply:
lpr myFile.ps
But ... the statement I quoted above is the direct, non-root-hacking
way to do it.
--
Michael J. Saletnik, PE Tufts E'91 G'93 <[EMAIL PROTECTED]>
Software Engineer, Thomson Financial Services
Registered Professional Structural Engineer
AIM: msaletni, ICQ: 24238794, www.tiac.net/users/icarus
------------------------------
From: Sid Kurias <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,alt.uu.comp.os.linux.questions
Subject: Re: Does Linux support plug & play
Date: Sat, 26 Dec 1998 11:02:59 -0500
I'm having the same problem, The serial port is set to irq 4 and
modem to 1rq 5 (under win95) and linux can't seem to detect the
modem correctly. Plug'n;play doesn't quite seem to be working right. I
use redhat 5.2
Sid
Thomas F. Ewald wrote:
> Luc De Cock <[EMAIL PROTECTED]> wrote in article
> <[EMAIL PROTECTED]>...
> > Pete wrote:
> >
> > > : Justin Headley <[EMAIL PROTECTED]> writes:
> > >
> > > :> what is wrong with PnP? I think it's one of the greatest things in
> the world.
> > > : > People don't have to fiddle with stupid jumpers anymore, sometimes
> the
> > > : > inexperienced ones actually ruining their card in the process, so
> they just
> > > : > slip it into the slot, and boot up.
> >
> > Linux supports PnP very well with PCI cards. ISA PnP is possible with the
> isapnp and
> > pnpdump tool.Luc.
> >
> Luc:
> Sounds interesting and useful. My PnP modem is on COM5 (via WIN95) and
> Linux can't find it. Could you
> run through a setp-by-step on how to use these utilities, please? Thanks.
>
> Tom
> >
------------------------------
From: [EMAIL PROTECTED] ([EMAIL PROTECTED])
Crossposted-To: alt.destroy.microsoft,comp.os.linux.advocacy,comp.os.os2.advocacy
Subject: Re: Anti-Linux FUD
Date: Sat, 26 Dec 1998 18:35:40 GMT
Let me add my $0.02 of opinion here,
On Sat, 26 Dec 1998 11:41:13 -0600, W R Carr wrote these
thought provoking words :
-> > Especially those two files. In Win95 even the DOS "kernel" is hardcoded to
-> > not let you touch them. (you can't even copy the buggers, making backup
-> > rather awkward)
->
-> In my experience, that's not true. It's a simple matter to execute "ATTRIB -S
-R -H *.*
-> /S" to have access to all files in the system and do anything desire. The same
is also
-> true in Windows 98. Pure DOS allows you to wreak havoc on any file you choose...
Yeah. Boot to a command line and enjoy. Copy anything you wish.
I would expect that these linux experts would know this. <laugh, duck
and running.>
-== Allie ==-
*----------------------*
Allie Martin (Mr.)
<[EMAIL PROTECTED]>
*---------/*\----------*
------------------------------
From: Ian Briggs <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,alt.uu.comp.os.linux.questions
Subject: Re: Does Linux support plug & play
Date: Sat, 26 Dec 1998 18:39:44 +0000
Thomas F. Ewald wrote:
> > Linux supports PnP very well with PCI cards. ISA PnP is possible with the
> isapnp and
> > pnpdump tool.Luc.
> >
> Luc:
> Sounds interesting and useful. My PnP modem is on COM5 (via WIN95) and
> Linux can't find it. Could you
> run through a setp-by-step on how to use these utilities, please? Thanks.
>
> Tom
I've recently managed to get my PNP modem running under Linux, as follows:
(1) find out address/IRQ settings in Windows
(2) disable PNP in motherboard BIOS
(3) run "pnpdump > /etc/isapnp.conf"
(4) edit /etc/isapnp.conf for the correct address and IRQ
Hope this helps. Good luck!
-- Ian --
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Changing CD ROMs
Date: Sat, 26 Dec 1998 18:41:02 GMT
Doug, use wmmount in X. If you're running windowmaker, it's a dock-app.
You can get it from http://mountapp.netpedia.net.
-Brent
Doug Andrews <[EMAIL PROTECTED]> wrote:
: Is there some, non-Xterm, way of changing from one CD to another while
: running Linux? When I used RedHat 5.1
: I used fstool to do this by unmounting, changing and then remounting.
: In RedHat 5.2 there seems to be no graphical tool by which I can mount
: and unmount file systems. i.e. fstool is no more.
: Thanks
: Doug
------------------------------
From: Jerry Lynn Kreps <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy
Subject: Re: Which book for newbie?
Date: Sat, 26 Dec 1998 10:08:47 -0600
As a recent newbie who has purchased tons of Linux books here are my
recommendations:
** Inside Linux, Randolph Bentson, SSC, 1996 ISBN:0-916151-89-1
As you can tell from the date, somewhat outdated. It is a light, breezy
description of Linux, mentioning the strong and the weak points. As a
programmer, I found it to be too light in many areas, but for the
non-professional Linux user it is probably a good read.
** Running Linux 2nd Edition, Matt Welsh & Lar Kaufman, O'Reilly &
Assc., 1996, ISBN: 1-56592-151-8
A MUST BUY for novice or expert! Even though a bit old, the command
useages it examples are current and typical. You will frequently
pagemark this book. If you have purchased either "Learning Linux in 24
hours" by Bill Ball, or an RH5 or SuSE disto then you have a manual
which is similar to Running Linux, but not as extensive. The manuals,
however, are more SPECIFIC to the distro than Running Linux. Even so, I
usually consult Running Linux unless I am dealing with YaST (SuSE) or an
RH specific software feature.
** Beginning Linux Programming, Neil Matthew & Richard Stone, WROX,
1997. ISBN: 1-874416-68-0
A GOOD BUY for the professional programmer *NEW* to Linux and Unix. Even
an aggressive, bright newbie should consider it. BUT, it DOES NOT
explain how to install or administer a Unix or Linux system. It assumes
NO prior knowledge of Unix or Linux and explains the Linux environment,
the shell, shell programming (very informative), terminals, Curses, Data
management, development tools, debugging, processes and signals, pipes,
sockets, Tcl, programming for X, programming for the Internet and CGI,
and portability issues.
It walks you through the development of a Curses CD collection
application.
** Linux Application Development, Erik W. Troan & Michael K Johnson,
Addison-Wesley, 1998, ISBN: 0-201-30821-5
A MUST BUY for the professional programmer *NEW* to Linux. All you
need to become knowledgeable about the Linux programming environment.
Still, it will take you time to come up to speed if you are new to C
programming. Lot's of terms and a whole culture to learn. But, this
book does it. Want to know how the make utility interprets the
Makefile? Explained. Plenty of code examples to put into emacs and
test out. (What? you don't use emacs? Your wasting time, son, get busy
and learn it! It's all you need for multi-file editing, version
control, Makefile editing, debugging and testing. In any language used
in Linux. All in one VERY cool package. Don't let the elaborate
keystroke command sequences put you off like it did me for a while.
Bite the bullet, jump in and go to work!)
** LINUX 6th Ed. The Complete Reference, Robert Kiesling editor, Linux
System Labs www.lsl.com, no ISBN. Order it from www.lsl.com
NICE, but not a must buy.
Three sections: 1 - Installing or upgrading Linux. 212 skimpy pages.
2. - 300 pages on administering a Linux system. 3. - 1000 pages of
Linux "How-to's". Now you can reach for that "How-to" when you are in
the middle of doing something and don't want to break open a new virtual
terminal so you can read an online How-to, assuming you have them on
line.
** Linux Complete Command Reference, Compiled by J. Purcell, Red Hat
Press, 1997, ISBN: 0-672-31104-6
A MUST BUY. Just what the title says. All those linux man and info
pages IN PRINT. Includes user commands, system calls, library
functions, special files, file formats, games, miscellaneous,
administration and privileged commands and kernel reference guide, to
quote the table of contents. Very Useful.
In an age when the printed manual accompanying the software is becoming
a thing of the past, this manual is a joy. Something you can take to
the library, ;->, and browse!
** Maximum RPM, Edward C. Bailey, Red Hat Press, 1997, ISBN:
0-672-31105-4
IF you are not running SuSE and so you don't have YaST then you need
this book. It tells all there is to know about the Red Hat Program
Manager, the primary tool for installing, updateing and removing
packages from a Linux system, except for those of us who simply use tar.
** The Linux Journal
You want to keep current with the latest in GPL and commerical Linux
software and hardware, don't you? Also, articles covering a wide range
of topics written by experienced Linux users and developers. When I was
in M$ stuff I read PC Magazine for the ads, also. The same with the
Linux Journal. Where else would you have found an NCR810 compatible
SCSI card for $53. Eh? The ads which appear and remain tell you the
future hardware and software. And, as much as I like GPL and free
software, it is the commercial side of Linux that is keeping an
expensive printed journal going. On the GPL side, every movement needs
an "offical" print mediam to spread the news. That may change as the 20
million Internet users expands to 100+ million but there will probably
be many Linux users out there who never follow comp.os.linux.misc or
browse much.
Online see the Linux Gazzette, a freebe.
[EMAIL PROTECTED] wrote:
>
> I've got quite a bit of dos/win31/win95 experience and would like to
> get experienced with Linux. The two books I'm considering as an
> initial purchase are:
> 1. Red Hat Linux Secrets 2 ed., by Naba Barkakati, IDG Books
> 2. Special Edition Using Linux 4 ed., by Jack Tackett & Steve Burnett,
> Que Books
>
> I'll probably end up buying some kind of reference as well. "Linux in
> a Nutshell", maybe?
>
> I'll probably be using RedHat. Is it worth trying other distributions
> as well?
>
> Thanks for any advice
------------------------------
From: [EMAIL PROTECTED] (Jeremy Crabtree)
Crossposted-To: alt.destroy.microsoft,comp.os.linux.advocacy,comp.os.os2.advocacy
Subject: Re: Anti-Linux FUD
Date: 26 Dec 1998 18:43:35 GMT
Reply-To: [EMAIL PROTECTED]
[EMAIL PROTECTED] allegedly wrote:
>Let me add my $0.02 of opinion here,
[SNIP, mostly because the formatting was atrocious, and I didn't
want to fix it]
>
>Yeah. Boot to a command line and enjoy. Copy anything you wish.
>
>I would expect that these linux experts would know this. <laugh, duck
>and running.>
Well, when you use the perfection that is BASH, you tend to let go of
the broken ways of DOS ;) (Also, it probably just slipped my mind)
(Or, CSH, or ASH, or PDKSH, or ZSH, or...)
--
"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: Jeff Read <[EMAIL PROTECTED]>
Crossposted-To: alt.destroy.microsoft,comp.os.linux.advocacy,comp.os.os2.advocacy
Subject: Re: Anti-Linux FUD
Date: Sat, 26 Dec 1998 13:45:38 -0500
"[EMAIL PROTECTED]" wrote:
> I don't know if this is related but I have a book here on the 9x/NT
> registry that states that the maximum size of an .ini file is 64Kb.
> This is why software vendors supplied .ini files of their own before
> the registry was designed.
Bullshit. If that's true, then that's due to an incredibly brain-dead
Microsoft API, and not to a fault of the idea of having .INI files. In
the Real World, text-based configuration files can be of any size. But
it is still a Good Thing to have one config file for each program rather
than lumping them all together into one huge heap.
> Because there was such a plethora of ini files all over the system
> there were hierarchical problems associated with this. If the win.ini
> file had a particular setting and an application's .ini file overrode
> that setting, who was responsible and where should a system-wide
> setting that had priority be made?
Depends on the application. An application with its own .INI file could
not override a setting that Windows uses with that .INI file. Each
application had to use its own judgement when deciding whih settings to
use. In the planned Microsoft Dictatorship in which Bill Gates tells you
what settings and interfaces to use and how to use them, that is
unacceptable.
> The ini files could easily be edited and tampered with by the
> inexperienced and mistakes could be made. Security was also an issue.
>
> The registry file size can be up to 40MB and it was made complex on
> purpose.
Security through obscurity. Microsoft obviously thinks its users are too
stupid to be given the opportunity to muck it up. Problem is, a
corrupted INI file can be fixed or rebuilt by someone with a little
basic knowledge. A corrupted registry file threatens the very integrity
of your system and is very difficult to repair without significant loss.
--
======================================================================
Jeff Read <[EMAIL PROTECTED]>/ http://genpc.home.ml.org
Unix / Linux / Windows Hacker, / Boycott Microsoft!
Anime & Sonic Fan, / Use Linux/GNU!
All Around Nice Guy / Let's keep the Net and the Land FREE!
======================================================================
------------------------------
** 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
******************************
