Linux-Misc Digest #756, Volume #26 Mon, 8 Jan 01 20:13:02 EST
Contents:
Re: lilo for secondary IDE (HomerWelch)
Re: lilo for secondary IDE (John in SD)
Re: SCSI/IDE/LILO problem (John in SD)
Re: SCSI/IDE/LILO problem (John in SD)
Re: Partition overlapped (Svend Olaf Mikkelsen)
Re: lilo for secondary IDE (Dave Platt)
Re: File System questions -- please help. (Raman Narayan)
Re: File System questions -- please help. (Raman Narayan)
Re: Kernel 2.4 problem ("Dan White")
Re: I want to know which one calles ~/.profile ("Dan White")
Limit of swap size? ("Yuan-Sen Yang")
Re: Partition overlapped (Svend Olaf Mikkelsen)
Re: How to obtain info on "GNOME vs KDE" ? (Roberto Alsina)
----------------------------------------------------------------------------
From: HomerWelch <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.system,comp.os.linux.setup
Subject: Re: lilo for secondary IDE
Date: Mon, 08 Jan 2001 23:32:23 GMT
"Hung P. Tran" wrote:
>
> I am trying to make a boot hard drive to boot from a
> secondary IDE. My lilo.conf is as followed:
>
> #boot=/dev/fd0
> boot=/dev/hdc
> map=/mnt/floppy/map
> install=/mnt/floppy/boot.b
> prompt
> timeout=50
> default=linux
>
> image=/mnt/floppy/vmlinuz
> label=linux
> root=/dev/hda5
>
> Note that the same lilo.conf works for a floppy (just by replacing
> the boot line to /dev/fd0). However, when I mount my secondary
> harddrive to the same place (to minimize lilo.conf change) using:
>
> mount /dev/hdc1 /mnt/floppy
>
> The same lilo.conf will not work. All I get is an "L" and then
> a bunch of 01 dump onto the screen. I also try to use "linear"
> to no avail. Any advice.
>
Did you rerun lilo after changing that parameter? You have
to install lilo in the MBR of hdc. Also, lilo creates the
map file and install it.
You may have to change your parameters in your bios to get
it to detect the hdc as a bootable disk. At least on my
system, it will only look at fd0 and hda for boot
information.
good luck,
--
Homer J. Welch [EMAIL PROTECTED]
Troy, Michigan
------------------------------
From: John in SD <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.system,comp.os.linux.setup
Subject: Re: lilo for secondary IDE
Reply-To: [EMAIL PROTECTED]
Date: Mon, 08 Jan 2001 23:38:37 GMT
On Mon, 08 Jan 2001 21:37:53 GMT, "Hung P. Tran" <[EMAIL PROTECTED]> wrote:
>I am trying to make a boot hard drive to boot from a
>secondary IDE. My lilo.conf is as followed:
>
>#boot=/dev/fd0
>boot=/dev/hdc
>map=/mnt/floppy/map
>install=/mnt/floppy/boot.b
>prompt
>timeout=50
>default=linux
>
>image=/mnt/floppy/vmlinuz
> label=linux
> root=/dev/hda5
>
>
>Note that the same lilo.conf works for a floppy (just by replacing
>the boot line to /dev/fd0). However, when I mount my secondary
>harddrive to the same place (to minimize lilo.conf change) using:
>
>mount /dev/hdc1 /mnt/floppy
>
>The same lilo.conf will not work. All I get is an "L" and then
>a bunch of 01 dump onto the screen. I also try to use "linear"
>to no avail. Any advice.
>
>Thank you for any help,
When you boot, the floppy will be read first (device 0x00), then device
(0x80). I don't know how to get your bios to first read device (0x82), even
if it installs that device. Older BIOSes will only install 0x80 and 0x81.
--John
>
>hung
LILO version 21.6 (04-Oct-2000) source at
http://www.ibiblio.org/pub/Linux/system/boot/lilo
patches at ftp://brun.dyndns.org/pub/linux/lilo
------------------------------
From: John in SD <[EMAIL PROTECTED]>
Subject: Re: SCSI/IDE/LILO problem
Reply-To: [EMAIL PROTECTED]
Date: Mon, 08 Jan 2001 23:45:41 GMT
On 8 Jan 2001 20:27:38 GMT, [EMAIL PROTECTED] (Matthew Fleming) wrote:
>Netmeisters,
>
>I would appreciate your help with the following problem: I have a
>system with a SCSI disk, which holds the root partition, and a 120 MB
>IDE superdisk, which is connected to the first IDE channel (so
>recognized as hda). I have just connected a 20 GB IDE disk to the
>second IDE channel (so hdc). The problem is that the system will now
>boot only when I have told the BIOS that the IDE HD is not installed.
>This is despite rerunning LILO with the following lilo.conf:
>
>append="hdc=16383,16,63"
># Start LILO global Section
>boot=/dev/hda
>disk = /dev/sda
> bios=0x80
>disk = /dev/hdc
> bios=0x81
>#compact # faster, but won't work on all systems.
>read-only
>prompt
>timeout=10
>vga = normal # force sane state
># End LILO global section
># Linux bootable partition config begins
>image = /boot/vmlinuz
>root = /dev/sda2
>label = Linux
># Linux bootable partition config ends
>#
>
The "append" should not be part of the global section; should be part of the
"image" section.
Do you know how your BIOS assigns device codes? You ask it to boot from
/dev/hda, but this MUST be device 0x80. And you say /dev/sda is 0x80?????
Try creating the diagnostic floppy from the lilo source distribution; run it,
and see how your BIOS is assigning device codes. Your "disk=/bios=" sections
must correspond to what the BIOS is doing.
--John
>If it matters, fstab looks like this:
>
>/dev/sda2 / ext2 defaults
>1 1
>/dev/sda4 /home ext2 defaults
>1 2
>/dev/sda3 swap swap defaults
>0 0
>/dev/hdc3 /home2 ext2 defaults
>1 2
>/dev/hdc2 /fromboth msdos defaults
>1 2
>/dev/hda1 /mnt/floppy ext2 noauto
>0 0
>/dev/cdrom /mnt/cdrom iso9660 noauto,ro
>0 0
>none /proc proc defaults
>0 0
>
>Oddly, with the BIOS set to know about the new disk, I can't even boot
>the system with a boot disk; when I try to do so, it starts to load
>the kernel but then reboots itself, and so on ad infinitum.
>
>The system also has Win NT on it, which recognizes the new IDE disk
>without any trouble.
>
>Your assistance much appreciated.
>
>Matthew Fleming
>------------------------------------------------------------------------------
>Matthew G. Fleming, MD phone : 414.456.4072
>Associate Professor fax : 414.456.6518
>Department of Dermatology s-mail: Dept. of Dermatology
>Medical College of Wisconsin Medical College of Wisconsin
> MFRC Room 4061
>e-mail: [EMAIL PROTECTED] Milwaukee, WI 53226-4810
>------------------------------------------------------------------------------
LILO version 21.6.1 (16-Dec-2000) source at
http://www.ibiblio.org/pub/Linux/system/boot/lilo
patches at ftp://brun.dyndns.org/pub/linux/lilo
------------------------------
From: John in SD <[EMAIL PROTECTED]>
Subject: Re: SCSI/IDE/LILO problem
Reply-To: [EMAIL PROTECTED]
Date: Mon, 08 Jan 2001 23:46:40 GMT
On 8 Jan 2001 20:27:38 GMT, [EMAIL PROTECTED] (Matthew Fleming) wrote:
>Netmeisters,
>
>I would appreciate your help with the following problem: I have a
>system with a SCSI disk, which holds the root partition, and a 120 MB
>IDE superdisk, which is connected to the first IDE channel (so
>recognized as hda). I have just connected a 20 GB IDE disk to the
>second IDE channel (so hdc). The problem is that the system will now
>boot only when I have told the BIOS that the IDE HD is not installed.
>This is despite rerunning LILO with the following lilo.conf:
>
>append="hdc=16383,16,63"
Without "lba32", you will not be able to boot beyond cylinder 1023.
--John
LILO version 21.6.1 (16-Dec-2000) source at
http://www.ibiblio.org/pub/Linux/system/boot/lilo
patches at ftp://brun.dyndns.org/pub/linux/lilo
------------------------------
From: [EMAIL PROTECTED] (Svend Olaf Mikkelsen)
Crossposted-To: linux.redhat.install,linux.redhat.misc
Subject: Re: Partition overlapped
Date: Mon, 08 Jan 2001 23:48:55 GMT
* Tong * <[EMAIL PROTECTED]> wrote:
>* Tong * <[EMAIL PROTECTED]> writes:
>
>Thanks to everybody who tried to answer my question. It seems to be
>a problem with no fix reason/solution.
>
>FYI, I ended up redo the whole extended partition with cfisk, trying
>to avoid any potential problem. The result is:
>
> fdisk -l
>
>Disk /dev/hda: 255 heads, 63 sectors, 2491 cylinders
>Units = cylinders of 16065 * 512 bytes
>
> Device Boot Start End Blocks Id System
>/dev/hda1 1 64 514048+ 83 Linux
>/dev/hda2 65 319 2048287+ 83 Linux
>/dev/hda3 * 320 1057 5927985 c Win95 FAT32 (LBA)
>/dev/hda4 1058 2491 11518605 5 Extended
>/dev/hda5 1058 2030 7815591 83 Linux
>/dev/hda6 2031 2491 3702951 c Win95 FAT32 (LBA)
FYI: Data on this disk will be damaged. If data are important, Linux
partitioning tools should not be used.
--
Svend Olaf
------------------------------
From: [EMAIL PROTECTED] (Dave Platt)
Crossposted-To: comp.os.linux.development.system,comp.os.linux.setup
Subject: Re: lilo for secondary IDE
Date: Mon, 08 Jan 2001 23:57:44 -0000
>> I am trying to make a boot hard drive to boot from a
>> secondary IDE. My lilo.conf is as followed:
>>
>> #boot=/dev/fd0
>> boot=/dev/hdc
#snip
>> The same lilo.conf will not work. All I get is an "L" and then
>> a bunch of 01 dump onto the screen. I also try to use "linear"
>> to no avail. Any advice.
>>
>
>Did you rerun lilo after changing that parameter? You have
>to install lilo in the MBR of hdc. Also, lilo creates the
>map file and install it.
A normal PC BIOS will boot only from the MBR of the primary hard
drive. It won't even "look" for the secondary hard drive MBR. The
normal way to boot a Linux system from a secondary hard drive is to
put LILO in the MBR of the primary hard drive (or put the standard MBR
there, and put LILO in the boot block of the active partition on the
primary hard drive). You can have the kernel itself, and the root
filesystem on the secondary hard drive, but the MBR and active active
partition normally need to be on the primary drive.
There are some BIOSes which can be configured to boot from the
secondary hard drive. There's a gotcha to enabling this feature,
though. Most disk-resident MBR and bootloader code isn't written to
be booted from a secondary drive (it "assumes" that the system is on
the primary drive). In order to cope with this lacking, the BIOS
doesn't just load the MBR etc. from the secondary drive - it actually
*swaps* the two drives at the BIOS level.
In a standard system, the first bootable disk (typically the master on
the IDE primary controller) is referred to as device 0x80 in the I/O
calls to the BIOS. The second drive is 0x81, and so forth.
If you tell your BIOS to swap controllers, it actually assigns device
ID 0x80 to the master drive on the secondary controller. Thus, when a
standard MBR is loaded from this drive and executed, it "thinks" that
it's really on the primary drive, and has no difficulty reading the
partition table and the O/S boot blocks. A similar thing occurs if
you have a SCSI controller, and tell your BIOS to "boot SCSI" - the
0x80 drive ID is assigned to the first disk device on the first SCSI
controller, rather than to the IDE primary master.
When /sbin/lilo is run to install LILO, it has to write information
into the MBR-resident portion of LILO, and into its own boot catalog,
which tells the boot code where to find each portion of the code being
booted. It must figure out which BIOS disk identifier is used for
each drive, and identify the location of each bootable bit of code by
(drive ID, location, size).
The /sbin/lilo installer normally honors the standard BIOS
conventions... IDE primary master, IDE primary slave, IDE secondary,
SCSI, in that order. This works just fine for a standard setup. It
will NOT work if you've told your BIOS to swap drives or controllers
around, because the BIOS ordering will disagree with the ordering that
the LILO installer assumed.
The net result will be the sort of thing you're observing... the first
(MBR-resident) portion of LILO will load, but the subsequent sections
won't load properly, because the MBR-resident portions of LILO will be
using the wrong device IDs.
The way around this problem is to use _explicit_ device IDs in your
/etc/lilo.conf file. Figure out what device IDs your BIOS is going to
assign at boot time, and then tell LILO to use precisely these IDs.
As an example: I have a system with two IDE hard drives, and one IDE
hard drive. In a standard setup, the IDE drive would be 0x80, and the
two SCSI drives would be 0x81 and 0x82. However, I've told my BIOS
that I want to boot from SCSI (the IDE drive is strictly for bulk
storage), and so it reorganizes the drive IDs (SCSI first, IDE
second). In my lilo.conf file, I say:
#
# LILO is installed in the boot sector of the extended partition at
# /dev/sda2. The disk's MBR is standard.
#
disk = /dev/sda
bios = 0x80
disk = /dev/sdb
bios = 0x81
disk = /dev/hda
bios = 0x82
boot = /dev/sda2
install = /boot/boot.b
delay = 50
and so forth. This gives LILO the information it needs to build the
boot-map files with the correct drive IDs, and the system boots up from
the SCSI drives just fine.
I suspect that you may need to do something similar. If you're
telling your BIOS to boot from the secondary controller, you'll need to
say something like:
disk = /dev/hda
bios = 0x81
disk = /dev/hdc
bios = 0x80
to swap around the BIOS drive IDs for the drives on these two
controllers.
--
Dave Platt [EMAIL PROTECTED]
Visit the Jade Warrior home page: http://www.radagast.org/jade-warrior/
I do _not_ wish to receive unsolicited commercial email, and I will
boycott any company which has the gall to send me such ads!
------------------------------
From: Raman Narayan <[EMAIL PROTECTED]>
Crossposted-To: alt.linux
Subject: Re: File System questions -- please help.
Date: Mon, 08 Jan 2001 15:59:32 -0800
If the files are in one of the binary formats (tar.gz, bzip etc),
then there should be no problem. There will be problem, only
when you try using source files directly in the linux(eg. xf86config
file save in windows and used under linux), in which case you
need to convert them to unix(strip out the extra carriage returns
-which shows up as ^M, using dos2unix or similar utilities).
Hope I've answered your question.
Vijaya Chandran wrote:
> Hi Group,
>
> I downloaded some freeware for linux (like Star Office etc), using a
> Windows PC and saved them in the Windows 98 file system. Now, I have to
> use these files to install the software in Linux 7.0. Is is possible to
> use these files directly to install them in Linux 7.0 ? Will there be
> any file system conflicts involved ?
>
> Thanks,
> Vijay.
------------------------------
From: Raman Narayan <[EMAIL PROTECTED]>
Crossposted-To: alt.linux
Subject: Re: File System questions -- please help.
Date: Mon, 08 Jan 2001 16:04:57 -0800
I forgot to mention that you need to mount your win98
filessytem as type "vfat", inorder to access the windows
partition(also you probably need to be logged in as "root"
to do this) with support for long names.
eg.
# mount -t vfat /dev/hda1 /mnt/win98
(assuming win98 mount
point exists).
Raman Narayan wrote:
> If the files are in one of the binary formats (tar.gz, bzip etc),
> then there should be no problem. There will be problem, only
> when you try using source files directly in the linux(eg. xf86config
> file save in windows and used under linux), in which case you
> need to convert them to unix(strip out the extra carriage returns
> -which shows up as ^M, using dos2unix or similar utilities).
> Hope I've answered your question.
>
> Vijaya Chandran wrote:
>
> > Hi Group,
> >
> > I downloaded some freeware for linux (like Star Office etc), using a
> > Windows PC and saved them in the Windows 98 file system. Now, I have to
> > use these files to install the software in Linux 7.0. Is is possible to
> > use these files directly to install them in Linux 7.0 ? Will there be
> > any file system conflicts involved ?
> >
> > Thanks,
> > Vijay.
------------------------------
From: "Dan White" <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.4 problem
Date: Tue, 09 Jan 2001 00:16:56 GMT
In article <93c0kb$57a$[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
> Hi, I'm using RH 7.0 and I've downloaded kernel 2.4. The kernel compiled
> OK, and I installed it just like the README tells. But there seem a few
> errors when booting with the new kernel. It says NFS lockd error. I
> can't remember exactly. There are also problems with my sound card
> (es1371). I compiled the sound card support into the kernel, not as a
> module. But the sndconfig utiliy reports that it must be a module! And
> the ppp is not correct either. It just says modprobe can't find ppp0. Is
> there anything I can do? Thanks!
>
>
> Sent via Deja.com http://www.deja.com/
Make sure you've upgraded to the required software listed in
Documentation/Changes in the kernel source.
- Dan white
------------------------------
From: "Dan White" <[EMAIL PROTECTED]>
Subject: Re: I want to know which one calles ~/.profile
Date: Tue, 09 Jan 2001 00:20:01 GMT
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
wrote:
> I want to know which one calles ~/.profile during your login session of
> CDE in a Solaris box.
You're shell probably reads it directly, see the man page for it.
- Dan White
------------------------------
From: "Yuan-Sen Yang" <[EMAIL PROTECTED]>
Subject: Limit of swap size?
Date: Tue, 9 Jan 2001 08:36:43 +0800
Hi everyone,
I need a large swap space (about 8 GB) but don't know how to set it up
(using RedHat 6.2).
It seems the largest size of each swap partition is 2GB. Therefore, I
'swapon' 4 swap partitions. But the monitor program 'top' shows that there
are only 4 GB of swap space is available.
Is 4 GB the limitation of swap size using Linux RedHat? If not, how can
I swapon swap space more than 4 GB?
Thanks
--yuansen
------------------------------
From: [EMAIL PROTECTED] (Svend Olaf Mikkelsen)
Crossposted-To: linux.redhat.install,linux.redhat.misc
Subject: Re: Partition overlapped
Date: Tue, 09 Jan 2001 00:38:26 GMT
* Tong * <[EMAIL PROTECTED]> wrote:
>Disk /dev/hda: 255 heads, 63 sectors, 2491 cylinders
>Units = cylinders of 16065 * 512 bytes
>
> Device Boot Start End Blocks Id System
>/dev/hda1 1 64 514048+ 83 Linux
>/dev/hda2 65 319 2048287+ 83 Linux
>/dev/hda3 * 320 1057 5927985 c Win95 FAT32 (LBA)
>/dev/hda4 1058 2491 11518605 5 Extended
>/dev/hda5 1058 2030 7815591 83 Linux
>/dev/hda6 2031 2491 3702951 c Win95 FAT32 (LBA)
I guess I could have told why. An extended partition ending 1 based
cylinder 1024 or later *must* by type 0F or 85 if DOS or Windows is
present. The type of hda6 should be 0B.
--
Svend Olaf
------------------------------
From: Roberto Alsina <[EMAIL PROTECTED]>
Subject: Re: How to obtain info on "GNOME vs KDE" ?
Date: Tue, 09 Jan 2001 00:31:29 GMT
In article <93dfjj$dq9$[EMAIL PROTECTED]>,
Harlan Grove <[EMAIL PROTECTED]> wrote:
> In article <93dc3q$aud$[EMAIL PROTECTED]>,
> Roberto Alsina <[EMAIL PROTECTED]> wrote:
> >In article <93daiq$9dc$[EMAIL PROTECTED]>,
> > Harlan Grove <[EMAIL PROTECTED]> wrote:
> ...
> >>In terms of anecdotal evidence, KDE users seem to like KDE much more
> >>than Gnome users like Gnome. For something a bit objective, see the
> >>Linux Magazine interview with the Nautilus folks (October, November or
> >>December 2000 issue - don't recall which) on why they decided on
> >>Gnome.
> >
> >Erm. Excuse me, but Eazel has a vested interest in GNOME becoming the
> >de facto standard desktop for Unix. I wouldn't say they are unbiased.
> >Besides, IIRC, that article had simple factual errors.
>
> They decided to go with Gnome in 1999 when KDE users were much more
> numerous than Gnome users. Why? Death wish? Lack of understanding?
> Lack of seriousness? Maybe their current explanation for their
> choice back then is biased, but the choice itself? I'd like to think
> they had a good reason not to have decided on KDE (other than Qt's
> licensing at the time).
Why? They are a company. They are in it to make money. GTK+ was
cheaper. They went that way. Now they shouldn't say anything bad
about GTK+/GNOME or good about Qt/KDE because it would be against their
interest.
Other than that, I could think of KDE already having a decent file
manager in development, thus a less eager market.
Now, is the reason why a company chose GNOME two years ago as basis for a
product (even if we were to accept that article as the pure unadultered
reason) a good reason for a user chosing between GNOME and KDE now? I don't
think so.
> So, if KDE/Gnome users/developers are all biased, counter
> biased, pro-Gnome atricles with biased, pro-KDE articles. Name some.
Hey, I am a KDE developer, I can't tell KDE bias from a hole in the
ground. I am sure GNOME guys can show you a dozen. At least I know I
am biased and will avoid pushing you based on it.
I will just quote all the GNOME/KDE stuff in the interview you mentioned (I
assume it's this one? http://www.linux-mag.com/2000-09/eazel_01.html):
==================================================
LM: What was the reason for choosing to work on the GNOME rather than
the KDE windowing environment?
Hertzfeld: I think that GNOME has a better architecture when it comes
to the component model, which is very important to what we're doing
with Nautilus. But beyond that, KDE seemed to be trying to clone
Windows. That was unappealing to me. GNOME has a more open-ended,
innovative feeling of trying to transcend Windows, of trying to do
something new. Later, as we started meeting with people, I just fell
in love with Miguel de Icaza [GNOME's lead developer] and some of the
other GNOME developers who had just terrific personalities that I
really related to.
==================================================
I dare say this is no basis for a decision, since it seems to be about
a) Not knowing squat about KDE. We are not cloning windows.
Notice how he seems to have created, entirely in his head, a climate
of stifling anything that is not windows-like. Trust me, it ain't like
that at all. And he didn't approach us to actually get that impression,
he just made it up all by himself.
b) Not knowing squat about KDE's object model. It can do anything
Bonobo can. And a bit more. And it's easier to script.
c) Liking Miguel. What can I say? People like Britney Spears, too.
That's all. 10 lines that are personal opinion with no technical
backing, and the personal impression about one of the choices made
without any personal contact. From a guy with a vested interest. Use
that to choose desktops? Surely you jest!
> Nuts. This is getting like the Windows vs Mac arguments of yore.
Indeed.
--
Roberto Alsina
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.misc.
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
******************************
