I've got a -STABLE GENERIC kernel, cvsupped and built this evening, that
is all
alone on a UFS floppy, and kgzipped.
My P-133 boots the -STABLE kernel fine.
My AMD-K6/2 400 stops immediately after "Uncompressing kernel ... done".
The same systems both can boot a -CURRENT GENERIC kgzipped
Since I am currently experimenting with BOOTP in -current, I patched ONLY
vfs_conf.c and vfs_subr.c with your rootfsid changes. Works fine in a BOOTP
configuration. -current sources are as of last night.
I can now boot a -current system from only a floppy disk with a (kgzipped) kernel
on it!
I've had this problem since at least FreeBSD 3.1-RELEASE (it works in
2.2.7/2.2.8). Same problem in 3.2-RELEASE and -current (as of last night).
Can someone reproduce this error? I can't believe that you can't newfs
a ccd... did I miss something?
spiffy# ./ccdtest.sh
[snip]
newfs
his and commit a fix
(possibly this one). John? Poul? Peter?
Without a similar fix, I don't think that BOOTP kernels will not work (as specified
in the file /usr/share/examples/diskless/README.BOOTP).
-Mark Taylor
NetMAX Developer
[EMAIL PROTECTED]
http://www.netmax.com/
On 23-Aug-99 Mark J. Ta
This may be related:
There is a long as a parameter to ccdbuffer that needs to be a u_long.
Otherwise, you'll get panics (can't remember where).
Basically, bcount needs to be a u_long in all cases.
I haven't gotten around, because of the NetMAX for Linux project, to
comitting things like this
Are you trying to configure your entire system using LDAP as the database
backend, or are you trying to serve current system info?
If you are trying *configure* the system using LDAP as a database, then
good luck. Our company, Cybernet Systems, has spent over ten man-years
developing a