Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Mar 2002 14:50:03 -0500 (EST)
From:      John Baldwin <jhb@FreeBSD.org>
To:        Maxim Sobolev <sobomax@FreeBSD.org>
Cc:        cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org
Subject:   RE: cvs commit: src/sys/boot/i386/loader conf.c src/lib/libstand
Message-ID:  <XFMail.20020320145003.jhb@FreeBSD.org>
In-Reply-To: <200203171218.g2HCI5831637@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On 17-Mar-2002 Maxim Sobolev wrote:
> sobomax     2002/03/17 04:18:05 PST
> 
>   Modified files:
>     sys/boot/i386/loader conf.c 
>     lib/libstand         Makefile bzipfs.c stand.h zipfs.c 
>   Added files:
>     lib/libstand         splitfs.c 
>   Log:
>   Add splitfs vfs layer into libstand, which allows loading big kernels and
>   modules split across several physical medias. Following is how it works:
>   
>   The splitfs code, when asked to open "foo" looks for a file "foo.split"
>   which is a text file containing a list of filenames and media names, e.g.
>   
>           foo.aa "Kernel floppy 1"
>           foo.ab "Kernel floppy 2"
>           foo.ac "Kernel and modules floppy"
>   
>   For each file segment, the process is:
>   
>   - try to open the file
>   - prompt "Insert the disk labelled <whatever> and press any key..."
>   - try to open the file
>   - return error if file could not be located
>   
>   RE team is free to use this feature in the upcoming 5.0-DP1.
>   
>   Reviewed by:    msmith, dcs

Erm, this seems to smake the loader spew a bit:

(over serial console):

cpu_reset called on cpu#0
cpu_reset: Stopping other CPUs
/boot/loader.conf.local
/boot/loader.conf.local.split
/boot/loader.conf.local.gz
/boot/loader.conf.local.gz.split
/boot/kernel/linker.hints
/boot/kernel/linker.hints.split
/boot/kernel/linker.hints.gz
/boot/kernel/linker.hints.gz.split
/boot/kernel/kernel.ko
/boot/kernel/kernel.ko.split
/boot/kernel/kernel.ko.gz
/boot/kernel/kernel.ko.gz.split
/boot/kernel/kernel text=0x1ee978 data=0x31474+0x24a2c
syms=[0x4+0x30540+0x4+0x3b53f]

Normall the /boot/kernel/kernel line would be right after the cpu_reset line. 
You didn't happen to commit some debugging code that dumped each filename it
checked did you?

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20020320145003.jhb>