Yes it will be separate, but only if it's possible to overwrite files from main sfs, with those from archapps.sfs

the way that i would accomplish that is by using the archpupx script and a tmp file stored on the archapps.sfs, so if it gets auto loaded archpupx could have an if command scripted at the beginning of it like:

What's important with adrv or better call it apdrive, is if that sfs module will be able to overwrite files in archpup-12.12.sfs.
If you add xfce desktop then /etc/profile needs to be overwritten in order to replace

Quote:

export WINDOW_MANAGER="openbox"

with:

Quote:

export WINDOW_MANAGER="xfce4-session"

EDIT: To continue using archapps-12.12.sfs, it's best to automatically load additional file
that contains archapps-*.sfs, so it will support newer version and also different names like archapps-xfce.sfs

Lets not get carried away.
The {a,apps,archapps}drv.sfs that auto-loads on boot should be only one (imagine someone trying to load and run 2 different desktops). For user facilitation a gtldialog/yad script could be included in the base as a GUI to choose which of the available SFSs will renamed to adrv.sfs for next boot, but even this might be an exaggeration. You do not even need terminal to rename a file and everyone know how to do it from the file manager.

Regarding over-writing, all the SFSs except the savefile and pup_rw are below the main sfs in the layered filesystem. So any overwriting must be done by an install script in the said SFS.
I believe SFS_load supports running install scripts (didn't check the archpup version) and something similar should be added in the rc.sysinit if adrv.sfs needs this._________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

/etc/profile wouldn't need to be overwritten anyhow if it only existed in the adrv, right?

It wouldn't need to be overwritten if I remove /etc/profile from main sfs, but I can't remove it, because it specifies needed environment variables. Anyway, for me it seems easier to just inside sfs file (xfce.sfs ?), make pinstall.sh script that will replace window manager in /etc/profile. This adrv thing looks like too complicated.

/etc/profile wouldn't need to be overwritten anyhow if it only existed in the adrv, right?

It wouldn't need to be overwritten if I remove /etc/profile from main sfs, but I can't remove it, because it specifies needed environment variables. Anyway, for me it seems easier to just inside sfs file (xfce.sfs ?), make pinstall.sh script that will replace window manager in /etc/profile. This adrv thing looks like too complicated.

Not really.
To "satisfy" stifiling all you need is to remove /usr/bin/archpupx. Then X will not start. And there are other ways too.

I had some progress on the adrv . The attached initrd patch will mount archapps sfs (renamed adrv_arch_1212.sfs) fine on /initrd/pup_a.
Pls remind me the script that you modify the puppy initrd.gz with so I can make a proper patch (including the mode'ing commands) for your repo (but please feel free to do it yourself )

Although not mandatory, I also included DISTRO_IDSTRING. Makes file detection more efficient. You just need to add it in the SFSs and the kernel with

Code:

echo -n "$DISTRO_IDSTRING" >> target_file

Are we ready then? No.
The union is not formed properly. The sfs in mounted in /initrd/pup_a and files there open ok (tried firefox) but /initrd/pup_a is not part of the union.
So I have to look in the main sfs .
Is Archpup using anything unique (comparing to traditional puppies) to set up the layered FS (besides missing aufs-utils)?

Latter. The 7 people that downloaded this patch please disregard it and download the new one that works OK!_________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Last edited by mavrothal on Thu 10 Jan 2013, 14:31; edited 4 times in total

It's not for me, it's for users that want it clean, but also with pacman. So just removing that file, isn't not gonna clean it out.

From what I can see the discussion was at the point of removing profile from the base so X will start when adrv is loaded without the need to overwite files in the base. Moving archpupx out of the base, an equally small file will do just that without affecting general OS architecture.

On the question of what goes in the base. As you said kernel and pacman is already available. Kernel, pacman, X and a WM also...
But even if you are not happy with these, archpup build scripts are there too. Changing the names of the packages that go to the base over adrv over devx, is not really the issue.

The real issue is having a usable sytem that things work together well OOTB with an 80-150MB iso. Splitting the SFSs within the iso is secondary at this point.

For the "OOTB system", I would worry first about the kernel, which because of an environmental variable miss-configuration during source download and compile (language), has problems with its headers (and elsewhere?) and does not allow aufs-util compilation and use. It may also be the reason of the problematic udev.
In the "kernel" section also add all the peripherals/subsystem detection and firmware.

Then I would wary about X switching and monitor detection and configuration. The first is perennial problem with the multitude of hardware out there, while the second is currently missing from archpup.

After you establish a solid system that works on most hardware reliably, then you look at basic functionality, ie ease of installation, saving and reconfiguration, which are fairly different in puppy compared to other distros.

Finally, you decide on userspace apps and how to distribute them in your iso. The reason that I put the "file distribution" last is that it can affect bug detection and solution in the previous steps if everyone is using a different system.

But then again, all these may not be as fun to work on _________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

A slower paced thread would be helpful. For example, seems I lost my default wallpaper while playing around. Unlike other pup's, when I put this red robot in /usr/share/backgrounds the system apparently renamed it "default" and the butterfly was gone! BTW, does anyone have a link to that butterfly? Anyone here use Twitter? Just a thought...

A slower paced thread would be helpful. For example, seems I lost my default wallpaper while playing around. Unlike other pup's, when I put this red robot in /usr/share/backgrounds the system apparently renamed it "default" and the butterfly was gone! BTW, does anyone have a link to that butterfly? Anyone here use Twitter? Just a thought...

dennis you can retrieve the butterfly from the location in your puppy:

Yes, it's there.... It took several trial & error "moves" with Thunar before I moved it from
/initrd/pup_ro2/usr/share/backgrounds/default.jpg --TO-- /root/default.jpg

Only after that it worked out via -- Preferences/Openbox/Change Wallpaper
Thanks for the solution. LOL, I was getting used to Red Robot..
*EDIT: If someone actually wants Red Robot, it's on my server at Godaddy.
**http://www.beok.com/Downloads/MARVINSKEW2.png (1.3MB)

/etc/profile wouldn't need to be overwritten anyhow if it only existed in the adrv, right?

It wouldn't need to be overwritten if I remove /etc/profile from main sfs, but I can't remove it, because it specifies needed environment variables. Anyway, for me it seems easier to just inside sfs file (xfce.sfs ?), make pinstall.sh script that will replace window manager in /etc/profile. This adrv thing looks like too complicated.

I haven't looked at archpup at all so take my comments with a grain of salt. For this particular problem, I think you can just drop SFS-specific /etc/profile into /etc/profile.d/ and name them accordingly, e.g. for the gui.sfs you can name it /etc/profile.d/gui.sh and make them executable. The code that does this lives in /etc/profile and has been there for a long time - Barry commented that he lifted it off from Vector. This way you can load any SFS in any order and all will have their required environment variables properly set._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

@stifiling: This test iso works only with kernel parameter apextsfs=arch_openbox.sfs, otherwise additional sfs is not loaded. So that would require patching grub4dos, but even with that user will have to edit menu.lst every time for another arch_*.sfs. It's good idea that you moved /usr/bin/X to another sfs, so on boot it will not stuck trying to exec archpupx over and over again.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum