Re: Install on compact flash

On 2015-10-19, Paolo Aglialoro wrote: > On Mon, Oct 19, 2015 at 12:27 PM, Stuart Henderson > wrote: > >> Some devices get chown()ed during normal system operation, see fbtab(5). > > Does this mean that write access on files in /dev is limited just to >

Re: Install on compact flash

Does this mean that write access on files in /dev is limited just to permissions change and, therefore, just some bytes of change in the filesystem? This seems pretty much acceptable for me in terms of CF wear-off, if it does not happen with a high frequence. On Mon, Oct 19, 2015 at 12:27 PM,

Re: Install on compact flash

On 2015-10-19, Josh Grosse wrote: > On Mon, Oct 19, 2015 at 04:34:31AM +0200, Einfach Jemand wrote: >> No. As far as I understand it: >> The type (char or block), the major and minor number of the device >> special file and its name are means to activate the corresponding

Re: Install on compact flash

I ran native on compact flash as an experiment for 5+ years without ever changing the CF card. I only migrated away from it because my old soekris couldn't keep up with my internet speeds once I upgraded. It still boots and works fine. Personally I found the hassle of maintaining a ramdisk

Re: Install on compact flash

On Mon, Oct 19, 2015 at 5:02 AM, Stuart Henderson wrote: > On 2015-10-19, Paolo Aglialoro wrote: >> On Mon, Oct 19, 2015 at 12:27 PM, Stuart Henderson >> wrote: >> >>> Some devices get chown()ed during normal system operation, see

Re: Install on compact flash

Am 18.10.2015 um 15:50 schrieb Josh Grosse: > On Sun, Oct 18, 2015 at 01:08:48PM +0200, Paolo Aglialoro wrote: > >> ...Still cannot understand why some of you have adviced to put /dev on >> ramdisk: isn't MAKEDEV just run at install time and then only manually? >> From what emerged in the

Re: Install on compact flash

On Mon, Oct 19, 2015 at 04:34:31AM +0200, Einfach Jemand wrote: > No. As far as I understand it: > The type (char or block), the major and minor number of the device > special file and its name are means to activate the corresponding device > handler ("driver") in the kernel and the bytes are

Re: Install on compact flash

On Sun, Oct 18, 2015 at 01:08:48PM +0200, Paolo Aglialoro wrote: > ...Still cannot understand why some of you have adviced to put /dev on > ramdisk: isn't MAKEDEV just run at install time and then only manually? > From what emerged in the discussion it looks that, besides /home, /var is > the

Re: Install on compact flash

Hi folks, first of all thanks for all your interesting answers! I didn't expect this topic to be so popular and I am quite satisfied to have received a broader perspective than I had in mind. My fault was not specifying exactly what jobs the machine would perform, that could have narrowed down

Re: Install on compact flash

On 2015-10-15 Thu 16:01 PM |, Kenneth Gober wrote: > > You may also want to move cron log files from /var/cron to /var/log (or > /var/log/cron if you want them to be separated from other logs). Doing so > involves modifying /etc/syslog.conf and /etc/newsyslog.conf. If you do > this be prepared

Re: Install on compact flash

On 10/15/15 12:43, Josh Grosse wrote: > On 2015-10-15 12:19, Paolo Aglialoro wrote: > > MyTL;DR - Don't bother. I used to create "live media" read/only > systems, > with MFS filesystems for read/write. > > You'll find maintaining a read-only system much more difficult. exactly. There are a

Re: Install on compact flash

On Oct 15 18:19:12, paol...@gmail.com wrote: > I would like to create an embedded amd64 installation, with system running > on a 8GB 233x CF card attached to an Intel ITX mb. > > In order to minimise nand wear off, I would like to put on ramdisk (the > machine would have 2GB ram, so I believe

Re: Install on compact flash

On Thu, Oct 15, 2015 at 12:19 PM, Paolo Aglialoro wrote: > In order to minimise nand wear off, I would like to put on ramdisk (the > machine would have 2GB ram, so I believe enough also for that, but I still > can upgrade it to 4GB if needed) the parts of the file hierarchy

Re: Install on compact flash

On 2015-10-15 12:19, Paolo Aglialoro wrote: MyTL;DR - Don't bother. I used to create "live media" read/only systems, with MFS filesystems for read/write. You'll find maintaining a read-only system much more difficult. I recommend just treating your flash memory like a disk drive. Modern

Install on compact flash

Hello, I would like to create an embedded amd64 installation, with system running on a 8GB 233x CF card attached to an Intel ITX mb. In order to minimise nand wear off, I would like to put on ramdisk (the machine would have 2GB ram, so I believe enough also for that, but I still can upgrade it

Re: Install on compact flash

On Thu, Oct 15, 2015 at 06:19:12PM +0200, Paolo Aglialoro wrote: > 2. What is the correct filesystem type to put in fstab for all the entries > of point 1. in order to store them in ramdisk? I'm using a line such as: swap /var/log mfs rw,nodev,nosuid,-s40M,-P/var/log.tmpl 0 0 to put /var/log

Re: Install on compact flash

Hi Paolo, check out flashrd as a starting point (possibly also finishing) - http://www.nmedia.net/flashrd/ Jan

Re: Install on compact flash

I run NetBSD 7.0/hpcarm (previously NBSD 6.1.1 through 6.1.5) on a daily-use machine directly from a CF since August 2013. During an upgrade from 6.1.5 to NetBSD 7.0 RC2 a few months ago, I finally ran into a pretty gnarly write error condition on a 4GB SanDisk CF. I bought a fresh 16GB card to

Re: Install on compact flash

On Thu, 15 Oct 2015 18:19:12 +0200 Paolo Aglialoro wrote: > Hello, > > I would like to create an embedded amd64 installation, with system > running on a 8GB 233x CF card attached to an Intel ITX mb. > > In order to minimise nand wear off, I would like to put on ramdisk > (the

Re: Install on compact flash

On 2015-10-15, Stefan Sperling wrote: > On Thu, Oct 15, 2015 at 06:19:12PM +0200, Paolo Aglialoro wrote: >> 2. What is the correct filesystem type to put in fstab for all the entries >> of point 1. in order to store them in ramdisk? > > I'm using a line such as: > > swap /var/log