release.8 (4.3-RELEASE)

I was reading the Makefile in /usr/src/release and wondering about the for dir in bin sbin ; do \ ln -sf /stand $$dir; \ done part in release.8 - it is my understanding that all that is under /stand is linked to files in $$dir. What does this accomplish? To Unsubscribe: send mail to [EMAIL

RE: release.8 (4.3-RELEASE)

But what does this accomplish in the contect of release.8 if our purpose is to 'copy' all the binaries to the new mfsroot? On 18-Jul-01 Etienne de Bruin wrote: > I was reading the Makefile in /usr/src/release and wondering about the > > for dir in bin sbin ; do \ >

roll of /stand in mfsroot

ainly to my mfsroot? > > Also, the /stand dir is bugging me - do I need it? or can I just use the > plain /bin and /sbin directories? > > Thanks > > > eT > -- > Etienne de Bruin : [EMAIL PROTECTED] > Quidel Corporation : http://www.quidel.com > To Unsubscrib

crunched binary oddity

Greetings. I crunchgen'd newfs and linked mount_mfs to it (among many other progs), compiled it with success. And yet when I boot my MFS kernel and try to mount /tmp to mfs, boot_crunch complains that 'mfs' is not compiled into it? My /etc/fstab: /dev/zero /tmpmfs rw,

chroot in rc?

In my quest to boot a kernel containing an mfs and the chroot'ing to a mounted CD, I have the following problem: Where should the chroot command go? Can I sorta leave init hanging in the air by putting it in /etc/rc (I modified this heavily so I don't use other startup scripts)? Can I configure

RE: crunched binary oddity

> When mount(8) invokes a mount_xxx program, it sets argv[0] to the > name of the filesystem (ufs, mfs, nfs etc). Crunched binaries use > the argv[0] name to determine which code to execute, so you need > to add > > ln mount_mfs mfs > > to your crunchgen config file to get this to work. Al

Sequence of Events in Kernel source?

Greetings Seniors. I am interested in establishing the sequence of events from a source code perspective from when the PC is switched on, to the login prompt. I am specifically interested in the setting up of lower level stuff like the drivers. memory etc. Can anyone please take a moment and

No Subject

When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh, the linker complains about not finding the following symbols: s_strlen s_strcmp vis_str short2str This all takes place during my attempt to do a make buildworld with the 3_4_0_RELEASE sources. I am currently on a 3.2-RELEAS

Compiling 3.4-RELEASE problems

When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh, the linker complains about not finding the following symbols: s_strlen s_strcmp vis_str short2str This all takes place during my attempt to do a make buildworld with the 3_4_0_RELEASE sources. I am currently on a 3.2-RELEAS