Just-Lighthouse64-801/802

For talk and support relating specifically to Puppy derivatives
Message
Author
Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

Just-Lighthouse64-801/802

#1 Post by Dry Falls »

App: JL64
Latest Version: 801B5 k4.17.12/k4.18.7
Homepage: just-lighthouse.000webhostapp.com

JL64-801 iso:Just-Lighthouse64-801B5.iso
md5sum: 545b44643fe3fe7f40e311b8a786cae3

Download Directory:
JL-802 Beta slackware64-current
JL-800 Experimental slackware64-current

Dual-hybrid iso & sfs files - Changes:
20180915 JL64-801B5 iso- slackware64-current package updates as of Sep14

20180901 JL64-801B4 delta patch - slackware64-current package updates as of Sep1

20180810 JL64-801B3 - slackware64-current package updates as of Aug 8; Discussion starts here

20180531 JL64-801B2 - slackware64-current package updates as of May 30; bug fixes.

20180526 JL64-801B1 - slackware64-current package updates; bug fixes. Considering this a beta version.

20180502 JL64-801 version upgrade - slackware64-current. Discussion starts here. Check sfs-update for packages.

20180208 JL64-706 updated to slackware64-current. glibc/gcc, etc

20180106 JL64-706 updated to slackware64-current. Discussion starts here. Check sfs-update for packages.

20171222 JL64-706 updated to slackware64-current. lots of bug fixes. Check sfs-update for packages.

20171114 JL64-704 updated to slackware64-current (gcc-720, glibc-2.26). Not yet Salix compatible (still at 14.2) but many packages will work. Consider this alpha quality.[/url][/b]
Last edited by Dry Falls on Fri 29 Mar 2019, 06:59, edited 10 times in total.

Gordie
Posts: 153
Joined: Tue 23 Aug 2016, 15:26
Location: Nolalu, Ontario, Canada

#2 Post by Gordie »

Why oh why would you use Slackware Current? It is as unstable as Hell most days. This is NOT equal to a rolling release

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#3 Post by Dry Falls »

see above:
Consider this alpha quality.
I'm practicing, ok? By the time 14.2 is obsolete and slackware issues the next stable release, I may have just figured this stuff out!

df

TyroBGinner
Posts: 236
Joined: Wed 30 Mar 2016, 20:18

#4 Post by TyroBGinner »

Though doing this seems like common knowledge, I can't install this pup. I removed the vmlinuz, initrd, and main sfs file from the iso and directed grub to find the files with the pdev1, psubdir, and pupsfs parameters. The boot process stops with the complaint that it can't find the main sfs. I also tried placing the files closer to the drive root so they could be more easily found. Does this situation require editing the initrd file? If so, can you briefly describe how to do this?

Thanks.....

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#5 Post by Dry Falls »

TyroBGinner wrote:Though doing this seems like common knowledge, I can't install this pup. I removed the vmlinuz, initrd, and main sfs file from the iso and directed grub to find the files with the pdev1, psubdir, and pupsfs parameters. The boot process stops with the complaint that it can't find the main sfs. I also tried placing the files closer to the drive root so they could be more easily found. Does this situation require editing the initrd file? If so, can you briefly describe how to do this?

Thanks.....
Looks like the kernel and initrd.xz loaded alright since you got the message "can't find the main sfs". The problem is either where you placed the main sfs (JL64-706.sfs) or in your added parameters. psubdir can only be one level down on the drive/partition (a top level folder), and pdev1 has to be in the form of "sda*", not hdd. You probably only need pmedia parameter if booting from a different device.

df

TyroBGinner
Posts: 236
Joined: Wed 30 Mar 2016, 20:18

What really happened...

#6 Post by TyroBGinner »

Thanks for the response, Dry Falls.

Before entering my first message here, I had tried placing the central files in a typical subdirectory such as sda3:/lin/jl. Then I tried placing them on the device root, namely, sda3:/ - neither method worked. I never used the archaic notation of "hdX" in any of these cases.

When the booting failed, and the output displayed the "dropping to /dev/console" message (or similar), I looked to see if the $PDEV1 and $PSUBDIR variables had been assigned, and they had not - they were simply blank. I then edited the init script to directly assign those variables to the correct values, and they still came up blank.

