Linux-Setup Digest #591, Volume #20 Thu, 8 Feb 01 17:13:11 EST
Contents:
Re: recompiling debian (newbie question) (Alex Yung)
help with telnet session freeze. ("Kenny@BUI")
Re: What does Lilo write to boot= ? ("Eric en Jolanda")
Re: Etherlink 3c509 on RedHat 6.2 (Craig Orsinger)
Re: What's the trick to make windows right itself? ([EMAIL PROTECTED])
Re: Stumped by random X freezes,slow system (Chet Vora)
Re: ATA100 RAID Question (jwk)
Re: Copying Linux 1:1 on new harddisk drive?? (Marcus Halbe)
Re: Lilo problem ("Philip Hoole")
gnome+sawfish: moving workspaces? (Greg Trafton)
Re: Invisible ".filename" files in user ftp directories (David Efflandt)
Re: No sound in RedHat 7.1 (Omar)
backspace vs. delete (John Doner)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Alex Yung)
Subject: Re: recompiling debian (newbie question)
Date: 8 Feb 2001 19:03:19 GMT
Reply-To: [EMAIL PROTECTED]
The base installation does not include the kernel source nor the
gcc compiler. It just gives you a functioning system so that you
can install additional software via the following medium ppp modem
dialin, ethernet connection or cdrom. Depending on the type of
installation you have selected, a lots of software packages may
have been selected for you. But you need to choose a medium which
completes the additional software installation.
When I said the type of installation, you should be prompted on how
you intend to use your machine such as development workstation or
server etc... Assuming you are using the Intel cpu, this is the
installation document:
http://www.debian.org/releases/stable/i386/install.en.html
You are about in the end of chapter 7. If your machine has no other
way of connecting to the net, your best option is to get the official
debian CD set. Everything you need is there. You can purchase the
CDs or make your own depending on what is available.
I don't know whether it is necessary to recompile the kernel if you
only want to use pppoe. The is a separate package for PPPoE in
"dists/potato/main/binary-i386/net/pppoe_1.0-1.deb"
Wayne Hayes ([EMAIL PROTECTED]) wrote:
: I recently downloaded and installed the base Debian Linux system from a few
: floppys. The install went well but I cannot seem to recompile my kernel.
: Some reading has led me to understand that I need a C++ compiler and kernel
: files to actually recompile. (I thought that these would automatically be a
: part of the install).
: I need to be able to recompile so I can get my DSL connection working in
: Linux (via pppoe) and finish installing the other modules.
: Can anyone please tell me what the actual filenames are and/or the
: directories are that they reside on? I've spent over a week digging and
: nothing yet. Frustration is beginning to set in.
: Thanks
: Wayne
------------------------------
From: "Kenny@BUI" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.misc
Subject: help with telnet session freeze.
Date: Thu, 8 Feb 2001 14:16:17 -0500
hello,
we have a rh6.2 server running an app. that uses microfocus.
when we telnet to the box from win98 and try to run the app. the session
freezes
as we move through the software. we have done this so many times that this
one is a mystery. we have other linux boxes that do not behave like this.
thank you,
kenny.
------------------------------
From: "Eric en Jolanda" <[EMAIL PROTECTED]>
Subject: Re: What does Lilo write to boot= ?
Date: Thu, 8 Feb 2001 20:30:22 +0100
> I have done that. It seems to be something to do with the fact that is on
> the third disk but I can't figure out what to do.
>
Suppose this is still the same problem as your previous thread (another lilo
problem?)
Was that last thing you tried a typo?
(boot=/dev/hdc instead of boot=/dev/hdc1 ?)
Or did it not solve your problem?
Then I still advise you to connect hdc as hdb, as your BIOS may be incapable
of booting from the second IDE controller.
You can try this by overwriting the MBR (on hda that is) with lilo code to
directly boot linux from hdc (back it up first, as it now contains the OS/2
bootmanager).
try it, no chaining yet, no map-drive stuff.(you will need the disk=/bios=
stuff)
If it fails: stop trying, or perhaps update your BIOS.
PS. what you also might wanna try first : skip the disk=/dev/hdb line. As it
is your CDROM, I'm not sure if it will be 0x82. It may be skipped, so hdc is
0x82 instead of 0x83
Succes,
Eric
------------------------------
From: Craig Orsinger <[EMAIL PROTECTED]>
Subject: Re: Etherlink 3c509 on RedHat 6.2
Date: Thu, 08 Feb 2001 19:39:35 GMT
Wade Lindsey wrote:
>
> I'm having a problem getting linux to recognize my ethernet card I think. I
> have everything setup correctly (or so I think) but when linux is booting
> up, when it gets to "Bringing up eth0" it always fails. It says its
> looking for something like " /modules/psmcia/3c509_c.o " , but I checked
This is very confusing. There is a 3c509 ISA board, but I'm not
aware of a 3c509 PCMCIA card. There is a 3c589 PCMCIA card, which is
supported by the 3c589_cs driver. If you are using a laptop, this is
probably the module you want. If you're running a desktop, it's probably
a 3c509, which is supported by the 3c509 module, which is located in
the /lib/modules/<kernel version>/net directory.
> that directory and while it has similar files, it doesn't have that object
> file. Is that my problem? And, if so, can anyone tell me how to fix it.
If your system is a laptop, you need to reconfigure the PCMCIA
card software. I don't use this software, so you'll just have to try
doing this through the administration software. Make sure it's looking
for the correct device (you can check the card to see if it's a 3c589).
If you're using a desktop, however, just check to the /etc/conf.modules
file to ensure that there is a line in it that looks like this:
alias eth0 3c509
You may need to tell Linux what the IRQ is that the 3c509 is
using. If so, do this with an options line of the form:
options 3c509 irq=11
or whatever.
> Also, someone mentioned to me to check my /proc/pci file. That's empty.
> What should be in there???? Thanks
If your computer doesn't have a PCI bus, nothing should be in
there. If you follow up this post, please include a description of the
hardware you're using.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: What's the trick to make windows right itself?
Date: Thu, 08 Feb 2001 19:26:19 GMT
When I first installed redhat, I told it to put lilo in the master boot
record. So when I tried to undo lilo, all I did was the fdisk /mbr.
After that, C: didn't show up at all when booting to a dos floppy. So
sys c: was out. It shouldn't matter though. I've done only the fdisk
/mbr in the past in similar situations to this one and it brought
everything back. Now, something else is out of whack.
brian
In article <[EMAIL PROTECTED]>,
subuno <[EMAIL PROTECTED]> wrote:
> When you did fdisk /MBR did you first so SYS C: to copy the files the
> machine needed to boot back over. Might give that a try. I did that
> first and then fdisk /MBR. Hope it helps.
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Chet Vora <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.os.linux.misc
Subject: Re: Stumped by random X freezes,slow system
Date: Thu, 08 Feb 2001 14:53:43 -0500
Tim,
<sheepish grin> I realized after sending out that mail what a idiotic impression that
statement must have given. What I meant to convey was the SCSI driver could be a
problem...oh, well, some days are just not your days.
Anyway, the reason I suspect SCSI driver is cos I vaguely remember hearing somewhere
that RH (and Linux in general) has somewhat unstable support for SCSI. Again, I'm a
relative newbie so don't know if this is so.
Regards,
Chet
Tim Roberts wrote:
> Chet Vora <[EMAIL PROTECTED]> wrote:
> >
> >... There doesn't seem to be any pattern to the freezes. The one thing worth
> >mentioning is that the system seems to be using the SCSI driver for the PCI bus.
> >
> >Relevant o/p of dmesg:
> >-------------------------
> >VFS: Mounted root (ext2 filesystem).
> >ncr53c8xx: at PCI bus 2, device 0, function 0
>
> Come on, that's silly. Your SCSI controller is a device ON your PCI bus.
> That's all it means.
> --
> - Tim Roberts, [EMAIL PROTECTED]
> Providenza & Boekelheide, Inc.
------------------------------
From: [EMAIL PROTECTED] (jwk)
Crossposted-To: comp.os.linux.hardware
Subject: Re: ATA100 RAID Question
Date: 8 Feb 2001 20:44:34 GMT
Reply-To: [EMAIL PROTECTED]
On Thu, 08 Feb 2001 09:11:13 GMT, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>Hi
> I have bought a ATA-100 RAID Card (use HPT370 chipset) .
>if I run Raid 0+1 ,if one of the Hard Disk have the problem, the System
>should still can Boot, but is that any Program or methods to know/
>monita the harddisk's status!?
>THanks!
>
You should double-check first if Linux supports the Raid feature (well
feature, let's call it the Raid windows driver) of the HPT370. IIRC, it
doesn't.
Good luck,
Jurriaan
--
Time is money. Especially if you make clocks.
GNU/Linux 2.2.19pre8 SMP/ReiserFS 2x1402 bogomips load av: 0.34 0.09 0.02
------------------------------
From: [EMAIL PROTECTED] (Marcus Halbe)
Subject: Re: Copying Linux 1:1 on new harddisk drive??
Date: Thu, 08 Feb 2001 20:47:27 GMT
Reply-To: [EMAIL PROTECTED]
On Thu, 01 Feb 2001 14:31:50 +0100, Eric <[EMAIL PROTECTED]> wrote:
Hi, Eric and all others who have helped!
Thanks for your answers!
I have solved the problem with Eric's help, as well as with the help of
mray at #linuxhelp on irc-server irc.linpeople.org as well as with a
bunch of other people at irc.linpeople.org channel #linpeople. What a
wonderful crowd.
I will pass on the favors done to me to mankind, though not as a
linux-helper (evidently), but I'll think of _something_.
I will try to reconstruct what I did in case somebody else has the same
problem:
the problem was:
A student made a firewall/router/comm-server for us on an old P133.
Distrib: SuSE 6.4 (I don't think that matters, though).
3 Hard disc drives (scsi):
sda, sdb, sdc
They were partitioned thus:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sdc1 993840 361276 581264 38% /
/dev/sda2 1493808 1229176 187520 87% /usr
/dev/sdb2 202188 51701 140045 27% /tmp
/dev/sda3 529048 307308 194432 61% /var
/dev/sda1 7496 2326 4770 33% /boot
/dev/sdb3 684660 65120 584200 10% /home
Problem:
2 of the drives where making really bad howling noises, like fingernails
scratching a blackboard, and I was afraid (and still am) that they would
faint anytime. Since the comm-server is/was really important for us, and
me being ignorant of Linux (Windows is soooo easy...) I worried.
I tried to make myself less ignorant, but time seemed an important
factor, so I asked without having read all the mans and damns.
I bought a new hdd (scsi, thus: sdd), capable of taking all data.
I formatted the new drive, mounted the existing partitions as
directories (/big) and:
First, followed Eric's advice:
cp -ax /boot /big/boot
cp -ax /usr /big/usr
cp -ax /var /big/var
cp -ax /tmp /big/tmp
cp -ax /home /big/home
cp -ax / /big
where /big would be the new hdd.
After some hassle, that worked.
Then, I thought FAT-oriented:
I changed the fstab such:
/dev/sdd2 swap swap defaults 0 0
/dev/sdd1 / ext2 defaults 1 2
/dev/sdd1 /usr ext2 defaults 1 2
/dev/sdd1 /tmp ext2 defaults 1 2
/dev/sdd1 /var ext2 defaults 1 2
/dev/sdd1 /boot ext2 defaults 1 2
/dev/sdb1 /home ext2 defaults 1 2
#/dev/sdb1 swap swap defaults 0 0
#/dev/sdc1 / ext2 defaults 1 1
#/dev/sda2 /usr ext2 defaults 1 2
#/dev/sdb2 /tmp ext2 defaults 1 2
#/dev/sda3 /var ext2 defaults 1 2
#/dev/sda1 /boot ext2 defaults 1 2
#/dev/sdb3 /home ext2 defaults 1 2
/dev/scd0 /cdrom auto ro,noauto,user,exec 0 0
/dev/fd0 /floppy auto noauto,user 0 0
none /proc proc defaults 0 0
and included in LILO.CONF:
image = /boot/vmlinuz.old
root = /dev/sdd1
label = newhdd
where sdd1 would be the location of the copied /root.
This brought me a decisive Kernel Panic; and since I was in much need, I
contacted above mentioned channel. After a bit of hin und her, uh, back
and forth, answer was:
><mray> Bingo... I think the problem is you're trying to use the same partition
>as different mount points. That's a unix no-no
...which was News for me.
Again, bear with me: I am a newbie.
So, mray suggested:
><mray> comment out the new stuff and go back to your old settings.
>Then run cfdisk on your new drive (assuming you don't need anything off of it).
>Setup a partition for each new mount point as necessary.
So I went and partitioned the new hdd same as the old ones, then copied
the partitions with
cp -ax /dev/sda2 /xhome (to take an example; of course, previously I
mounted the new sdd-partitions as /xhome, /xvar etc.):
old:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sdc1 993840 361276 581264 38% /
/dev/sda2 1493808 1229176 187520 87% /usr
/dev/sdb2 202188 51701 140045 27% /tmp
/dev/sda3 529048 307308 194432 61% /var
/dev/sda1 7496 2326 4770 33% /boot
/dev/sdb3 684660 65120 584200 10% /home
new:
/dev/sdd1 7496 2315 4781 33% /xboot
/dev/sdd3 1493808 1229164 187532 87% /xusr
/dev/sdd5 529016 307120 194588 61% /xvar
/dev/sdd6 188130 51697 126394 29% /xtmp
/dev/sdd7 684628 65120 584168 10% /xhome
/dev/sdd8 1221468 1221468 0 100% /x
I then rewrote fstab thus:
#was old:
#/dev/sdb1 swap swap defaults 0 0
#/dev/sdc1 / ext2 defaults 1 1
#/dev/sda2 /usr ext2 defaults 1 2
#/dev/sdb2 /tmp ext2 defaults 1 2
#/dev/sda3 /var ext2 defaults 1 2
#/dev/sda1 /boot ext2 defaults 1 2
#/dev/sdb3 /home ext2 defaults 1 2
#now new:
/dev/sdd2 swap swap defaults 0 0
/dev/sdd8 / ext2 defaults 1 1
/dev/sdd3 /usr ext2 defaults 1 2
/dev/sdd6 /tmp ext2 defaults 1 2
/dev/sdd5 /var ext2 defaults 1 2
/dev/sdd1 /boot ext2 defaults 1 2
/dev/sdd7 /home ext2 defaults 1 2
/dev/scd0 /cdrom auto ro,noauto,user,exec 0 0
/dev/fd0 /floppy auto noauto,user 0 0
none /proc proc defaults 0 0
# End of YaST-generated fstab lines
Then, as afore mentioned, I included in lilo.conf:
image = /boot/vmlinuz
root = /dev/sdd8
label = newhdd
I booted anew and had a kernel panic.
So I remembered Eric's advice:
>boot lilo like this:
>LILO: newhdd root=/dev/sdd8
and that worked. Everything was beautiful.
So I then thought: okey, now Eric said to do:
>Don't forget to run /sbin/lilo
which I did, and rebooting, resulted in
>Warning: BIOS drive 0x83 may not be accessible.
Bringing this problem to the attention of well-meant linpeople, they
said:
><jaeger> warning doesn't necessarily mean it won't work
which I regarded, and after booting again, everything worked just fine.
I unhooked the pained hard disc drives, changed the /dev/sda-sdc to sdd
1 - 8 in fstab and the appropriate path in lilo.conf to /dev/sda and
everything is working and I am happy.
Eric, and all others:
thank you again for your time and patience! I will pass on the favor
however I can.
Greetings from Marcus.
--
Marcus Halbe / Kiel, Germany
"I don't make predictions. I never have and I never will."
- Tony Blair -
------------------------------
From: "Philip Hoole" <[EMAIL PROTECTED]>
Subject: Re: Lilo problem
Date: Thu, 8 Feb 2001 20:47:29 -0000
With RH7 you can type "linux lba32" when you boot from the CD and this
should get round the 1024 cylinder LILO limit. Worked for me !!
Good luck
"Marvin (Georg Ortmanns)" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Scott ZH wrote:
>
> > Hi, i am a newbie to linux. i have a problem to dualboot, i post message
> > in this
> > newsgroup, and i want to get a derect answer to slove this
> > problem(Because i am really a newbie and i want to boot from hard
> > disk very much).
> > sysytem:win2k(0-8.5GB of my HD) and RH7.o(8.5-20GB)**I only have one
> > hard disk**
> > partitions:C:&D:(8.5GB); **both are not FAT OR FAT32**
> > /boot(15MB);
>
> /boot is to big, see lilo message below..
>
> > problem: when run #lilo:
> > warning:device 0x1603 exceeds 1024 cylinder limit
> > fatal:sector 18292515 too large for linear
>
> !!!!!!!!!!!!!!!!
>
> --
> Regards
>
> Georg Ortmanns (Marvin) eMail [EMAIL PROTECTED]
> To get my PGP key send mail with subject "Send PGP key"
>
>
>
------------------------------
From: Greg Trafton <[EMAIL PROTECTED]>
Subject: gnome+sawfish: moving workspaces?
Date: 08 Feb 2001 15:53:08 -0500
Hi, All. I've been using fvwm for a while and in fvwm you can cycle
through your virtual desktops by using control-right or control-down
(etc). I'd really like to be able to do the same thing in
gnome+sawfish. is there a way to do that?
I know I can explicilty select (in my defaults) a workspace by pushing
meta-F1 or some such, but I haven't been able to figure out how to do
it with control-arrow keys yet..
any ideas?
thanks!
greg
--
Greg Trafton
([EMAIL PROTECTED])
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Subject: Re: Invisible ".filename" files in user ftp directories
Date: Thu, 8 Feb 2001 21:35:19 +0000 (UTC)
Reply-To: [EMAIL PROTECTED]
On Wed, 07 Feb 2001 19:41:23 -0800, Dan Poynor <[EMAIL PROTECTED]> wrote:
> I can't remember how I made .filename files invisible to users when they
>login via ftp. Somehow I thought I was being security conscious and
>avoiding questions from users who didn't really need to know they even
>existed. But now I need to see the .qmail files in my personal user
>directory at least when I ftp into the my server.
>
>After going over ftpaccess and other man pages I don't think I did this via
>a flag in the /etc/inetd.conf ftpd line or anything too obvious. If I
>telnet in and do "ls -la" in a directory the .filename files are definitely
>there.
>
>Now how'd I do that? (Using RH6.2 and wu-ftpd)
Are you saying that when you do 'ls -a' or 'ls -al' in your ftp client,
the dot files do NOT show up (sometimes 'dir' is an alias for that too)?
For GUI ftp clients it depends upon settings in the client program.
--
David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/
------------------------------
From: Omar <[EMAIL PROTECTED]>
Subject: Re: No sound in RedHat 7.1
Date: Thu, 08 Feb 2001 21:50:49 GMT
Lee Laniear wrote:
> Kevine,
>
> Thanks for the suggestion. I tried sndconfig, it first suggested that I
> "NOT" run it in a window (but I did anyway <G>). The sndconfig
> recognized the sound cardm as a Rockwell card and then said that it is
> not supported. I'm wondering whether the fact that I was running
> sndconfig through a window may have had anything to do with it. Here's
> a slightly related question. How can I startup Linux in text mode
> (ocassionally)? I tried switchdesk but it only gave me other graphical
> options.
alt-ctrl-F2 should give you a text mode login.
alt-ctrl-F7 switches back to the gui.
------------------------------
From: [EMAIL PROTECTED] (John Doner)
Subject: backspace vs. delete
Date: 8 Feb 2001 13:48:18 -0800
I run Linux on a PC at home, and MacX 1.5 on a Macintosh at
work. I work a lot on a Unix system, via MacX. I can also
have windows from my Linux system open at work. Emacs likes
to use 'Delete' (octal 177) for its erase character, so I set
my xterm sessions the same way, using stty. That works for
the Unix system, but not for Linux. Regardless of what I do
with stty, or the -tm option of xterm, I can't get it to
recognize Delete as an erase character; it remains Backspace
(octal 10). Interestingly, Emacs is normal; an Emacs session
with a window on my Mac responds to Delete as expected. The
xterm session just flashes the menu bar (I suppose it would
beep if I made some other change), and doesn't erase.
Obviously, there's something I'm missing. Any ideas, folks?
--
John E. Doner, UCSB Math. Dept., [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 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
******************************
