Re: debian-installer for GNU/kFreeBSD
On Mon, Aug 31, 2009 at 07:11:49PM +0200, Bjørn Mork wrote:
> I just tried the AMD64 flavour on a kvm virtual machine. Most of the
> issues I noticed seem to already be documented:
> - installation report fails
This is on the TODO list of things to do.
> - keyboard configuration missing
That too, but that's not something that will happen soon, as a lot of
work is needed.
In the meanwhile you can run 'dpkg-reconfigure kbdcontrol' after
rebooting on the installed system.
> Apart from that, the only problem I had was enabling the serial console.
> But that might be due to me not knowing FreeBSD too well. The installer
> worked nicely, except for the already documented missing features.
All the other issue are not directly related to debian-installer, but
rather to GNU/kFreeBSD in general.
>
> More details:
>
> I installed using this command line:
>
> kvm -m 512 -usb -hda debian-kfreebsd.base.raw -net nic,vlan=0,macaddr=00:aa:00:ff:00:fb -net vde,vlan=0,sock=/var/run/vde2/tap0.ctl -serial mon:stdio -monitor null -cdrom mini-kfreebsd-amd64-20090831.iso -boot d
>
> Original plan was to use serial console only, but this seems to be
> unsupported (probably more of a generic d-i problem). Also meant to use
This should be supported, but currently it requires editing the boot
command line of grub and that is not possible through the serial line...
We have to find a solution.
> an e1000 NIC but forgot to specify it. That caused a minor problem when I
> remembered it afterwords, as the primary NIC was renamed from re0 to em0.
> But that is of course to be expected with FreeBSD and obviously an user
> error anyway...
>
> Serial console woes:
>
> /etc/inittab had a couple of commented out lines as usual, so I just
> uncommented the first in the belief that the device name was correct:
>
> # Example how to put a getty on a serial line (for a terminal)
> #
> #T0:23:respawn:/sbin/getty -L cuaa0 9600 vt100
>
>
> But this ended up with
>
> INIT: Id "T0" respawning too fast: disabled for 5 minutes
>
> So I looked around in /dev/ for other possibilities, and remembered that
> JUNOS routers (which are the only FreeBSD machines I've ever used before
> :-) use ttyd0. And this seems to work fine:
>
> T0:23:respawn:/sbin/getty -L ttyd0 9600 vt100
>
> But that posed another minor problem: ttyd0 was not in /etc/securetty so
> I couldn't log in as root on the console. Easily fixed of course. but
> makes me wonder: Did I do something wrong, or are both /etc/inittab and
> /etc/securetty really using the wrong serial console device names?
The problem is that those files are currently plenty of linuxisms. They
need to be change, but that involves other packages so it will probably
takes a lot of time until this is added. I'll fill the bugs for that
later today.
> Then came the attempt to configure grub for serial console: Getting
> grub itself to use is of course the same as with Linux:
>
> GRUB_PRELOAD_MODULES=serial
> GRUB_TERMINAL=serial
> GRUB_SERIAL_COMMAND="serial --unit=0 --speed=9600"
>
> But how am I supposed to make the freebsd kernel use it? Adding "-h" on
> the kernel command line maybe? But there does not seem to be any way to
> do that using /etc/grub.d/10_freebsd. Or am I missing the obvious?
> Hmm, maybe the missing feature "support for boot options". Right.
That should be:
set FreeBSD.console=comconsole
but I haven't tested it.
> For now, I've just added a static copy of the automatic configuration
> with the command line parameter, but this is of course not a good
> solution.
>
> BTW, while looking for docs, I noticed this weird path:
>
> kvm-kfreebsd:~# dpkg -L kfreebsd-image-7.2-1-amd64|grep home
> /usr/share/doc/home
> /usr/share/doc/home/aurel32
> /usr/share/doc/home/aurel32/tmp
> /usr/share/doc/home/aurel32/tmp/kernel
> /usr/share/doc/home/aurel32/tmp/kernel/kfreebsd-7-7.2
> /usr/share/doc/home/aurel32/tmp/kernel/kfreebsd-7-7.2/debian
> /usr/share/doc/home/aurel32/tmp/kernel/kfreebsd-7-7.2/debian/kfreebsd-image-7.2-1-amd64
> /usr/share/doc/home/aurel32/tmp/kernel/kfreebsd-7-7.2/debian/kfreebsd-image-7.2-1-amd64/README.Debian
>
> Guess that's not supposed to happen :-)
>
Ouch, I'll fix that asap.
Thanks for your tests,
Aurelien
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: