Linux-Misc Digest #688, Volume #25 Thu, 7 Sep 00 06:13:02 EDT
Contents:
Re: what's up with Sun? (T. Max Devlin)
buffer_dirty - what's the @#$%? ("Ian Dichkovsky")
Re: what's up with Sun? ("Andrew N. McGuire ")
Re: fstab question (f vassalli)
removing double files (Bruno van Wayenburg)
Re: Redhat Newbie question (David M. Cook)
Re: Now I'm stuck with XFree86 again! ([EMAIL PROTECTED])
Re: red hat help (David M. Cook)
Re: Fail in upgrading glibc RPM package (Fung Wai Keung)
Re: buffer_dirty - what's the @#$%? ([EMAIL PROTECTED])
Re: nameless process ("Peter T. Breuer")
Re: Loopback Device Creation ("Peter T. Breuer")
Re: Fail in upgrading glibc RPM package ("Peter T. Breuer")
Re: Efax and LT modem ("Peter T. Breuer")
Problem with "swiss german" keyboard layout (Beda Rickenbacher)
Re: random Linux freezing (Crni Gorac)
INIT_RD in rc.config (Holger Meinecke)
Re: Loopback Device Creation (Daniel Robert Franklin)
----------------------------------------------------------------------------
From: T. Max Devlin <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.advocacy,comp.os.linux.hardware
Subject: Re: what's up with Sun?
Date: Thu, 07 Sep 2000 03:14:34 -0400
Reply-To: [EMAIL PROTECTED]
Said <[EMAIL PROTECTED]> in comp.os.linux.advocacy;
>
>Ez-Aton <[EMAIL PROTECTED]> wrote in message
>news:newscache$n8jf0g$k21$[EMAIL PROTECTED]...
>
>> Both Intel and AMD should stick to the home-office computers, and leave
>the
>> servers to the real tough computers, since they will never reach the Sun
>> stability and power.
>> My oppinion.
>
>Better yet. Intel and AMD should stick to producing processors and let the
>users determine how the computers built with their processors should be
>used.
Ooh-rah.
--
T. Max Devlin
-- Such is my recollection of my reconstruction
of events at the time, as I recall. Consider it.
Research assistance gladly accepted. --
====== Posted via Newsfeeds.Com, Uncensored Usenet News ======
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
======= Over 80,000 Newsgroups = 16 Different Servers! ======
------------------------------
From: "Ian Dichkovsky" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.system,comp.os.linux.hardware,comp.os.linux.questions
Subject: buffer_dirty - what's the @#$%?
Date: Thu, 7 Sep 2000 10:33:46 +0300
Hi all ! (sorry for bad English)
when I copy file from floppy,
on the console apppear message
.... buffer_dirty .... 512
(don't remember exactly)
I reboot to the win98 and files copyied without messages.
Floppy hasn't bad blocks.
So, what it mean - buffer_dirty ?
Thanks!
Bye!
------------------------------
Crossposted-To: alt.os.linux,comp.os.linux.advocacy,comp.os.linux.hardware
From: "Andrew N. McGuire " <[EMAIL PROTECTED]>
Subject: Re: what's up with Sun?
Date: Thu, 7 Sep 2000 02:35:23 -0500
On Thu, 7 Sep 2000, T. Max Devlin quoth:
~~ Date: Thu, 07 Sep 2000 03:14:34 -0400
~~ From: T. Max Devlin <[EMAIL PROTECTED]>
~~ Newsgroups: alt.os.linux, comp.os.linux.advocacy, comp.os.linux.misc,
~~ comp.os.linux.hardware
~~ Subject: Re: what's up with Sun?
~~
~~ Said <[EMAIL PROTECTED]> in comp.os.linux.advocacy;
~~ >
~~ >Ez-Aton <[EMAIL PROTECTED]> wrote in message
~~ >news:newscache$n8jf0g$k21$[EMAIL PROTECTED]...
~~ >
~~ >> Both Intel and AMD should stick to the home-office computers, and leave
~~ >the
~~ >> servers to the real tough computers, since they will never reach the Sun
~~ >> stability and power.
~~ >> My oppinion.
~~ >
~~ >Better yet. Intel and AMD should stick to producing processors and let the
~~ >users determine how the computers built with their processors should be
~~ >used.
~~
~~ Ooh-rah.
Marine?
anm
--
Andrew N. McGuire
[EMAIL PROTECTED]
perl -le'print map?"(.*)"?&&($_=$1)&&s](\w+)]\u$1]g&&$_=>`perldoc -qj`'
------------------------------
From: f vassalli <[EMAIL PROTECTED]>
Subject: Re: fstab question
Date: Thu, 07 Sep 2000 11:39:51 +0200
Reply-To: [EMAIL PROTECTED]
I dont try to mount a physical CD-ROM; it's just an CD-ROM-image-file
(the file you burn on a physical CD) on a loop device to handle it like
a Physical CD-ROM.
alex k wrote:
>
> oh
> i found it myself
> its mounted through the rc-scripts.
> /etc/rc.d/rc.M checks to see if there
> is a executable rc.cdrom.
> if there is, it runs it.
>
> --
> .
> .
> ...: [ ~~~~~~~ ] :...
>
> Sent via Deja.com http://www.deja.com/
> Before you bu
------------------------------
From: Bruno van Wayenburg <[EMAIL PROTECTED]>
Subject: removing double files
Date: Thu, 07 Sep 2000 09:34:20 +0200
I have been archiving a lot recently, in order to transfer all files
from scattered accounts to my (slackware) linux system. As a result, I
have a lot of identical files in separate directories. Is there an app
that finds double files, and deletes all but one if they are really
equal. Thank you.
Bruno van Wayenburg
------------------------------
From: [EMAIL PROTECTED] (David M. Cook)
Subject: Re: Redhat Newbie question
Date: 7 Sep 2000 07:49:43 GMT
On Thu, 07 Sep 2000 04:13:16 GMT, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>follow,, traceback (innermost last ): file /usr/bin/anaconda/line342
You might try the anaconda update at http://www.redhat.com/errata
Dave Cook
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Now I'm stuck with XFree86 again!
Date: Thu, 07 Sep 2000 07:52:30 GMT
In article <[EMAIL PROTECTED]>,
"D. C. & M. V. Sessions" <[EMAIL PROTECTED]> wrote:
>
> Look for tcl-8.0.5-35.rpm and tk-8.0.5-35.rpm
>
> You should find them in (IIRC) $CDROM/RedHat/RPMS
>
> --
> | Engineers solve problems -- it's what we do. |
> | Do you want to be a problem? |
> | D. C. Sessions === [EMAIL PROTECTED] |
>
Thanks D.C. for your info, I've tried the solutions and it
worked. But when I tried to install the XFSetup's rpm, it
gives me error:
"failed dependencies: Xserver is needed by XFee86-XF86Setup-3.3.6-20"
I've looked into all of the RPM in CDROM/RedHat/RPMS but fails to
find the file(Xserver).
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED] (David M. Cook)
Subject: Re: red hat help
Date: 7 Sep 2000 07:59:20 GMT
On Wed, 06 Sep 2000 06:29:30 GMT, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>it says "Boot Partition too big"
This could mean
o You don't have space below cylinder 1024 to put the kernel.
o You're root partition extends past cylinder 1024, and there's no way to
guarentee that the kernel will be below cylinder 1024.
If you do have space below cylinder 1024, try creating a small (16M) /boot
partition there.
Otherwise, you will need to do an expert install, choose fdisk to partition,
and create a bootfloopy for booting Linux.
BTW, this 1024 cylinder limitation has been removed in later versions of
lilo (depending on how recent your BIOS is.)
Dave Cook
------------------------------
From: Fung Wai Keung <[EMAIL PROTECTED]>
Subject: Re: Fail in upgrading glibc RPM package
Date: 7 Sep 2000 07:52:56 GMT
Hi,
: Sure. But why would you want to! I imagine that the libc in the initrd
: is highly modified and unsuitable for use on an installed system. Why
: not just extract the libc from a rpm or tgz and put it in place?
I have a problem in copying useful libc into the PC. I only have floppy
installed in my PC, no CDROM and any other I/O peripheral device
connected. However, floppy is not supported in the rescue mode and no
/dev/fd0 is created in /dev. How to copy the required files into my PC?
: You haven't said what is stopping you deleting files on the
: harddisk while running from the rescue bootdisk. I suggested what
: it might be above, but you didn't comment. Can you clarify, please?
After mounting the filesystems with read-write access, the problem is
solved.
--
Regards,
Wai Keung, Fung
Department of Automation and Computer Aided Engineering,
The Chinese University of Hong Kong,
Shatin, N.T.,
Hong Kong
Tel: (852)26098056 Fax: (852)26036002
Email: [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: buffer_dirty - what's the @#$%?
Crossposted-To:
comp.os.linux.development.system,comp.os.linux.hardware,comp.os.linux.questions
Date: 7 Sep 2000 04:06:00 -0400
In comp.os.linux.misc Ian Dichkovsky <[EMAIL PROTECTED]> wrote:
> So, what it mean - buffer_dirty ?
Caching. It happens in Windows if you speed Windows up (but Windows
defaults to turn off write caching). When you write a file to floppy all
the OS does is note which file you want to write and when it finds time it
will do it in the background (this makes the system more responsive). BUT
if you remove the drive before the write - boom.
Try the "sync" command (which forces the buffer write to the disk) before
umounting or removing the disk
(sync has a manual page)
(of course if you have, say a removable hard drive and the hardware has a
cache and you remove the drive before the cache is written to disk
... the data will have been written to the hard drive's cache but not the
disk ... sync will get it written that far though)
(by "buffer dirty" - well the buffer is used to hold data to be written to
disk and it is "dirty" - that is, it hasn't been cleaned out by finishing
the write - you can wait awhile until the system is done writing the data
or use the sync command)
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: nameless process
Date: 7 Sep 2000 08:20:02 GMT
Omkar Sathe <[EMAIL PROTECTED]> wrote:
: Hello,
: Can we have a process entry which is "nameless" ???
: If yes, how do we identify it if we dont know the PID ?
: How to write such a process(daemon) which will create such a nameless entry
man main. The bit about argc and argv ;-))))
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: aus.computers.linux
Subject: Re: Loopback Device Creation
Date: 7 Sep 2000 08:17:10 GMT
Jim Bell <[EMAIL PROTECTED]> wrote:
: I need to create an arbitrary number of loopback devices on the fly. I
: then want to mount filesystem images on these devices. /dev/loop[0-7]
: are not enough.
: So far, I can create the device fine, but when I use losetup the command says
: Device Not Found error. When I list the /dev dir, the device is there,
: so I presume the kernal doesn't know or like my new device. I have
: rebooted since creating the device (not necessary, but Windows habits
: die hard!). Any suggestions would be appreciated.
Modify the kernel driver. There is no other way.
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Fail in upgrading glibc RPM package
Date: 7 Sep 2000 08:36:08 GMT
Fung Wai Keung <[EMAIL PROTECTED]> wrote:
: : Sure. But why would you want to! I imagine that the libc in the initrd
: : is highly modified and unsuitable for use on an installed system. Why
: : not just extract the libc from a rpm or tgz and put it in place?
: I have a problem in copying useful libc into the PC. I only have floppy
: installed in my PC, no CDROM and any other I/O peripheral device
: connected. However, floppy is not supported in the rescue mode and no
Yes, floppy is supported! You booted from it (or are running on a ramfs
loaded from it) so you know that!
: /dev/fd0 is created in /dev. How to copy the required files into my PC?
It probably appears when you need it, if you are using devfs.
If not, the answer is: use a different rescue disk or dump it in the dos
partition using a dos boot disk.
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Efax and LT modem
Date: 7 Sep 2000 08:31:43 GMT
[EMAIL PROTECTED] wrote:
: I am unable to send fax using efax. The phone connects
faxes with efax work fine for me and always have, for years and years
and years. I use version 0.7a.
: to other side successfully but fails to send the file over.
: efax: 57:04 failed -> test.001
: I have Debian Potato, Lucent WinModem (Driver ltmodem.o) and
: latest efax. The modem works fine with ppp.
: I hope someone can tell me what is going wrong.
Why? Go to debians pages and click on "file bug report". You will get
a form to fill out, with spaces that you must fill that will encourage
you to produce an actionable report.
I somewhat suspect that the lucent is the problem! Surely IT DOES NOT
DO FAXES!!!
: Thanks - Hari
: Here is the log file:
: efax: Wed Sep 6 22:56:31 2000 efax v 0.9 Copyright 1999 Ed Casas
Well, you have efax 0.9.
: efax: 56:31 compiled Dec 15 1999 21:05:01
: efax: 56:31 TIFF version 4.2 file (little-endian)
: efax: 56:31 TIFF directory at 8 with 20 tags, last image.
: efax: 56:31 argv[7]=/var/lock/LCK..ttyS14
right modem.
: efax: 56:31 argv[8]=-iZ
: efax: 56:31 argv[9]=-i&FE&D2S7=120
I must remember that!
: efax: 56:31 created text lock file /var/lock/LCK..ttyS14
: efax: 56:31 opened /dev/ttyS14
: efax: 56:32 command "+FCLASS=?"
: efax: 56:32 waiting 5.0 s
Well, well, it says it does fax class 1!
: efax: 56:32 .402 [<CR><LF>0,1<CR><LF>]
: efax: 56:32 .402 [<CR><LF>OK<CR><LF>]
: efax: 56:32 response "OK"
: efax: 56:32 command "+FCLASS=1"
: efax: 56:32 waiting 5.0 s
Amazing.
: efax: 56:32 .532 [<CR><LF>OK<CR><LF>]
: efax: 56:32 response "OK"
: efax: 56:32 using LT V.90 Data+Fax Modem Version 5.68 in class 1
: efax: 56:32 command "+FTM=?"
: efax: 56:52 .612 [<CR><LF>OK<CR><LF>]
: efax: 56:52 response "OK"
: efax: 56:52 Warning: bit-reversed HDLC frame, reversing bit order
: efax: 56:52 received 13 bytes:
: efax: 56:52 ff c0 04 b5 00 6c 02 01 23 80 0f 38 f4
And it works!
: efax: 56:52 received NSF - answering features
: efax: 56:52 command "+FRH=3"
: efax: 56:52 waiting 35.0 s
: efax: 56:52 .652 [<CR><LF>CONNECT<CR><LF>]
: efax: 56:52 response "CONNECT"
: efax: 56:53 waiting 2.0 s
: efax: 56:53 .392 [<CR><LF>OK<CR><LF>]
: efax: 56:53 response "OK"
: efax: 56:53 received 25 bytes:
: efax: 56:53 ff c0 02 6c ac 8c 4c ac 2c cc 0c 1c 2c 04 04 04
: efax: 56:53 04 04 04 04 04 04 04 a4 e5
: efax: 56:53 received CSI - answering ID
: efax: 56:53 remote ID -> 4803452156
: efax: 56:53 command "+FRH=3"
Perfect.
: efax: 56:53 received DIS - answering capabilities
: efax: 56:53 remote has no document(s) to send, and can receive
: efax: 56:53 local 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
: efax: 56:53 remote 196lpi 9600bps 8.5"/215mm any 2D ECM-64 -
: 20/10ms
: efax: 56:53 session 196lpi 9600bps 8.5"/215mm any 1D - -
: 10ms
: efax: 56:55 response "OK"
: efax: 56:55 command "+FTM=96"
: efax: 56:55 waiting 3.1 s
: efax: 56:56 .002 [<CR><LF>CONNECT<CR><LF>]
: efax: 56:56 response "CONNECT"
: efax: 56:56 waiting 30.0 s
: efax: 57:02 .732 [<CR><LF>ERROR<CR><LF>]
: efax: 57:02 response "ERROR"
: efax: 57:02 Error: wrong response after waiting
The other side doesn't do the right thing. Try against a different
receiver.
: efax: 57:02 sent TCF - channel check of 1800 bytes
: efax: 57:02 local 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
: efax: 57:02 remote 196lpi 9600bps 8.5"/215mm any 2D ECM-64 -
: 20/10ms
: efax: 57:02 session 196lpi 9600bps 8.5"/215mm any 1D - -
: 10ms
: efax: 57:02 command "+FTS=8"
: efax: 57:02 waiting 3.0 s
: efax: 57:02 .852 [<CR><LF>OK<CR><LF>]
: efax: 57:02 response "OK"
: efax: 57:02 local 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
: efax: 57:02 remote 196lpi 9600bps 8.5"/215mm any 2D ECM-64 -
: 20/10ms
: efax: 57:02 session 196lpi 9600bps 8.5"/215mm any 1D - -
: 10ms
: efax: 57:02 command "+FTS=8"
: efax: 57:02 waiting 3.0 s
: efax: 57:02 .962 [<CR><LF>OK<CR><LF>]
: efax: 57:02 response "OK"
: efax: 57:02 Error: no command/response from remote
Seems clear to me. What are you trying to do? Send or receive? It
almost looks like receive mode, when the other side doesn't have
anything to send!
Peter
------------------------------
From: [EMAIL PROTECTED] (Beda Rickenbacher)
Subject: Problem with "swiss german" keyboard layout
Date: Thu, 07 Sep 2000 09:17:02 GMT
Hi,
I just installed the RH6.1 (incl. KDE 1.X) and it seems to run just
perfect, except the keyboard.
I call on a terminal window the program kbdconfig and select the sg as
my layout. I close everything and restart the Linux completly. But
still I have US Lay-out on my keyboard.
Does anyone have an idea, what I am doing wrong?
Many thanks for your assistance
Beda
------------------------------
From: Crni Gorac <[EMAIL PROTECTED]>
Subject: Re: random Linux freezing
Date: Thu, 07 Sep 2000 09:06:14 GMT
In article <8n1pqj$79n$[EMAIL PROTECTED]>,
Crni Gorac <[EMAIL PROTECTED]> wrote:
> I'm experiencing strange problems with a PentimPro/166 machine. After
> installing RedHat Linux 6.2, machine is freezing at random intervals
> upon boot. It is freezing even in runlevel 3, without X windows, so I
> guess this has nothing to do with it. First thing that I'm usually
> doing upon installation is to compile kernel and machine is always
> freezing during this operation, sometimes when compiling kernel and
> sometimes when compiling modules. RedHat Linux was installed
> previously on this machine and was working without any problems
> (and several versions of kernel were recompiled). During last two
> months machine was dual booted between Windows NT Workstation 4.0
> and SCO OpenServer 5.0.5a, also without any problems. Nothing
> changed in the BIOS in the meantime.
>
> I would be grateful for any hint.
>
Some time ago, freezing problem suddenly dissappeared. I suppose it was
caused by extremly hight air temperatures in my region (40+ Celzius
degrees). However, I'm wondering now was this normal, i.e. should I
trust to this machine further?
Thanks.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Holger Meinecke <[EMAIL PROTECTED]>
Subject: INIT_RD in rc.config
Date: Thu, 07 Sep 2000 11:09:01 +0200
Hi,
I use Linux SuSE Distribution 6.3. In the configuration file rc.config there is a
Parameter INITRD_MODULES which is responsible for loading modules in ram disk during
the boot process.
Example: INITRD_MODULES="aha152x"
The question is, how can I set parameters for this modules. I have set my parameters
in /etc/modules.conf, but it doesn't work.
Thanks
------------------------------
Crossposted-To: aus.computers.linux
Subject: Re: Loopback Device Creation
From: [EMAIL PROTECTED] (Daniel Robert Franklin)
Date: 7 Sep 2000 17:29:47 +1100
Jim Bell <[EMAIL PROTECTED]> writes:
>Hi,
>I need to create an arbitrary number of loopback devices on the fly. I
>then want to mount filesystem images on these devices. /dev/loop[0-7]
>are not enough.
Tell the kernel you want more loopback devices - e.g., in your lilo.conf add
this:
append = "max_loop=32"
or if you already have an append line, just add the max_loop=32 after a
comma to give you 32 loopback devices.
Hope that helps,
- Daniel
--
******************************************************************************
* Daniel Franklin - Postgraduate student in Electrical Engineering
* University of Wollongong, NSW, Australia * [EMAIL PROTECTED]
******************************************************************************
------------------------------
** 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
******************************
