![Very Happy :D](./images/smilies/icon_biggrin.gif)
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
![Laughing :lol:](./images/smilies/icon_lol.gif)
![Razz :P](./images/smilies/icon_razz.gif)
![Question :?:](./images/smilies/icon_question.gif)
Regarding c:drv, let me recycleanother postgreengeek wrote:Now that we have adrv, ddrv and zdrv, could you also add c:drv please (to contain all my Windows files). I noticed ever since I first tried puppy that the c:drv has been missing...
It can run from NTFS partitions.
Actually I find this a flaw! (also for puppy)
NTFS. So primarily you are a windows user, used to be asked 5 times if you "really, truly, positively want to open this application".
And now you are granted root access in a system that you do not know very well and you are one typo/click away from messing your Windows partition (and then spend a day try to recover your "graduation pictures" ).
Besides NTFS already implies that it is a hobby/test OS and is not really used
Not that I know off. But is the filemnt behavior changes in you setting depending on "set -x"?R-S-H wrote: To set option -x (set -x) in filemnt would have which effect?
Code: Select all
#!/bin/bash -a
#------------------------------------------------------------------------------
# Make loop devices for LazY Puppy
#------------------------------------------------------------------------------
for i in 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64;
do
mknod -m664 /dev/loop$i b 7 $i
done
exit 0
#------------------------------------------------------------------------------
# End
#------------------------------------------------------------------------------
Code: Select all
mknod -m664 /root/init_rd_temp/dev/loop$i b 7 $i
I do not know.R-S-H wrote: I assume different path makes no difference?
No, the devices are not outside /dev. What I meant is, if I'm extracting the initrd.gz to edit the files those files will be extracted to /root/init_rd_temp. Therefor the path for the mknod command script would be /root/init_rd_temp/dev. Sorry for confusing you.I do not know.
I have not seen devices outside /dev but this may just be a convention.
As usual useful information!RSH : If the initrd.gz initscript should mount these dozen .sfs to merge them into the layered aufs/unionfs filesystem, then it must be altered. This sfs_load by shinobar is a nice and apparently good working script to mount and merge .sfs by /etc/rc.d/rc.sysinit or rc.local or /root/Startup/my_sfs_load_script.sh .
Thanks, but so far: nothing crashed!Happy crashes while experimenting with /init !
The adrv and ydrv are already in woof-CE and slacko-5.7 initrd could use them if defined in DISTRO_SPECS. You could use those instead of a pdrv.greengeek wrote: My question is - could it be possible that puppy could use a 'pdrv' which contains the personal configuration?
OK thanks thats a good start - two things I want to clarify -mavrothal wrote:The adrv and ydrv are already in woof-CE and slacko-5.7 initrd could use them if defined in DISTRO_SPECS. You could use those instead of a pdrv.
As I said adding the a,y,zdev name in initrd DISTRO_SPECS will make it mountable when present.greengeek wrote: 1) My question is really directed at the idea of HOW such a drv.sfs is used when the initrd grabs it and uses it.
Firstly because it is much easier to add a xdrv into an iso by using isomaster than it is to remaster a puppy, and secondly I was hoping someone would say 'yes, we can force the initrd to load a textfile from the cd' which would be a very simple way of grabbing a users setup parameters. Simpler even than making an xdrv. One simple text file containing basic desktop setup defaults in a standard format - for puppy init scripts to refer to during boot.But why do you think that building an cdrv.sfs with ones personal setting will be easier than just a good old puppy remaster?
It appears I am the only one. If it were dangerous then pets are even more soMy question is - are there any types of .sfs files that ARE able to overwrite the main.sfs? Is there any version of puppy that has an initrd which contains the ability to accept an "xdrv.sfs" that can be used to 'override' or 'overwrite' a file within the main puppy.sfs?