Comments for propaganda and lies

Comment on flashrd by nickbeee

nickbeee — Fri, 17 Feb 2012 19:47:48 +0000

@vlad – I edited the flashrd script. Look for the lines
export vnddirs="root bin etc sbin usr" # must match vnddirs= in stand/rc and fstab #export vndsize="102400 auto 102400 auto auto"
which show the mappings between the dirs and the vndsize. Change the appropriate parameter in vndsize. For mine I made a 1GB /usr
export vndsize="102400 auto 102400 auto 2097152" # 1GB /usr partition tweak

I’ve not investigated how flashrd creates the auto sizes yet though.

Comment on flashrd by nickbeee

nickbeee — Tue, 14 Feb 2012 19:24:16 +0000

Correction to the above – dd command should end with
BS=64k
(WP doesn’t allow me to preview before submitting :cry:

Comment on flashrd by nickbeee

nickbeee — Tue, 14 Feb 2012 19:21:53 +0000

Thanks for this package Chris. Been playing around with OpenBSD for a while now and this will be useful for a diskless ipv6 router project.
I managed to install to CF using my Mac OSX 10.6 – firstly I built flashrd in a OpenBSD 5.0 Virtual Box VM then exported the image back to the Mac via sftp (OpenBSD VM wouldn’t recognise my USB cardreader).

Under OSX I put the CF in an external USB cardreader where it appears as /dev/disk1.
macbookpro:flashrd nickb$ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted, nobrowse) map auto_home on /home (autofs, automounted, nobrowse) /dev/disk1s1 on /Volumes/FLASHRD (msdos, local, nodev, nosuid, noowners)

I then unmounted the disk from the OSX filesystem -
macbookpro:flashrd nickb$ diskutil unmount /Volumes/FLASHRD Volume FLASHRD on disk1s1 unmounted

Finally I wrote the image file to the flash card using dd -
macbookpro:flashrd nickb$ sudo dd if=flashimg.i386-20120126 of=/dev/disk1 bs=64

Finally I installed the CF card using a CF to 3.5IDE adapter bought on Ebay.

Comment on flashrd by vlad

vlad — Sun, 12 Feb 2012 10:30:21 +0000

I think I asked about this before but cannot find an answer. My openbsd.vnd has cca 273 MB and the /usr slice within is running out of space, had to exclude man pages for the system to fit. How to resize/grow it ? The underlying storage has enough space left.

Comment on flashrd by chris

chris — Sun, 06 Nov 2011 16:11:20 +0000

From the point of view of syslogd, nothing should be different at all. However, /var is writeable in the default flashrd setup but it’s also transient, unless you save it on shutdown.

Comment on flashrd by quist

quist — Mon, 31 Oct 2011 15:49:37 +0000

What is the default operation of the syslog daemon on flashrd? Does it differ from the standard OpenBSD configuration?

Russell

Comment on flashrd by chris

chris — Fri, 28 Oct 2011 14:42:46 +0000

I believe the flashrd edition for 4.9-current should work fine on 5.0 release. I’ll mark it as so on the web site.

Comment on flashrd by quist

quist — Fri, 28 Oct 2011 12:08:01 +0000

What is the status of flashrd for OpenBSD 5.0? Do you wait for the official release and then start the testing/porting at that time? Or have you already been testing.

Russell

Comment on flashrd by Sam Vaughan

Sam Vaughan — Mon, 10 Oct 2011 22:42:27 +0000

Hi Chris, thanks very much for flashrd, I’ve fallen in love with single board computers now!

I’m using 20110303 and finding that even though tardirs is commented out in /etc/rc.shutdown, /var gets tarred anyway by default. (except in single user mode when rc.shutdown is skipped)

I think this is because /etc/rc sources /etc/rc.conf, which sources /etc/rc.conf.local, which defines tardirs to “var”. The solution is to explicitly define tardirs to the empty string in /etc/rc.shutdown instead of leaving it commented out.

The reason I started looking into this was because I was occasionally getting a partially populated /var on boot, presumably as a result of the power being cut whilst /var was being tarred.

Can I suggest that you change /etc/rc.shutdown to a) define an empty tardirs variable and b) tar the files to a temporary file that gets moved to the destination file on completion instead of overwriting the existing file?

Cheers and thanks again for flashrd.

Comment on flashrd by chris

chris — Mon, 16 May 2011 04:40:34 +0000

the FAQ lists some simple upgrade methods, get openbsd.vnd from a 4.9 image and it would be fairly easy

you have to configure the kernel image for sd0 if you don’t use wd0 as your default disk device