Text 6293, 138 rader
Skriven 2006-06-11 20:44:02 av Paul Rogers (1:105/360.0)
     Kommentar till en text av Maurice Kinal
Ärende: follow up
=================
 MK> arena to the mix) and using lilo I copied the resulting
 MK> rootfs.gz (8M ramdisk) to /boot on /dev/hda1 which is a 64M

Not an initrd or kernel?  I don't know what you're doing there.
Ahh, lilo.conf says it's an initrd.  OK.

 MK> M-Systems 40-pin iDOC which dmesg shows as;

 MK>     hda: M-Systems iDOC V1.01 030804, ATA DISK drive
 MK>     ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

 MK> and was mounted on the build system's (/dev/sda1 mounted as

Mounting an IDE/ATA drive as SCSI?!  You're explaining this
backwards I think.

 MK> /) /mnt/flashdisk.  The sata drive's dmesg entry shows as;

Or the host system booted from sda1, and then you mounted
your thumb-drive (/dev/hda1)?  That I can understand.
(Linux understand sata drives as SCSI???  Wierd.)

 MK>     scsi1 : sata_nv
 MK>       Vendor: ATA       Model: ST3300831AS       Rev: 3.06
 MK>       Type:   Direct-Access                      ANSI SCSI revision: 05

 MK> Now the /mnt/flashdisk/etc/lilo.conf became;

 MK>     disk=/dev/hda bios=0x80

Damn straight!  "Button, button, who's got the button?"

 MK>     boot=/dev/hda

I don't understand why this isn't enough to tell lilo where
to write the boot.b.  Disk= does that and boot= is what it
will be at boot time?

 MK>     map=/mnt/flashdisk/boot/map

Where'd you get the map?

 MK>     prompt
 MK>     timeout=0
 MK>       image=/mnt/flashdisk/boot/vmlinuz-2.6.16.20
 MK>       label=sixtyfour
 MK>       root=/dev/ram0
 MK>       initrd=/mnt/flashdisk/boot/rootfs.gz
 MK>       read-only

What you SEEEEEEM to be telling me is lilo wants these to point
to the files on the host system at the time it's writing the
boot records, not something the code it writes is going to read
at boot time, ala grub's /boot/grub/menu.lst, or what the
target system is going to use itself.

 MK> I then ran 'lilo -C /mnt/flashdisk/etc/lilo.conf' from the host system,

It was on the thumb drive, but referring to files on the
host, so is going to have to be changed pretty much as
soon as you get it booted to refer to "local" files?  Or
there was one of those already there.

 MK> the /  mounted /dev/sda1 in this case, so that the lilo would be
 MK> installed to the proper mbr and the iDOC would be made
 MK> bootable and when booted it's rootfs would be loaded into

Running the host's lilo in the host's address space.
Only when I did that I didn't even get a "L".

 MK> ramspace.  Given that the iDOC in this case is on the same
 MK> system as the host was then it was a simple matter to use
 MK> the three finger salute and given that the bios is set to
 MK> boot to the first HD it runs across, magically /dev/hda,
 MK> then once the bios did it's thing ttylinux-64 automagically
 MK> booted.  So far so good.

I think I went that way and got no joy.

But let me check, I think perhaps the lilo.conf I made was
for the target system's address space, and that's what the
chroot was achieving.  Still, it doesn't quite explain why
that only got me a "LI", unless I ran lilo by hand with the
same lilo.conf.

OK, that's admiting to the fact that it must have been
referring to the target system's address space.

 MK> In order to liberate a monitor and keyboard from that
 MK> machine I customized the bootup so I could telnet from my
 MK> workstation into it and this is what happens;

 MK>     root@smpguy:~# telnet sixtyfour
 MK>     Trying 192.168.2.64...

Obviously!  ;-)

 MK>     Connected to sixtyfour.2things.net.
 MK>     Escape character is '^]'.

 MK>     ttylinux 5.0
 MK>     Linux 2.6.16.20 on x86_64 arch

 MK>     sixtyfour.2things.net login: root
 MK>     Password:

 MK>     Chop wood, carry water.

Well, Pascal appreciates Zen too, why not you?  Go to the
same dojo?

 MK> Cool eh?

"Because it's there."  ???  <shrug>

The point I always make^H^Hde to prospective employers is
that I manage computers because I must, not because I like
to.  Computing has always been important to me solely for
what it DOES, not what it is.  I am essentially a computing
user/consumer, but as the picture of my 1976 IMSAI on my
website demonstrates, I'll BUILD the sucker if I have to!

See, I had this idea of a bunch of points in a 7-space that
I wanted to examine by projecting into a subset 3-space cube
and rotating it in real time as an astronomer might.  Even
had/have an S-100 graphics card for this honkingly HEAVY 19"
Mitsubishi fixed frequency monitor.  Never got anything done
in that direction though.

Paul Rogers, paulgrogers@yahoo.com                       -o)
http://www.angelfire.com/or/paulrogers                   /\\
Rogers' Second Law: Everything you do communicates.     _\_V

... A kiss can be a comma, a ?, or a !
___ MultiMail/MS-DOS v0.35

---
 * Origin: The Bare Bones BBS (1:105/360)