tar@ksuvax1.cis.ksu.edu (Tim Ramsey) (02/09/89)
I'm a little confused. All I wanted to do was increase the number of process
table entries on my system. This is what I did:
# vi /etc/master.d/kernel
[change NPROC to 500 -- system admin guide said this was the max]
[change MAXUP to 50 -- no max listed in system admin guide]
# cd /boot
# mkboot -k KERNEL
# cd /
# cp unix ounix
# shutdown -i5 -g0 -y
[system goes down to firmware, boot switch is off]
> boot
enter path: /etc/system
[system goes to single-user]
# init 2
[system goes to run level 2]
[log in as root]
# mkboot -o /unix
mkunix: Warning -- boot program "/boot/KERNEL" timestamp= Wed Feb 8 18:27:05
mkunix: input file "/boot/KERNEL" timestamp= Wed Feb 8 21:57:52
mkunix: *** Results are unpredictable! ***
Using /boot/KERNEL for input file
Read 1791 symbols from /boot/KERNEL
918 symbols added
What did I do wrong? What does this message mean? Sure 'nuff, when I tried
to boot from /unix, strange things happened (the WIN/3B 1.1 driver wouldn't
initialize -- I got "/dev/Sh -- not owner"). When I boot with /ounix, things
work fine.
Thanks in advance,
Tim
--
Timothy Ramsey
BITNET: tar@KSUVAX1
Internet: tar@ksuvax1.cis.ksu.edu
UUCP: ...!rutgers!ksuvax1!tar -or- ...!{pyramid,ucsd}!ncr-sd!ncrwic!ksuvax1!tarscott@rdahp.UUCP (Scott Hammond) (02/10/89)
In article <722@deimos.cis.ksu.edu> tar@ksuvax1.cis.ksu.edu (Tim Ramsey) writes: > { remarks on changing NPROC and MAXUP kernel parms } > { and then to rebuild UNIX... } |# cd /boot |# mkboot -k KERNEL |# cd / |# cp unix ounix |# shutdown -i5 -g0 -y | [system goes down to firmware, boot switch is off] |> boot |enter path: /etc/system | [system goes to single-user] |# init 2 | [system goes to run level 2] | [log in as root] |# mkboot -o /unix I cannot speak for the warnings you received after this point, but about the networking driver, I believe your mistake is right here. The problem with the WIN3b1.1 driver is not related to the parameters you changed. Rather, certain driver initialization does not take place (or not correctly) if you rebuild UNIX from multi-user mode. You must do the mkboot in single user mode in order to get the WIN3b driver to work correctly. -- Scott Hammond R & D Associates, Marina del Rey, CA Email: rdahp!scott, rdahp!scott@sm.unisys.com, scott@harris.cis.ksu.edu
tar@ksuvax1.cis.ksu.edu (Tim Ramsey) (02/12/89)
In article <722@deimos.cis.ksu.edu> I wrote: >I'm a little confused. All I wanted to do was increase the number of process >table entries on my system. This is what I did: [ ... ] In article <207@rdahp.UUCP> scott@rdahp.UUCP (Scott Hammond) writes: >I cannot speak for the warnings you received after this point, but about >the networking driver, I believe your mistake is right here. The >problem with the WIN3b1.1 driver is not related to the parameters you >changed. Rather, certain driver initialization does not take place (or >not correctly) if you rebuild UNIX from multi-user mode. You must do >the mkboot in single user mode in order to get the WIN3b driver to work >correctly. Bingo. Thanks to Scott and the others who pointed this out by mail. Remaking the kernel (mkunix -o /unix, *not* mkboot -o /unix -- silly fingers) in single user mode seems to have solved everything. No error messages about timestamps, and the WIN/3B drivers are working fine. I dunno what the cause is, but remaking the kernel in multi-user mode doesn't seem to work. Tim -- Timothy Ramsey BITNET: tar@KSUVAX1 Internet: tar@ksuvax1.cis.ksu.edu UUCP: ...!rutgers!ksuvax1!tar