Linux-Setup Digest #532, Volume #20 Mon, 29 Jan 01 20:13:05 EST
Contents:
Cannot make raid1 array bootable in RedHat 7 ... HELP! ([EMAIL PROTECTED])
Re: dhcp delay time? (Bit Twister)
A simple question ("Tobias Bengtsson")
Re: error during kernal compiling.. (jw)
Re: Errors In Partition Table (Svend Olaf Mikkelsen)
Re: pam_tally + faillog ([EMAIL PROTECTED])
Re: how do i tell what features the prebuilt redhat 6.2 kernel has included ?
(Mathieu Brabant)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.misc,linux.dev.raid,linuix.redhat.install
Subject: Cannot make raid1 array bootable in RedHat 7 ... HELP!
Date: Mon, 29 Jan 2001 23:31:31 GMT
Hello,
Please help me get raid 1 working as the boot device on my new RedHat
7 installation.
I have followed several HOW-TOs as close as possible, and now I have:
2 x 4.2 SCSI disk drives.
the system installed on /dev/sda1 ...
/dev/md0 with /dev/sdb1 as raid-disk 0 and /dev/sda1 as failed-disk 1
the idea I believe is to copy the system to /dev/md0 mounted as /raid
(which I did), then boot the raid as /, then add the /dev/sda1 to the
raid, nuking the first system installation.
I also made an initrd-raid.img file as instructed and put it in /boot
...
But as soon as I change /etc/fstab to specify /dev/md0 as / the system
will not boot and I get just an emergency console.
Please, anyone?
Here are all the relevant files:
[wm@wm wm]$ cat /raid/etc/raidtab
# Sample raid-1 configuration
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/sdb1
raid-disk 0
device /dev/sda1
failed-disk 1
[wm@wm wm]$ cat /raid/etc/fstab
/dev/md0 / ext2 defaults 1 1
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
none /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/sdb5 swap swap defaults 0 0
/dev/sda5 swap swap defaults 0 0
[wm@wm wm]$ cat /raid/etc/lilo.conf
boot=/dev/md0
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
image=/boot/vmlinuz-2.2.16-22
label=linux
initrd=/boot/initrd-raid.img
read-only
root=/dev/md0
## The ones in the current / are the same except for one line:
[wm@wm wm]$ diff /etc/raidtab /raid/etc/raidtab
[wm@wm wm]$ diff /etc/lilo.conf /raid/etc/lilo.conf
[wm@wm wm]$ diff /etc/fstab /raid/etc/fstab
1c1
< /dev/sda1 / ext2 defaults 1 1
---
> /dev/md0 / ext2 defaults 1 1
But if I change /etc/fstab to set /dev/md0 as / the system won't boot!
And if it is not there (as now) the system boots fine with the current
/ but does not even mount the raid :(
[wm@wm wm]$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda1 3897800 210612 3489192 6% /
That's all the info for now ... please help me, I'm a programmer, not
a sysadmin and I've spent four days on this so far! Argh!
-- nick
------------------------------
From: [EMAIL PROTECTED] (Bit Twister)
Subject: Re: dhcp delay time?
Reply-To: [EMAIL PROTECTED]
Date: Mon, 29 Jan 2001 23:43:43 GMT
Helps if you provide what distro and release level you are using
when you post questions to the news groups. Different distros
have different commands, files, and links to files. Even happens
between release levels of the same distribution.
Depends on which dhcp client you are using.
man pump
man dhcpcd
man dhclient
On Mon, 29 Jan 2001 11:08:29 -0600, S. Umar
> <[EMAIL PROTECTED]> wrote:
>Since I upgraded to 2.4.0 whenever I turn on my notebook and I am not
>connected
>to the nework dhcp request takes a long couple of minutes...this was not
>the case
>before and it is very annoying. Is there a way to adjust the dhcp
>wait/delay time?
>Thanks
>--
>
>Prof. S. Umar
>Dept. of Physics & Astronomy
>Vanderbilt University
>Nashville, TN 37235
>Tel : (615) 322-2459
>Fax : (615) 343-7263
>[EMAIL PROTECTED]
>http://compsci.cas.vanderbilt.edu/~umar/resu.htm
--
The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a, man command_here or cat command_here, before using it.
------------------------------
From: "Tobias Bengtsson" <[EMAIL PROTECTED]>
Subject: A simple question
Crossposted-To: linux.debian.user,linux.debian,comp.os.linux.misc,comp.os.linux
Date: Tue, 30 Jan 2001 00:46:57 +0100
Hi!
Up until recently, I was running the 2.2r0 Potato release. The day before
yesterday, I upgraded to one of the Woody releases and since then the
system hasn't been the same. I'm thinking that this can be a problem
generated by the fact that I didn't download the Woody upgrades directly,
but I used some packages that I had on a few cd's here. At any rate, ever
since the upgrade my soundcard has refused to have anything to do with
anyone except root.
Since I've got a Soundblaster PCI128, I decided to use the ALSA drivers to
get it up and running. No problems there, I downloaded the alsa packages
(driver, libs, utils) and compiled just fine. Then I installed and off i
went, everything was working great until I upgraded to Woody. Now the ALSA
drivers simply won't be available to the ordinary user, when I try to do
"amixer" with my usual account I get the following;
tjolle@willow:~$ amixer
The ALSA sound driver was not detected in this system.
Although, I do the same thing just after running su;
tjolle@willow:~$ su
Password:
willow:/home/tjolle# amixer
Group 'Input Gain',0
Capabilities: volume mute jointly-mute Channels: Front-Left Front-Right
[..snip..]
Also, I thought I would include what it looks like when I try to run "gamix";
tjolle@willow:~$ gamix
probe.c 31: No ALSA device. main.c 29: Can not make mixer.
Now, all I want to know is; what gives? I mean, why the heck are my ALSA
drivers hiding from everyone except root? Could I mistakenly have
installed the ALSA debs when I upgraded the system? I had problems with
the included ALSA debs earlier, that's why I decided to compile them on my
own.
Thanks in advance,
Tobias Bengtsson
------------------------------
Date: Mon, 29 Jan 2001 19:15:59 -0500
From: jw <[EMAIL PROTECTED]>
Subject: Re: error during kernal compiling..
==============474A8308467F350473DEACA4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
OK, I have updated my ksymoops, as the previous message suggested (using rpm
-Fvh ksymoops-2.4.0-1.i386.rpm), updated all the rpm's from the latest patches
as well. I have symlinked /usr/src/linux-2.2.16.redhat to /usr/src/linux, and
then cd'ed to /usr/src/linux. I ran a 'make menuconfig', 'make dep', and a
'make bzImage', in that order (two times, once preceeded by a 'make mrprproper
clean distclean'
my system is redhat 7.0 (kernel 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT 2000 i686
unknown)
and i got:
kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486
-malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686
-DUTS_MACHINE='"i386"' -c -o init/version.o init/version.c
make -C kernel
make[1]: Entering directory `/usr/src/linux-2.2.16.redhat/kernel'
make all_targets
make[2]: Entering directory `/usr/src/linux-2.2.16.redhat/kernel'
kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486
-malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -DEXPORT_SYMTAB
-c ksyms.c
In file included from /usr/src/linux/include/linux/modversions.h:50,
from /usr/src/linux/include/linux/module.h:19,
from ksyms.c:14:
/usr/src/linux/include/linux/modules/i386_ksyms.ver:6: warning: `cpu_data'
redefined
/usr/src/linux/include/asm/processor.h:96: warning: this is the location of the
previous definition
/usr/src/linux/include/linux/modules/i386_ksyms.ver:28: warning: `smp_num_cpus'
redefined
/usr/src/linux/include/linux/smp.h:77: warning: this is the location of the
previous definition
/usr/src/linux/include/linux/modules/i386_ksyms.ver:118: warning:
`smp_call_function' redefined
/usr/src/linux/include/linux/smp.h:83: warning: this is the location of the
previous definition
In file included from /usr/src/linux/include/linux/interrupt.h:51,
from ksyms.c:21:
/usr/src/linux/include/asm/hardirq.h:23: warning: `synchronize_irq' redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:138: warning: this is the
location of the previous definition
In file included from /usr/src/linux/include/linux/interrupt.h:52,
from ksyms.c:21:
/usr/src/linux/include/asm/softirq.h:75: warning: `synchronize_bh' redefined
/usr/src/linux/include/linux/modules/i386_ksyms.ver:142: warning: this is the
location of the previous definition
/usr/src/linux/include/linux/kernel_stat.h: In function `kstat_irqs':
In file included from ksyms.c:17:
/usr/src/linux/include/linux/kernel_stat.h:47: `smp_num_cpus' undeclared (first
use in this function)
/usr/src/linux/include/linux/kernel_stat.h:47: (Each undeclared identifier is
reported only once
/usr/src/linux/include/linux/kernel_stat.h:47: for each function it appears
in.)
make[2]: *** [ksyms.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.2.16.redhat/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.2.16.redhat/kernel'
make: *** [_dir_kernel] Error 2
I have seen a number of references to this in posts elsewhere, and i find it
hard to believe that i, and all thjose other people, are all doing the same
thing exactly wrong.
Werner Fangmeier wrote:
> Just FYI: People will be less confused, if you correct the spelling of
> "kernal" to "kernel". And, it is common practice to create a symbolic link
> /usr/src/linux to the compiling source tree. So, normally you have
> directories named /usr/src/linux-2.2.16, /usr/src/linux-2.2.18,
> /usr/src/linux-2.4.0 and so on, and when you need to compile e.g. a 2.2.16
> kernEl :-), you do sort of
>
> rm -f /usr/src/linux # remove old symlink, if it exists
> ln -s /usr/src/linux-2.2.16 /usr/src/linux # create new symlink
> cd /usr/src/linux
> make xconfig dep bzImage modules modules_install
>
> And moreover, you should honour the others posts in this thread, especially
> the ksymoops-upgrade mentioned...
>
> "SS" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
> news:952pps$a3e$[EMAIL PROTECTED]...
> > Hope someone here can help me out... I am running RH7 on IBM600X, 320mb
> > RAM, 12G HD...
> > I am getting this error during kernal compiling.. I see this after I type
> > "make bzImage" I didn't even modify the kernal.
> > make[2]: *** [ksyms.o] Error 1
> > make[2]: Leaving directory '/usr/src/linux-2.2.16/kernal'
> > make[1]: *** [first_rule] Error 2
> > make[1]: Leaving directory '/usr/src/linux-2.2.16/kernal'
> > make: *** [_dir_kernal] Error 2
==============474A8308467F350473DEACA4
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
OK, I have updated my ksymoops, as the previous message suggested
(using <font face="Courier New,Courier">rpm -Fvh ksymoops-2.4.0-1.i386.rpm)</font>,
updated all the rpm's from the latest patches as well. I have symlinked
<font face="Courier New,Courier">/usr/src/linux-2.2.16.redhat</font>
to
<font face="Courier New,Courier">/usr/src/linux</font>, and then cd'ed
to <font face="Courier New,Courier">/usr/src/linux</font>. I ran
a '<font face="Courier New,Courier">make menuconfig</font>', '<font face="Courier
New,Courier">make
dep</font>', and a '<font face="Courier New,Courier">make bzImage</font>',
in that order (two times, once preceeded by a '<font face="Courier New,Courier">make
mrprproper clean distclean</font>'
<p>my system is redhat 7.0 (kernel 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT
2000 i686 unknown)
<p>and i got:
<p><font face="Courier New,Courier">kgcc -D__KERNEL__ -I/usr/src/linux/include
-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
-pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
-DCPU=686 -DUTS_MACHINE='"i386"' -c -o init/version.o init/version.c</font>
<br><font face="Courier New,Courier">make -C kernel</font>
<br><font face="Courier New,Courier">make[1]: Entering directory
`/usr/src/linux-2.2.16.redhat/kernel'</font>
<br><font face="Courier New,Courier">make all_targets</font>
<br><font face="Courier New,Courier">make[2]: Entering directory
`/usr/src/linux-2.2.16.redhat/kernel'</font>
<br><font face="Courier New,Courier">kgcc -D__KERNEL__ -I/usr/src/linux/include
-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
-pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
-DCPU=686 -DEXPORT_SYMTAB -c ksyms.c</font>
<br><font face="Courier New,Courier">In file included from
/usr/src/linux/include/linux/modversions.h:50,</font>
<br><font face="Courier
New,Courier">
from /usr/src/linux/include/linux/module.h:19,</font>
<br><font face="Courier
New,Courier">
from ksyms.c:14:</font>
<br><font face="Courier
New,Courier">/usr/src/linux/include/linux/modules/i386_ksyms.ver:6:
warning: `cpu_data' redefined</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/asm/processor.h:96:
warning: this is the location of the previous definition</font>
<br><font face="Courier
New,Courier">/usr/src/linux/include/linux/modules/i386_ksyms.ver:28:
warning: `smp_num_cpus' redefined</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/linux/smp.h:77:
warning: this is the location of the previous definition</font>
<br><font face="Courier
New,Courier">/usr/src/linux/include/linux/modules/i386_ksyms.ver:118:
warning: `smp_call_function' redefined</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/linux/smp.h:83:
warning: this is the location of the previous definition</font>
<br><font face="Courier New,Courier">In file included from
/usr/src/linux/include/linux/interrupt.h:51,</font>
<br><font face="Courier
New,Courier">
from ksyms.c:21:</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/asm/hardirq.h:23:
warning: `synchronize_irq' redefined</font>
<br><font face="Courier
New,Courier">/usr/src/linux/include/linux/modules/i386_ksyms.ver:138:
warning: this is the location of the previous definition</font>
<br><font face="Courier New,Courier">In file included from
/usr/src/linux/include/linux/interrupt.h:52,</font>
<br><font face="Courier
New,Courier">
from ksyms.c:21:</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/asm/softirq.h:75:
warning: `synchronize_bh' redefined</font>
<br><font face="Courier
New,Courier">/usr/src/linux/include/linux/modules/i386_ksyms.ver:142:
warning: this is the location of the previous definition</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/linux/kernel_stat.h:
In function `kstat_irqs':</font>
<br><font face="Courier New,Courier">In file included from ksyms.c:17:</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/linux/kernel_stat.h:47:
`smp_num_cpus' undeclared (first use in this function)</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/linux/kernel_stat.h:47:
(Each undeclared identifier is reported only once</font>
<br><font face="Courier New,Courier">/usr/src/linux/include/linux/kernel_stat.h:47:
for each function it appears in.)</font>
<br><font face="Courier New,Courier">make[2]: *** [ksyms.o] Error 1</font>
<br><font face="Courier New,Courier">make[2]: Leaving directory
`/usr/src/linux-2.2.16.redhat/kernel'</font>
<br><font face="Courier New,Courier">make[1]: *** [first_rule] Error 2</font>
<br><font face="Courier New,Courier">make[1]: Leaving directory
`/usr/src/linux-2.2.16.redhat/kernel'</font>
<br><font face="Courier New,Courier">make: *** [_dir_kernel] Error 2</font>
<p>I have seen a number of references to this in posts elsewhere, and i
find it hard to believe that i, and all thjose other people, are all doing
the same thing exactly wrong.
<br>
<br>
<p>Werner Fangmeier wrote:
<blockquote TYPE=CITE>Just FYI: People will be less confused, if you correct
the spelling of
<br>"kernal" to "kernel". And, it is common practice to create a symbolic
link
<br>/usr/src/linux to the compiling source tree. So, normally you have
<br>directories named /usr/src/linux-2.2.16, /usr/src/linux-2.2.18,
<br>/usr/src/linux-2.4.0 and so on, and when you need to compile e.g. a
2.2.16
<br>kernEl :-), you do sort of
<p> rm -f /usr/src/linux # remove old symlink,
if it exists
<br> ln -s /usr/src/linux-2.2.16 /usr/src/linux
# create new symlink
<br> cd /usr/src/linux
<br> make xconfig dep bzImage modules modules_install
<p>And moreover, you should honour the others posts in this thread, especially
<br>the ksymoops-upgrade mentioned...
<p>"SS" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
<br><a
href="news:952pps$a3e$[EMAIL PROTECTED]">news:952pps$a3e$[EMAIL PROTECTED]</a>...
<br>> Hope someone here can help me out... I am running RH7 on IBM600X,
320mb
<br>> RAM, 12G HD...
<br>> I am getting this error during kernal compiling.. I see this
after I type
<br>> "make bzImage" I didn't even modify the kernal.
<br>> make[2]: *** [ksyms.o] Error 1
<br>> make[2]: Leaving directory '/usr/src/linux-2.2.16/kernal'
<br>> make[1]: *** [first_rule] Error 2
<br>> make[1]: Leaving directory '/usr/src/linux-2.2.16/kernal'
<br>> make: *** [_dir_kernal] Error 2</blockquote>
</html>
==============474A8308467F350473DEACA4==
------------------------------
From: [EMAIL PROTECTED] (Svend Olaf Mikkelsen)
Crossposted-To: comp.os.linux.misc,microsoft.public.win98.gen_discussion
Subject: Re: Errors In Partition Table
Date: Tue, 30 Jan 2001 00:17:17 GMT
"Werner Fangmeier" <[EMAIL PROTECTED]> wrote:
>Findpart, version 3.95.
>Copyright Svend Olaf Mikkelsen, 2001.
>
>OS: DOS 7.10 WINDOWS 4.10 Partition tables:
>
>Disk: 1 Cylinders: 3722 Heads: 255 Sectors: 63 MB: 29196
>
>-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
> 0 1*0C 63 20980827 10244 0 1 1 1305*254 63 OK OK
> 0 2 0F 20980890 34925310 17053 1306* 0 1 3479*254 63 OK
> 1306 1 0B 63 20980827 10244 1306* 1 1 2611*254 63 OK OK
> 1306 2 05 20980890 12546765 6126 2612* 0 1 3392*254 63 OK
> 2612 1 83 63 4658787 2274 2612# 1 1 2901*254 63 OK OK
> 2612 2 05 25639740 7887915 3851 2902* 0 1 3392*254 63 OK
> 2902 1 83 1 6249284 3051 2902# 0 2 3290*254 63 NB OK
> 2902 2 05 31889025 1638630 800 3291* 0 1 3392*254 63 OK
> 3291 1 82 1 610469 298 3291# 0 2 3328*254 63 OK
The partition tables seems OK, although not standard.
The "end cylinder" for link to next extended partition table (ID 05)
usually is the same as end cylinder for the following logical
partition. Example: End cylinder (not the actual entry) in the
extended partition table cylinder 1306, entry 2, should be 2901. The
"Num" field should be corrected accordingly.
The logical partition belonging to an extended partition table usually
begins at a head 1, sector 1, meaning that there are (sectors-1)
unused sectors between the partition table and the partition. In your
tables two partitions begin in the sector following the extended
partition table.
The "NB" may be the result of the actual partition space being a
little smaller than according to the partition tables. This is as it
should be, since "end sector" should be 63.
A "*" at the cylinder number indicates that the actual entry is 1023,
the largest cylinder number that fits in the tables.
A "#" indicates that the actual CHS entry is 1023/(heads-1)/sector.
In extended partition tables I prefer CHS entries as (cylinder mod
1024)/head/sector.
In the primary partition table I prefer 1023/(heads-1)/sector for
cylinders > 1023.
--
Svend Olaf
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: pam_tally + faillog
Date: Tue, 30 Jan 2001 00:09:59 GMT
Just in case what I wrote before did not make any sense, the problem is
setting up the PAM pam_tally module. This module is used (supposedly)
to limit the number of continous logins by a user. If the given user
mistypes its password more than X times, the account is disabled. To
do this, I'm trying to set the module up for use by the login program.
Thus, I entered the lines below in the PAM "login" config file. And, as
stated below, I tried to force the use of this module by mistyping a
user's password more than X times. The problem is that nothing
happened. After a few more tries, I entered the correct password and I
was able to log in. What I believe that pam_tally is supposed to do is
check /var/log/faillog file, and determine given the data on the login
config file if the account should be disabled. This obviously hasn't
happened.
Any help will be appreciated!
Cheers, ajam
In article <94slmc$b6b$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> I'm trying to setup a RH Linux 7.0 with pam_tally in order to limit
the
> number of access tries to an X number of attempts by adding the
> following two lines to the pam "login" configuration file:
>
> auth required /lib/security/pam_tally.so
> account required /lib/security/pam_tally.so per_user deny=X no_reset
>
> , where X is any number of tries.
>
> After setting up the file, I logged out and using a non-root account I
> mistyped the account's password several times (>3). At about the
fourth
> or fifth time, I typed in the right password, and was able to login
> without any problem. This was repeated a few times.
>
> According to the documentation, the lines entered are the supposedly
> needed ones, but there seems to be a problem with them. I also tried
it
> having a second terminal open to check the number of failures
occurring
> using the "faillog -u 'username'" command. But its output maintained
> the number of failures equal to 0 everytime.
>
> Am I doing something stupidly wrong here, or is this an error regards
to
> the faillog command + files or the pam_tally module?
>
> Thanks, ajam
>
> Sent via Deja.com
> http://www.deja.com/
>
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Mathieu Brabant <[EMAIL PROTECTED]>
Subject: Re: how do i tell what features the prebuilt redhat 6.2 kernel has included ?
Date: Tue, 30 Jan 2001 00:30:02 -0000
You must have the kernel sources installed to look at it's configuration
file. Type the command 'grep CONFIG_SCSI_MULTI_LUN /usr/src/linux/.config'
to see if it is set. If it is not set, you will need to reconfigure and
recompile the kernel (this feature is not a loadable module):
#cd /usr/src/linux
#make xconfig
Select SCSI support -> Probe all LUNs on each SCSI device -> Y
...
To complete the process, you can find complete instructions on how to
recompile the kernel here:
http://www.linuxnewbie.org/nhf/intel/compiling/kernelcomp.html
FYI, on my RH62 default installation, this option is not set.
Have fun!
Mathieu Brabant
dan wrote:
>
> i have a problem with the rh6.2 kernel not recognizing multiple LUN
> disks
> the response from the newsgroup was:
>
> >> Is multi LUN support configurd in the kernel in the SCSI device
> section?
>
> >> CONFIG_SCSI_MULTI_LUN
>
> how do i tell if the kernel has a feature or not ?
>
> is this particular feature loadable as a module ?
>
> thanks for any help,
> dan
>
--
Posted via CNET Help.com
http://www.help.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
******************************
