(old)Puppy Linux Discussion Forum

Ted Dog wrote:cool...

Ted Dog wrote:Does it contain multisession code or Apple filesystem support? Wondering I am working on another two 64 distros a iPuppy and FAsTDOG 64 630 which has a different methods of remastering and multisession saves and should be faster even if it does not have memory for auto expand in RAM.

Ted Dog wrote:multisession code also from fd64? there was a bug fix but I havent located code or did a difference check on source to see what was changed.. But I do not think ARCH even knows how puppylinux does multisession then the newer fatdog64 method... then my mixed old new method to remake multisession into a roll back and forward machine.. IE I want a rolling release style puppylinux as a result. Arch based puppylinux would be ideal base for a rolling puppy.
iPuppy base must be 185M or less to fit and quick boot directly from spare space in EFI boot partition. I have done it before but both Slacko and Fatdog64 have past that mark....

menuentry "Grub2" {
	icon /EFI/boot/icons/os_linux.icns
	loader /EFI/grub2/grub2.efi
}

ally wrote:mirrored here: http://archive.org/details/Puppy_Linux_AlphaT64

tigs wrote:... cannt seem to get the connman to connect to wifi.

will play with it a bit more, more on how the savefile works. I really like the puppy way where you can choose whether to save it or not, when to save it, the feature of the puppysaveconfig 2.2.6 by sinobar.

Ted Dog wrote:Fatdog64 630 also now fully supports Bluray to the same but even better speed wise as DVD. both share same scripts its just a matter of what media you placed in drive. I have a bluRay burner that also burns DVD. The code changes I worked on and others polished and strengthened are In text scripts with in fatdog64 . What has changed was a burning limit somewhere in one or two compiled executables. I do not have the source of those changes.. but will need to or someone with those changes need to compile 32bit and or ARM.
I knew of the code limit and was unable to follow the code easily to find where limit existed if it was even there it may have be a integer size with a hi bit as Negitive logic error. It my only be a compiler flag for defualt integer size.. I do not know.. I did not know anyone else was looking into the bug. I found out it was fixed by happy accident. Or better laziness, I knew it sbould throw an error and not save a session so I did not eject disc to skip a session when rebooting..

gcmartin wrote:

tigs wrote:... cannt seem to get the connman to connect to wifi.

will play with it a bit more, more on how the savefile works. I really like the puppy way where you can choose whether to save it or not, when to save it, the feature of the puppysaveconfig 2.2.6 by sinobar.

I am assuming you are using something akin to FATDOG's new packaging and boot logic. Asuming that this resembles the same path to desktop, you will need to open the Control Panel to the Service Manager where there is a setting "wl" which may be the cause. I've had to do this on each of my Laptops to get wireless working with the chipset(s).

This may not apply. I have not had a chance to boot this 64bit implementation, yet.

Hope this helps.

labbe5 wrote:My hope is that AlphaOS is known at large in the Puppy community, and that developers get inspired by it. By the look of it, AlphaOS already has a few developers actively working on it.

bark_bark_bark wrote:

labbe5 wrote:My hope is that AlphaOS is known at large in the Puppy community, and that developers get inspired by it. By the look of it, AlphaOS already has a few developers actively working on it.

The community knows about it, it was just that the developer simargl was just not a very friendly person.