Linux-Misc Digest #213, Volume #20 Sat, 15 May 99 05:13:09 EDT
Contents:
FIXED(?): Staroffice/glibc problem (Peter Englmaier)
FIXED(?): Staroffice/glibc problem (Peter Englmaier)
Adding ethernet to dial-up machine (Colin Walls)
FIXED(?): Staroffice/glibc problem (Peter Englmaier)
FIXED(?): Staroffice/glibc problem (Peter Englmaier)
Re: All of a sudden system will not boot ([EMAIL PROTECTED])
Libraries Needed? (Jason Bond)
Re: Getting PPP to work (gus)
Re: What happened to fdformat (James Stafford)
Re: Energy Star Usage? (jason)
Re: Strange password problem (Robert Hull)
Re: Linux on K62 ok? (fred smith)
Re: The Best Linux distribution? (was Re: FreeBSD vs. Linux) ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: Peter Englmaier <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: FIXED(?): Staroffice/glibc problem
Date: Sat, 15 May 1999 02:07:39 -0400
Yet another solution for the Staroffice/glibc problems.
RH6.0 has problems with old glibc-2.0.7 binaries. Staroffice and
many other programs do not work with the new glibc. Here is
a workaround based on the 'misc. binary format' feature of
the linux kernel. Even printing seems to work (at least for me).
Please post if this does or does not work for you.
Note: This may also fix other problems reported with the glibc.
0) do *not* modify any staroffice scripts or binaries... (the easy
step first)
1) install the rpm's for
compat-glibc-5.2-2.0.7.1
compat-libs-5.2-1
2) install the appended wrapper file in
/usr/i386-glibc20-linux/lib/ld-wrapper
and do
chmod a=rx /usr/i386-glibc20-linux/lib/ld-wrapper
This file will be used to run old applications.
3) install the appended rc.binfmt file below in /etc/rc.d/
make it execute:
chmod a=rx rc.binfmt
run rc.binfmt to activate it. If it produces error
messages, you probably have no misc. binary format
compiled in the kernel. You want to call the
file from /etc/rc.d/rc.serial as well (add a line
saying '/etc/rc.d/rc.binfmt'.
This works as follows: when the kernel is asked to 'execute' a
binary with extension '.bin', it runs the wrapper file instead.
The wrapper loads the binary with the 'right' loader. To run
other old binaries, e.g. 'goodie', simply do:
mv goodie goodie.bin
ln -s goodie.bin goodie
BTW, if somebody finds out the 'magic' bytes of old binaries,
the script could be triggered using the magic fingerprint.
Peter.
>>>>>>>>>>>>>>>>>>>ld-wrapper:
#!/bin/sh
# wrapper for old glibc binaries
p=`basename $1`
if [ "$p" = "soffice.bin" -o "$p" = "psetup.bin" -o "$p" = "setup.bin"
]; then
exec /usr/i386-glibc20-linux/lib/ld-linux.so.2 --library-path
/usr/i386-glibc20-linux/lib:$LD_LIBRARY_PATH "$@"
fi
exec /lib/ld-linux.so.2 "$@"
>>>>>>>>>>>>>>>>>>rc.binfmt
#!/bin/sh
if /sbin/modprobe binfmt_misc.o ; then
# clear register first
echo -1 >/proc/sys/fs/binfmt_misc/status
REGISTER=/proc/sys/fs/binfmt_misc/register
# old glibc
echo ':oldglibc:E::bin::/usr/i386-glibc20-linux/lib/ld-wrapper:'
>${REGISTER}
fi
------------------------------
From: Peter Englmaier <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: FIXED(?): Staroffice/glibc problem
Date: Sat, 15 May 1999 02:18:32 -0400
Yet another solution for the Staroffice/glibc problems.
RH6.0 has problems with old glibc-2.0.7 binaries. Staroffice and
many other programs do not work with the new glibc. Here is
a workaround based on the 'misc. binary format' feature of
the linux kernel. Even printing seems to work (at least for me).
Please post if this does or does not work for you. Staroffice
still gives some error message at startup, but works fine.
Note: This may also fix other problems reported with the glibc.
0) do *not* modify any staroffice scripts or binaries... (the easy
step first)
1) install the rpm's for
compat-glibc-5.2-2.0.7.1
compat-libs-5.2-1
2) install the appended wrapper file in
/usr/i386-glibc20-linux/lib/ld-wrapper
and do
chmod a=rx /usr/i386-glibc20-linux/lib/ld-wrapper
This file will be used to run old applications.
3) install the appended rc.binfmt file below in /etc/rc.d/
make it execute:
chmod a=rx rc.binfmt
run rc.binfmt to activate it. If it produces error
messages, you probably have no misc. binary format
compiled in the kernel. You want to call the
file from /etc/rc.d/rc.serial as well (add a line
saying '/etc/rc.d/rc.binfmt'.
This works as follows: when the kernel is asked to 'execute' a
binary with extension '.bin', it runs the wrapper file instead.
The wrapper loads the binary with the 'right' loader. To run
other old binaries, e.g. 'goodie', simply do:
mv goodie goodie.bin
ln -s goodie.bin goodie
BTW, if somebody finds out the 'magic' bytes of old binaries,
the script could be triggered using the magic fingerprint.
Peter.
>>>>>>>>>>>>>>>>>>>ld-wrapper:
#!/bin/sh
# wrapper for old glibc binaries
p=`basename $1`
if [ "$p" = "soffice.bin" -o "$p" = "psetup.bin" -o "$p" = "setup.bin"
]; then
exec /usr/i386-glibc20-linux/lib/ld-linux.so.2 --library-path
/usr/i386-glibc20-linux/lib:$LD_LIBRARY_PATH "$@"
fi
exec /lib/ld-linux.so.2 "$@"
>>>>>>>>>>>>>>>>>>rc.binfmt
#!/bin/sh
if /sbin/modprobe binfmt_misc.o ; then
# clear register first
echo -1 >/proc/sys/fs/binfmt_misc/status
REGISTER=/proc/sys/fs/binfmt_misc/register
# old glibc
echo ':oldglibc:E::bin::/usr/i386-glibc20-linux/lib/ld-wrapper:'
>${REGISTER}
fi
------------------------------
From: Colin Walls <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Adding ethernet to dial-up machine
Date: Sat, 15 May 1999 07:00:23 +0100
Until recently my machine has only had ppp dial-up networking.I have
just added a network card so I can use the box as a file and mail server
for my daughters' machines (W95 unfortunately).
I have a problem in that I must keep my ppp hostname/IP address to
communicate with my ISP. However if I set this as a default Samba (v2.0)
attempts to bind to this and fails.
If I set the default hostname to correspond to the ethernet IP address
the sendmail (v8.9.3) refuses to relay between my ISP and my local
network.
Any ideas how I resolve the conflict? Please reply by mail as I can't
always get to this group.
--
Colin Walls
Email: [EMAIL PROTECTED]
Web: http://www.murorum.demon.co.uk
Phone: 01625 535123
------------------------------
From: Peter Englmaier <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: FIXED(?): Staroffice/glibc problem
Date: Sat, 15 May 1999 02:04:56 -0400
Yet another solution for the Staroffice/glibc problems.
RH6.0 has problems with old glibc-2.0.7 binaries. Staroffice and
many other programs do not work with the new glibc. Here is
a workaround based on the 'misc. binary format' feature of
the linux kernel. Even printing seems to work (at least for me).
Please post if this does or does not work for you.
Note: This may also fix other problems reported with the glibc.
0) do *not* modify any staroffice scripts or binaries... (the easy
step first)
1) install the rpm's for
compat-glibc-5.2-2.0.7.1
compat-libs-5.2-1
2) install the appended wrapper file in
/usr/i386-glibc20-linux/lib/ld-wrapper
and do
chmod a=rx /usr/i386-glibc20-linux/lib/ld-wrapper
This file will be used to run old applications.
3) install the appended rc.binfmt file below in /etc/rc.d/
make it execute:
chmod a=rx rc.binfmt
run rc.binfmt to activate it. If it produces error
messages, you probably have no misc. binary format
compiled in the kernel. You want to call the
file from /etc/rc.d/rc.serial as well (add a line
saying '/etc/rc.d/rc.binfmt'.
This works as follows: when the kernel is asked to 'execute' a
binary with extension '.bin', it runs the wrapper file instead.
The wrapper loads the binary with the 'right' loader. To run
other old binaries, e.g. 'goodie', simply do:
mv goodie goodie.bin
ln -s goodie.bin goodie
BTW, if somebody finds out the 'magic' bytes of old binaries,
the script could be triggered using the magic fingerprint.
Peter.
>>>>>>>>>>>>>>>>>>>ld-wrapper:
#!/bin/sh
# wrapper for old glibc binaries
p=`basename $1`
if [ "$p" = "soffice.bin" -o "$p" = "psetup.bin" -o "$p" = "setup.bin"
]; then
exec /usr/i386-glibc20-linux/lib/ld-linux.so.2 --library-path
/usr/i386-glibc20-linux/lib:$LD_LIBRARY_PATH "$@"
fi
exec /lib/ld-linux.so.2 "$@"
>>>>>>>>>>>>>>>>>>rc.binfmt
#!/bin/sh
if /sbin/modprobe binfmt_misc.o ; then
# clear register first
echo -1 >/proc/sys/fs/binfmt_misc/status
REGISTER=/proc/sys/fs/binfmt_misc/register
# old glibc
echo ':oldglibc:E::bin::/usr/i386-glibc20-linux/lib/ld-wrapper:'
>${REGISTER}
fi
------------------------------
From: Peter Englmaier <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: FIXED(?): Staroffice/glibc problem
Date: Sat, 15 May 1999 02:10:57 -0400
Yet another solution for the Staroffice/glibc problems.
RH6.0 has problems with old glibc-2.0.7 binaries. Staroffice and
many other programs do not work with the new glibc. Here is
a workaround based on the 'misc. binary format' feature of
the linux kernel. Even printing seems to work (at least for me).
Please post if this does or does not work for you. Staroffice
still gives some error message at startup, but works fine.
Note: This may also fix other problems reported with the glibc.
0) do *not* modify any staroffice scripts or binaries... (the easy
step first)
1) install the rpm's for
compat-glibc-5.2-2.0.7.1
compat-libs-5.2-1
2) install the appended wrapper file in
/usr/i386-glibc20-linux/lib/ld-wrapper
and do
chmod a=rx /usr/i386-glibc20-linux/lib/ld-wrapper
This file will be used to run old applications.
3) install the appended rc.binfmt file below in /etc/rc.d/
make it execute:
chmod a=rx rc.binfmt
run rc.binfmt to activate it. If it produces error
messages, you probably have no misc. binary format
compiled in the kernel. You want to call the
file from /etc/rc.d/rc.serial as well (add a line
saying '/etc/rc.d/rc.binfmt'.
This works as follows: when the kernel is asked to 'execute' a
binary with extension '.bin', it runs the wrapper file instead.
The wrapper loads the binary with the 'right' loader. To run
other old binaries, e.g. 'goodie', simply do:
mv goodie goodie.bin
ln -s goodie.bin goodie
BTW, if somebody finds out the 'magic' bytes of old binaries,
the script could be triggered using the magic fingerprint.
Peter.
>>>>>>>>>>>>>>>>>>>ld-wrapper:
#!/bin/sh
# wrapper for old glibc binaries
p=`basename $1`
if [ "$p" = "soffice.bin" -o "$p" = "psetup.bin" -o "$p" = "setup.bin"
]; then
exec /usr/i386-glibc20-linux/lib/ld-linux.so.2 --library-path
/usr/i386-glibc20-linux/lib:$LD_LIBRARY_PATH "$@"
fi
exec /lib/ld-linux.so.2 "$@"
>>>>>>>>>>>>>>>>>>rc.binfmt
#!/bin/sh
if /sbin/modprobe binfmt_misc.o ; then
# clear register first
echo -1 >/proc/sys/fs/binfmt_misc/status
REGISTER=/proc/sys/fs/binfmt_misc/register
# old glibc
echo ':oldglibc:E::bin::/usr/i386-glibc20-linux/lib/ld-wrapper:'
>${REGISTER}
fi
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: All of a sudden system will not boot
Date: 15 May 1999 06:15:39 GMT
In article <[EMAIL PROTECTED]>,
Chunky <[EMAIL PROTECTED]> wrote:
>All of a sudden my 2.2.7 linux system will only boot up to the point :-
>
>VFS: Mounted Root (ext2 filesystem) read only
>Free unused kernel memory 48K freed
>
>I can mount the root FS from a rescue disk but beyond this point I have no
>idea what to do to repair the system.
>
>Up until now my system was very reliable however just prior to this event
>starting I had quit KDE and the system started to play up with segmentation
>faults, core dump etc.
>
>Any ideas?
>
>Regards,
>
>
>
Well, supposing you had mounted your hard disk's root filesystem
on /mnt from your rescue disk. Remove your rescue disk and put in a
fresh floppy diskette. Let's say your kernel image was /vmlinuz when
things were working. You could try the command 'cat /mnt/vmlinuz /dev/fd0'.
This would hopefully copy the kernel (which hopefully was not corrupted)
to the floppy and you could boot from the floppy to your old root filesystem.
If you have a dos partition (or an MS-DOS floppy that is bootable, made
with format /s under dos), you could copy some kernel onto that floppy
and loadlin, and run a command like loadlin zimage root=/dev/hda1 under
dos. If your problem is something else, like bad memory, or something
corrupt in init.d or some rc.d file, then that would have to be investigated.
Probably other people will post better suggestions, but these
kinds of things have worked for me in the past.
Good luck.
--
Praeterea censeo Micromolle non esse utendum.
("Moreover, I maintain that Microsoft should not be used." A toned down
adaptation of a sig from Cato the Elder regarding the city of Carthage.
---- Remove "UhUh" and "Spam" to get my real email address -----
------------------------------
From: Jason Bond <[EMAIL PROTECTED]>
Subject: Libraries Needed?
Date: Sat, 15 May 1999 00:03:50 -0700
Does anyone know where I can get ahold of the following libraries?
failed dependencies:
libaudiofile.so.0 is needed by x11amp-0.9-beta1.1-1
libesd.so.0 is needed by x11amp-0.9-beta1.1-1
Thanks kindly for any assistance.
Jason
------------------------------
From: gus <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,linux.redhat.install,linux.redhat.misc
Subject: Re: Getting PPP to work
Date: Fri, 14 May 1999 09:56:18 +0100
Having read the other replies, it may just be that the error message is
correct. If ppp is compiled as a module, it still needs to be loaded.
Type "lsmod" as root to see which modules are loaded. If there is no ppp
then type "modprobe ppp". This should load it.
Obviously (or maybe not), if ppp is compiled in to the kernel (not as a
module), or ppp appears in the lsmod list, then the other advice is the
next step. But first, the ppp code has to be loaded somewhere.
gus
Jay wrote:
>
> Can anyone explain how I can get PPP to work. First I noticed that PPP was
> not installed. So I recompiled using 'make config' and 'make dep'. Then I
> recompiled the modules. However on rebooting I still can't find PPP as
> installed. What am I missing?
>
> -Jay
------------------------------
From: James Stafford <[EMAIL PROTECTED]>
Crossposted-To: linux.debian.user,linux.redhat.misc,comp.os.linux.hardware
Subject: Re: What happened to fdformat
Date: Sat, 15 May 1999 00:31:39 -0700
Rob Komar wrote:
> [EMAIL PROTECTED] wrote:
> : I know this sounds stupid, but I used to think that you can low-level
> : format a floppy in Linux using "fdformat". Well, on my Debian system
> : this is what I get:
> : ----------------------------------
> : histria ~ # fdformat
> : bash: fdformat: command not found
> : histria ~ # man fdformat
> : No manual entry for fdformat
> : -----------------------------------
> : (as root). How can I format a floppy ?
>
> fdformat is part of the util-linux-2.9X package. You could download
> the source code and build it yourself if you're feeling adventurous.
>
> Cheers,
> Rob Komar
That's hoe I got fdformat on my Slackware boxes. Except I downloaded it
separately off the net some where.
jamess
------------------------------
From: jason <[EMAIL PROTECTED]>
Subject: Re: Energy Star Usage?
Date: Sat, 15 May 1999 03:50:18 -0400
Just saw a tip for X:
xset dpms 1800
will put your monitor in power-saving mode in 1800 seconds (30 min).
HTH,
-jason
(to reply via email, make the appropriate substitution in my email address)
------------------------------
From: Robert Hull <[EMAIL PROTECTED]>
Subject: Re: Strange password problem
Date: Fri, 14 May 1999 22:25:47 +0100
In article <[EMAIL PROTECTED]>, The Graphical Gnome
<[EMAIL PROTECTED]> writes
>Robert Hull <[EMAIL PROTECTED]> wrote in
><U2$[EMAIL PROTECTED]>:
>
>>In article <[EMAIL PROTECTED]>, Robert Thomas
>><[EMAIL PROTECTED]> writes
>>>Rob Fisher wrote:
>>>
>>>>
>>>> How long is your passwd? Unix only uses the first eight characters of
>>>> the passwd, so the ninth letter onward are igonred.
>>
>>>You are right.
>>[snip]
>>>
>>>Eight characters seems to me to
>>>be too short for a really secure system, don't you think?
>>>
>>If you are using mix and match with upper and lower case alpha together
>>with numerics, you have over 218 000 000 000 000 possible combinations
>>of password, is that not secure enough for you ?
>
> 218 340 105 584 896 possibilities (to be precise)
>
You're right, that's too easy to break ;-) At one attempt per second,
you could exhaust all possibilities in less than seven million years
--
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: [EMAIL PROTECTED] (fred smith)
Subject: Re: Linux on K62 ok?
Date: Sat, 15 May 1999 02:53:36 GMT
The Graphical Gnome ([EMAIL PROTECTED]) wrote:
: fred smith <[EMAIL PROTECTED]> wrote in
: <[EMAIL PROTECTED]>:
: >i've had serious trouble with Windoze95 on it, though, (the system
: >dul-boots) apparently because windoze hates to have the world changed
: >out from under it without its permission.
: No, Windows can't handle a K6/II running more than 300.
No, that's not true:
1. Microsoft has an updte on their site for K6-2 machines at 350 and
higher which fixes the intermittent boot-time problem (it is also
availablle from AMD's web site and the FIC web site,and probably
elsewhere). 2. It runs just fine on the other machine which got a fresh
install of win95 when the new motherboard (identical to mine in all
respects) was installed.
--
---- Fred Smith -- [EMAIL PROTECTED] -----------------------------
I can do all things through Christ
who strengthens me.
============================== Philippians 4:13 ===============================
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: The Best Linux distribution? (was Re: FreeBSD vs. Linux)
Crossposted-To: comp.unix.bsd.freebsd.misc
Date: Sat, 15 May 1999 05:33:24 GMT
Steve Lamb <[EMAIL PROTECTED]> wrote:
: On Thu, 13 May 1999 01:16:11 +0200, Serge Terryn <[EMAIL PROTECTED]>
: wrote:
:>But there is only one FreeBSD.
:
: There is only one Windows as well. Go away, FUD boy.
Steve Lamb of all people calling *anyone* a "FUD boy". Now that's
classic!
>snip<
: Unless the current version is no longer availabe, then you don't get squat
: unless it has been deemed worthy enough to reside on the FreeBSD servers.
If "worthy" had anything to do with it, I doubt that the dist file
for my port of wmeyes (quite: "The World's Most Useless App") would
have been added.
>snip<
: First off, it is MESS.
>snip<
To use your words; Go away, FUD boy.
--
-Zenin ([EMAIL PROTECTED])
My code is filled with comments! It's just that my comments are
written in Perl.
------------------------------
** 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
******************************