So, I put the whole "jl" subdirectory into the root of another partition, such that the three central files resided in sda7:/jl - and then the booting went smoothly. The only difference that I can see here is that sda3 was formatted to ntfs and sda7 was formatted to ext2. Perhaps this could be a source of trouble for others. It may be necessary to place at least some puppy distros onto linux or unix-esque filesystems rather than DOS/Windows filesystems.

Thanks for providing all the sfs files. Did you make any info available on what those programs do?

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

Re: What really happened...

#7 Post by Dry Falls »

TyroBGinner wrote:The only difference that I can see here is that sda3 was formatted to ntfs and sda7 was formatted to ext2. Perhaps this could be a source of trouble for others. It may be necessary to place at least some puppy distros onto linux or unix-esque filesystems rather than DOS/Windows filesystems.

Thanks for providing all the sfs files. Did you make any info available on what those programs do?
Yes, I wouldn't recommend putting lighthouse (or fatdog, for that matter) on anything other than ext3 or ext4. I've not had any luck with f2fs. As I recall, ext2 was pretty clunky. The base file and sfs files don't need to be with the kernel and initrd.xz (which contains the modules). They (the kernel package) are fine left on the boot partition, however it's formatted. In fact, if you use grub2, it's better if the base & sfs files are somewhere else entirely.

So far, only sfs-update has very brief descriptions of the various sfs addons.

glad to hear you got it to boot. Thanks for the interest.

df

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#8 Post by don570 »

Latest mtpaint compiled easily on JL64 706

mtpaint-JL64-3.49.13.pet
Size 322mb
https://drive.google.com/open?id=1_rGH3 ... aZpcgJqFb8


Foreign languages
mtpaint-JL64_NLS-3.49.13.pet
Size 178mb
https://drive.google.com/open?id=13KoNh ... aOZ9WX-dST

______________________________________________

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#9 Post by Dry Falls »

Thanks Don. The pet works great. But didn't you mean 322K and 178K? They're tiny little files considering what they do!

It's good to hear the devx worked out for you, but that one is still a bit buggy (ex., still some relic headers which could get in the way for some programs like ffmpeg) I'll be uploading new 704 and 706 iso's and devx soon.

df

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#10 Post by Dry Falls »

Just-Lighthouse64-706a2.iso uploaded.

considerable changes & fixes. new devx, docs, nls, etc. check sfs-update. Jives with Slackware640current as of Dec 21

df

slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

#11 Post by slavvo67 »

I've been in the Quirky world, lately but recalling just how great Lighthouse was/is, I'll be burning it onto a R/W dvd shortly.

Thanks Dry Falls!!

Slavvo67

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#12 Post by don570 »

I'm working on a simple countdown timer .. I'll test it on the new version.
_____________________________________________________

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

Issues!

#13 Post by Dry Falls »

A few issues have cropped up with the slackware-current upgrades.

ffmpeg > 3.3 broke parole, so I obligingly removed parole. Not really a big deal since mpv and audacious and pmusic did the trick. However, after all Zigbert's work fixing pmusic, now upgrading ffmpeg from 3.4.1-x86_64-1 to 3.4.1-x86_64-2 breaks pmusic. This upgrade also requires samba and gstreamer upgrades. I'm starting to get irritated with the whole samba/ffmpeg game. I'll not be upgrading them in the future unless they start to behave.

