mikeslr wrote:@ der-schutzhund,
- Possibility to customize using a start script at booting:
Not sure it would provide everything you want, but all "DebianDogs" and "XenialDogs" use boot arguments, and which boot arguments are a choice you make.
- Updating via a shutdown-script when shutting down. At shut-down you have the option to Save changes or not. You can also Save change while the system is running. If an icon to do so isn't on the desktop, open a terminal and type, code: save2flash.
"- dynamic integration of SFS...
I would like to start each program via its own script. This script checks if a dependent module is already loaded and if it is not loaded automatically. Of course I define the dependent modules before. This is exactly how it works in my current system.
As mentioned, Apt2sfs will include necessary dependencies for any SFS you create. The ones you create yourself will have an ending of "squashfs" rather than SFS. But see below.
There are several ways to use SFSes. I'm not sure any can be loaded automatically at bootup. One way creates a script file adjacent to the SFS. To load the application, you click the script. It may be possible to create symlinks to these script in a folder in /root so you don't have to open to /mnt/home and scan thru all files looking for the script you want. I don't know to what extent these scripts can be modified.
- my current SFS should run (possibly after an adjustment)! All SFSes created for Puppies can be loaded. But only some may run and even those may require 'adjustments'.
I'm not sure which version of LazyPuppy you are using. There's one based on Lupu, one based on Precise, and if my memory isn't playing tricks, the latest one is based on Tahr. All, however, are base on Ubuntu binaries. TrinityDog is based on debian. Much in common with Ubuntu, but not identical. SFSes built for 'Ubuntu' Puppies may not include all dependencies as some of the dependencies may be provided by/included in the Puppy itself. A debiandog may lack them entirely.
MintPup (LST), http://murga-linux.com/puppy/viewtopic. ... 430#858430 or XenialDog, http://murga-linux.com/puppy/viewtopic. ... 548#901548 being closer to your LazyPuppy, in their foundations may require less 'adjustments'. To find out if a required library is missing, browse to the binary/executable's folder, open a terminal and type, code: ldd EXACT-NAME-OF-BINARY. You'll receive a report of both the libraries it found and those 'NOT FOUND'. Those 'not found' may be available via synaptic or apt-get. If they are not, rather than to download them via a web-browser and install them --which may break your system-- it would be preferable if you downloaded them and rebuild the SFS to include them.
But I suggest you do the following. Keep your present system. Install TrinityDog, or XenialDog --if your computer will run 64-bit OSes, DebianDog64 or XenialDog64-- and experiment with their SFS capabilities. It took RSH (AKA LazyPuppy) hundreds of hours to create his unique operating system. Don't expect any 'Dog' to duplicate that without a lot of work. As both LazyPuppy and 'Dogs' only need their own folders, you may find your best solution is to have both, booting into whichever best fills your then current needs.
mikesLr
Code: Select all
apt-get update
apt-get install peasywifiCode: Select all
build-essential automake autoconf libtool pkg-config libcurl4-openssl-dev intltool libxml2-dev libgtk2.0-dev libnotify-dev libglib2.0-dev libevent-dev checkinstall upx-ucl cmake linux-headers-4.9.0-3-686-pae python2.7 python3 libc6-dev yasm libgtk2.0-dev baconNot for me (as I said, I cannot test uefi) but for a newcomer.zagreb999 wrote:"@zagreb999
It is nice that you share your uefi boot setup for xenialdog, but I really think you should give much more detailed information how to make it work, otherwise it makes no sense, in my opinion.
(I cannot test uefi boot and don't know anything about it, btw)"
REGARDS, FRED
UEFI WORKS AS IN MX LINUX.
JUST, TO PUT IN THE SAME FOLDER WHERE IS CASPER
FOR XENIALDOG.
FOR FAT 32 FORMATED USB IN WINDOWS COMPUTERS 64 BIT
NO NEED ANY INSTALLATION. TO EXTRACT ISO AND PUT
ON USB, AND REBOOT. SECURE BOOT DISABLED.
IF YOU WISH , YOU CAN OPEN THE CONTENT AND SEE WHAT IS
INSIDE.
Thanks again, updated my post here:rcrsn51 wrote:@Fred: Here is a modification to Names. It resets the Ethernet profiles in /etc/pwf/ethernet.
I have also updated the Help screen.
Thanks zagreb!zagreb999 wrote:in Documents there are
"boot" and "efi"
.....
.....
Code: Select all
if [ -f /etc/pwf/firstrun.flg ]; then
SETDEVICENAMES
RECONNECT
rm /etc/pwf/firstrun.flg
fiIf only the wired interface would be recognized at boot (if, as you call, crypted) it would be nice already, so that it auto-connects anyway (just my wish, don't know if possible without negative side-effects).rcrsn51 wrote:@Fred: Excellent.
I thought about setting up a "first-run" mechanism that would pop up the Names dialog screen. That would be a quick way to enable cryptic names and make a network connection. Something like:Probably insert it at line 727.Code: Select all
if [ -f /etc/pwf/firstrun.flg ]; then SETDEVICENAMES RECONNECT rm /etc/pwf/firstrun.flg fi
But if the OS is going to switch back to conventional names on the next run, it would be self-defeating.
But if your system is 100% cryptic, this would be useful.
[Edit] I may add this to the Puppy version anyway. In Puppy, a reconnect is always needed to switch from dhcpcd to udhcpc.
Code: Select all
apt-get update
apt-get install realtek-wifi-drivers-k4.9.0-i386
i try it (monday)
