XenialDog (Ubuntu 16.04 'Xenial Xerus' LTS, 32-bit)

[mcewanw]

As for the github DD organization repositories (with exception of XenialDog and doglinux-website), I will not add or delete anything (I think most that's there is valuable, also the older versions), I see it as an archive (at least at this point of time), but if any owner or team member has the aspiration to make improvements, new versions or whatever, I'm absolutely fine with that (and, who knows, I might feel inspired to help :) ).

Hopefully this can be called an agreement, and can we all leave the DD conflicts behind forever.

The only thing is, Fred, I hope you will respect Toni's wish that any future work on DebianDog itself, by anyone, should not include any non-free components (and certainly not on my DD organization github site) since that was indeed clearly his original concept for it. As for the chosen open-source licenses, I know you never meant to omit these from any scripts, but when you have time one day (no hurry from me) I'd be grateful if you could fix that, just so everything is correct in that sense. I feel that should be the end of any conflict.

The composition of XenialDog project and doglinux sites, on the other hand, are entirely up to you, of course, within the limits of github site open-source rules. Whether you decide it is better to later move all these to a github site registered by yourself is something you might want to consider, because otherwise, as you said, I also don't know a way for you to create any new repository without asking me to do that for you (which I would do of course).

More generally, I am fine with the existing site continuing to be used by Toni or yourself with repository admin rights, or frozen as a useful archive (which might be better?).

In that regard, should Toni ever want admin rights to any existing DebianDog repository, I trust you understand I would not hesitate to give that.

Yes, it's nice when the sun shines backi.

William

[mcewanw]

Actually, I see that Toni is no longer claiming ownership of DebianDog project so anyone taking it over would become free to future develop it any way they like. So that conflict is resolved anyway - so forget what I said. The community will decide later, if anyone (which could be Toni of course) takes the DebianDog project up again. Let's all just agree to be careful to get the licenses correct in future - it was a good point.

William

[fredx181]

The only thing is, Fred, I hope you will respect Toni's wish that any future work on DebianDog itself, by anyone, should not include any non-free components (and certainly not on my DD organization github site) since that was indeed clearly his original concept for it.

I will never do anything anymore on my own with DebianDog, but -as I said- maybe, maybe try to help if asked and/or appropriate.

As for the chosen open-source licenses, I know you never meant to omit these from any scripts, but when you have time one day (no hurry from me) I'd be grateful if you could fix that, just so everything is correct in that sense.

