compactbsd-devel Mailing List for CompactBSD
Status: Alpha
Brought to you by:
ttul
Menu
▾
▴
compactbsd-devel — CompactBSD Development Mailing List
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(5) |
Oct
(4) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
|
From: Mike M. <mmc...@xy...> - 2007-11-03 15:28:49
|
Hi Justin, I believe it's just edited by hand. For just the base install, using the existing dist.raw, you really should just have to change the libraries and some of the Perl paths, since it's a newer version. The easiest way to generate those new lists might be to do a find and delete the stuff you don't want. =20 Then again, large CF cards are pretty cheap now. So maybe putting everything on there isn't such a bad idea. :) Just do a find on a fresh install of OpenBSD and pipe it to your dist.raw after filtering out /dev and you're done. =20 I have some old "OpenBrick" boxes that I want to turn into something useful. Ideally, they'd run KDE and Firefox/Mozilla to just be a very simple web browser appliance type thingy. So maybe I'll go that route. - Mike > -----Original Message----- > From: com...@li... [mailto:compactbsd- > dev...@li...] On Behalf Of Justin Payne > Sent: Friday, November 02, 2007 3:53 PM > To: com...@li... > Subject: [Compactbsd-devel] CompactBSD update >=20 > Hello, >=20 > I have been attempting to modify this to work with the new release of > flashdist. I was able to work out the changes in build.py easily. Can > anyone tell me how dist.raw is generated so that I may generate a new > one to match OpenBSD 4.2? >=20 > Thank You, >=20 > Justin Payne, RHCE > Senior Technical Support Engineer >=20 > ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Compactbsd-devel mailing list > Com...@li... > https://lists.sourceforge.net/lists/listinfo/compactbsd-devel |
|
From: Justin P. <jp...@re...> - 2007-11-02 20:53:17
|
Hello, I have been attempting to modify this to work with the new release of flashdist. I was able to work out the changes in build.py easily. Can anyone tell me how dist.raw is generated so that I may generate a new one to match OpenBSD 4.2? Thank You, Justin Payne, RHCE Senior Technical Support Engineer |
|
From: James N. <ja...@fa...> - 2003-01-03 22:57:39
|
Hi Mike, I can't say i've seen that yet... The worst i've seen is the mfs.tgz tarball get corrupted, so the box doesn't boot properly. You might want to check your 64MB parameters when the flash was burnt. They are quite touchy. As far as distance goes, the OpenBrick/FatPoint can use POE (power over ethernet) adapters to get power over a great distance. I have tested this, and it works great. James -- James Nedila Field Engineer ja...@fa... FatPort - Secure Broadband Wireless Internet |
|
From: Mike M. <mmc...@pn...> - 2002-11-26 22:34:22
|
I'm having problems with CompactBSD 0.1.0 after a power loss. Several critical files are replaced with zero-length files after the system is powered back on. One of them is usually /sbin/init, which causes very bad things to happen. I think it might be fsck doing it, but it's really difficult to catch in the act. Has anyone encountered this? Any solutions? The specific system I'm working with is an OpenBrick/FatPoint/NET-2100, on a 64MB CF card. O/S is OpenBSD 3.1. On another note, has anyone had success with getting that system powered over any kind of distance? I may have a need to do so over about 50 feet. Any suggestions would be helpful. Thanks, - Mike -- Mike McClure, CCIE # 5125, CISSP # 30232 PNE Services, Inc. - http://www.pneservices.com mmc...@pn... mobile: 913-636-5590 |
|
From: Mike M. <mmc...@pn...> - 2002-10-27 17:44:46
|
Hello everyone, I have two questions. First, why does the build process make MFS filesystems *and* put all the files directly on the media? Shouldn't it just put the MFS filesystems, along with a minimal /, /etc and /stand on there? Am I doing something wrong? Second, what is the best method of adding directories and file to the build? Let's say I have directory /usr/local/fnord. I could just copy it to the media, but it won't be in the MFS filesystems, so it won't be there after booting, right? Thanks very much, Mike Here's my latest build output, in case it helps determine if I'm doing something wrong in the build. -------------- # /usr/local/bin/python build.py -b sd0 1035721209.91 [18306]: Creating working stand directory... 1035721209.91 [18306]: Copying boot files into working stand directory... # using MBR partition 3: type A6 off 32 (0x20) size 124896 (0x1e7e0) fdisk: sysctl(machdep.bios.diskinfo): Device not configured # using MBR partition 3: type A6 off 32 (0x20) size 124896 (0x1e7e0) tar: Unable to access ./root/.profile <No such file or directory> tar: Unable to access ./root/.klogin <No such file or directory> tar: Unable to access ./stand/fpconfig <No such file or directory> tar: WARNING! These file names were not selected: ./root/.profile ./root/.klogin ./stand/fpconfig using MBR partition 3: type 166 (0xa6) offset 32 (0x20) 1035721324.83 [18306]: flashdist.sh 20020501 ch...@dq... 1035721324.83 [18306]: Using disk device: sd0 1035721324.83 [18306]: Using distfile: /root/CompactBSD-0.1.0/flashdist/flashsma ll.txt 1035721324.83 [18306]: Copying kernel from: /bsd 1035721324.83 [18306]: 1035721324.83 [18306]: Please pay attention to any error messages that you may 1035721324.83 [18306]: receive from the commands this script it using. If you 1035721324.83 [18306]: end up having problems, they could explain why. 1035721324.83 [18306]: Setting up disklabel... 1035721324.83 [18306]: 1035721324.83 [18306]: The install script is using the following parameters: 1035721324.83 [18306]: Total size of media: 125441 sectors (64225792 bytes) 1035721324.83 [18306]: Bytes/Sector: 512 1035721324.83 [18306]: Sectors/Track: 32 1035721324.83 [18306]: Sectors/Cylinder: 2048 1035721324.84 [18306]: Tracks/Cylinder (heads): 64 1035721324.84 [18306]: Cylinders: 61 1035721324.84 [18306]: 1035721324.84 [18306]: Updating MBR and partition table... 1035721324.84 [18306]: Note, you may ignore "sysctl(machdep.bios.diskinfo)" erro rs if present. 1035721324.84 [18306]: 1035721324.84 [18306]: Installing disklabel... 1035721324.84 [18306]: disklabel -R sd0 /tmp/_ahhA14924 1035721324.84 [18306]: 1035721324.84 [18306]: Creating new filesystem... 1035721324.84 [18306]: newfs -c 61 -S 512 -u 32 -z 64 -o space /dev/rsd0a 1035721324.84 [18306]: Warning: 32 sector(s) in last cylinder unallocated 1035721324.84 [18306]: /dev/rsd0a: 124896 sectors in 122 cylinders of 32 tr acks, 32 sectors 1035721324.84 [18306]: 61.0MB in 2 cyl groups (61 c/g, 30.50MB/g, 7680 i/g) 1035721324.84 [18306]: super-block backups (for fsck -b #) at: 1035721324.84 [18306]: 32, 62528, 1035721324.84 [18306]: Copying OpenBSD distribution to media...done 1035721324.84 [18306]: Copying bsd kernel, boot blocks, /etc/resolv.conf... 1035721324.85 [18306]: Installing boot blocks... 1035721324.85 [18306]: Running MAKEDEV...done 1035721324.85 [18306]: Setting up ttys... 1035721324.85 [18306]: Setting up directories and links... 1035721324.85 [18306]: Unmounting filesystem...done! # # df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 3965052 1878343 1888457 50% / # mount /dev/sd0a /mnt # cd /mnt # ls bin boot bsd dev etc mnt sbin stand tmp usr var # df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 3965052 1878343 1888457 50% / /dev/sd0a 60479 26992 30464 47% /mnt # ls -la /mnt/sbin total 8960 drwxr-xr-x 2 root bin 1024 Oct 27 06:20 . drwxr-xr-x 11 root wheel 512 Oct 27 06:22 .. -r-xr-xr-x 1 root bin 57344 Apr 13 2002 atactl -r-xr-xr-x 2 root bin 163840 Apr 13 2002 chown -r-xr-xr-x 1 root bin 221184 Apr 13 2002 dhclient -r-xr-xr-x 1 root bin 5869 Apr 13 2002 dhclient-script -r-xr-xr-x 1 root bin 106496 Apr 13 2002 dmesg -r-xr-xr-x 1 root bin 69632 Apr 13 2002 fsck -r-xr-xr-x 1 root bin 196608 Apr 13 2002 fsck_ffs -r-xr-xr-x 2 root bin 147456 Apr 13 2002 halt -r-xr-xr-x 1 root bin 180224 Apr 13 2002 ifconfig -r-x------ 1 root bin 212992 Apr 13 2002 init -r-xr-xr-x 1 root bin 159744 Apr 13 2002 ipsecadm -r-xr-xr-x 1 root bin 958464 Apr 13 2002 isakmpd -r-xr-xr-x 1 root bin 65536 Apr 13 2002 ldconfig -r-xr-xr-x 1 root bin 94208 Apr 13 2002 mount -r-xr-xr-x 1 root bin 49152 Apr 13 2002 mount_ffs -r-xr-xr-x 2 root bin 151552 Apr 13 2002 mount_mfs -r-xr-xr-x 2 root bin 151552 Apr 13 2002 newfs -r-xr-xr-x 1 root bin 188416 Apr 13 2002 pfctl -r-xr-xr-x 1 root bin 233472 Apr 13 2002 pflogd -r-sr-xr-x 1 root bin 163840 Apr 13 2002 ping -r-xr-xr-x 2 root bin 147456 Apr 13 2002 reboot -r-xr-xr-x 1 root bin 176128 Apr 13 2002 route -r-xr-xr-x 1 root bin 61440 Apr 13 2002 scan_ffs -r-xr-xr-x 1 root bin 135168 Apr 13 2002 sysctl -r-xr-xr-x 1 root bin 12288 Apr 13 2002 tbrconfig -r-xr-xr-x 1 root bin 53248 Apr 13 2002 ttyflags -r-xr-xr-x 1 root bin 159744 Apr 13 2002 umount -r-xr-xr-x 1 root bin 86016 Apr 13 2002 wicontrol # ls -la /mnt/stand total 21236 drwxr-xr-x 2 root wheel 512 Oct 27 06:20 . drwxr-xr-x 11 root wheel 512 Oct 27 06:22 .. -r-xr-xr-x 1 root bin 110592 Sep 22 12:47 gunzip -rw-r--r-- 1 root wheel 10733232 Oct 26 06:40 mfs.tgz # ------------------------------ -- Mike McClure, CCIE # 5125, CISSP # 30232 PNE Services, Inc. - http://www.pneservices.com mmc...@pn... mobile: 913-636-5590 |
|
From: Mike M. <mmc...@pn...> - 2002-10-26 15:15:21
|
D'oh! Never mind, I should have done "disklabel -d sd0" like it says in the comments in flashdist.sh. It's working now. Thanks again! > Thanks for the fast response, it's very much appreciated! > > I'm still having no luck, however. Here's the output of 'disklabel sd0', after I > cleared out the partitions: > > ------------------ > # disklabel sd0 > # using MBR partition 3: type A6 off 32 (0x20) size 125408 (0x1e9e0) > # /dev/rsd0c: > type: SCSI > disk: SCSI disk > label: ImageMate II > flags: > bytes/sector: 512 > sectors/track: 32 > tracks/cylinder: 8 > sectors/cylinder: 256 > cylinders: 490 > total sectors: 125440 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # microseconds > track-to-track seek: 0 # microseconds > drivedata: 0 > > 16 partitions: > # size offset fstype [fsize bsize cpg] > c: 125440 0 unused 0 0 # (Cyl. 0 - 489) > # > ----------------- > > So I changed flashdist.sh to this: > > -------------- > # Value Disklabel name > # > #totalsize=62720 # "total sectors:" > totalsize=125440 > bytessec=512 # "bytes/sector:" > sectorstrack=32 # "sectors/track:" > sectorscylinder=256 # "sectors/cylinder:" > trackscylinder=8 # "tracks/cylinder:" > #cylinders=245 # "cylinders:" > #cylinders=285 > #cylinders=213 # doesn't work > #cylinders=245 > cylinders=490 > ---------------- > > And when I run 'python build.py -b sd0', I get this: > > ----------------- > # /usr/local/bin/python build.py -b sd0 > 1035585396.92 [12687]: Creating working stand directory... > 1035585396.93 [12687]: Copying boot files into working stand directory... > # using MBR partition 3: type A6 off 32 (0x20) size 125408 (0x1e9e0) > fdisk: sysctl(machdep.bios.diskinfo): Device not configured > # using MBR partition 3: type A6 off 32 (0x20) size 125408 (0x1e9e0) > newfs: /dev/rsd0a: Device busy > 1035585410.76 [12687]: flashdist.sh 20020501 ch...@dq... > 1035585410.76 [12687]: Using disk device: sd0 > 1035585410.76 [12687]: Using distfile: /root/CompactBSD-0.1.0/flashdist/flashbig.txt > 1035585410.76 [12687]: Copying kernel from: /bsd > 1035585410.76 [12687]: > 1035585410.76 [12687]: Please pay attention to any error messages that you may > 1035585410.76 [12687]: receive from the commands this script it using. If you > 1035585410.76 [12687]: end up having problems, they could explain why. > 1035585410.76 [12687]: Setting up disklabel... > 1035585410.76 [12687]: > 1035585410.77 [12687]: The install script is using the following parameters: > 1035585410.77 [12687]: Total size of media: 125440 sectors (64225280 bytes) > 1035585410.77 [12687]: Bytes/Sector: 512 > 1035585410.77 [12687]: Sectors/Track: 32 > 1035585410.77 [12687]: Sectors/Cylinder: 256 > 1035585410.77 [12687]: Tracks/Cylinder (heads): 8 > 1035585410.77 [12687]: Cylinders: 490 > 1035585410.77 [12687]: > 1035585410.77 [12687]: Updating MBR and partition table... > 1035585410.77 [12687]: Note, you may ignore "sysctl(machdep.bios.diskinfo)" errors > if present. > 1035585410.77 [12687]: > 1035585410.77 [12687]: Installing disklabel... > 1035585410.77 [12687]: disklabel -R sd0 /tmp/_ahhr17752 > 1035585410.77 [12687]: > 1035585410.77 [12687]: Creating new filesystem... > 1035585410.78 [12687]: newfs -c 490 -S 512 -u 32 -z 8 -o space /dev/rsd0a > 1035585410.78 [12687]: There was a problem running newfs. Maybe the geometry is wrong? > # > ----------------- > > And finally, after the run, I tried it again manually: > > ------------------ > # newfs -c 490 -S 512 -u 32 -z 8 -o space /dev/rsd0a > Oct 25 17:39:59 cthulhu /bsd: sd0: mode sense (4) returned nonsense; using > fictitious geometry > Oct 25 17:39:59 cthulhu /bsd: sd0: mode sense (4) returned nonsense; using > fictitious geometry > Block size restricts cylinders per group to 285. > # disklabel sd0a > # /dev/rsd0a: > type: SCSI > disk: SCSI disk > label: ImageMate II > flags: > bytes/sector: 512 > sectors/track: 32 > tracks/cylinder: 8 > sectors/cylinder: 256 > cylinders: 490 > total sectors: 125440 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # microseconds > track-to-track seek: 0 # microseconds > drivedata: 0 > > 16 partitions: > # size offset fstype [fsize bsize cpg] > a: 125152 32 4.2BSD 1024 8192 16 # (Cyl. 0*- 488) > b: 1 125184 swap # (Cyl. 489 - 489*) > c: 125440 0 unused 0 0 # (Cyl. 0 - 489) > # > ------------------------- > > >> If you run 'disklabel /dev/sd0' (or sd1), I think it will show you the >> parameters you need to change in flashdist.sh to use the 64MB card. >> >> Steve >> >> -----Original Message----- >> From: com...@li... >> [mailto:com...@li...]On Behalf Of Mike >> McClure >> Sent: Friday, October 25, 2002 7:21 PM >> To: com...@li... >> Subject: [Compactbsd-devel] (no subject) >> >> >> Howdy. >> >> What parameters must I change in flashdist.sh to use a 64MB CF card? >> >> Or should they be changed somewhere else? >> >> Thanks, >> >> Mike >> >> >> -- >> Mike McClure, CCIE # 5125, CISSP # 30232 >> PNE Services, Inc. - http://www.pneservices.com >> mobile: 913-636-5590 >> >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: Influence the future >> of Java(TM) technology. Join the Java Community >> Process(SM) (JCP(SM)) program now. >> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en >> _______________________________________________ >> Compactbsd-devel mailing list >> Com...@li... >> https://lists.sourceforge.net/lists/listinfo/compactbsd-devel >> >> > > > -- > Mike McClure, CCIE # 5125, CISSP # 30232 > PNE Services, Inc. - http://www.pneservices.com > mmc...@pn... > mobile: 913-636-5590 > > > > -- Mike McClure, CCIE # 5125, CISSP # 30232 PNE Services, Inc. - http://www.pneservices.com mmc...@pn... mobile: 913-636-5590 |
|
From: Mike M. <mmc...@pn...> - 2002-10-26 03:42:18
|
Thanks for the fast response, it's very much appreciated! I'm still having no luck, however. Here's the output of 'disklabel sd0', after I cleared out the partitions: ------------------ # disklabel sd0 # using MBR partition 3: type A6 off 32 (0x20) size 125408 (0x1e9e0) # /dev/rsd0c: type: SCSI disk: SCSI disk label: ImageMate II flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 8 sectors/cylinder: 256 cylinders: 490 total sectors: 125440 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # size offset fstype [fsize bsize cpg] c: 125440 0 unused 0 0 # (Cyl. 0 - 489) # ----------------- So I changed flashdist.sh to this: -------------- # Value Disklabel name # #totalsize=62720 # "total sectors:" totalsize=125440 bytessec=512 # "bytes/sector:" sectorstrack=32 # "sectors/track:" sectorscylinder=256 # "sectors/cylinder:" trackscylinder=8 # "tracks/cylinder:" #cylinders=245 # "cylinders:" #cylinders=285 #cylinders=213 # doesn't work #cylinders=245 cylinders=490 ---------------- And when I run 'python build.py -b sd0', I get this: ----------------- # /usr/local/bin/python build.py -b sd0 1035585396.92 [12687]: Creating working stand directory... 1035585396.93 [12687]: Copying boot files into working stand directory... # using MBR partition 3: type A6 off 32 (0x20) size 125408 (0x1e9e0) fdisk: sysctl(machdep.bios.diskinfo): Device not configured # using MBR partition 3: type A6 off 32 (0x20) size 125408 (0x1e9e0) newfs: /dev/rsd0a: Device busy 1035585410.76 [12687]: flashdist.sh 20020501 ch...@dq... 1035585410.76 [12687]: Using disk device: sd0 1035585410.76 [12687]: Using distfile: /root/CompactBSD-0.1.0/flashdist/flashbig.txt 1035585410.76 [12687]: Copying kernel from: /bsd 1035585410.76 [12687]: 1035585410.76 [12687]: Please pay attention to any error messages that you may 1035585410.76 [12687]: receive from the commands this script it using. If you 1035585410.76 [12687]: end up having problems, they could explain why. 1035585410.76 [12687]: Setting up disklabel... 1035585410.76 [12687]: 1035585410.77 [12687]: The install script is using the following parameters: 1035585410.77 [12687]: Total size of media: 125440 sectors (64225280 bytes) 1035585410.77 [12687]: Bytes/Sector: 512 1035585410.77 [12687]: Sectors/Track: 32 1035585410.77 [12687]: Sectors/Cylinder: 256 1035585410.77 [12687]: Tracks/Cylinder (heads): 8 1035585410.77 [12687]: Cylinders: 490 1035585410.77 [12687]: 1035585410.77 [12687]: Updating MBR and partition table... 1035585410.77 [12687]: Note, you may ignore "sysctl(machdep.bios.diskinfo)" errors if present. 1035585410.77 [12687]: 1035585410.77 [12687]: Installing disklabel... 1035585410.77 [12687]: disklabel -R sd0 /tmp/_ahhr17752 1035585410.77 [12687]: 1035585410.77 [12687]: Creating new filesystem... 1035585410.78 [12687]: newfs -c 490 -S 512 -u 32 -z 8 -o space /dev/rsd0a 1035585410.78 [12687]: There was a problem running newfs. Maybe the geometry is wrong? # ----------------- And finally, after the run, I tried it again manually: ------------------ # newfs -c 490 -S 512 -u 32 -z 8 -o space /dev/rsd0a Oct 25 17:39:59 cthulhu /bsd: sd0: mode sense (4) returned nonsense; using fictitious geometry Oct 25 17:39:59 cthulhu /bsd: sd0: mode sense (4) returned nonsense; using fictitious geometry Block size restricts cylinders per group to 285. # disklabel sd0a # /dev/rsd0a: type: SCSI disk: SCSI disk label: ImageMate II flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 8 sectors/cylinder: 256 cylinders: 490 total sectors: 125440 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # size offset fstype [fsize bsize cpg] a: 125152 32 4.2BSD 1024 8192 16 # (Cyl. 0*- 488) b: 1 125184 swap # (Cyl. 489 - 489*) c: 125440 0 unused 0 0 # (Cyl. 0 - 489) # ------------------------- > If you run 'disklabel /dev/sd0' (or sd1), I think it will show you the > parameters you need to change in flashdist.sh to use the 64MB card. > > Steve > > -----Original Message----- > From: com...@li... > [mailto:com...@li...]On Behalf Of Mike > McClure > Sent: Friday, October 25, 2002 7:21 PM > To: com...@li... > Subject: [Compactbsd-devel] (no subject) > > > Howdy. > > What parameters must I change in flashdist.sh to use a 64MB CF card? > > Or should they be changed somewhere else? > > Thanks, > > Mike > > > -- > Mike McClure, CCIE # 5125, CISSP # 30232 > PNE Services, Inc. - http://www.pneservices.com > mobile: 913-636-5590 > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en > _______________________________________________ > Compactbsd-devel mailing list > Com...@li... > https://lists.sourceforge.net/lists/listinfo/compactbsd-devel > > -- Mike McClure, CCIE # 5125, CISSP # 30232 PNE Services, Inc. - http://www.pneservices.com mmc...@pn... mobile: 913-636-5590 |
|
From: Mike M. <mmc...@pn...> - 2002-10-26 00:04:22
|
Howdy. What parameters must I change in flashdist.sh to use a 64MB CF card? Or should they be changed somewhere else? Thanks, Mike -- Mike McClure, CCIE # 5125, CISSP # 30232 PNE Services, Inc. - http://www.pneservices.com mobile: 913-636-5590 |
|
From: Steve D. <sdi...@no...> - 2002-09-15 13:59:22
|
http://neon1.net/misc/minibsd.html Just a link with a lot of usefull info. Its geared towards FreeBSD, but is still applicable. Appendix C has a nice solution for saving data across reboots. I am working on pulling certain config files from the main tar file and creating a seperate tar for them. Its small enough that I can untar it in memory and make the changes I need. Then tar it back up for the next boot. I was also thinking about a short script that just reads a list of files to tar/untar. Easy way to make small changes (i.e. pf.conf, passwd etc.) and save it to the CF disk. Anybody had any luck using Current? Quite a few things changed, and I haven't had enough time to track them all down.... Steve D. |
|
From: Ryan S. <rrs...@tt...> - 2002-09-15 08:20:31
|
Hi, In the current form compactBSD will not work on a CDROM. The problem is with how it deals with the root partition, it needs to be rw accessible. This is definitely something that is needed however, expecially for compact flash. Ideally we want to mount the whole filesystem in memory, but it just doesn't do that yet. Ryan Sadler On Sat, 14 Sep 2002, Earle Lyons wrote: > I was curious if CompactBSD could be used to build a self-contained OpenBSD > Live CD distribution? > > Thank you, > -earle |
|
From: Earle L. <ev...@ea...> - 2002-09-15 00:15:05
|
I was curious if CompactBSD could be used to build a self-contained OpenBSD Live CD distribution? Thank you, -earle |
|
From: James N. <kr...@te...> - 2002-09-11 22:38:52
|
Hi Steve, Yes it is possible to make changes persistent. There is a file called /stand/mfs.tgz. This tarball contains all the files that are copied into the mfs memory partitions. Within this tarball are all the files you would need to modify to make changes persistent. The reason for having mfs memory partitions, is because the size of the 32MB flash is limiting but useful to small installs. Another reason is performance - mounting as many partitions into RAM greatly increases the speed of the system, even if the hardware is not so speedy underneath. Hope this answers your questions, and I apologize for not getting back to you sooner... James Nedila ja...@fa... Steve D. wrote: >Ok, > >I finally managed to get things up and running and its working great. One >question I have is....how do I make changes to the running configuration and >have it carry over to the next boot? It looks to me like the only real >mount is / and all the others are mfs mounts. Is there any way to make >changes without burning a new image? > >Thanks, > >Steve > > |
|
From: Steve D. <st...@no...> - 2002-09-10 03:11:13
|
Ok, I finally managed to get things up and running and its working great. One question I have is....how do I make changes to the running configuration and have it carry over to the next boot? It looks to me like the only real mount is / and all the others are mfs mounts. Is there any way to make changes without burning a new image? Thanks, Steve |
|
From: Earle L. <ev...@ea...> - 2002-08-24 18:27:55
|
I was curious if CompactBSD could be used to build a self-contained OpenBSD Live CD distribution? Thank you, -earle |
|
From: Ken S. <ksi...@Fa...> - 2002-08-22 23:43:26
|
> Ehh... it's worth noting up front that as it is this most definitely > needs a BSD host system. "Well duh" perhaps? I'll try to find somewhere on the project page where that can be made more clear. > It could be made to not, I think, but it wasn't immediately clear that > this was this was a requirement. Make->pmake, specify the ARCH > explicitly (no i686 on bsd?) gets you a ways... the big issues being > tools cap_mkdb and pwd_mkdb missing, flashdist.sh bsd-oriented. It would be nice to make it work with *BSD and even Linux. It could evolve into a generic build system for compact-flash based *nix devices. BTW: I'm going on vacation now, so please don't be offended if I don't reply to emails until mid-September :) TTUL Ken > On Wed, 21 Aug 2002 17:22:17 -0700 (PDT), Ken Simpson said: > > > I just released CompactBSD-0.1.0, which is a tool that we use here at > > FatPort to burn OpenBSD onto compact flash for use inside our > > FatPointOEM box (http://www.fatport.com/products/fatpoint_OEM). The > > source is available on SourceForge > > (https://sourceforge.net/projects/compactbsd/) and is covered under > > the FatPointOEM license -- which is very similar to the BSD license. > > > > The CompactBSD tool automagically fetches OpenBSD, builds a tiny > > profile of it, and then loads it onto compact flash. You can use the > > basic CompactBSD setup as a launching pad for your own embedded BSD > > project, adding or removing files from the default build to add or > > remove features. > > > > We spent a long time gluing together all the little pieces that make > > this tool work. Hopefully, many of you will find it useful. > > > > If you have any questions or comments about CompactBSD, please refer > > them to the project mailing list, to which you can subscribe at > > http://lists.sourceforge.net/lists/listinfo/compactbsd-devel. > > > > This is an early release and there are bound to be problems with it. > > Contributions are welcome :) > > > > Best Regards, > > Ken Simpson, > > CTO, FatPort > > > > -- > > Secure Broadband Wireless. Why wait? FatPort is here. > > http://www.FatPort.com -- 1-866-FAT-PORT (328-7678) > > > > -- > > The Personal Telco Project - http://www.personaltelco.net/ > > Un/Subscribe: http://lists.personaltelco.net/mailman/listinfo/ptp/ > > Archives: http://lists.personaltelco.net/pipermail/ptp/ > > Etiquette: http://www.personaltelco.net/index.cgi/MailingListEtiquette > > > -- > The Personal Telco Project - http://www.personaltelco.net/ > Un/Subscribe: http://lists.personaltelco.net/mailman/listinfo/ptp/ > Archives: http://lists.personaltelco.net/pipermail/ptp/ > Etiquette: http://www.personaltelco.net/index.cgi/MailingListEtiquette > > |
|
From: Jerritt C. <co...@li...> - 2002-08-22 07:46:40
|
Ehh... it's worth noting up front that as it is this most definitely needs a BSD host system. "Well duh" perhaps? It could be made to not, I think, but it wasn't immediately clear that this was this was a requirement. Make->pmake, specify the ARCH explicitly (no i686 on bsd?) gets you a ways... the big issues being tools cap_mkdb and pwd_mkdb missing, flashdist.sh bsd-oriented. Thanks (will play more when I have a BSD in front of me), Jerritt On Wed, 21 Aug 2002 17:22:17 -0700 (PDT), Ken Simpson said: > I just released CompactBSD-0.1.0, which is a tool that we use here at > FatPort to burn OpenBSD onto compact flash for use inside our > FatPointOEM box (http://www.fatport.com/products/fatpoint_OEM). The > source is available on SourceForge > (https://sourceforge.net/projects/compactbsd/) and is covered under > the FatPointOEM license -- which is very similar to the BSD license. > > The CompactBSD tool automagically fetches OpenBSD, builds a tiny > profile of it, and then loads it onto compact flash. You can use the > basic CompactBSD setup as a launching pad for your own embedded BSD > project, adding or removing files from the default build to add or > remove features. > > We spent a long time gluing together all the little pieces that make > this tool work. Hopefully, many of you will find it useful. > > If you have any questions or comments about CompactBSD, please refer > them to the project mailing list, to which you can subscribe at > http://lists.sourceforge.net/lists/listinfo/compactbsd-devel. > > This is an early release and there are bound to be problems with it. > Contributions are welcome :) > > Best Regards, > Ken Simpson, > CTO, FatPort > > -- > Secure Broadband Wireless. Why wait? FatPort is here. > http://www.FatPort.com -- 1-866-FAT-PORT (328-7678) > > -- > The Personal Telco Project - http://www.personaltelco.net/ > Un/Subscribe: http://lists.personaltelco.net/mailman/listinfo/ptp/ > Archives: http://lists.personaltelco.net/pipermail/ptp/ > Etiquette: http://www.personaltelco.net/index.cgi/MailingListEtiquette > |
