Date: Fri, 3 Feb 1995 18:47:22 -0500 From: Wankle Rotary Engine <wpaul@skynet.ctr.columbia.edu> To: freebsd-hackers@FreeBSD.org Subject: The all-singing, all-dancing install... Message-ID: <199502032347.SAA03732@skynet.ctr.columbia.edu>
next in thread | raw e-mail | index | archive | help
...looks pretty good so far. I did an NFS install and it worked
*reasonably* smoothly. However, I wouldn't be me if I didn't pick nits. :)
Two small things:
- The silly install program still insists that you create a /usr partition
whether you want one or not. It so happens that I don't want one:
I have only small disks in my PC at work, so /usr gets mounted
via NFS. (I also have to remember to properly hack /etc/rc, but
that's my problem.) There should be a way to bypass this restriction:
if I don't want to do things the 'right way,' I should be able to.
A warning message would be preferable.
- The instructions in the 'NFS mount options' screen are wrong. They
say you should use things like '-o resvport' or '-o -r4096 -w4096,'
which would be the correct syntax for mount, but the install uses
mount_nfs, which doesn't grok these arguments. Instead of
'-o resvport' you need to use '-P'. The -r4096 and -w4096 options
are correct, but you don't need to use -o with them. Since I happen
to know the right options this wasn't a problem for me, but anyone
who hasn't read the mount_nfs man page would become hopelessly
confused.
Using '/kernel -c' to disable syscons, I was able to test the
install on a serial console for the first time. Unfortunately,
I encountered another panic while trying to get my ethernet interface
configured during the second stage of the install (note that I
didn't get the mail suggesting /kernel -c until after I'd already
completed the first stage):
(Note: the menu screen doesn't really look as trashy as it appears
below: it's been mangled due to 8->7 bit stupidity.)
lqqqqqqqqqq Network Configuration qqqqqqqqqqqk
x Any extra flags to ifconfig, put them here x
x lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x
x x x x
tqmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqjqu
x < OK > <Cancel> x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
(I didn't need to specify any extra flags, so I pressed ENTER.)
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xf01c04eb
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 7 (sh)
interrupt mask =
panic: page fault
syncing disks... 9 9 7 3 done
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
marple# ls -l kernel
-rw-r--r-- 1 root wheel 1012937 Feb 2 08:49 kernel
marple# nm kernel | grep f01c0
f01c0418 t _alloc_scp
f01c062c t _get_fstr
f01c07e0 t _history_down_line
f01c06dc t _history_to_screen
f01c075c t _history_up_line
f01c04bc t _init_scp <---- likely culprit
f01c085c t _scgetc
f01c022c t _scinit
f01c0580 t _scput
f01c0668 t _update_leds
My guess is that it puked while trying to write to /dev/ttyv1, which
didn't exist because syscons was disabled. I'm not sure what the proper
fix for this would be, except possibly some extra sanity checking
somewhere.
-Bill
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Bill Paul (212) 854-6020 | System Manager
Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Møøse Illuminati: ignore it and be confused, or join it and be confusing!
~~~~~~~~ FreeBSD 2.1.0-Development #2: Fri Feb 3 16:18:16 EST 1995 ~~~~~~~~~
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502032347.SAA03732>