Puppy Linux Discussion Forum

Hi Dry Falls,

Just wanted to welcome you back into active play in the game.

Just noticed this WoofCE adventure and am looking to dive in.

Seems the history of Lighthouse had a seemingly beginning collaboration of 3 Contributors; namely @Tazoc (author), @01micko , and @jamesbond in the packaging of this with some fabulous reviews on its feature-set.

As I dive in @Dry Falls , what do you recommend to 'attach' the REPO such that appropriate matching apps+libs, will integrate properly? It appears from the filelists in the OP that it is its own app packaging. For example should I run the ISO, then add the DEVX, then ??? for REPO access before saving or should I ???

I will probably run the OS and use the Lighthouse ability for using QEMU testing that I do from time to time via the LH64 desktop.

Thanks in advance for guidance.

@Dry Falls :-

I'll echo t'other Mike. It IS good to see ya back, you old scalliwag!

Just Lighthouse "Mariner Edition" was the very first of this series I ever tried, going back around 7 years I would guess. Not sure if you'd taken the reins at this point, but it was gcmartin (Clarity as he is now; ignore his protestations to the contrary! ) who prompted me to give it an outing; first 64-bit Pup I'd ever tried.

This was the first time the infant version of my now standard "infocenter" had made an appearance on the desktop. I was really taken with gKrellM, and compiled it for every Pup in the kennels; in those days each Pup had its own partition, as you can see! Nowadays I use the one partition->many sub-directories approach.

I probably used it for around 6-8 months, by which time PhilB finally had Tahrpup64 up-and-running. This was good practice for the latter....and was also the first time I'd used my favourite Windoze photo-editor, MooiTech's PhotoScape, running under WINE, to design an entire desktop backdrop.

I know you don't post often, but for gawd's sake, don't drop off the radar. Your very occasional input was always welcome, y'know?

Mike.

I used Mariner-lighthouse for a while too. I'm glad someone is keeping it going.

Tazoc did a lot of good work.

Hello Dry Falls !
I can't download your iso without installing first an app on my pc, what's that ?
Amol

works fine for me

archive was down ealier so couldn't provide a link, you can get it here if you want

http://archive.org/download/Puppy_Linux ... .23%29.iso

Hello everyone !
I've succeeded to download it.
Waaooh ! There is a lot of thing in this distro.The job made in it is impressive !
Amol.

Booted the ISO file in a VM. Problem with it getting to desktop. Seems something is missing:

Edit: Manual start of desktop via "xorgwizard-auto" command

QEMU stanza for running Lighthouse in a VM:

qemu-system-x86_64 -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "Just-Lighthouse64 v805 via QEMU" -cdrom Just-Lighthouse64-805.iso

The beauty of your continuing effort on this project ... continues. It is fast and responsive.

Seems that this was, at one time, closely aligned with FATDOG. Is this still true?

If so, would this project get more attention if it was listed under the FATDOG sub-forum section?

Curious

Hello Clarity ! THANK YOU for this tip.
I 've succeeded to boot JL-805 only one time.The boot process is not like the other puppy distros ( It's remind me this of TinyCore Linux ).I've remarked a strange thing in this boot process concerning the use of my internal partition sda1 where as i use a usb key for JL-805.
Best regards,
Amol

Hi @Dry Falls

Additional information related to aboves I have provided: Not sure if you are aware, but booting the ISO file directly into a VM shows the issue that is not allowing the boot to proceed to desktop. Here's the messages just before it stops requiring a manual terminal command to get to desktop. Are you aware?

Boot Menu item selected was/is ...nosavefile (GRUB2 Menu option 3)

So far, this is a fully capable distro.

Thanks @Dry Falls for this long-standing distro. I enjoy seeing how it evolves. And thanks @Clarity for posting the qemu stanza that gets this iso starting on Fatdog 813. Btw, I recall that @stemsee posted a cross between JL64 and Fatdog. It was in the old forum, I can't find the link now.

@step

is this it?

http://archive.org/download/Puppy_Linux ... 64_602.iso

@step

edit

actually think it's this:

http://archive.org/details/Puppy_Linux_FatHouse64

Great @ally, your unrelenting archival work is a big help to this community.

Dry Falls wrote: Tue Feb 28, 2023 11:11 pm

Updated Mega. ...

Thanks

This may be a problem with my qemu build.

There are several v7 PETs available in the forum.

Request
Could your PET/version be upgraded and it added to your Repo?

Maybe in your next version.

Dry Falls wrote: Mon Feb 28, 2022 7:08 pm

TazOc's Lighthouse...

any...archived...links?

pup2023 wrote: Thu Jul 13, 2023 11:35 am

Dry Falls wrote: Mon Feb 28, 2022 7:08 pm

TazOc's Lighthouse...

any...archived...links?

https://archive.org/details/Puppy_Linux_Lighthouse64 is the final version I think, but there are dozens of builds on archive.org (thanks ally).

It's worth booting up and looking at. A lot of good design ideas.

https://archive.org/details/puppylinux? ... ghthouse64

you're welcome D

Dry Falls wrote: Wed May 29, 2024 6:36 am

It still incorporates pupmode 14 and 15 developed by TazOC and Q5sys

Can you describe how they work and how they differ from others?

Dry Falls wrote: Wed May 29, 2024 8:58 am

Hi Dimkr. Noautosave forces the event manager to keep all changes in pup_rw no matter what media lighthouse is booted from. The following may be overkill but...

Thanks, this makes perfect sense. I'm trying to reduce the number of boot options, PUPMODEs, etc' in my woof-CE fork. Currently it's only PUPMODE 5, 12 or 13 (without periodic saving - only at shutdown or on user request), and I'm looking for a clean way to implement shutdown without any save/no save prompts for users interested in an "immutable" but customized Puppy. I think I'm looking for something similar to pfix=noautosave.

What is the script in the ISO.zip for?

Just a comment: This new v900 is different from the old v900 (otherwise it would not have been presented to us).

But, it still has the same name as the old. Would it be prudent, in the future to name updates with a updated version number?

Reason: Some of us keep all ISO files in a single folder on our system. Same name updates 'overlay' the old version. Thus the ability to compare is lost.

Hope this is reasonable

P.S. If this comment is vague, I draw attention to FD which when a need to replace its older version, it releases with a newer version to avoid confusion. For example they released v900...then when updated, they released v901 as the update...and so on.

Just a comment.

Hi Dry Falls

Thank you for continuing this cool project. I used it a long time ago as 32 bit before that jerk with the ID10T error invented 64 bit.

I just hit my quota with Mega so I will wait to download the rest later.

Vektor

Hello @Dry Falls
I have 3 different versions of v900 from you. When reporting what do you recommend as how to differentiate when all are numbered v900?

Could a suffix addition be appropriate from you on these?

Curious