Linux-Misc Digest #761, Volume #27 Tue, 1 May 01 21:13:02 EDT
Contents:
File System going bad (Scott)
Re: Multiple mount point for 1 partition (Grant Edwards)
Re: gethostbyname_r in glibc 2.2? (Paul Kimoto)
Apache php4 and Postgresql !!! ("Nunzio Falcone")
Re: Quake3 + XFree86-4.0.3 + Voodoo3 = Death Slow (Richard Laskey)
Re: File System going bad ("Peter T. Breuer")
Redhat 7.1 and Sun Java JDK1.3 ("Jeremy Haile")
right suggestions for sendmail with multi-domaine/setup ("Paul")
modem driver, kernal, and other distro (Farrell Farahbod)
Re: File System going bad
grub default values (Timothy Washington)
Re: smart media and linux? (esp. w/ notebooks) (Dances With Crows)
----------------------------------------------------------------------------
From: Scott <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup,comp.os.linux.help,alt.linux.slakware
Subject: File System going bad
Date: Tue, 01 May 2001 17:14:30 -0500
Ok, here's my question:
Is there any known issue with Linux packages and file systems
getting corrupted?
I've got:
Slackware 7.1, kernel 2.2.16, Samba, Apache, PSQL,
and a host of other things. It's on a UPS, so
I'm fairly sure it's not a power issue, and I know
it's not improper shutdown.
Every couple of weeks, I do a fsck and e2fsck, and it
comes back with illegal inodes, invalid DTime values,
and a host of other problems.
I repeatedly run e2fsck and fsck to repair the system.
When it's back up, everything is great for a while.
(i.e. I can re-check the FS, and have no problems)
But after a few weeks, it's bad again.
I keep my backups current, but I'm still nervous.
Are there any known packages that may be causing this?
(I use midnight Commander A LOT!)
The machine NEVER has a kernel panic and halts. It's
only during reboots (or the occasional console message
about a bad inode somewhere) that the FS shows up as bad.
Any thoughts or ideas in tracking down the problem
would be appreciated.
-Scott Weber
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: Multiple mount point for 1 partition
Date: Tue, 01 May 2001 22:26:14 GMT
In article <EaGH6.113448$[EMAIL PROTECTED]>, Frank de Bot wrote:
>At the moment I got 2 spool directory. On is located as usual at /var/spool
>. But the other one is at /usr/local/news/spool . Both may require a bunch
>of MB's. I just wondered if it's possible to mount those 2 dirs on to 1
>partition. I'm too lazy to reinstall my news server and so let it use
>/var/spool :-)
Create a symbolic link that points from one spot to the other:
# cd /usr/local/news
# rm -rf spool
# ln -s /var/spool .
--
Grant Edwards grante Yow! We are now enjoying
at total mutual interaction in
visi.com an imaginary hot tub...
------------------------------
From: [EMAIL PROTECTED] (Paul Kimoto)
Subject: Re: gethostbyname_r in glibc 2.2?
Date: 1 May 2001 18:34:18 -0400
Reply-To: [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>, Louis LeBlanc wrote:
> Now, with glibc 2.2, gethostbyname_r is implemented, but not
> documented. At least not as far as I can find.
See the (g)libc info pages for the node "Host Names".
--
Paul Kimoto
This message was originally posted on Usenet in plain text. Any images,
hyperlinks, or the like shown here have been added without my consent,
and may be a violation of international copyright law.
------------------------------
From: "Nunzio Falcone" <[EMAIL PROTECTED]>
Subject: Apache php4 and Postgresql !!!
Date: Tue, 01 May 2001 22:50:36 GMT
We have downloaded POSTACI, a webmail program based on php4.
Our sysop is RedHat 6.2.
We have installed the following sources:
c-client.4.7
qpopper.3.0.2
postgresql.6.5.3
apache.1.3.12
php4.0.4pl1
then configure and compile them as follow (without errors):
cd postgresql.6.5.3.sorces
./configure --prefix=/usr/lib/pgsql --with-odbc
make all
make install
adding "/usr/lib/pgsql/lib" to /etc/ld.so.conf
ldconfig
setting POSTGRES user and Environment Variable (PGDATA, PGLIB, etc)
initdb
starging postmaster (ok)
create testdb (ok)
psql testdb (ok)
cd apache.1.3.12.sources
./configure --prefix=/home/httpd
cd php.4.0.4pl1.sources
./configure --with-apache=/path/to/apache.1.3.12.sources --with-pgsql=/usr/l
ib/pgsql --with-imap --enable-track-vars
make
make install
cp php.ini-dist /usr/local/lib/php.ini
(but if I do <find / -name "php"> I don't reach any php binary)
cd apache.1.3.12.sources
./configure --prefix=/home/httpd --activate-module=src/modules/php4/libphp4.
a
make
make install
configuring httpd.conf
starting httpd (ok)
ok for compiling c-client and qpopper
telnet localhost 110 (ok)
telnet localhost 143 (ok)
Php test (browsing page with <?phpinfo()?> and other php tag) are ok
Connect test to postgresql database "testdb" failed:
createdb testdb
createuser test
createuser nobody (apache run with nobody rights)
psql testdb
create table mytable(lastname char(16), firstname char(12), email char(40));
populating table
grant all on mytable to public;
\q
create test.php3 file with
<?php
$connection = pg_Connect ("dbname=testdb port=5432 user=test");
?>
opening test.php3 in a browser get a follow view:
"<?php
$connection = pg_Connect ("dbname=testdb port=5432 user=test");
?>"
without error or other
And connecting to POSTACI do "Cannot connect to database"
What's wrong
------------------------------
Crossposted-To: alt.os.linux.slackware,3dfx.glide.linux,alt.games.quake3
From: [EMAIL PROTECTED] (Richard Laskey)
Subject: Re: Quake3 + XFree86-4.0.3 + Voodoo3 = Death Slow
Date: 1 May 2001 18:59:14 -0500
On Tue, 1 May 2001 22:24:48 +0100, Mjx2001 <[EMAIL PROTECTED]> wrote:
> "Charles Fultz" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
>> I'm having a bit of trouble getting Quake3Arena to play at an
>> acceptable speed. My setup is as follows: CPU: dual PII-overdrives
>> 333MHz
>
> Quake 3 Arena does not use dual CPU systems, so the second CPU is
> useless... Also, a P2 333 overdrive is prehistoric and nowhere near
> minimum requirements.
I ran Quake 3 on a p200 mmx for a while, and it ran. Not terribly well,
but at 800x600 it was playable. Unless a P2 333 is much worse than
that, he should not have too much of a problem. And, yeh, we all can
upgrade, but there isn't any sense in throwing out what (we) already
have.
>> RAM: 384MB Video: 3Dfx Voodoo3 3000 PCI
>
> I do use Linux, but I stopped using a voodoo3 years ago. My Athlon 950
> MHz / Geforce 2 can manage 80 fps @ 1024 x 768 x 32 full detail... Get
> yourself a new video card, preferably, one with a little more power.
I have, and currently use a 3dfx v3 2000 pci. It runs, and it runs
well. Again, this should not be too much of a problem.
>> Disk: 18GB IBM SCSI (40MB/sec) 7200RPM Kernel: 2.4.3 X: XFree86-4.0.3
>> w/ tdfx driver and DRI and GLX modules
>>
>> The game looks fine, but the response is horrible. I get anywhere
>> from 2-10 secs/frame. That's right secs/frame, not frames/sec. I
>> get the same results playing as a user or root. Can anyone help me
>> out here? I know I should be getting like anywhere from 30-50
>> frames/sec.
>
> 50 fps with a p2 333 and voodoo3 - you are dreaming.
Well, at 640x480 or lower, with options lowered, he should at least be
in the 20fps range.
As to Charles: I had the same problem as you on my system. I fixed it
by installing a glide dri package designed for 3dfx cards, which came in
the contrib directory of Slackware. The main file of concern was
usr/lib/libglide3.so.3.10.0. After I installed this, everything ran as
it should.
Good luck. If this doesn't work for you, then maybe there's something
else awry. Also, it is probably worth running the app glxinfo; this
might give you some incite as to where to go next.
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.help,alt.linux.slakware
Subject: Re: File System going bad
Date: Wed, 2 May 2001 00:47:01 +0200
In comp.os.linux.help Scott <[EMAIL PROTECTED]> wrote:
> Ok, here's my question:
> Is there any known issue with Linux packages and file systems
> getting corrupted?
No. You have bad memory. (or cpu - check the fan).
Peter
------------------------------
From: "Jeremy Haile" <[EMAIL PROTECTED]>
Subject: Redhat 7.1 and Sun Java JDK1.3
Date: Tue, 1 May 2001 19:09:26 -0700
I can't seem to get JDK1.3 to work with RedHat 7.1. At first, it has
trouble locating "cut." It was looking for it in /usr/bin/cut and apparently
redhat moved it to /bin. I symlinked it in /usr/bin and that fixed that
problem. Javac compiles, but when I run "java", it simply freezes up with
no error message. Running with -verbose didn't help me much either. Has
anyone tried this? Any ideas?
Thanks,
Jeremy
------------------------------
From: "Paul" <[EMAIL PROTECTED]>
Subject: right suggestions for sendmail with multi-domaine/setup
Date: Wed, 2 May 2001 01:17:33 +0200
Reply-To: "Paul" <[EMAIL PROTECTED]>
Hello ....
I'm a begginner with sendmail .....
I'm using a redhat 7.1 and I'm trying to setup
the configuration files but it seem that I'm wrong in some place...
Of course I've read carrefully the
http://www.sendmail.org/virtual-hosting.html but I'm still
confused ....
I've setup --the following files:
domaintable .....(declared domain inside the file )
=================
new_domain1.com
new_domain2.com
=================
local-host-names .....(declared domain inside the file )
=================
# local-host-names - include all aliases for your machine here.
new_domain1.com
mail.new_domain1.com
new_domain2.com
mail.new_domain2.com
=================
virtusertable .....(declared domain inside the file )
=================
[EMAIL PROTECTED] user1
[EMAIL PROTECTED] user2
=================
then a did the following command
# makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable
and I've restart sendmail
# /etc/rc.d/init.d/sendmail restart
But when I'm trying to test this two emails nothing happens .. :-(( I mean
I can't recive any kind of emails .....
Can help me some one ? .... Thank's ...
Bye Paul
[EMAIL PROTECTED]
** Ps Sorry for my long questions and for my poor English .... :-((
------------------------------
From: Farrell Farahbod <[EMAIL PROTECTED]>
Subject: modem driver, kernal, and other distro
Date: Tue, 01 May 2001 17:48:48 -0700
i downloaded a driver for linux for my winmodem. i currently use rh7,
which appears to have kernel 2.2.16-22. the drivers was oringionaly
written fro caldera openlinux 2.2 as it says at the beginning for the
file (wich is pasted below this). it says that i might need to recompile
the source code to make it work on my rh7 box. i am very new and had
troble just doing the commands outlines in the file pasted below. when i
got to the 'ismod' (step3) it told me that it was written for kernal
2.4.0-0.26, anh that i have 2.2.16-2. so i went to
http://www.redhat.com/support/errata/rh7-errata.html
and found out that the newsest kernal for rh7 is 2.2.19. so how do i
make the drive work, or how do i compile the source for rh7. again im
very new so i would need very specific instructions if possible. thank
you all soo much,
farrell farahbod
PCTel LINUX MODEM DRVER INSTALLATION GUIDE
By David Oakley
LINUX VERSIONS SUPPORTED:
This driver has been tested on RedHat Linux versions 6.0 - 6.1 and Linux
Mandrake 6.1 - 7.0. The driver was originally written for Caldera Open
Linux 2.2 and should therefore also work with Open Linux though I have
not personally tested it.
HARDWARE REQUIREMENTS:
This driver requires that you have a motherboard with the following
features:
SiS Chipset.
C-Media CMI8738 Sound Chipset.
PCTel HSP56 Modem Riser Module.
SOFTWARE REQUIREMENTS:
In order to successfully compile and install the modem driver there are
certain software packages that must first be installed on your system.
Before you continue please make sure that the following software
packages and their dependents are installed. If these packages are not
installed you will receive error messages while trying to compile the
driver.
kernel-source Kernel source code
kernel-headers Kernel source code headers
glibc-develop GLIB C source code
binutils Binary utilities
ncurses-develop Ncurses source code
gcc GNU C language compiler
make Make file creator.
DRIVER FILES:
The driver files should be in a single archive file, which includes the
following.
/src/module/Makefile
/src/module/ptmodule.c
/lib/control.a
/lib/dsp.a
/lib/hal.a
/lib/pctel.o
/lib/ptserial.a
/pctel_readme.txt
BEFORE YOU BEGIN:
Before you begin there are a few things you should remember and be
causous of.
1) In order to install any device driver you must have superuser (root)
access to the Linux system.
2) Linux is a case sensitive operating system and incorrectly
capitalizing commands or file names will cause errors.
3) When loged in as the superuser (root) you are capable of causing
great damage to both your system's hardware and software. BE CAREFUL.
INSTALLING THE DRIVER:
Step 1: Decompress the archive file and/or copy the modem driver source
code to the ( / ) root directory on your system. Make sure that the
files listed above are in the correct folders. The 'Makefile' and
'ptmodule.c' files should be in the /src/module directory on your
harddrive. The files 'dsp.a', 'control.a', 'hal.a', 'pctel.o' and
'ptseral.a' should all be in the /lib/ directory on your harddrive.
Step 2: At the Linux command prompt or in a Linux terminal window,
change to the /src/module directory using the 'cd /src/module' command
and use the 'make' command to rebuild the driver file and create the
/lib/pctel.o file. If you receive an error message during this step then
you are most likely missing some necessary software packages. Make sure
that all of the kernel source code is installed and that gcc and all of
its dependents are installed. If no errors are reported it's safe to
continue to step 3.
Step 3: Change to the /lib/ directory with the command 'cd /lib/' and
use the command 'insmod pctel.o' to install the modem driver. This
driver uses the major number 62 and the minor number 79 which maps to
serial port 16 (/dev/ttyS15).
Step 4: Create a character device node for the modem driver by using the
'mknod /dev/ttyS15 c 62 79' command. Remember, when typing Linux
commands pay close attention to your capitalization. Linux is a case
sensitive operating system and incorrectly capitalizing a command will
return an error message.
Step 5: Use the command 'chgrp uucp /dev/ttyS15' to change the group
ownership for the modem.
Step 6: Use the command 'chmod 666 /dev/ttyS15' to grant users
read/write access to the modem. Without this on the superuser (root)
will be able to use the modem.
Step 7: Use the command 'ln -s /dev/ttyS15 /dev/modem' to create a
symbolic link to the modem named modem. If you choose not to create a
symbolic link named modem, them some communications programs will be
unable to access the modem.
Step 8: Use the command 'cp /lib/pctel.o /lib/modules/2.2.14-15mdk/net'
to copy the pctel.o file to the /lib/modules/2.2.14-15mdk/net
subdirectory. On your system the 2.2.14-15mdk may be slightly different
dependig on which Linux kernel you are using. If you are using a kernel
other than 2.2.14-15mdk, replace the '2.2.14-15mdk' with the kernel
version you are using.
Step 9: Use a program such as kppp to test the modem. If everything is
working you will need to edit the /etc/rc.sysinit file and add the
following command to the end of the file to load the modem driver every
time the system starts.
#Load the modem driver pctel.o
modprobe pctel.o -a
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: File System going bad
Crossposted-To: alt.linux.slakware
Date: Wed, 02 May 2001 01:00:20 GMT
In comp.os.linux.misc Scott <[EMAIL PROTECTED]> wrote:
>The machine NEVER has a kernel panic and halts. It's
>only ********during reboots******
maybe this will help...as some machines don't clear mem on reboot
The Linux Tips HOWTO
Paul Anderson, [EMAIL PROTECTED]
v3.6, June 1998
2.10. How do I stop my system from fscking on each reboot?
Q: How do I stop e2fsck from checking my disk every time I boot up.
A: When you rebuild the kernel, the filesystem is marked as 'dirty'
and so your disk will be checked with each boot. The fix is to run:
rdev -R /zImage 1
This fixes the kernel so that it is no longer convinced that the
filesystem is dirty.
Note: If using lilo, then add read-only to your linux setup in your
lilo config file (Usually /etc/lilo.conf)
2.11. How to avoid fscks caused by "device busy" at reboot time.
If you often get device busy errors on shutdown that leave the
filesystem in need of an fsck upon reboot, here is a simple fix:
To /etc/rc.d/init.d/halt or /etc/rc.d/rc.0, add the line
mount -o remount,ro /mount.dir
for all your mounted filesystems except /, before the call to umount
-a. This means if, for some reason, shutdown fails to kill all pro�
cesses and umount the disks they will still be clean on reboot. Saves
a lot of time at reboot for me.
Regards, John
------------------------------
From: Timothy Washington <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.admin,comp.os.linux.setup,comp.os.linux.questions
Subject: grub default values
Date: Wed, 02 May 2001 00:50:35 GMT
I'm trying to get GRUB (Grand Unified Boot Loader) to boot my linux
partition automatically. I am able to boot from a command line at boot
time, but I want to reboot my machine remotely and have it come up with
a default OS (linux).
Here is what I do:
1. untarring grub
2. configure (no parameters), make, make install
3. grub-install /dev/hda
4. (as root) grub
5. grub prompt> install (hd0,4)/boot/grub/stage1 d (hd0)
(hda0,4)/boot/grub/stage2 p (hd0,4)/boot/grub/menu.1st
*error or bad stage1/stage2 file*
I had gotten a warning when doing "configure" and "make". The
warnings had somethig to do with pointers, but I am not able to get a
log to attach (its on a machine that is not connected to a network).
I've done everything that I think has to be done. If I can resolve this
error, I will be over a major hump. Has anyone had this problem?
tim
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: smart media and linux? (esp. w/ notebooks)
Reply-To: [EMAIL PROTECTED]
Date: 02 May 2001 00:56:52 GMT
On 1 May 2001 14:10:30 GMT, [EMAIL PROTECTED] staggered
into the Black Sun and said:
>Ok, i hope i don't get flamed for too many mini-postings but i figured
>i would risk it. I previously posted about compact flash due to the
>fact that i was dazzled by the ability to just plug it into a pcmcia
>slot (with a converter) and use it like a hard drive. Unfortunatly the
>cammera i am drooling over uses "smartmedia" (the Olympus America
>Camedia C-2040). What kind of support of linux have for smart media?
>While i am at it, would anyone happen to know if (assuming it exists)
>converting USB to serial would be a problem? (i have a old notebook).
AFAIK, there is a small device you can get called a "smartmedia-to-USB"
adapter. Put the smartmedia card in one end, plug the USB plug into
your machine, then "modprobe usb-storage" and attempt to access
/dev/sdX1 as a FAT-formatted disk, where X is one letter higher than the
highest-lettered SCSI disk you have connected.
If you don't have a USB port, why not just use the camera's serial-line
out and hook the thing to your DB9 serial port? It's highly probable
that gphoto supports whatever protocol your camera uses. It'll be slow,
but converting USB to serial would not be any faster. If your camera
does not have a serial line out (most cameras do!) then you'll have a
tough time using it with your old machine.
I thought I saw a PCMCIA smartmedia adapter the other day at the
CompUSelessA. That should work just like the CompactFlash thing....
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com / Workin' in a code mine, whoops!
=============================/ I hit a seg fault....
------------------------------
** 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.misc.
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
******************************
