Re: slink: Which directory am I supposed to install from?
On Mon, 24 May 1999 Marc.Haberemail@example.com wrote:
>>>/vmlinuz -> boot/vmlinuz-2.0.36. I needed to mount the CD to install
>>>the base system since /install doesn't contain the base*.bin files.
>>Hmmm. You'd need to mount the CD regardless.
>What if I don't have a locally installed CD drive? I usually copy the
>base system to the hard disk and install from there. Sure, it's
>possible to have both /install and
>/dists/slink/main/disks-i386/2.1.8-1999-02-22 copied to the hard disk,
>but this means having significant information doubled.
OK, that makes things a little clearer. Anyway, checking on the CD,
/install/boot.bat and /dists.../install.bat do effectively the same job.
This confuses me a little - how are you getting a kernel without the SCSI
drivers from one but not the other? Ah, hang on - you're not using the
laptop (tecra) kernel on one of these are you?
>>>Why does the other directory exist?
>>Good question. I'll ask the boot-floppies team.
>Is this the Debian-boot mailing list?
Explanation: the .../disks-i386/ tree is the place where the boot-floppies
and documentation are placed first. The CD build script tries to make
things easier for new users by adding copies of most of this stuff (docs
and boot kernels) in an easier-to-find location (/install). The two should
be functionally identical.
The installation of the base system etc should always go looking for a
tree under dists/stable/.../current for the base*.tgz file.
Actually, thinking about things a bit more: why are you copying just the
base files to a local hard disk? Are you then using NFS or similar to
install the rest? If so, just using the boot/root floppy should cope with
>>>How can I make the disks-i386-install-System install a kernel that
>>>actually works on my system?
>>By the sounds of things your first attempt should have worked. If it
>>didn't, then when/where did it fail?
>I failed it since it needed files from the
>/dists/slink/main/disks-i386/2.1.8-1999-02-22 directory. I thought
>"cool, there is a base system too, so I probably don't need that
>/install stuff" and started over with the other base system.
Steve McIntyre, Allstor Software firstname.lastname@example.org
Getting a SCSI chain working is perfectly simple if you remember that there
must be exactly three terminations: one on one end of the cable, one on the
far end, and the goat, terminated over the SCSI chain with a silver-handled
knife whilst burning *black* candles. --- Anthony DeBoer