Date: Thu, 7 Mar 2002 15:23:43 -0500 From: "Clark C . Evans" <cce@clarkevans.com> To: freebsd-hackers@FreeBSD.org Subject: Re: read-only root partition? Message-ID: <20020307152343.B12503@doublegemini.com> In-Reply-To: <20020228012649.A23259@doublegemini.com>; from cce@clarkevans.com on Thu, Feb 28, 2002 at 01:26:49AM -0500 References: <20020227175541.A17132@doublegemini.com> <20020228003540.V39476-100000@nohow.demon.co.uk> <20020228012649.A23259@doublegemini.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 28, 2002 at 01:26:49AM -0500, Clark C . Evans wrote: | | http://people.freebsd.org/~bsd/cdroot/ | | Ok. I've tried this route and it seems to be working, | thank you all so much for your help and pointers. Thus far, cdroot has worked well for me. I have a PleXwriter 23/10/40A and an old Mitsumi 12x CD-ROM (PIO 3). I get the following boot messages... cd9660: RockRidge extension Warning: bytes per inode restricts cylinders per group to 9. Warning: inode blocks/cyl group (285) >= data blocks (256) in last cylinder group. This implies 4096 sector(s) cannot be allocated. 496 blocks Warning: block size restricts cylinders per group to 26. 496 blocks After that, all seems to go well. Unfortunately, when this same CD-ROM is placed into a newer CD-ROM reader it either doesn't boot at all... (such as the Data Research 56x max or Vintech Intl. VIN-44A) or it gives me the following result: (results vary) pid 7 (sh) uid 0: exited on signal 5/10/11 Where it can't seem to make up it's mind about what signal it exits with 5, 10, or most frequently, 11. I've tried everything... and purched 2 additional new CD-ROM units with the same result... the new CD-ROMs don't like the file that's being generated. Thoughts? Clark I've had some problems getting cdroot to work | | I also see a few drives complaining (like the mouse), | I think I know how to re-do the kernel to leave out | the mouse driver though. Is this a cd driver that | needs to be removed? | | Anyway, I log-in and everything works nicely. Cool. | Given that I've gotten this far with cdroot, I think | I'm going to stick with this solution... and figure | out how it works. This kit makes three mfs for me: | tmp, var, etc, dev. I'm wondering if the etc | and dev must be done as mfs? | | My next step is to make a custom boot process: | | 1. Check to see if /dev/ad0s1b exists and is a | swap partition, if so, load it. | | 2. Check to see if /dev/ad0s1? exists and is | a FreeBSD partition. If so, see if it looks | like a /tmp, /var, or /home partition. If | so mount as appropriate. | | 3. Modify (2) above, to search on /ad?s1? for | a similar structure. If so, then mount it | using vinum. | | If steps 1-3 above fail, then assume it is an | "uninitialized" box. Ask the user to verify | this fact, and then create the partitions | automagically. If there are two disks, ask | the user if a software mirror is to be used, | if so, then configure this as well. | | If any of you have any suggestions/comments/ideas | as to how to best do this, I'd love to hear them! | | Best, | | Clark | | | | | | | | | | | Thank you all so much for your | suggestions and thoughts! | | My next step is to examine the file system: | | (a) if the "data" partition exists, then this | can be mounted and /var and /tmp can be | | | | | | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-hackers" in the body of the message -- Clark C. Evans Axista, Inc. http://www.axista.com 800.926.5525 XCOLLA Collaborative Project Management Software To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020307152343.B12503>