Am I the only one that can fix it? (don't know in detail what you mean by that)
Of course I'm willing to co-operate but If that means a whole lot of work, e.g. change most scripts, make all new ISO's, I don't feel for that.
(now please don't tell me that the conflict stays in case I won't do all that work, I'm dead tired)

I also don't know a way for you to create any new repository without asking me to do that for you (which I would do of course)

That's a pity, probably can be done only if you would give me co-ownership.
Well maybe you will later, when you feel like trusting me more again (I know i've placed a bomb in that Review of DebianDog thread, felt at that time as the only way out).

Edit:

so forget what I said

You said a lot but I guess you mean about fixing licences?

Fred

[mcewanw]

As for the chosen open-source licenses, I know you never meant to omit these from any scripts, but when you have time one day (no hurry from me) I'd be grateful if you could fix that, just so everything is correct in that sense.

Am I the only one that can fix it? (don't know in detail what you mean by that)
Of course I'm willing to co-operate but If that means a whole lot of work, e.g. change most scripts, make all new ISO's, I don't feel for that.
(now please don't tell me that the conflict stays in case I won't do all that work, I'm dead tired)

I was only meaning to make sure there is a set of your scripts for future isos and work, licenced the way you want them to be licensed. Anything else would be too much work and unreasonable IMO. I guess we consider the previous isos obsolete alpha or beta releases, so not guaranteed fit for purpose.

You can put whatever licence you like on that set of scripts (which could remain none at all), of course, since they are yours. However, I doubt they would be able/likely to be used in future work by others if the license you assigned isn't an appropriate open-source licence. (EDIT: Like I said, there is no hurry as far as I am concerned, and whether you do so or not is entirely up to you). Since Toni has given up ownership anyway there is no more conflict as far as I understand things, but would be good to protect the future.

If no way can be found for you to be able to make new repositories without my intervention you may be best to start up new github repository for new work. What I said about being willing to make new repositories when and if requested, however, stands.

Cheers, William

[mcewanw]

I have only made a quick check
https://help.github.com/articles/reposi ... positories

and that link starts off with:

By default, all organization members can create repositories for the organization. If you choose, you can restrict repository creation permissions to organization owners only.

So, it may then be that all members of the organization can create repositories; if so you don't need ownership permission to the organization site itself.

I don't understand yet - maybe I need to make you team maintainers or something (but my first reading suggests that simply being Members allows you to create repositories and having Admin permissions allows you to do most things). See here:

https://help.github.com/articles/reposi ... anization/

Will check further later.

EDIT: Just try it Fred, I think you have full permissions to create repositories and then be admin of what you create, which means you should also be able to delete them. Same with Toni, actually, in terms of creating new repositories and administering them. I've also created a new team called "Maintainers" and made Toni and yourself "team maintainers" of that with admin rights to the DebianDog named repositories Wheezy, Sid, SFSget, Stretch, and Jessie. My understanding, however, is that you already had all the repository creation permissions you need without that though, but the Maintainers team should give better fine-grained permission control if decision is made to not allow all invited Members to have repository-creation permissions.

William

[fredx181]

I was only meaning to make sure there is a set of your scripts for future isos and work, licenced the way you want them to be licensed. Anything else would be too much work and unreasonable IMO. I guess we consider the previous isos obsolete alpha or beta releases, so not guaranteed fit for purpose.

Ah.. relief I will probably do later and may ask you for advice (later, not now)

EDIT: Just try it Fred, I think you have full permissions to create repositories and then be admin of what you create, which means you should also be able to delete them.

Still not, (see pic)
It's in fact a strange situation, I have full permissions to the DD repositories (which I really don't want or need anymore) and don't have the single permission I want.

Oh well, as I said earlier, there's no hurry at all, thanks for trying anyway.
EDIT:
I take that back, indeed there's no hurry, but truly I think it's unfair, undeserved, I might as well leave the organization, all the fun is gone.

Fred

[mcewanw]

Hello Toni,

If you are reading this do you mind doing me a favour and seeing if you find yourself able to create a new repository on DebianDog github site, Fred apparently is unable to yet all the documentation I have checked suggests any member of the organization at all should be able to (no matter what other permissions they have been given).

Please both check the github documentation for yourself also to see if you can see what the problem might be.

William

EDIT: I will invite myself as a normal member from a test github account and check/fix the creation of repositories by non site owner and report back thereafter.

[saintless]

Hello Toni,

If you are reading this do you mind doing me a favour and seeing if you find yourself able to create a new repository on DebianDog github site...

Hi William.
I would half an hour ago but unfortunately I can't help with this now.
I left the organisation again. The reason this time - noone will try to make this community project as long as I and Fred are members there. And it is clear there is no way I and him to work together again on any project.

Just to confirm your words - I don't mind anyone to take over the project development (including Fred) and develop it the way he likes (including non-free packages and unlicensed scripts included).

DebianDog project deserves better than me or Fred.

All the best.

Toni

[mcewanw]

Thanks Toni,

It is okay, I have now created a 'test' ordinary member and modified permissions such that I find I was able to give them permissions to create new repositories in DebianDog organization site. All it needed was some time and a little patience to help me find the simple fix.

Fred, please try again. It should work now. If by some magic it doesn't let me know - easiest way then to fix it would simply be to temporarily delete your membership and re-invite. It certainly works now that someone who is not the 'owner' of the site can create repositories, but there was an error before.

William

EDIT: Any further problems and I'll reply tomorrow. It is late here and real work tomorrow.

EDIT2: By the way, I will not be further involved in development work for these projects either. Currently they are on my registered github account, so I do have a few background admin tasks I have to perform - but these are insignificant, so anyone using these repositories or creating new ones should for all extents and purposes consider me not there. Should anyone want to continue the projects or join the existing developments by Fred you just lneed to sign up for a github account, let me know the user name, and you will receive the invitation to be a member of the team. What you then do, is entirely between yourself and the other members (apart from myself). If no one wants to continue on that site, as I said, I will leave it untouched as an archive if github so allows.

[fredx181]

Hi solicitor William,

Yes, works now, I can create new repository now. Appriciated the effort you've done.
Last thing I ask you:
Can you invite Toni again?
But don't tell him please that I invited you to invite him
(previous sentence is another humurous attempt from me, people knowing me well say that I have sense of humor, but sometimes a bit weird )
But I'm dead serious about you inviting Toni !! (I would like to do but can't because I'm member)
Also tell him that I will personnally sh**t him if he don't accept or ever leave again.

Now Peace, Quiet

Fred

[backi]

Also tell him that I will personnally sh**t him if he don't accept or ever leave again

Yes that`s right !!!..... because !.................Happiness is a warm Gun ...

https://vimeo.com/32313020

[mikeslr]

Dear Fred,

I am indeed saddened by your decision. But it is understandable. Linux projects exist because the people who work on them love what they are doing. When that love is gone --for whatever reason-- so is the reason for engaging in that mental state required for the work; and doing the work not only becomes drudgery, but a reminder of what once was and now is gone.

Yet, I can not help but grieve for the lost potential of this project. Together, in two years, you and Toni devised a light-weight, truly portable, operating system with the power of apt and synaptic to easily and accurately expand from its base to whatever debian or Ubuntu repositories had to offer. For "passengers" like me, it could only get better. Except, it won't.

Perhaps in time you may again find the passion needed to re-engage, or to engage in a similar project. Humans are odd creatures and the worlds they create do not evolve with mathematical precision. Yesterday's bitter enemies become today's respected trading partners.

But, if that is not the case, can you find the sufficient stamina to leave those who might desire to carry on with sufficient information to do so.

As I understand it --and always assume I may be wrong-- your recipe for creating operating systems:

1, Starts with a netboot ISO; then
2. "Remastering" initrd to support porteus boot. How is this accomplished?

I can only wish you peace and luck in your future efforts.

mikesLr

[rufwoof]

Hi Mike.

After all the issues with DD and being left high-and-dry, I transitioned over to just using a frugal boot of pure Debian. Basically created a ext3 partition, installed grub4dos to that and then copied the /live folder from Debian LiveCD to that partition.

With live-boot commands (similar for ubuntu's manual) http://manpages.ubuntu.com/manpages/pre ... oot.7.html I allocated that same partition a 'persistence' label so it became the save space as well (partition based save rather than a save file or save folder). With a single imported/modified script based on save2flash, that could then be booted and have changes optionally saved. Loading sfs's is also possible.

I took that a stage further and extracted all of the main filesystem.squashfs to the save partition, so the main sfs was in effect redundant (I created a empty version of the sfs purely for booting purposes). With everything in the save space that is also the primary partition it means I can also boot as though a full install, which I do only to update the kernel as and when new kernels are released.

Given the ease of access and extent of the Debian repository I've dropped using sfs's now and just apt-get install .... to install whatever I need that's not already installed, and just don't bother save the session.

None of the drama, works really well, great stability, security updates comes through in a timely manner, extensive repository and runs frugally. Best of both (Debian and Puppy) worlds as far as I'm concerned.

Getting used to not running as root by default was a bit awkward at first, but I added a right click context option to the filemanager to open a sub-folder as a root filemanager and have got totally used to that now. Along with running su to switch to root in a terminal window if so desired. Kept forgetting to to that at first, now its second nature.

As part of that transition I did go through various desktop choices, Gnome, KDE ... etc, but finally opted for LXDE. Similar to most pup's, but I prefer my menu bar at the top of screen (which pup's can also do). I've also transitioned over to using systemD boot which personally I've found works great despite many seeming to have a intense dislike.

Still light enough to fully load into ram at startup if you so desire (on a moderately newish machine), but I personally don't bother with that. What you gain is speed once its up and running is lost in slower initial startup (once a program has been loaded once anyway it tends to remain in cache so its quicker to start the second time).

I've sym linked a bottom layer folder in to my home directory, so that any docs/data want saved during a session simply uses that folder. I also have the likes of osmo calendar/diary set to store in that folder as well so changes are also preserved.

The modified save2flash script that I called flush2disk to distinguish a difference looks like

Code: Select all

#!/bin/bash
#
#2007 Lesser GPL licence v2 (http://www.fsf.org/licensing/licenses/lgpl.html)
#Barry Kauler www.puppylinux.com
#Edited for 'porteus-boot' on Debiandog for the "save on exit" boot option, by fredx181
#2016-02-26 Change; Line 89 "--remove-destination" instead of "-f", workaround possible crashing when 
#              copying files from upgraded libc6
#2016-07-19 fredx181 make save 'on demand' (to directory) work also with live-boot (originally idea from
#              Toni (saintless) https://github.com/MintPup/DebianDog-Wheezy/commit/9d510cd0189be4bdfe8ead97 ).
#2016-07-22 fredx181 parse location of live folder more exact (works now on DebianDog also)
#2016-07-29 Rufwoof - renamed to avoid confusion from save2flash to flush2disk and changed to specifically
#              run on persistence persistence-read-only pure Debian Live CD frugal
#2016-07-30 Rufwoof changed the BASE grep to pick up just the first line (partition) [added -m 1 parameter]
#2016-08-08 fredx181 changed: do the copying by 'rsync' instead of 'cp'
#              rsync does a better job, will skip copying files that are earlier copied to BASE by this script,
#              so much faster then, also it will 'flush' the memory space (tmpfs) in SNAP to (almost) how it was
#              at startup (see last code block). 
#2016-10-05 Rufwoof - changed to launch find as early as possible as for first run that slows things down
#              Also added spinner that's shown whilst waitign for that pre-find to finish
################################################################################################################

spinner()
{
    local pid=$1
    local delay=0.25
    local spinstr='|/-\'
    while [ "$(ps a | awk '{print $1}' | grep $pid)" ]; do
        local temp=${spinstr#?}
        printf " [%c]  " "$spinstr"
        local spinstr=$temp${spinstr%"$temp"}
        sleep $delay
        printf "\b\b\b\b\b\b"
    done
    printf "    \b\b\b\b"
}


if [ "`whoami`" != "root" ]; then
	exec sudo ${0}
fi


export LANG=C #110206 Dougal: I **think** this should not cause problems with filenames
PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R7/bin"


# Debian LiveCD defaults to use a partition with a label of persistence or a partition
# with a label that matches the perisistence-label= kernel boot parameter (menu.lst)
LABEL=`cat /proc/cmdline | grep persistence-label`
if [ -z "$LABEL" ]; then
 	LABEL="persistence"
else
 	LABEL=`cat /proc/cmdline | awk 'BEGIN{FS="persistence-label="} {print $2}' | awk 'BEGIN{FS=" "} {print $1}'`
fi
BASE=`mount -l | grep "\[$LABEL\]" | grep -m 1 /lib/live/mount/persistence | awk 'BEGIN{FS=" "} {print $3}'`
if [ -z "$BASE" ]; then
 	echo -----------------------------------------------------
 	echo Only valid when booted a Read Only session and when 
 	echo persistence-label boot parameter specified - exiting
 	echo -----------------------------------------------------
 	sleep 4
 	exit
fi


# Remount the 'home' partition read-write, otherwise we can't copy the changes
mount -o remount,rw $BASE 2> /dev/null


# help speed up find by pre-running as early as possible
find $BASE/. >/dev/null &
PID=$!      # record pid of background find


dialog --backtitle "Are you sure you want to flush all changes to disk?" --yesno " Save " 5 20
if test $? -ne 0
then
	exit
fi
clear


#dialog --backtitle "Should I leave existing network and graphics values?" --yesno " Save " 5 20
#if test $? -ne 0
#then
#	rm -f /etc/udev/rules.d/70-persistent*
#	rm -f /home/user/.config/autostart/LXRandR*
#	rm -f /etc/X11/xorg.conf
#fi
#clear


# fredx181 mod, create variable for list containing files to save (to be used further below).
FILESAVELIST="/tmp/filesave$RANDOM"


# By default overlay is mounted twice (in case no persistence), unmounting it, sort of 'releases' it, not sure why but it works ;)
# On DebianDog it's different, but doing the below does not harm  
umount /lib/live/mount/overlay 2> /dev/null


# Rufwoof append root to path
SNAP="/lib/live/mount/overlay/root/"
if [ ! -d /lib/live/mount/overlay/root ]
then
	echo "Looks like you're running a continual save session"
 	echo "Invalid operation. Exiting"
 	sleep 5
 	exit 
fi


# create BASE directory if not exist
mkdir $BASE 2> /dev/null
cd $SNAP || exit 1
echo "Merging $SNAP onto $BASE..."
if [ -f /mnt/live/tmp/modules ]; then
 	SFSPoints=$( ls -d -1 /mnt/live/memory/images/* |sort -u ) #110206 Dougal: get a list of the sfs mountpoints
else
 	# live-boot v3 or v4
 	SFSPoints=$( ls -d -1 /lib/live/mount/rootfs/* |sort -u ) #110206 Dougal: get a list of the sfs mountpoints
fi


# Wait for early launched find to finish, showing a spinner whilst waiting
echo -n "Scanning ..."
spinner ${PID}
#wait $PID # wait until background updatedb finishes
echo
echo "Updating ..."


#Handle Whiteouts...
find . -mount \( -regex '.*/\.wh\.[^/]*' -type f \) | sed -e 's/\.\///;s/\.wh\.//' |
while read N
do
 	BN="`basename "$N"`"
 	DN="`dirname "$N"`"
 	[ "$BN" = ".wh.aufs" ] && continue #w003 aufs has file .wh..wh.aufs in /initrd/pup_rw.
 	#[ "$DN" = "." ] && continue
 	#110212 unionfs and early aufs: '.wh.__dir_opaque' marks ignore all contents in lower layers...
 	if [ "$BN" = "__dir_opaque" ];then #w003
  		#'.wh.__dir_opaque' marks ignore all contents in lower layers...
  		rm -rf "${BASE}/${DN}" 2>/dev/null #wipe anything in save layer. 110212 delete entire dir.
  		mkdir -p "${BASE}/${DN}" #jemimah: files sometimes mysteriously reappear if you don't delete and recreate the directory, aufs bug? 111229 rerwin: need -p, may have to create parent dir.
  		#also need to save the whiteout file to block all lower layers (may be readonly)...
  		touch "${BASE}/${DN}/.wh.__dir_opaque" 2>/dev/null
  		rm -f "$SNAP/$DN/.wh.__dir_opaque" #should force aufs layer "reval".
  		continue
 	fi
 	#110212 recent aufs: .wh.__dir_opaque name changed to .wh..wh..opq ...
 	if [ "$BN" = ".wh..opq" ] ; then
  		rm -rf "${BASE}/${DN}" 2>/dev/null  #wipe anything in save layer.
  		mkdir -p "${BASE}/${DN}" #jemimah: files sometimes mysteriously reappear if you don't delete and recreate the directory, aufs bug? 111229 rerwin: need -p, may have to create parent dir.
  		#also need to save the whiteout file to block all lower layers (may be readonly)...
  		touch "${BASE}/${DN}/.wh..wh..opq" 2>/dev/null 
  		rm -f "$SNAP/$DN/.wh..wh..opq"  #should force aufs layer "reval".
  		continue
 	fi
 	#comes in here with the '.wh.' prefix stripped off, leaving actual filename...
 	rm -rf "$BASE/$N"
 	#if file exists on a lower layer, have to save the whiteout file...
 	#110206 Dougal: speedup and refine the search...
 	for P in $SFSPoints
 	do
   		if [ -e "$P/$N" ] ; then
     			[ ! -d "${BASE}/${DN}" ] && mkdir -p "${BASE}/${DN}"
     			touch "${BASE}/${DN}/.wh.${BN}"
     			break
   		fi
 	done #110206 End Dougal.
done


#Directories... v409 remove '^var'. w003 remove aufs .wh. dirs.
#w003 /dev/.udev also needs to be screened out... 100820 added var/tmp #110222 shinobar: remove all /dev
find . -mount -type d | busybox tail +2 | sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^root/tmp|^\.wh\.|/\.wh\.|^dev/|^run|^var/run/udev|^run/udev|^var/tmp|^etc/blkid-cache' |
#110224 BK revert, leave save of /dev in for now, just take out some subdirs... 110503 added dev/snd
#find . -mount -type d | busybox tail +2 | sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^root/tmp|^\.wh\.|/\.wh\.|^dev/\.|^dev/fd|^dev/pts|^dev/shm|^dev/snd|^var/tmp' |
while read N
do
 	mkdir -p "$BASE/$N"
 	# I think nathan advised this, to handle non-root user:
 	chmod "$BASE/$N" --reference="$N"
 	OWNER="`stat --format=%U "$N"`"
 	chown $OWNER "$BASE/$N"
 	GRP="`stat --format=%G "$N"`"
 	chgrp $GRP "$BASE/$N"
 	touch "$BASE/$N" --reference="$N"
done


#Copy Files... v409 remove '^var'. w003 screen out some /dev files. 100222 shinobar: more exclusions. 100422 added ^root/ftpd. 100429 modify 'trash' exclusion. 100820 added var/tmp #110222 shinobar: remove all /dev
find . -mount -not \( -regex '.*/\.wh\.[^/]*' -type f \) -not -type d |  sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^pup_|^zdrv_|^root/tmp|_zdrv_|^dev/|^\.wh\.|^run|^var/run/udev|^run/udev|^root/ftpd|^var/tmp' | grep -v -E -i '\.thumbnails|\.trash|trash/|^etc/blkid-cache|\.part$'  |
#110224 BK: revert, leave save of /dev in for now... 120103 rerwin: add .XLOADED
#find . -mount -not \( -regex '.*/\.wh\.[^/]*' -type f \) -not -type d |  sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^run|^pup_|^zdrv_|^root/tmp|_zdrv_|^dev/\.|^dev/fd|^dev/pts|^dev/shm|^\.wh\.|^var/run|^root/ftpd|^var/tmp|\.XLOADED$' | grep -v -E -i '\.thumbnails|\.trash|trash/|\.part$'  |
while read N
do
 	[ -L "$BASE/$N" ] && rm -f "$BASE/$N"
 	# Finally, copy files unconditionally.
 	# fredx181 mod, no, don't use 'cp' just create filelist (for to save) here and run rsync later. 
 	#cp -a --remove-destination "$N" "$BASE/$N"
 	echo "$N" >> "$FILESAVELIST"
 	BN="`basename "$N"`" #111229 rerwin: bugfix for jemimah code (110212).
 	DN="`dirname "$N"`" #111229  "
 	[ -e "$BASE/$DN/.wh.${BN}" ] && rm "$BASE/$DN/.wh.${BN}" #110212 jemimah bugfix - I/O errors if you don't do this
done


# fredx181 mod, rsync copy from $FILESAVELIST
[ -f "$FILESAVELIST" ] && rsync -a --files-from=$FILESAVELIST "$SNAP" "$BASE"


# Remove files, corresponding with .wh files, from zchanges.dir
# Taken from 'cleanup' script included in the official Porteus initrd.xz 
MNAME="$BASE"; NAME="basename "$MNAME""
find $MNAME -name ".wh.*" 2>/dev/null | while IFS= read -r NAME; do wh=`echo "$NAME" | sed -e 's^$MNAME^^g' -e 's/.wh.//g'`; test -e "$wh" && rm -rf "$NAME"; done


# fredx181 mod, remount BASE and remove the just copied files from SNAP. 
if [ -f "$FILESAVELIST" ]; then
 	# remount BASE 
 	mount -no remount,add:1:"$BASE"=ro+wh aufs /
 	REMOVE=$(echo $(cat "$FILESAVELIST" | grep -v '\->'))
 	cd "$SNAP"
 	# remove files from SNAP that had just been copied to BASE 
 	rm -fr $REMOVE
 	rm -f "$FILESAVELIST"
else
 	echo "No changes found, nothing to do!"
fi

sync &
echo Done
sleep 1

exit 0

###END###

My menu.lst looks like

Code: Select all

# menu.lst
color white/blue black/cyan white/black cyan/black
timeout 2
default 1

title Debian FULL *** USE THIS TO UPGRADE KERNEL *** Install RW filesys must be extracted (/boot/grub/menu.lst)
  find --set-root /debian-usb
  configfile /boot/grub/menu.lst
  commandline

title 0 Debian Jessie Frugal RO only saves if run flush2disk
find --set-root /live/frugalboot
kernel /vmlinuz boot=live timezone=Europe/London xorg-resolution=1280x768 config nofastboot persistence persistence-read-only persistence-label=persistence quickreboot noprompt showmounts live-media-path=/live/ config rw fsck.mode=auto fsck.repair=preen
initrd /initrd.img

The first boot option is for as though fully installed bootup, it chains to the standard debian bootup menu. The second is the default choice i.e. frugal that I most often boot (read only, with optional save if so desired via flush2disk (save2flash) i.e. I tend to keep the system factory-fresh, and only use the full boot (read/write) to apply updates before booting back frugally again (sometimes for small updates I will apply those in the frugal session before running a save (flush2disk)).

[mcewanw]

Last thing I ask you:

I have now done that.

Cheers,

William

All things are possible of course; far bigger wounds than these have healed and sometimes wake up calls end up forging stronger bonds not weaker ones. Takes time and being at retirement age now (but still young and active) time and enjoying it becomes the main importance.

[spandey]

Hi rufwoof,
Will you be kind enough to create a separate thread for the steps you have done so that passengers like us can also benefit from this wonderful creation?
Thanks a lot in advance.

[saintless]

Hi Fred.

I will not accept the invitation from William because my idea about DebianDog is still valid. If something is non-free or without license (which is the same) I don't want to have any part of it. Even working on the same github page where non-free license isn't respected.
I care more for the developers wishes and much less for the passengers wishes.

I understand the huge efforts to build and upload all newer iso images and it isn't acceptable for you to rebuild everything. And you don't have to. My idea is mine and your idea is different.

Now Peace, Quiet

Yes.

Toni

[fredx181]

Dear Fred,

I am indeed saddened by your decision. But it is understandable. Linux projects exist because the people who work on them love what they are doing. When that love is gone --for whatever reason-- so is the reason for engaging in that mental state required for the work; and doing the work not only becomes drudgery, but a reminder of what once was and now is gone.

Yet, I can not help but grieve for the lost potential of this project. Together, in two years, you and Toni devised a light-weight, truly portable, operating system with the power of apt and synaptic to easily and accurately expand from its base to whatever debian or Ubuntu repositories had to offer. For "passengers" like me, it could only get better. Except, it won't.

Perhaps in time you may again find the passion needed to re-engage, or to engage in a similar project. Humans are odd creatures and the worlds they create do not evolve with mathematical precision. Yesterday's bitter enemies become today's respected trading partners.

But, if that is not the case, can you find the sufficient stamina to leave those who might desire to carry on with sufficient information to do so.

As I understand it --and always assume I may be wrong-- your recipe for creating operating systems:

1, Starts with a netboot ISO; then
2. "Remastering" initrd to support porteus boot. How is this accomplished?

I can only wish you peace and luck in your future efforts.

mikesLr

Thanks for your kind reply Mike.

As for your question: "Remastering" initrd to support porteus boot. How is this accomplished?"
I can't answer that in a short way, I better write in the How-to section (but at a much later point in time, presumably) is that OK?

Fred

[dancytron]

Dear Fred,

I am indeed saddened by your decision. But it is understandable. Linux projects exist because the people who work on them love what they are doing. When that love is gone --for whatever reason-- so is the reason for engaging in that mental state required for the work; and doing the work not only becomes drudgery, but a reminder of what once was and now is gone.

Yet, I can not help but grieve for the lost potential of this project. Together, in two years, you and Toni devised a light-weight, truly portable, operating system with the power of apt and synaptic to easily and accurately expand from its base to whatever debian or Ubuntu repositories had to offer. For "passengers" like me, it could only get better. Except, it won't.

Perhaps in time you may again find the passion needed to re-engage, or to engage in a similar project. Humans are odd creatures and the worlds they create do not evolve with mathematical precision. Yesterday's bitter enemies become today's respected trading partners.

But, if that is not the case, can you find the sufficient stamina to leave those who might desire to carry on with sufficient information to do so.

As I understand it --and always assume I may be wrong-- your recipe for creating operating systems:

1, Starts with a netboot ISO; then
2. "Remastering" initrd to support porteus boot. How is this accomplished?

I can only wish you peace and luck in your future efforts.

mikesLr

Thanks for your kind reply Mike.

As for your question: "Remastering" initrd to support porteus boot. How is this accomplished?"
I can't answer that in a short way, I better write in the How-to section (but at a much later point in time, presumably) is that OK?

Fred

Take your time Fred, but I think "How To" is an excellent idea and will be of great value to a lot of people.

[mikeslr]

Hi Fred,

dancytron beat me to the answer. No hurry. You take care of yourself.

mikesLr

[rufwoof]

I transitioned over from Porteus to systemD/debian initrd some months back (I run Debian) and haven't looked back since. You can still link your own modules/code into that if you so desire, however having the single centrally managed (systemD) works well IMO. More eyes all looking/maintaining the same thing rather than lots of independent/different versions. All part of the Debian rock solid stability.

A single additional script similar to save2flash, all the rest being core Debian, but with many Puppy like qualities (sfs's, load to ram if desired, save on demand otherwise changes lost ...etc.) works great. Best of both worlds.