Linux-Setup Digest #895, Volume #20 Fri, 23 Mar 01 14:13:10 EST
Contents:
Re: Linux <scream>Frustration!</scream> (Laura Goodwin)
Mandrake 7.1 vs Mandrake 7.2 ? (peter)
Re: php probs ("Josh Warren")
Printer set-up problem (David Courard-Hauri)
Re: Coyote Linux & Linksys Ethernet card ("Stephen E. Canell")
Re: RPM exe upgrade v3 => v4 (=?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?=)
IRQ revelation command ("Allan Jones, ComUnity Systems")
Re: Linux <scream>Frustration!</scream> (olgnuby)
Re: SuSe Linux 7.2 or Redhat??? ("Scot Mc Pherson")
Re: Coyote Linux & Linksys Ethernet card ("Karl W. Schaefer")
----------------------------------------------------------------------------
From: Laura Goodwin <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware.pc-homebuilt
Subject: Re: Linux <scream>Frustration!</scream>
Date: Fri, 23 Mar 2001 12:17:11 -0500
Thumper wrote:
>
> I was using that as a response that newbies get a lot. I avoid a recompile
> like the plague when I can..:) But will do it when I have to.
Speaking of recompiling, isn't there a groovy way to rerun the automatic
hardware detection that runs at first install, instead of having to muck
through all the hardware config by hand? If not, ding-dong it, there
should be!
------------------------------
From: peter <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Mandrake 7.1 vs Mandrake 7.2 ?
Date: Fri, 23 Mar 2001 17:01:53 GMT
What are the major differences ?
-KDE ?
-Kernel ?
Which do you like better ?
Why ?
I'm running 7.1, should I upgrade to 7.2 ?
What will be different ?
Peter
------------------------------
From: "Josh Warren" <[EMAIL PROTECTED]>
Subject: Re: php probs
Date: Fri, 23 Mar 2001 10:31:33 -0700
john
my $CFG_LIBEXECDIR = 'modules';
change 'modules' to '/usr/lib/apache'.
my $CFG_LD_SHLIB = 'q(-gcc)';
my $CFG_LDFLAGS_SHLIB = q(-shared);
the above changes to /usr/bin/apxs file would have correct the apache-devel
to support PHP. the apache-devel RPM must be installed and you have to use
the PHP tarball.
"Michael Heiming" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Jonathan Snyder wrote:
> >
> > Yes, this what I already had uncommented in my httpd.conf file:
> >
> > # The following is for PHP4 (conficts with PHP/FI, below):
> > <IfModule mod_php4.c>
> > AddType application/x-httpd-php .php4 .php3 .phtml .php
> > AddType application/x-httpd-php-source .phps
> > </IfModule>
> >
> > # The following is for PHP3:
> > <IfModule mod_php3.c>
> > AddType application/x-httpd-php3 .php3
>
> That makes no sence to me, you define .php3 to be handled with PHP4 above,
> now you want to handle .php3 with the PHP3 engine?
>
> > AddType application/x-httpd-php3-source .phps
> > </IfModule>
> >
> > # The following is for PHP/FI (PHP2):
> > <IfModule mod_php.c>
> > AddType application/x-httpd-php .phtml
> > </IfModule>
> >
> > However I still get text to come up instead of having the script run.
>
> Do you load mod_php in httpd-conf or preload via apache start script?
>
> Try setting something like this in your httpd.conf (Where the other
modules are
> loaded):
>
> LoadModule php4_module /usr/lib/apache/libphp4.so
>
> AddModule mod_php4.c
>
> you need something like this for php3 too, but both modules must have been
> compiled
> with --enable-versioning or PHP3 and PHP4 will not work toogether...
>
> Good luck
>
> Michael Heiming
>
------------------------------
From: David Courard-Hauri <[EMAIL PROTECTED]>
Subject: Printer set-up problem
Date: Fri, 23 Mar 2001 11:29:18 -0500
I am having trouble setting up my printer. Jobs start (i.e. I see them
with
lpq), but then they are removed about a minute later without any
communication
that I can see with the printer. Earlier, I got a message that it
couldn't
find localhost, so I figured that I had the Hosts file messed up, but I
futzed around and now I don't get that anymore. However, now I don't
get any
written errors at all that I know of (I don't see any /var/log/lpd-errs
file,
is there somewhere else I should look?). I know that the printer is
installed
properly because it works when I boot the machine in Windows (but I
never do
that anymore!). The Print Tool finds a printer at /dev/lp0, but if I
cat a
file there, nothing happens (no blinking light, no nothing). I am using
Red
Hat 7.0.
Any thoughts on what I might try or where I might look for more
troubleshooting info would be greatly appreciated.
=======================================================
David Courard-Hauri
Assistant Professor of Environmental Science and Policy
Drake University -- Olin Hall
2507 University Avenue
Des Moines, IA 50311
voice: 515.271.3812
fax: 515.271.3702
[EMAIL PROTECTED]
=======================================================
------------------------------
From: "Stephen E. Canell" <[EMAIL PROTECTED]>
Subject: Re: Coyote Linux & Linksys Ethernet card
Date: Fri, 23 Mar 2001 08:58:12 -0800
Karl,
You need to get the latest tulip driver, build it and
place the module into you /lib/modules/<kernel version>.
Also, though they don't tell you this, the latest
version also requires an associated pci driver... I
think it is called pci-scan.o...
Check out:
http://www.telematik.informatik.uni-karlsruhe.de/lehre/seminare/LinuxSem/downloads/netfilter/iptables-HOWTO-6.html
Karl W. Schaefer wrote:
> Hello all,
>
> I've been following some of the postings in comp.os.linux.dial-up, .misc,
> ..networking, and .setup for a while, just trying to gather wisdom from those
> of you who are willing to graciously share. And as a newbie, I give much
> thanks for your efforts with us not-so-ready-for-prime-time folks.
>
> I essentially have three questions/problems, and for brevity and you
> power-answer people, will say them here, and elaborate further on. They
> are:
> 1.) LinkSys LNE2000T 16-bit Ethernet card not coming up.
> 2.) Don't fully understand assignment of an IP to the ppp0 interface during
> makefloppy.sh, or the subnet.
> 3.) How can I test the ppp0 interface from the Coyote machine?
>
> One thing I've learned, is that it would be foolish to try to set up a
> web portal for my local home network on a fully loaded Linux installation.
> And I take such recommendations seriously. I've since obtained a small
> machine and would like to get Coyote Linux running on it as an interface
> from my small home network to the internet. I've been using W98se's ICS,
> and somewhat satisfied with it actually - but wish to use something with
> more control available, as well as learn more about it along the way (gee,
> sounds like a perfect fit for ummm... Linux!)
>
> I downloaded the source from www.coyotelinux.com, and using my RH7.0
> installation, ran the makefloppy.sh, and found everything quite easy. I was
> then able to boot up into Coyote Linux with success on the small machine
> I've aquired. It has a Am486DX4-Plus CPU, runs at 100Mhz, 32MB RAM.
>
> I've put in a LinkSys brand "Ether16 10BaseT LAN Card", Model No:
> LNE2000T and am able to use it no problems in W95. I know from experiences
> with my RH7.0 install, and a LinkSys LNE100TX Version 4 - that I needed to
> use the tulip driver. I even reverified that in documentation I have.
>
> Well, here's the short of it, when I boot the machine up in Coyote Linux,
> the ethernet device will not come up. These are the messages I see:
>
> /lib/modules/tulip.o init_module: Device or resource busy
> SIOCSIFADDR: Operation not supported by device
> eth0: unknown interface
> SIOCSIFNETMASK: Operation not supported by device
> SIOCSIFBRADDR: Operation not supported by device
> eth0: unknown interface
>
>
> I thought perhaps it was the tulip driver supplied with the distribution,
> and figured, a good test for that would be to boot up my linux box with the
> disk - and whaddaya know, it worked ok there. So I am confident that this
> tulip driver works, and therefore suspect something with my hardware.
>
> So, does anyone have some experience they are willing to share with me,
> on how to get beyond the booting "Device or resource busy" message with
> Coyote Linux?
>
> And one question concerning setup. In the questions asked, one was what
> IP to give the ppp interface. It recommended 192.168.0.3, and said as long
> as it is in the same subnet, all is fine. Well, I switched to use
> 192.168.2.1 as my Coyote IP to my local LAN - but why do I have to supply an
> IP for the ppp0 device, when my ISP does that at the time I make the call?
> Guess I am also questioning, should I use 192.168.2.x for that input, or
> leave it at 192.168.0.3? How do I know I am in the same subnet, or even
> designate my subnet?
>
> The last question (for now *grin*), is how can I test the ppp0 device,
> from the local machine? Do I simply want to say "pppd call isp" ??
>
>
> Thank you all,
>
> --
> Karl W. Schaefer
>
> Remove the obvious between and including
> the underscores, and then you'll reach me :-)
--
Stephen E. Canell
Technical Lead, UNIX SA
Institutional Business Systems
Jet Propulsion Laboratory
4800 Oak Grove Dr.
Pasadena, Calif. 91109
818-354-1731
------------------------------
From: =?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?= <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: RPM exe upgrade v3 => v4
Date: Fri, 23 Mar 2001 19:07:17 +0100
On Tue, 20 Mar 2001, Cyrille wrote:
> I would like to know how to upgrade the RPM tool
> from version 3x to 4x.
>
> If I try rpm -U --test for package I found , rpm says :
>
> [root@ktaland2 src]# rpm -U --test rpm-4.0-4.4.src.rpm
> only packages with major numbers <= 3 are supported by this version of
> RPM
> error: rpm-4.0-4.4.src.rpm cannot be installed
>
> Do you know how to upgrade RPM ???
You have to upgrade to 3.0.5, which support v4 files, and then upgrade
to 4.0.
Rasmus
--
-- [ Rasmus 'M�ffe' B�g Hansen ] --------------------------------------
If you only have a hammer
everything looks like a nail
========================================= [ Remove 'spam' to reply ] ==
------------------------------
From: "Allan Jones, ComUnity Systems" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.questions,linux.redhat
Subject: IRQ revelation command
Date: Fri, 23 Mar 2001 17:57:53 GMT
Is there a way to reveal which IRQ's are being used?
I am trying to install a second NIC by inserting a script at the end of
lilo.conf
so it will probe for the second card:
append="ether=11,0x6500,eth0 ether=17,0xccc0,eth1
where "ether=17" is the IRQ
at address "0xccc0"
assigning "eth1"
[a la' Red Hat Linux Bible p. 513]
I found the settings for eth0 with the ifconfig command, and I am assuming
that the "c's"
in 0xccc0 are variables that will be replaced (or something).
How can I find out exactly what settings to include?
------------------------------
From: olgnuby <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware.pc-homebuilt
Subject: Re: Linux <scream>Frustration!</scream>
Date: Fri, 23 Mar 2001 12:14:20 -0600
Laura Goodwin wrote:
> Speaking of recompiling, isn't there a groovy way to rerun the automatic
> hardware detection that runs at first install, instead of having to muck
> through all the hardware config by hand? If not, ding-dong it, there
> should be!
Dunno, been a long time it seems since I took a sledge hammer to my MDK
7.2 CD distribution and a brillo pad to my disk to get rid of it, but it
seems like I remember something about, (if you didn't disable it in
system startup) HardDrake will run each time on system start up and
detect any new hardware recently installed and unconfigured. Of course
all that is dependent on whether the hardware is pnp, isapnp, plug and
pray or just uncouth manufacturers preying type stuff. ;-) There are
some config parameters in HardDrake as to what kind of probe options to
run etc.
I don't know what version of the 7.2 distribution you have Laura, but if
it's the one that I have (didn't really bash it up. just need to take a
break from it for a spell) most of the stuff on it, KDE, XFree, and a
lot of other stuff is pre release and the best and firstest thing a
person can do is as soon as they gets it installed is log straight onto
Mandrake Update and do about a five hour download at 56k and update
everything on the system. I played with it for about two weeks before I
did that and it was about like a Mississippi Delta porch light on a hot
August night. Once I did that, things smoothed out and started working
pretty good. It also comes with both a 3.something release of XFree and
a 4.something kind of pre release that it may or not install according
to what kind of vid card it detects or you choose for it. During the
config it will tell you that possibly your card is capable of 3D
acceleration with the later and ask you which you want, but put up two
windows with the same thing in them for you to click on. The one on the
right seems to be typo in the distro and actually, I think is the
4.something. At least that is what I finally got it to do to use XFree86
4 version. You will probably wind up with an /etc/X11/XF86Config and an
XF86config-4. My 8 meg of vid memory caused me some color problems until
I disabled the vga color console stuff by eliminating the frame buffer
in console start up.
Actually getting back to where I started, I did upgrade the kernel to
2.4.0 and configed for isapnp and pnp as loadable modules support for
kernel auto module loading and then set my /etc/modules.conf with the
necessary options to auto load any of my modules as needed. The v4l
config on the original kernel is kind of grungy and to really make use
of your WinTV card, FM tuner capabilities and other good stuff that you
have in that home made puter of yours, an up date might be in order.
Mandrake 7.2 is gonna be a good distribution, or can be a good distro if
a person works with it and learns all the under the hood configuration
that can be done with it.
Good luck. Have fun. It's worth it in the long run.
Charlie (probably one of the world's oldest Linux Users)
PS: helps to get full qt install of 1 and 2 versions to match up with
your KDE also if you plan to do any builds from source of KDE apps.
------------------------------
From: "Scot Mc Pherson" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.questions
Subject: Re: SuSe Linux 7.2 or Redhat???
Date: Fri, 23 Mar 2001 18:53:31 GMT
If you are planning on workstations, I would suggest SuSE because they have
tweaked some nice stuff in the desktop environment. I used to like RedHat
for this environment but the latest version has got some problems.
For Servers I would suggest Debian or if you have some experience or aren;t
afraid to dive in, get Slackware...
RedHat used to be really great in my opinion, but the latest version has
given me loads of trouble...If you like redhat, use version 6.2 for server
environments.
Workstations SuSE & RedHat
Servers and Routers Debian and Slackware.
--
Scot Mc Pherson
N27� 19' 56"
W82� 30' 39"
"TD" <[EMAIL PROTECTED]> wrote in message
news:vigu6.18157$[EMAIL PROTECTED]...
> I'm considering purchasing a retail version of Linux. Is there a
preferred
> or recommended version of this software? Comp USA has Mandrake, SuSe,
> Redhat.
>
> Thanks for your help.
>
> TD
>
>
>
> --
> Sandy Valley Ranch ~ Your Western Adventure
> www.sandyvalleyranch.com
>
>
------------------------------
From: "Karl W. Schaefer" <[EMAIL PROTECTED]>
Subject: Re: Coyote Linux & Linksys Ethernet card
Date: Fri, 23 Mar 2001 14:09:50 -0500
I thought the driver was ok, because it worked with my newer card on the RH
system, that's why I booted it on that system too, to test the tulip.o.
Since it came up ok there, I thought should be ok there too - as well as I
did not need the pci-scan.o when booting on my "fancier" machine, which
booted fine with the Coyote Linux floppy.
I checked out your link, but that's all talking about iptables, I see no
relevance to the pci-scan, nor other issues I was asking about. Could you
be more specific on what it is you desire me to observe in that link please?
thanks
--
Karl W. Schaefer
Remove the obvious between and including
the underscores, and then you'll reach me :-)
"Stephen E. Canell" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Karl,
> You need to get the latest tulip driver, build it and
> place the module into you /lib/modules/<kernel version>.
>
> Also, though they don't tell you this, the latest
> version also requires an associated pci driver... I
> think it is called pci-scan.o...
>
> Check out:
>
http://www.telematik.informatik.uni-karlsruhe.de/lehre/seminare/LinuxSem/dow
nloads/netfilter/iptables-HOWTO-6.html
>
>
> Karl W. Schaefer wrote:
>
> > Hello all,
> >
> > I've been following some of the postings in comp.os.linux.dial-up,
.misc,
> > ..networking, and .setup for a while, just trying to gather wisdom from
those
> > of you who are willing to graciously share. And as a newbie, I give
much
> > thanks for your efforts with us not-so-ready-for-prime-time folks.
> >
> > I essentially have three questions/problems, and for brevity and you
> > power-answer people, will say them here, and elaborate further on. They
> > are:
> > 1.) LinkSys LNE2000T 16-bit Ethernet card not coming up.
> > 2.) Don't fully understand assignment of an IP to the ppp0 interface
during
> > makefloppy.sh, or the subnet.
> > 3.) How can I test the ppp0 interface from the Coyote machine?
> >
> > One thing I've learned, is that it would be foolish to try to set up
a
> > web portal for my local home network on a fully loaded Linux
installation.
> > And I take such recommendations seriously. I've since obtained a small
> > machine and would like to get Coyote Linux running on it as an interface
> > from my small home network to the internet. I've been using W98se's
ICS,
> > and somewhat satisfied with it actually - but wish to use something with
> > more control available, as well as learn more about it along the way
(gee,
> > sounds like a perfect fit for ummm... Linux!)
> >
> > I downloaded the source from www.coyotelinux.com, and using my RH7.0
> > installation, ran the makefloppy.sh, and found everything quite easy. I
was
> > then able to boot up into Coyote Linux with success on the small machine
> > I've aquired. It has a Am486DX4-Plus CPU, runs at 100Mhz, 32MB RAM.
> >
> > I've put in a LinkSys brand "Ether16 10BaseT LAN Card", Model No:
> > LNE2000T and am able to use it no problems in W95. I know from
experiences
> > with my RH7.0 install, and a LinkSys LNE100TX Version 4 - that I needed
to
> > use the tulip driver. I even reverified that in documentation I have.
> >
> > Well, here's the short of it, when I boot the machine up in Coyote
Linux,
> > the ethernet device will not come up. These are the messages I see:
> >
> > /lib/modules/tulip.o init_module: Device or resource busy
> > SIOCSIFADDR: Operation not supported by device
> > eth0: unknown interface
> > SIOCSIFNETMASK: Operation not supported by device
> > SIOCSIFBRADDR: Operation not supported by device
> > eth0: unknown interface
> >
> >
> > I thought perhaps it was the tulip driver supplied with the
distribution,
> > and figured, a good test for that would be to boot up my linux box with
the
> > disk - and whaddaya know, it worked ok there. So I am confident that
this
> > tulip driver works, and therefore suspect something with my hardware.
> >
> > So, does anyone have some experience they are willing to share with
me,
> > on how to get beyond the booting "Device or resource busy" message with
> > Coyote Linux?
> >
> > And one question concerning setup. In the questions asked, one was
what
> > IP to give the ppp interface. It recommended 192.168.0.3, and said as
long
> > as it is in the same subnet, all is fine. Well, I switched to use
> > 192.168.2.1 as my Coyote IP to my local LAN - but why do I have to
supply an
> > IP for the ppp0 device, when my ISP does that at the time I make the
call?
> > Guess I am also questioning, should I use 192.168.2.x for that input, or
> > leave it at 192.168.0.3? How do I know I am in the same subnet, or even
> > designate my subnet?
> >
> > The last question (for now *grin*), is how can I test the ppp0
device,
> > from the local machine? Do I simply want to say "pppd call isp" ??
> >
> >
> > Thank you all,
> >
> > --
> > Karl W. Schaefer
> >
> > Remove the obvious between and including
> > the underscores, and then you'll reach me :-)
>
>
> --
> Stephen E. Canell
> Technical Lead, UNIX SA
> Institutional Business Systems
> Jet Propulsion Laboratory
> 4800 Oak Grove Dr.
> Pasadena, Calif. 91109
> 818-354-1731
>
------------------------------
** 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 by posting to comp.os.linux.setup.
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-Setup Digest
******************************