Also, I noticed raw cd images (iso's) are now being type-set as model/x.stl-binary (STL 3d model) instead of application-x-cd-image. Haven't been able to track down the problem, but it occurred between 11-30 and 12-09. Doesn't make sense. Here's a little work around (ROX_STL3d-mime.txz). If you work with stl3d modeling, this is probably not recommended! Also here's a purely cosmetic fix for mtpaint icons (mtpaint_mimeIcon.txz).

edit: icu/libical broke abiword. Rather than recompile it, here's a simple fix (copy into terminal):

Code: Select all

cd /usr/lib64

ln -s libicudata.so.56 libicudata.so.51
ln -s libicuuc.so.56 libicuuc.so.51
ln -s libicalvcal.so.3 libicalvcal.so.2
ln -s libicalss.so.3 libicalss.so.2
ln -s libical.so.3 libical.so.2
Attachments
mtpaint_mimeIcon.txz.gz
fake gz. rename & right click 'Install-txz'
(412 Bytes) Downloaded 386 times
ROX_STL3d-mime.txz.gz
fake gz. rename & right click 'Install-txz'
(14.64 KiB) Downloaded 359 times

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#14 Post by Dry Falls »

I noticed raw cd images (iso's) are now being type-set as model/x.stl-binary (STL 3d model) instead of application-x-cd-image. Haven't been able to track down the problem, but it occurred between 11-30 and 12-09. Doesn't make sense. Here's a little work around (ROX_STL3d-mime.txz). If you work with stl3d modeling, this is probably not recommended!
On the other hand this only seems to affect rox-filer, and probably a better solution is to set type manually in rox for each instance. In rox window, rightclick -> 'Set Type...'

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#15 Post by don570 »

I finished PTM timer.
http://murga-linux.com/puppy/viewtopic. ... 8&t=112410
_____________________________

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#16 Post by Dry Falls »

don570 wrote:I finished PTM timer.
http://murga-linux.com/puppy/viewtopic. ... 8&t=112410
_____________________________
This timer/alarm is Great! Thanks. It's actually just what I need. There's ptiming, pschedule, osmo and orage but I just get bogged down trying to navigate them. This one's for me! And the note! I often need reminded why I set the damn alarm in the first place. Seriously.

df

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#17 Post by don570 »

icewm updated
http://murga-linux.com/puppy/viewtopic. ... 6&t=112471
_________________________________

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

update

#18 Post by Dry Falls »

Thanks Don570. I'll look at that. Pretty much re-abandoned icewm after JL64-704, thinking it may be a bit redundant.

Slackware updates. Fixed Parole and pmusic (see note)

5_JL64-706.sfs (contains former media-lt)
Backgrounds-JL64.sfs (minor changes - not essential)
BaseFile-delta.tar.gz (contains JL64-706.sfs___JL64-706.sfs.delta) 56M
DOC_JL64-706.sfs
Devx-JL64_706.sfs
NLS_base-JL64_706.sfs
Parole-0.9.2-x86_64-JL64.sfs (renamed gstreamer addon with gst-libav from Arch Linux)
Xfce-4.12.1-1-x86_64.sfs (minor changes - not essential)
ffmpeg-3.4.1-x86_64-2.sfs (full package from slackware)
ffmpeg-3.4.1-x86_64-2_706.sfs (trimmed ffmpeg with samba libraries)
gtk-doc-reference_706.sfs
man_tools-14.2-5.sfs
mediacenter-12.sfs (minor changes - not essential)
minillvm-706.sfs (just the libraries)
python3-3.6.4-x86_64-1.sfs
samba-4.7.4-x86_64-2.sfs
xscreensaver-5.38-x86_64-JL64.sfs

note: changing Nothing from JL64-704, pmusic now needs samba, no matter which ffmpeg is used. Tried ffmpeg from arch linux which does not require samba, and pmusic will play sound files, but not web streams (kind of defeats its purpose). Likewise, parole now played anything I've thrown at it, but it hitches its giddy-up with web streams. Also has some problems getting around some commercial dvd encryption (as does xine). Admittedly, my dvd-player is warped. The all-round media player of choice is vlc for video and audacious for audio, both which as of yet have presented no problem.

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#19 Post by Dry Falls »

thanks again go to Don for pointing here (and thanks fatdog team!)
Attachments
drirc.gz
fake gz rename and drop into /etc
(11.75 KiB) Downloaded 263 times

Dry Falls
Posts: 616
Joined: Tue 16 Dec 2014, 23:37
Location: Upper Columbia

#20 Post by Dry Falls »

kernel 4.14.12 (k4.14.12.txz) uploaded to gdrive repo.

Seems to work pretty good and I might even say I'm impressed, but JL64 is still no match for my favoritest puppy since precise-5.71, which is ShibaInu. Whatever happened to Josejp?

Anyway, Install and run mkMariner-iso (in devx) to create a new iso with the new kernel and whatever sfs files you have loaded, or manually extract the txz (right click), open the archive and extract the contents to where you need them.

df

edit: not sure if the extra 20M kernel-modules size (a 30% increase!) is really worth the kernel upgrade. Personally, I'm sticking with k4.14.2.

edit2: wrong. The extra size is accounted by the huge firmware pkg in the modules. I've re-uploaded k4.14.12.txz with Radky's smaller firmware (which I've been using) from smokey01.com. initrd.xz is now 45M.

Post Reply