Linux-Setup Digest #576, Volume #20 Tue, 6 Feb 01 08:13:08 EST
Contents:
Re: Mounting a zip drive throw a network ("Peter T. Breuer")
Re: apt-get --> seg fault ("Peter T. Breuer")
Re: Help: Linux on Intel 386 problem ("Peter T. Breuer")
Re: Serious Partition Problems ("Peter T. Breuer")
Segmentation fault ("Nicolas DUTEIL")
Re: I need an advice for Zip USB, ("cazzi miei")
Re: INIT: Id "x" respawing too fast: disabled for 5 minutes. (JJK)
Re: setup issue: boot partition size too big (Eric)
Re: What am I doing wrong? (Mark Bratcher)
Re: Linux as a gateway (Eggert Ehmke)
Linux Boot + Windows2000 or Windows ME ([EMAIL PROTECTED])
Windows Read & Write Access For All (Mike Gratis)
Re: Windows Read & Write Access For All (Alexander Roalter)
Trying to compile 2.4 (Jeffrey Hood)
newsgroup server on the Intranet - linux 5.2 (niketan sharma)
Re: Windows Read & Write Access For All (Eric)
Re: My Redhat 7.0 doesn't reboot ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Mounting a zip drive throw a network
Date: Tue, 6 Feb 2001 00:04:54 +0100
FilipeMaia <[EMAIL PROTECTED]> wrote:
> Is it possible to mount a zip drive so that it can be read/written by
> everyone?
Depends if it's an ext2fs or vfat file system. In principle, the
question has nothing to do with zip drives (answer is yes to both).
> Or is there an easy way to mount it throw a graphic interface in a win box
> connected to the linux box?
eh?
> I have samba installed and i want to share the zip drive in r/w mode, but i
> can't do it.
> Can anyone help?
I suspect you are talking about the FAQ of how to make dos filesystems
read/write for all. Man mount. Option umask.
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: apt-get --> seg fault
Date: Tue, 6 Feb 2001 00:02:56 +0100
james <[EMAIL PROTECTED]> wrote:
> I'm using Corel (probably my first mistake) and within a few days
> apt-get (0.3.11) has stopped working, throwing a segmentation fault
> every time I try to install anything. The wonderful thing is that I
> can't replace it from the CD or debian's site because it's distributed
> in a .deb file (chicken/egg problem) And I can't convert it to a tgz
You don't need apt-get for a .deb. You need dpkg (and not even that).
> because I can't install Alien (it's a deb, too) I also tried grabbing
You can unpack the .deb easily enough. It's an "ar" of two tars.
"ar x foo.deb" should get them out.
> the sources for dpkg, but they require configure, which isn't installed
> on my system (which I can't add from the CD for the same reason)
> Or rather than reinstall apt, is the seg fault likely to be a relatively
> simple thing to fix?
No .. it should never happen. Likely your disk is full or the
executable is corrupted. If I were you I'd cut down the number of
sources listed in /etc/apt/...
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.suse,alt.os.linux
Subject: Re: Help: Linux on Intel 386 problem
Date: Mon, 5 Feb 2001 23:59:29 +0100
In comp.os.linux.setup Erik Leunissen <[EMAIL PROTECTED]> wrote:
> locks up at a certain stage in linuxrc. The stage where the system locks
> up is after the selection of the keybord settings, and the main linuxrc
How far after? If it's just the setting the kbd, don't do it!
> menu never appears. A manual reset is needed to unlock the machine
> (<Ctrl> <Alt> <Del> does not work anymore).
> I believe that the very stage at which this happens, could be a clue to
> the nature of the problem (that is to more experienced Linux users than
> me).
Only if you show us the command that locks the machine. Sorry .. that's
up to you.
> Below, I've described the hardware (in case that this information is
> has also run under Win95 previously). The Linux distribution I've been
> using is SuSE 6.4.
Try something older .. slackware 3.0 or redhat 4.2.
> Can the nature of the problem (more or less) be deduced from this
> information ?
No .. I'm surprised it's an ide disk and not an rll.
> ==== Hardware (very old stuff) =========
> Intel 386 DX 40 Mhz
> 8 MB RAM
> 1 IDE hard disk 1,2 MB
> 1 IDE/ATAPI CDROM (cannot boot from here, alas!)
Try dispensing with the cdrom and see if it helps.
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Serious Partition Problems
Date: Tue, 6 Feb 2001 08:39:53 +0100
HockeyChief1 <[EMAIL PROTECTED]> wrote:
> I already tried that with Redhat installer and there was an error
> message...something about no drive to partition (sounds bad)
Sounds bad enough that you would think to take note of it, eh?
Unsupported IDE controller, probably. Don't use dma100 at install. Plug
your disk in somewhere standard.
Peter
------------------------------
From: "Nicolas DUTEIL" <[EMAIL PROTECTED]>
Subject: Segmentation fault
Date: Tue, 6 Feb 2001 10:57:19 +0100
Hi, Does anybody know where the "segmentation fault" comme from ?
On my suse 7.0, it just happens randomly...I just keep reinstalling Linux.
All works ok for a few hours and then the "segmentation fault" appears (not
always after launching the same prog) and I have to lauche manually e2fsck
after rebooting.
When I try to launch e2fsck, I get another "segmentation fault" and I can't
do anything but reinstalling.
My PC is a PIII 650 with 256M Ram using suse 7.
0
Thanks by advance
Nico
------------------------------
From: "cazzi miei" <cazzi_miei@micros~1.com>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: Re: I need an advice for Zip USB,
Date: Tue, 6 Feb 2001 13:03:17 +0100
Glitch <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]
> ME wrote:
>
> > Thanks for reading this,
> >
> > I am trying to mount (dev/sda4) a Zip 100 USB drive under Kernel 2.2.16
> > (Suse 7.0). The modules usbcore, usb-ohci and usb-storage are loaded,
but
> > yet the system fails to communicate with the Zip drive. While booting up
the
> > system it finds the Zip drive. The error message is:
> >
> > sda: Read Capacity failed
> > sda: status=0, message=00, host=7, driver=00
> > sda: sense not available
> > sda: block size assumed 512 bytes, disk size 1 GB
> >
> > sda: scsidisk I/O Error: dev08:00, sector 0
> > unable to read partition table.
> >
> > My USB Sony CD/RW drive is also seen but can not be mounted. I think it
is a
> > SCSI issue, which I have tried to remedy with the insertation of module
sg,
> > but that did not help either. Perhaps somebody has an advice for me, any
> > input is appreciated.
> >
> > Thanks,
> >
> > Bruce
>
>
> The error message is 'unable to read partition table'......maybe it
> can't read one b/c there isn't one in the first place? (ie. there is no
> disk in the drive)
>
you gotta load the module sd_mod to make the device recognized, because it's
seen as a scsi device....
then you mount sda4... and that's done... i took a while to understand that
too as I'm not used to scsi devices...
Byez
Giorgio Agrelli
========================================================================
I'm at university away from my Linux Box...
heck this lookout thing sucks men
------------------------------
From: [EMAIL PROTECTED] (JJK)
Subject: Re: INIT: Id "x" respawing too fast: disabled for 5 minutes.
Date: Tue, 06 Feb 2001 09:54:43 GMT
In article <94Of6.82775$[EMAIL PROTECTED]>, "Jason"
<[EMAIL PROTECTED]> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi,
> Im a fairly new user to linux, I have had Rad Hat 6.1 (cartman)
>running for a while now, when I added some cooling fans I started
>getting this error:
>
>INIT: Id "x" respawing too fast: disabled for 5 minutes.
>
>What happened?
>
>The machine is:
>Intel P166 running @ 200mhz
>1.2gb Maxtor (/ /swap /boot)
>10gb Western Digital (/home)
>Kingston 10/100 NIC
>
>The machine is not here with me, but in my office, I dont remember
>what the video card is.
>Im not running X Windows, just Apache and an ftp server.
>Please email any help you might have. Thanx
>
does it say Id "x" or is "x" shorthand for, say, ttyS0?
At any rate, look in /etc/inittab and look for
id:<n>:initdefault:
where <n> is most likely 5, change this number to 3.
Also, comment out the line
x:5:respawn:/etc/X11/prefdm -nodaemon
by putting a '#' in front of it.
Afterwards, reboot and see if you still see the problem. No idea why this
started happening all of a sudden though.
HTH,
JJK
===========================
JJK / Jan Just Keijser
Unix/Linux Systems Engineer
smtp: [EMAIL PROTECTED]
flames > /dev/null 2>&1
===========================
------------------------------
From: Eric <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.questions
Subject: Re: setup issue: boot partition size too big
Date: Tue, 06 Feb 2001 11:24:51 +0100
Reply-To: [EMAIL PROTECTED]
It's actually really simple:
1) either get a lilo version 21.4.3 or higher.
compile and install it (read the documentation that is included)
2) get a non-destructive repartitioning tool.
examples are: PowerQuest's Partition Magic : easy to use, but not
free
GNU's parted : perhaps less easy, but
free
I'm not sure(And actually doubt it), but FIPS might be capable of
this too.
Just take off one cylinder from the beginning of C: and make that
/boot
Succes.
Eric
------------------------------
From: [EMAIL PROTECTED] (Mark Bratcher)
Subject: Re: What am I doing wrong?
Date: Tue, 06 Feb 2001 11:09:23 GMT
John,
I just read the manual for the latest LILO that I have (21.6).
It says this regarding the warning message you are referring to:
LILO's boot sector can only be booted from the first disk unless some
special boot manager is used.
The 'LI' appears when the primary boot loader of LILO has successfully
run and is then going to load the secondary boot loader. This is
what is failing.
I think the way to fix it is to at least create your /boot partition
(which does not need to be very large, a few megabytes) on your
primary IDE drive. The other Linux partition(s) can be on the
secondary.
Thanks.
Mark
In article <95l29r$ste$[EMAIL PROTECTED]>, John Bilbao wrote:
>Thanks Mark. To be fair, I was impressed at the way RH7 installed - much
>better than RH5, my last dip into Linux. It's just a pity that I can't get
>it to boot without a floppy, which is of course slow and not as elegant as a
>hd boot. I remember having lots of "fun" with lilo last time too so was
>hoping to avoid that this time around. No such luck.
>
>Here's what I'm doing:
>
>1) Boot into linux using the boot floppy. Linux is installed totally in a
>2.5GB /root partition on hdb1 (a 15GB eide drive). There is also a 500MB
>swap partition on the drive somewhere too (maybe hdb6).
>2) I edit /etc/lilo.conf to install lilo in the root partition - i.e.
>/dev/hdb1.
>3) I execute lilo and it installs but gives a warning that it is not on the
>first drive.
>4) I dd the boot sector onto a fat16 floppy.
>5) I boot into Win2k and copy the boot sector into the root folder.
>6) I edit boot.ini to show a Linux option pointing to the boot sector file.
>7) I reboot and choose "Linux"
>
>The computer hangs at "LI".
>
>John
>
>
>"Mark Bratcher" <[EMAIL PROTECTED]> wrote in message
>> Although I don't have a fast answer to why you're having the problems,
>> I will say that LILO is no different than, say, the boot manager in
>Windows NT.
>> So, LILO is not what is making your Linux loading experience worse than
>Windows.
>> That being said, if you obtain the latest version of LILO, the 1023
>cylinder
>> limit disappears, so you would be able to eliminate that issue (if it is
>an
>> issue in your case).
>>
>> I've loaded Linux on several PCs and always found it to really be smoother
>> than Windows. I've even seen Linux recognize hardware that Windows has had
>> trouble recognizing (really exotic stuff, like COM2 and LPT2). :-)
>>
>> I hope you'll stick with it a little longer. I think you'll find in
>hindsight
>> it was probably something simple being overlooked.
>
>
--
Mark Bratcher
To reply, remove _UNSPAM from my email address
=========================================================
Escape from Microsoft's proprietary tentacles: use Linux!
------------------------------
From: Eggert Ehmke <[EMAIL PROTECTED]>
Subject: Re: Linux as a gateway
Date: Tue, 06 Feb 2001 12:13:49 +0100
Reply-To: [EMAIL PROTECTED]
On Mon, 5 Feb 2001 17:14:10 -0700, "George" <[EMAIL PROTECTED]> wrote:
>Ya ya ya ya - No I don't want to search my readme's and how to's. Don't
>waste your time with flames.
So here's a howto ready for you:
http://www.linuxdoc.org/HOWTO/IP-Masquerade-HOWTO.html
Some reading must be done on your part, I guess.
--
Eggert Ehmke
Email: [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: Linux Boot + Windows2000 or Windows ME
Date: Tue, 06 Feb 2001 11:13:18 GMT
I try to install Windwos2000 with Linux Redhat 7, I installed LILO not
in MBR, but is the same partion with Linux.
I do exactly like How-to Doc said (Install Windows NT with Linux), and
copy first 512Kb in file called bootsec.lnx, and modefied file
(boot.ini), but it did not work...... I dont know why??????
can any one help me plz
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Mike Gratis <[EMAIL PROTECTED]>
Subject: Windows Read & Write Access For All
Crossposted-To: alt.os.linux.caldera
Date: Tue, 6 Feb 2001 07:13:20 -0500
After installing Caldera 2.4, I followed the instructions for enabling
write access to my Windows HDs & partitions as outlined in the
documentation (via Webmin), checked that it worked properly (...as Root at
that point) and didn't think much more of it. This weekend, I went to
write something to the Windows drive as a User and got an error message
that I couldn't do it. Root still works fine. I've tried to change the
properties by right clicking on the drives (hda1, hda5 & hda6) for the
Windows HDs/partitions; but they won't stay for Users or Groups, only for
Root. Either the checkboxes uncheck themselves, or I get an actual message
saying that the properties can't be changed. I've done my usual reading
and checking the web; but to no avail. So, what am I missing here -- How
do I enable Windows write access for all users and not just Root? Any help
is appreciated, and thanks in advance....
--
Mike Gratis
[EMAIL PROTECTED]
------------------------------
From: Alexander Roalter <[EMAIL PROTECTED]>
Subject: Re: Windows Read & Write Access For All
Date: Tue, 06 Feb 2001 13:22:43 +0100
Mike Gratis wrote:
>
> After installing Caldera 2.4, I followed the instructions for enabling
> write access to my Windows HDs & partitions as outlined in the
> documentation (via Webmin), checked that it worked properly (...as Root at
> that point) and didn't think much more of it. This weekend, I went to
> write something to the Windows drive as a User and got an error message
> that I couldn't do it. Root still works fine. I've tried to change the
> properties by right clicking on the drives (hda1, hda5 & hda6) for the
> Windows HDs/partitions; but they won't stay for Users or Groups, only for
> Root. Either the checkboxes uncheck themselves, or I get an actual message
> saying that the properties can't be changed. I've done my usual reading
> and checking the web; but to no avail. So, what am I missing here -- How
> do I enable Windows write access for all users and not just Root? Any help
> is appreciated, and thanks in advance....
>
> --
> Mike Gratis
> [EMAIL PROTECTED]
you may have to check the options in /etc/fstab . Here you can specify
with the user or users options who can access to the partitions. man
fstab should
do fine.
--
MfG
Ro-ee
------------------------------
From: Jeffrey Hood <[EMAIL PROTECTED]>
Subject: Trying to compile 2.4
Date: Tue, 06 Feb 2001 12:23:32 GMT
[RedHat 6.2]
I am relatively new to kernel compiling, and downloaded the 2.4 source
last week... as per the instructions that I found, I did the following:
make mrproper
make xconfig
make dep
make bzImage
make modules
make modules_install
I -tried- to select all of the appropriate options in xconfig, but seemed
to have missed some of them as the kernel ran fine (after a few tries...)
but was missing some modules... most notably the nic driver... I ran
insmod on the modules that compiled, and some seemed to install okay...
After playing around, and having some more success, I got everything
pretty much working, but now I want to put 2.4 on my "real" box, and
found an option "make oldconfig" and was wondering if that is what I
should use to get ALL of the old kernel configuration before I start to
change things (my Athelon 800 wasn't picked up right by RHat 6.2, and I
have to put a lilo switch... supposedly if I pick the Athelon in xconfig
that should be fixed...)
So mostly, my question is should I run the following sequence, and am I
missing anything in trying to compile on a box that has all of the
devices and modules working fine (don't want to loose anything...)
make mrproper
make oldconfig
make xconfig - set new settings - and how do I check to see if everything
came in fine...
make dep
...
What should I be running prior to all of this to get an accurate list of
what I need to check, and where are the kernel options that were used in
the install of RedHat 6.2 located...
Also, what -should- I have downloaded to sucessfully compile... I got the
2.4 kernel source, as well as modutils-2.4.2, util-linux2.10r,
ksymoops2.4.0.1, mkinitrd3.0.5 --- and are any of these not necessary ?
Thanks in advance...
JH
--
Jeffrey Hood
HM Consulting, Inc.
jhood [you-know-why] at hmcon.com
------------------------------
From: niketan sharma <[EMAIL PROTECTED]>
Subject: newsgroup server on the Intranet - linux 5.2
Date: Tue, 06 Feb 2001 12:30:03 -0000
how to setup a newsgroup news server on the intranet want to use INN
preferably books site suggestion required
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: Eric <[EMAIL PROTECTED]>
Subject: Re: Windows Read & Write Access For All
Date: Tue, 06 Feb 2001 13:46:05 +0100
Reply-To: [EMAIL PROTECTED]
Alexander Roalter wrote:
>
> Mike Gratis wrote:
> >
> > After installing Caldera 2.4, I followed the instructions for enabling
> > write access to my Windows HDs & partitions as outlined in the
> > documentation (via Webmin), checked that it worked properly (...as Root at
> > that point) and didn't think much more of it. This weekend, I went to
> > write something to the Windows drive as a User and got an error message
> > that I couldn't do it. Root still works fine. I've tried to change the
> > properties by right clicking on the drives (hda1, hda5 & hda6) for the
> > Windows HDs/partitions; but they won't stay for Users or Groups, only for
> > Root. Either the checkboxes uncheck themselves, or I get an actual message
> > saying that the properties can't be changed. I've done my usual reading
> > and checking the web; but to no avail. So, what am I missing here -- How
> > do I enable Windows write access for all users and not just Root? Any help
> > is appreciated, and thanks in advance....
> >
> > --
> > Mike Gratis
> > [EMAIL PROTECTED]
> you may have to check the options in /etc/fstab . Here you can specify
> with the user or users options who can access to the partitions. man
> fstab should
> do fine.
The manpage is indeed the place to look,
but it's the umask option that's needed for this.
Eric
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: My Redhat 7.0 doesn't reboot
Date: Tue, 06 Feb 2001 12:45:24 GMT
> What command are you using? To re-boot the machine, try
>
> shutdown -r now
>
> This should re-boot the machine to Linux.
>
> I can't tell exactly, but it sounds as if you're using the halt
> command:
>
> shutdown -h now
>
> If so, the OS is shutting down your machine completely, and your
> monitor is complaining because the PC isn't sending it anything.
>
> HTH
>
> Sent via Deja.com
> http://www.deja.com/
>
Hi John,
Thanx for your post, it did not solve problem, but let me find strange
behaviour of my box. I tried two commands and they works in other way
arround: shutdown -h reboots system, while shutdown -r halts it !!!
Weird !!! I will do further investigation, but if someone had this
problem before, please give me a help.
Thanx alot
Qlos
Sent via Deja.com
http://www.deja.com/
------------------------------
** 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
******************************
