what's this usr_dex.sfs and usr_more.sfs thing?

[Tito]

so...

what's this usr_dex.sfs and usr_more.sfs thing ?
Can puppy function without them ?

I have some idea about what they are but I still got some noob questions:

The pup001 file holds all saved files right ?
So if I install apps, the program files all go into the pup001 right ?
...so can I carry my personal pup001 file with my apps/files/emails, and copy them on systems with puppy already installed ?

Are hardware dependent settings also saved in the pup001 file ?
Like xorg config, ethernet, etc ?
If so, can they be saved to a separate usr_more.sfs ?

Or is there a way to make a pupxxx file which I can mount separately which contains my installed apps and files/emails, without anything else ?

[PeterSieg]

Hi.

pup001 is actually a filesystem mounted by puppy with the loop function.
By using unionfs, it contains your /root folder and any changes made to
/etc, /usr (goes to /root/.etc + /root/.usr).

So the result is, that any settings and installed software (as long as it does not install to locations mapped in ram disk!!) will be saved inside pup001.

So you can copy pup001 to a new machine and booting puppy from live-cd
brings up an puppy with your settings and addons...

*.sys are also filesystem using squashfs for compression. They are
READ ONLY!. For Puppy, they must be copied to /mnt/home (that is were
you will find the pup001 file). If puppy boots and finds these *.sfs files,
they will be automatically mounted to /usr as well and so will work as
they were in native Puppy..

usr_devx.sfs contains gcc/g++/Perl compiler + supporting libraries and
tools. So this is for compiling apps for puppy...

usr_more.sfs is for any other such filesystems. The first one now just been
released contains wine-the windows emulation layer to allow you to run
some windows apps under Puppy...

Hope that clarifies some things..

PS

[Tito]

Hope that clarifies some things..

yep, thx !

Still a question though...

If the settings are also stored in the pup000 file, wont that cause trouble when using the same pup000 on another pc ?
fe: I use 1024x768 display, but the other machine has only 800x600. when using the pupfile on the older pc, after using it on the new pc, the screen will turn black, i asume... no ? (i'm using the xorg server with xorg.conf)

[brad_chuck]

I dont carry around a pup001 file i just have a folder on my flash disk named UsedInstall that has all my .pup files and other files to install.

so if i use a new computer i just let puppy put the pup001 file where it likes and then install all my stuff.

then when i bootup on that computer the next time it is all there.

[Tito]

when using the same pup000 file on another computer,
I lost :
1. my emails + settings (sylpheed)
2. Xorg server (dotpup install)

Things it did save :
Newly installed win manager and file manager, all through dotpups...

so, where does it save the /mail folder to ? and to xorg server ? Can they be put in a se

[MU]

The xorg-server is in pup001.

If it does not work on another PC, hit CTRL-ALT-BACKSPACE to exit the nonworking X.

then type
mp /etc/X11/xorg.conf to set up the new Graficscard.

I made 2 scripts, m1 and m2 (I've put them in /usr/bin)

They look like this:

m1

Code: Select all

#!/bin/sh
rm -f /etc/X11/xorg.conf
cp  /etc/X11/xorg.conf.vesa  /etc/X11/xorg.conf

m2

Code: Select all

#!/bin/sh
rm -f /etc/X11/xorg.conf
cp  /etc/X11/xorg.conf.sis  /etc/X11/xorg.conf

This assumes you have 2 xorg.conf with different names:

So I can switch between Vesa (works nearly everywhere) and my optimized SIS-Driver by typing "m1" or "m2" in console.

You might run m1 every time you exit X.
You can do that by adding the line

Code: Select all

m1

as LAST line to /root/.xinitrc

Then it should be executed when the Desktop shuts down,and you always have the Vesa-Driver as default, when you start Puppy.
This can be important, if you use it with a Computer, where a wrong Graficscard-Driver messes up X so strong, that you cannot exit it with CTRL-ALT-BACKSPACE to get the console.

Mark

[Tito]

k thx !! ill try that out. This way I can switch on and off virtual viewports.

But I still dont understand my emails arent saved...
(im using the xp installer)

[saintlangton]

*.sys are also filesystem using squashfs for compression. They are
READ ONLY!. For Puppy, they must be copied to /mnt/home (that is were
you will find the pup001 file). If puppy boots and finds these *.sfs files,
they will be automatically mounted to /usr as well and so will work as
they were in native Puppy..

usr_devx.sfs contains gcc/g++/Perl compiler + supporting libraries and
tools. So this is for compiling apps for puppy...

usr_more.sfs is for any other such filesystems. The first one now just been
released contains wine-the windows emulation layer to allow you to run
some windows apps under Puppy...

Hope that clarifies some things..

PS

With more ideas for these usr_more.sfs (Kde,Openoffice,Wine) would it be possible for them to have different names ie usr_wine.sfs, usr_kde.sfs etc. As I understand it they have to be in the same directory to work so I couldn't have say KDE and WINE at the same time because once one is there the next would overwrite it. I tried renaming the usr_more.sfs for wine like this but it broke it

Chris