Page 3 of 3
Posted: Mon 23 May 2016, 15:06
by musher0
Hi nic007.
It's easy to squish stuff with this procedure. I hope you have a back-up?
Please see my post
above and jrb's reply.
BFN.
Posted: Mon 23 May 2016, 16:09
by nic007
musher0 wrote:Hi nic007.
It's easy to squish stuff with this procedure. I hope you have a back-up?
Please see my post
above and jrb's reply.
BFN.
Hi musher0, not sure I follow. I don't have a devx file. Will it work if the two sfs files are not in the same location... where should I move it to? ....or does this method just have issues anyway like it may work or may not?
Use boot params
Posted: Mon 23 May 2016, 21:46
by gyro
Of course instead of renaming files or moding the initrd.gz, you could try specifying them as boot params.
Here is an extract from slacko 5.7 "init", (it's been in standard "init" for a while now)
Code: Select all
[ $pupsfs ] && PUPSFS=$pupsfs #format partition:<path><filename> ex: sda2:/wary071/wary_071.sfs
[ $zdrv ] && ZDRV=$zdrv #ex: sda2:/wary071/zdrv_071.sfs
[ $adrv ] && ADRV=$adrv
[ $ydrv ] && YDRV=$ydrv
This shows how to use these params. e.g.
Code: Select all
pupsfs=sda2:/wary071/zdrv_071.sfs zdrv=sda2:/wary071/wary_071.sfs
or
Just be aware of the following limitations:
1) They don't fail gracefully, so get it right.
2) They cannot work on usb drives
3) Only the pup..sfs and pupsave code is capbable of mounting a partition. All other sfs's must reside on one of these 2 partitions.
Remember the order of the sfs's in the aufs stack is adrv, ydrv, pupsfs, zdrv.
gyro
Posted: Tue 24 May 2016, 09:08
by nic007
I've copied the files to hard drive and re-booted. It now seems to load without kernel panic but later stops at a login error