Introducing Just-Lighthouse64

[Dry Falls]

Hi edoc. First off, almost everything suggests not to use gparted on an ntfs partition, unless you want to destroy windows and put something else there.

If you run a mozilla browser as spot (ie, from the menu instead of the wbar as explained in the readme file), you will only be able to download into a spot-exclusive directory. Ice cat needs to be configured to accept java scripting (and almost everything else as well) to utilize g-drive. I use seamonkey for that. Icecat is basically a light and very secure browser for the paranoid at heart.

3.19.2 is a bigger number, but it is in an older Lighthouse. I've reverted to 3.18.8 and just uploaded a new JL64 iso. It's a much better behaved system. PPM works very well, but update is still, as I explained in the readme link on the iso, on hold until there is a repository to hold the packages.

Please use the browser addons at g-drive rather than from another system as they are all configured specifically for lighthouse.

I've removed the /spot/.mozilla directory from the browsers and placed it in the profile sfs, only to preserve Tazoc's links. It is not necessary and could cause confusion at first. Personally, there's no reason to run as spot if you're running in ram. Konqueror is a pretty feature-rich browser and should work for you, but seamonkey (or firefox) are probably the most trouble free, all-around and ready-to-use mozilla browsers.

The new iso includes a completely new kde desktop addon which itself includes the gvfs and xfce window manager. No more extra files to load. NLS also includes the locale's and Documentation is restricted to doc, info and man pages (as well as gtkdoc). A lot of other redundancy has been removed from the devx file, so it's a bit lighter as well. kde4.10.5 is also packed with its own dev tools (6_kde-xtras.sfs is games and such).

From the opening post on this thread, all the updated files are in this directory:

Just_Lighthouse (JL64-3.18.8.iso )

ps.,, Stemsee, I will try out your new kernel.

[Dry Falls]

And now i have an issue. Xorg.conf seems to be reset sometimes, so i should write this again.

Thanks for that. I've got arch wiki in the search box on all my browsers. I should have guessed! On xorg reseting, the newer kernels will find your hardware and use it. Unless you run xorgwizard-puppy, xorg.conf is largely bypassed. I run it routinely (for new pupsaves) because I've found the KMS is a lot better than the builtin or evdev.

If you're still having problems with the xorg.conf option, separate the code and put it into a rule in /etc/X11/xorg.conf.d/. That will take precedence over xorg.conf during boot-up, as far as I understand.

df

[edoc]

Just powered-up the laptop and it's not seeing the Save File.

But then it popped up a window about sfs files and I let it load them. I opened one and it appeared to have downloaded successfully despite the previously mentioned errors re. PPM, etc.

Checked in the /abcsave subdirectory that I had specified at Shutdown last night and there is a Save file there, plus a copy of JL64-602.sfs and the other sfs (downloads I thought had failed)..

There is also another directory that I didn't create in the same folder - it contains the Frugal files and another copy of the JL64-602.sfs

What am I doing wrong, please?

Thanks!

[Dry Falls]

Did you boot off the cd/dvd or were you able to boot from the partition from your frugal install (ie., dual boot)? And are you using grub2 or isolinux? It makes a difference because if it was a frugal install, grub.cfg or isolinux.cfg will be on the root partition and you can edit them by adding

Code: Select all

 psubdir=yourdirectoryname

next to linux /vmlinuz. That would be the folder both your save file and JL64-602.sfs are located. It won't look anywhere else. If there is a base file already on the root partition, that will be the one loaded. Grub should look like this:

