Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 21 Jul 2018, 04:10
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
Just-Lighthouse64-801
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 3 [38 Posts]   Goto page: 1, 2, 3 Next
Author Message
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Wed 15 Nov 2017, 02:30    Post subject:  Just-Lighthouse64-801
Subject description: slackware64-current
 

App: JL64
Latest Version: 801B2 k4.16.8
Homepage: just-lighthouse.000webhostapp.com

JL64-801 iso: Just-Lighthouse64-801B2.iso
md5sum: a80d7f22b354f3cc83ef5ccaa186f527

Download Directory:
JL-800 Experimental slackware64-current

Dual-hybrid iso & sfs files - Changes:
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]

Last edited by Dry Falls on Thu 31 May 2018, 23:53; edited 6 times in total
Back to top
View user's profile Send private message 
Gordie

Joined: 23 Aug 2016
Posts: 120

PostPosted: Wed 15 Nov 2017, 12:40    Post subject:  

Why oh why would you use Slackware Current? It is as unstable as Hell most days. This is NOT equal to a rolling release
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Wed 15 Nov 2017, 13:13    Post subject:  

see above:
Quote:
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
Back to top
View user's profile Send private message 
TyroBGinner

Joined: 30 Mar 2016
Posts: 218

PostPosted: Sat 25 Nov 2017, 19:32    Post subject:  

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.....
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Mon 27 Nov 2017, 17:53    Post subject:  

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
Back to top
View user's profile Send private message 
TyroBGinner

Joined: 30 Mar 2016
Posts: 218

PostPosted: Tue 28 Nov 2017, 19:41    Post subject: What really happened...  

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?
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Wed 29 Nov 2017, 10:32    Post subject: Re: What really happened...  

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
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5088
Location: Ontario

PostPosted: Thu 21 Dec 2017, 19:04    Post subject:  

Latest mtpaint compiled easily on JL64 706

mtpaint-JL64-3.49.13.pet
Size 322mb
https://drive.google.com/open?id=1_rGH3E-q3Plqn2Y-6mHdezaZpcgJqFb8


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

______________________________________________
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Fri 22 Dec 2017, 12:11    Post subject:  

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
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Sat 23 Dec 2017, 10:50    Post subject:  

Just-Lighthouse64-706a2.iso uploaded.

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

df
Back to top
View user's profile Send private message 
slavvo67

Joined: 12 Oct 2012
Posts: 1538
Location: The other Mr. 305

PostPosted: Sat 23 Dec 2017, 11:03    Post subject:  

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
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5088
Location: Ontario

PostPosted: Sat 23 Dec 2017, 13:11    Post subject:  

I'm working on a simple countdown timer .. I'll test it on the new version.
_____________________________________________________
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Mon 25 Dec 2017, 18:25    Post subject: Issues!  

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:
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
mtpaint_mimeIcon.txz.gz
Description  fake gz. rename & right click 'Install-txz'
gz

 Download 
Filename  mtpaint_mimeIcon.txz.gz 
Filesize  412 Bytes 
Downloaded  121 Time(s) 
ROX_STL3d-mime.txz.gz
Description  fake gz. rename & right click 'Install-txz'
gz

 Download 
Filename  ROX_STL3d-mime.txz.gz 
Filesize  14.64 KB 
Downloaded  106 Time(s) 
Back to top
View user's profile Send private message 
Dry Falls

Joined: 16 Dec 2014
Posts: 564
Location: Upper Columbia

PostPosted: Wed 27 Dec 2017, 01:42    Post subject:  

Quote:
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...'
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5088
Location: Ontario

PostPosted: Wed 27 Dec 2017, 16:22    Post subject:  

I finished PTM timer.
http://murga-linux.com/puppy/viewtopic.php?search_id=1344555448&t=112410
_____________________________
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 3 [38 Posts]   Goto page: 1, 2, 3 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1007s ][ Queries: 14 (0.0096s) ][ GZIP on ]