Puppy Linux Discussion Forum

[Dry Falls]

reuploaded 4_kde, 5_JL64 and xscreensaver (standalone, also in 5_JL64) sfs files to reflect changes. New JL64-702 delta patch (7+M) includes all changes current (not cumulative; apply to base sfs on iso).

Stemsee, how do you (personally) start wifi-connect? /etc/init.d start-stop? /root/.config/autostart desktop file? Link to script in Startup folder? Which would you suggest, wifi-connect or wifi-connect2? What's the difference other than dependency checking?

thanks,
df

[stemsee]

Hi Dry falls

I have a gtk icon panel (orig. by ETP) 4x4 icon grid with scanner wifi-connect and wifi-profiles there. One click starts them. I also start from menu. Wifi-Connect is my default connector, scanner and Wifi-Profiles equally second. Scanner is fascinating for me. Wifi-Eduroam at University. Although all oher scripts also handle eduraom AP.

Wifi-Connect scans using wlan0. But wlan1 (2nd card) can be selected to connect to selected AP. Checking the ethernet check-box and pressing ok connects eth0, not wifi, and restarts gui for wifi connection selector. When joining an AP for the first time user must check the save profile box (not necessary using scanner). Checking default-start adds script to ~Startup with selected AP and auto-connects when X starts.

Wifi-Connect-2 only uses wlan1-9 or whatever label is assigned to wifi card 2. When started it scans with card 2 thus not interfering with wifi card 1 connection if established.

Scanner scans with card 1. The good thing about scanner is its tray menu starts first and gives access to most wifi-connect functions e.g. start mobile phone tether, or eth0 or eth1 connection, and or start any other script from the suite wifi-profiles, eduroam etc
scanner also continuously updates AP availablitiy and displays passkey on-off, mac address of ap, quality-level of signal etc. (cli - scanner admin - mode allows editing info, copy paste etc)

Funny thing happened just now.....usb wifi dongle assigned label wlan123 ....

[stemsee]

BTW the undeb link solution doesnt work! Did you test it thoroughly! If possible replace or update all dpkg undeb deb install stuff. I tried everything nothing actually working as is. Yes, appears to work , but doesnt ... on my system anyways.

[Dry Falls]

[stemsee]

How can I change the language to chinese or portuguese. I have been trying unsuccessfully using fatdog packages from icake. He supports older lighthouse but not latest. Any help appreciated! Need to get this done rather quickly or look foolish to a lot of people!!!

[Dry Falls]

Did you load DOC_JL64-2.sfs? That has the full /usr/share/locale directory for internationalisation, If the original lighthouse works, then I'll take a look at the NLS_base sfs to see if I've missed something. Back later.

df

ps. while gettext is on the base file, gettext-tools-0.19.8.1-x86_64-1 is on Devx.

[Dry Falls]

For the moment, JL64 appears to be an English-only system. While keyboard, country and timezone changes seem to function correctly (correct changes are made to /etc/profile & xorg.conf &et), language always seems to default back to English. Something's definitely broken.

Any help for where to start looking would be appreciated

df

[Dry Falls]

Uploaded a new delta file for the base (same instructions & link as before) now 36M.
uploaded a heftier 'DOC_JL64-3.sfs' (152M) which provides i18n & localisation tools (NLS) as well as full documentation and gtk-docs.
Updated man_tools-14.2.sfs.
kcompile has updated initrd.xz in kernel package (still k4.8.14)

Chooselocale/countrywizard (firstrun) settings now persist. However, there are no language pets (icake has pets for some previous JL64 versions which have some functionality in JL64-702, but might be seen to create more problems than they solve).

What is not included in the uploads is an updated rc.country (runs prior to profile, so isn't likely to affect localisation in X. Here it is:

[Dry Falls]

Broke up DOC_JL64-3.sfs into

DOC_JL64-702-4.sfs
NLS_base-JL64_702.sfs
gtk-doc-reference_702.sfs

recompiled k4.1.11 and uploaded sources and kernel package.
fixed kcompile. now v17;
added tor browser. v6.0.4. will offer to update to v.6.0.8 first run. this puts the working directory in the spot directory, after which you may wish to symlink outside the save file (/mnt/home) or to keep the new configuration between boots when running in ram.

todo (next release): put pmusic back in base since a minimal fmplay and dependency library files are back in;
update Lighthouse help files.

[Dry Falls]

functions_x from slacko64 (called by rc.country):

also, fix for version, includes replaced wcpufreqdriver, an artifact from remaster which should be a blank text in the base):

[Dry Falls]

Uploaded 702-B3delta.tar.gz (see opening post) delta file to upgrade Mariner iso from 702B2 to 702B3.
Also some new sfs addons (check sfs-update)

edit: Radky's JWMDesk-2.2.1.pet works ootb for jwm desktop management. I include it here.
Known issue with or without pet installation: jwm themes only has darkgrey and stardust dark and light working properly until I finish translating the other themes into xml.
Here's Radky's pet:

[Dry Falls]

some old libraries I think can be safely removed (about 4M worth)
remove fake '.gz' extension:

[Dry Falls]

Issue with loading both python-2 and python3 under openbox DE: Unfortunately, python3 sfs loads first (alphanumeric order). I've symlinked python3 to python for building py3 programs, but openbox needs python to direct to python-2 to enable openbox-autostart (load ~/.config/autostart). Two possible fixes:
1. rename python-2...sfs to Python-2...sfs (caps load first) or
2. add to .xinitrc (somewhere near the top)

[Dry Falls]

uploaded Just-Lighthouse64-702B4.iso (minimal @ 341M). Please see opening post or check sfs-update if running JL64.

df

[Dry Falls]

Just-Lighthouse64-702rc delta file applies to Just-Lighthouse64-702B4.iso. 52M
Please see opening post or check sfs-update if running JL64.

df