search

Webconverger / webc

Webconverger's curated chroot from which updates originate
https://webconverger.org/upgrade/
73 stars 37 forks source link

/etc/webc/cmdline needs to be writable #73

Closed kaihendry closed 12 years ago

kaihendry commented 12 years ago

Maybe move this to a writeable partition.

To be honest, I prefer to see a git clone here: https://github.com/Webconverger/webc/blob/master/etc/webc/install-to-disk.sh#L120

The live version can mount the git-fs, but for the install version, I wanted to see a normal "open" (not sure on terminology) clone so one could:

1) Write /etc/webc/cmdline for example 2) Notice runtime differences in the files with git status

kaihendry commented 12 years ago

12:08 @blathijs hendry: I was considering putting the cmdline file (and/or other config files) outside of the rootfs, on the actual boot medium 12:09 @blathijs so they can be accessed through /live/image/somewhere

kaihendry commented 12 years ago

I noticed that /live/image is mounted readonly. I don't where this mounting happens, not the /etc/fstab after checking it. Any hints ? I'm not the expert here, just trying to help and drive things @matthijskooijman @patrickhaller :)

kaihendry commented 12 years ago

Just had a thought that with "noclean" we did /home to be also writeable and persistent between boots.

matthijskooijman commented 12 years ago

Yup, but that's something for live-boot / live-config to do. I've been using a second partition, labeled "home-rw" for this to work, but I think it could even be a filesystem image file on the main partition called "home-rw.img" (or something), so /live/image/home-rw.img.

kaihendry commented 12 years ago

Create a spare file of 2G http://intgat.tigress.co.uk/rmy/uml/sparsify.html ?

One thing I want to make clear, is this is more of a persistent performance cache, for people who use the config service (configs get cached) and "noclean". It should work without this rw.img, or if it gets recreated imo.

matthijskooijman commented 12 years ago

I don't think the sparseness of files gets preserved through a HTTP download, so this only saves space on the download server, people will still need to download 2G of zeroes (gzip might help here) and write all those zeroes to an USB disk (burning this image to a cdrom won't work, I guess).

About the cache thing, I don't quite think I'm following you? The configs will be cached whenever there is a rw filesystem through /live/image/somewhere, regardless of noclean or persistent. The persistent option serves to make /home persistent, so the browser cache and cookies get preserved?

kaihendry commented 12 years ago

The command line is cached at /live/image/live/webc-cmdline