insmod png
background_image /menu.png
set timeout=10
menuentry "Default Just-Lighthouse64 - noautosave" {
linux /vmlinuz pfix=noautosave,copy,fsck
initrd /initrd.xz
}
menuentry "1 Just-Lighthouse64" {
linux /vmlinuz
initrd /initrd.xz
}
menuentry "2 Just-Lighthouse64 without savefile" {
linux /vmlinuz pfix=ram
initrd /initrd.xz
}
menuentry "3 Clean boot Just-Lighthouse64 from CD/DVD / first multisession" {
linux /vmlinuz pmedia=cd pfix=ram,copy
initrd /initrd.xz
}
menuentry "3b Clean boot Just-Lighthouse64 from USB / first multisession" {
linux /vmlinuz pmedia=usbflash pfix=ram,copy
initrd /initrd.xz
}
menuentry "4 Just-Lighthouse64 with multisession support CD/DVD" {
linux /vmlinuz pmedia=cd pfix=copy
initrd /initrd.xz
}
menuentry "4b Just-Lighthouse64 with multisession support USB" {
linux /vmlinuz pmedia=usbflash pfix=copy
initrd /initrd.xz
}
menuentry "5 Lighthouse64 without graphical desktop" {
linux /vmlinuz pfix=nox
initrd /initrd.xz
}
menuentry " ---" { true; }
menuentry "6 For problematic Radeon cards - disable radeon driver" {
linux /vmlinuz blacklist=radeon
initrd /initrd.xz
}
menuentry "7 For problematic Nvidia cards - disable nouveau driver" {
linux /vmlinuz blacklist=nouveau
initrd /initrd.xz
}
submenu "8 For severe video problems - disable KMS, use wizard" {
menuentry "Set video resolution to 640x480" {
terminal_output console
set gfxmode=640x480
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "Set video resolution to 800x600" {
terminal_output console
set gfxmode=800x600
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "Set video resolution to 1024x768" {
terminal_output console
set gfxmode=1024x768
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "List all supported video resolutions" {
videoinfo
echo "Press Enter to continue ..."
read
}
menuentry "Use video resolution not listed in this menu" {
echo "Enter video resolution (WxH e.g. 800x600), press Enter to continue."
read gfxmode
terminal_output console
set gfxpayload=keep
terminal_output gfxterm
}
menuentry "Start Lighthouse64 with the chosen resolution" {
linux /vmlinuz nomodeset pfix=xorgwizard,ram
initrd /initrd.xz
}
}
menuentry "9 Just-Lighthouse64 with file system check" {
linux /vmlinuz pfix=fsck
initrd /initrd.xz
}
menuentry " ---" { true; }

menuentry "Firmware configuration" {
fwsetup
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}

If you're booting from a cd/dvd. press "e" when the menu selection is made and you can edit on the console (good for this session only). Otherwise, if you want the noautosave mode, go ahead and let it boot first run (ram) and drag your base file and savefile out of the directory and onto the root of the partition (also zWine if you want 32lib). Then reboot/do not save.

Third option is to click menuentry "1 Just-Lighthouse64", and it will find all the save files. UEFI booting is still experimental. I think we should just erase Windows and go back to the old-fashioned way of doing things. Rewriting the init script is just beyond my capabilitiy. The way I do it is boot off the cd but have a grub.cfg on the root/boot partition. Grub will use that unless you specify "pmedia=cd" (bootmenu 3 or 4). Then you can edit the cfg file to your heart's content.

Yes, I know it's complicated and it seems there are too many options for this age of total no-think automation. But everyone's tastes differ. "Free" choice must always imply some jogglin' of yer noggin, or it's all just hit-and-miss.

df

[edoc]

I've not had troubles changing Puppy versions or making MS/Linux installs for years - other than the one HP laptop with a messed up UEFI for which I needed help creating a USB boot workaround.

I wiped the Savefile.

I booted from the 3.18.8 DVD.

I ran a clean Frugal install.

Question: Is it correct that the Savefile must be in the same folder as the system files?

[Dry Falls]

Question: Is it correct that the Savefile must be in the same folder as the system files?

The base file (JL64-602-sfs) is best located with the save file. Also any z-files. The kernel and initrd.xz have to be with the grub.cfg or isolinux.cfg. If they are not in the root partition (they can be on another drive, or anywhere) but in a directory, you must add the directory ahead of vmlinuz like so:

Code: Select all

linux /Test/vmlinuz psubdir=Test-b

. The biggest problem booting with the system files at root-partition is if you have any other basefiles hanging around, Init will pick the first one it comes to, even when burried inside folders within folders. Multiple save files shouldn't present a problem.

df

[edoc]

I moved everything (system files, save file, add-on SFS's) into the /LH64602frugal folder and things are playing nicely now.

I was also able to symlink (link absolute) the old Mozilla Profile and modify profile.ini to successfully import the old emails, folders, settings, bookmarks, etc.

It all looks great!

Thanks.

[edoc]

We're having some troubles viewing HTML5 and other media via YouTube and Facebook links.

What set of Seamonkey add-on apps are best to solve this, please?

I loaded YouTube Flash Video Player - which helped some.

Thanks!

[Dry Falls]

Made a small pet with some post-last-minute changes, and to my surprise, pets are no longer installable! For the time being, one will have to download-only the desired pet and use pet2txz from the terminal. The attached txz file will make it possible and add the patch I intended. Stay tuned...

[edoc]

Clicking on the download converted it to "kdepatch-JL64-2-x86_64-PET.txz" and clickingf on that generated a dialog that looked like the PET being successfully loaded.

How does one verify that it in-fact did as intended, please?

[edoc]

Added the Chromium w/PepperFlash SFS to the SFS load menu.

The icon shows up in the bottom toolbar but nothing happens when clicked.

It does not show up in the Menu.

What step did I miss, please?

Thanks ...

[Dry Falls]

How does one verify that it in-fact did as intended, please?

Save session, then go to /root/.packages/user-installed-packages' That should resemble this:

Code: Select all

kdepatch-JL64-2-x86_64-PET|kdepatch-JL64|2-x86_64-PET|kdepatch-JL64-2-x86_64-PET||||kdepatch-JL64-2-x86_64-PET.txz||PolicyKit Authentication Agent|

Also, it will show up in /var/log/packages. Finally, in /root/.packages, the file 'kdepatch-JL64-2-x86_64-PET.files' will show the files actually installed and their locations.

Basically, the patch includes configuration files for kde (some mistakes I made before are corrected) and library support for kdm which Tazoc had missed. KDM is still experimental but is included for those who don't want to log in as root. Prior to this patch, permissions were not configurable.

01micko's Dir2txz is included from fatdog (with their modifications), but needs work to better jive with lighthouse. It runs from the terminal. So far I'm stumped as to why pet install quit functioning. PPM won't even download pets (though it's fine with txz files). It may be a function of incompatibility with Distro_Compat, but then noarch shouldn't present a problem - yet it does.

df

ps. use the chromium browser from extrasfs link on the opening post. chromium-40b.0.2214.91-x86_64-1alien.sfs

[Dry Falls]

Used update manager to extract the address for Takao-fonts-ttf-003.02.01.pet from Tazoc's repo as an experiment. Lighthouse update won't download it because it expects JL64 rather than L64. Browser is too slow, but pwget had no problem accessing and downloading the pet package. PPM/Petget installed the pet without a hitch. So what appeared broken is in fact not. Will add the distro to PPM (ppm_auto-1.9.7) and test that. Obviously a compatibility issue with foreign pets. Picky, picky, picky!

df

[Dry Falls]

KDM is still experimental but is included for those who don't want to log in as root. Prior to this patch, permissions were not configurable.

Should you not wish to run kdm or login authentication, best to drag /usr/share/autostart/polkit-kde-authentication-agent-1.desktop into the DisabledItems directory. The little daemon seems to cause everything else to lag and even stumble.

df

[edoc]

This is what I found in the user upgraded packages file:

brother_hl2170w-2.0|brother_hl2170w|2.0||BuildingBlock|284K||brother_hl2170w-2.0.pet||Brother printer driver|t2|8.0rc||
peasyscan-2.7|peasyscan|2.7||Graphic|168K||peasyscan-2.7.pet||Peasyscan simple image scanner|slackware|14.0||
kdepatch-JL64-2-x86_64-PET|kdepatch-JL64|2-x86_64-PET|kdepatch-JL64-2-x86_64-PET||||kdepatch-JL64-2-x86_64-PET.txz||PolicyKit Authentication Agent|

OK re. the version and location of chromium - will give that a quick go.

[edoc]

There is no listing for chromium at that Google Drive link.

https://drive.google.com/folderview?id= ... sp=sharing

Where else might I look, please?

Thanks

[Dry Falls]

There is no listing for chromium at that Google Drive link.

whoops! Could it have been a freudian slip? Now try it.

df

[edoc]

OK, that worked ... but no Flash.

I'm only interested in Chromium because it has PepperFlash.

Thanks

[Dry Falls]

OK, that worked ... but no Flash

Chromium is perfectly capable of searching and installing addons, including flash. On top of that, there is an existing flash sfs at gdrive (v.202.411). If you think it's too old, being last years model, rebuild it with the guts of the newest of the new, which itself will be declared insecure next week, and next month, you will be advised to switch to html5 like all the "cool" people.

Did you ever consider it's not your security they're concerned with, but their own?

[edoc]

Not sure what happened to my prior reply ...

Anyhow, yeah, I get that they are about their own profit - but have to pretend to care that we are satisfied.

EDIT: Found my missing reply, it was over in a Seamonkey window ...

Google appears to have entered an unholy alliance with Adobe to try to block everything from moving to the non-proprietary HTML5 for video via their jooin PepperFlash project.

For the moment we are caught between the two formats, some things are available in both, some just in HTML5, and a huge installed base is in Flash.

Many sites are popping up Flash errors and I was not able to get Flash to work properly in Seamonkey - which I would prefer rather than mess with Chromium - but best I can tell there isn't/won't be a PepperFlash for Mozilla and the old Flash is aging-out.

I was able to get Flash working in Seamonkey so will probably delete chromium to save space and limit clutter.

Still have to figure out why printing to the ASUS router connected printer doesn't work - it does work from my LH64 laptop and a Carolina 1.3 laptop.

Thanks