Lighthouse Pup 4.43 Gu2 215M

[Jim1911]

Hi tazoc,

You may want to consider these additions to LHP which have been working fine for me with your latest 4.43Gu1.

1. snap2, a powerful rsync-based, open-source, free backup program for Linux by Istandish
snap2 home page -- snap2.pet download
2. dirdiff, which allows comparison of up to 5 directories at once.
dirdiff-2.1-4fixed2.pet

Really enjoying LHP, I've tried all your window managers, however, I keep going back to KDE4, primarily due to it's fine Kickoff Menu which eliminates so much of the menu clutter.

Jim

[tazoc]

TazOC,
Twoother quick questions for you. 1) As far as audio settings, I have been dropping out to CL and running alsamixer to change the volume levels, however I noticed that once I shut down, the changes are lost. What do I need to edit so that my alsamixer settings stay persistant? 2) In what file do I find the actual execution of wbar at startup? I want to tweak it a little but I cant seem to find it in the places ive looked. I've edited my .wbar file, but im looking for where I can change the execution switches.

Hi Q5sys,
I tried Zmixer in the Multimedia menu and it does save the settings; no idea about alsamixer.

Wbar starts from ~/Startup/wstart. It is generated by Wbar Setup | Start Wbar, removed by Wbar Setup | Stop Wbar and tweaked with Wbar Setup | Configuration. Is there something you want to change that Wbar Setup cannot?
TazOC

[tazoc]

Hi Jim,
Thanks for the links and feedback. I grabbed the snap2 and dirdiff pets and will look them over. I'm working on Gu2 with updated SeaMonkey, Shinobar's updated net-setup and some bugfixes.
TazOC

[edoc]

Hi Jim,
Thanks for the links and feedback. I grabbed the snap2 and dirdiff pets and will look them over. I'm working on Gu2 with updated SeaMonkey, Shinobar's updated net-setup and some bugfixes.
TazOC

Gu2 sounds exciting!

Thump, thump, thump! Waiting patiently by the door ... errr ... Inbox ...

[Q5sys]

I'm working on Gu2 with updated SeaMonkey

Anyay you can include a more up to date version of GCC? LHP-Gu1 only has 4.2.2.

Q5sys,
I tried Zmixer in the Multimedia menu and it does save the settings; no idea about alsamixer.

Wbar starts from ~/Startup/wstart. It is generated by Wbar Setup | Start Wbar, removed by Wbar Setup | Stop Wbar and tweaked with Wbar Setup | Configuration. Is there something you want to change that Wbar Setup cannot?
TazOC

Thanks for the info on zmixer... i'll dig around and see if I can find anything more on alsamixer.
As for wbar... wbar setup can do everything I need (well mostly), I was just unaware of it before. lol I was altering the wbar manually, as well as changing the config settings at the CL when starting it. The Setup does make it ALOT eaiser for the simple stuff... as for the more complex stuff...

Something in an older pet here, that ive been trying to replicate. Instead of desktop Drive icons, they showed up in a bar.
This is what I have figured out so far. wbar was copied and named vbar. Then at startup that command was run along with switches so that it'd load a 2nd bar. I've been able to get this to work.
the wstart that im using is as follows:

Code: Select all

#!/bin/sh
cd /root && sleep 1
wbar -config /root/.wbar -above-desk -jumpf 0.0 -pos top 
-offset 0 -nanim 3 -zoomf 2.5 -idist 4 -isize 24 -bpress -balfa 50 -falfa 100 &
! pidof wt-shoot 1>/dev/null && exec wt-shoot --quiet &
vbar -config /root/.vbar -vbar -above-desk -jumpf 0.0 -pos left -offset 0 
-nanim 3 zoomf 2.5 -isize 30 -idist 4 -bpress -balfa 0 -falfa 100  >/dev/null &

(Code format changed so it'd fit on smaller screens)

Now right now however the .vbar is just a static file, where I am getting lost is how to make it dynamic. 1) The way it works in BoxPup is that when you plug in new devices they are loaded into the bar. Double click on the drive and if its not mounted you'll get dialog box asking if you want to mount it. Choose mount and it'll then open the file manager with that drive. If it is mounted you'll get a dialog box asking if you want to unmount it or open the drive. It also changes the icon at this point from the unmounted icon to the mounted one.
I've got a post in the old Boxpup thread asking about this, but as its such an old thread I doubt I'll get a reply. However I thought this might be something you'd look at and go 'oh thats easy, you just...' Then again, perhaps not.

My current .vbar file that shows the data as it was on my boxpup system. ie a snapshot. It was based on 4.12 so Im thinking the commands would have to change.

Code: Select all

# The Bar && Font
i: /usr/share/wbar/wbar.icons/osxbarback.png
c:
t: /usr/share/wbar/wbar.icons/VeraBd/6

i: /usr/local/lib/X11/pixmaps/drive48.png
c: drive_all sda1 drive ntfs
t: sda1

i: /usr/local/lib/X11/pixmaps/drive48.png
c: drive_all sda5 drive ntfs
t: sda5

i: /usr/local/lib/X11/pixmaps/usbdrv_mntd_boot48.png
c: drive_all sdb1 usbdrv ext2
t: sdb1

i: /usr/local/lib/X11/pixmaps/usbdrv_mntd48.png
c: drive_all sdc1 usbdrv ext2
t: sdc1

i: /usr/local/lib/X11/pixmaps/usbdrv48.png
c: drive_all sdc2 usbdrv ext3
t: sdc2

Lastly a screenshot showing my current setup with the standard upper bar wbar, along with my vertial drive bar.




EDIT: Ok THISthe extent of the research ive been able to do. I simply dont know enough to proceed at this point.
Am I on the right track? or am I hopelessly lost?

FYI, /etc/hotbar/hdbar is where Boxpup saves the config file for the bar. On my system i've chosen to make it /root/.vbar for simplicity sake.

[tazoc]

Hi Q5sys,
LHP has gcc-4.2.2-1 from Puppy 4.3.1 and glibc-2.9 from Slackware. The glibc update was needed for the KDE 4.3 add-on. If I updated to a newer gcc, would that break the devx.sfs (also from Puppy 4.3.1) needed for compiling in LHP? What are the pros and cons of updating gcc?

If you start with a clean pupsave you can use Gslapt to experiment with a newer gcc. It shows gcc-4.4.3-i486-2 is available.

I've begun some preliminary testing of KDE 4.4 and found that glibc needs updating again. I'm testing glibc-2.11 for possible inclusion in LHP 4.44.

Using Wbar for the drive icons is a novel idea. It looks like Gray has made extensive changes to the scripts for Boxpup. I wonder if /sbin/pup_event_frontend_d and /etc/rc.d/functions4puppy4 were updated in addition to the mount/umount scripts you found. I have updated most of those scripts for multi-user support in LHP, primarily replacing /tmp with /tmp/${USER} and /root with ${HOME}. I don't quite understand how they work and don't know how to go about implementing drive icons for Wbar in Lighthouse!
TazOC

[Q5sys]

Hi Q5sys,
LHP has gcc-4.2.2-1 from Puppy 4.3.1 and glibc-2.9 from Slackware. The glibc update was needed for the KDE 4.3 add-on. If I updated to a newer gcc, would that break the devx.sfs (also from Puppy 4.3.1) needed for compiling in LHP? What are the pros and cons of updating gcc?

If you start with a clean pupsave you can use Gslapt to experiment with a newer gcc. It shows gcc-4.4.3-i486-2 is available.

I've begun some preliminary testing of KDE 4.4 and found that glibc needs updating again. I'm testing glibc-2.11 for possible inclusion in LHP 4.44.

Using Wbar for the drive icons is a novel idea. It looks like Gray has made extensive changes to the scripts for Boxpup. I wonder if /sbin/pup_event_frontend_d and /etc/rc.d/functions4puppy4 were updated in addition to the mount/umount scripts you found. I have updated most of those scripts for multi-user support in LHP, primarily replacing /tmp with /tmp/${USER} and /root with ${HOME}. I don't quite understand how they work and don't know how to go about implementing drive icons for Wbar in Lighthouse!
TazOC

I need the update GCC for a few projects im trying to compile. I didnt realize that the newer one might break it. I might just create a test install on another device and install it, compile what I need and then copy the binaries back over my main system. I'll play around with it later this weekend when Im bored.

As far as the wbar stuff, i'll take a look in those two other scripts that you mentioned and see how they differ between Boxpup and LHP. The only problem ive found so far, is that you've done extensive work in LHP, so your scripts are already quite edited. Which is where I get lost in where to edit them. However if I am making a test system to do some compiling on, I might as well go ahead and mess around and see if I cant manage to figure something out. I've never messed around with scripts at that level before, but there is no problem if I completely kill a test system. lol

I'll keep you informed of my success or failure.

[remussatala]

It supports for ATI video cards?

I have ATI AH 3450 Video Card.

[tazoc]

It supports for ATI video cards?

I have ATI AH 3450 Video Card.

I don't know if Xorg 7.3 in LHP supports that card. I do know that your card is not listed in the release notes for the ATI Catalyst 9.9 driver in the Mariner SFS. If you've tried Puppy 4.3.1 with it you'll likely get the same result with the Xorg driver in Lighthouse Pup 4.43.
TazOC

[cgt_1991]

tazoc hello, I had no time to fix the problem he had of the videos on youtube, but I did what you told me and if I could solve. download the tar.gz package and reinstall flash. thanks.

these days adding more RAM to my pc and I could install KDE 3.5 with compiz fusion and is truly spectacular. I really congratulate you and all who have helped make this puplet.
size is also incredible that point, since to install kubuntu on a usb memory 4 gb minimum required, however, pup lighthouse install it on my 2 gb usb memory and only takes up 1 gb.

PS: excuse my English because I use google translator

[Barburo]

Hi TazOC,
I posted my problems here
http://www.murga-linux.com/puppy/viewto ... 649#405649
It's an Intel chipset problem. Just wondering if you could take a quick look and see if you have any insights to offer.
Briefly the 2.6.30.5 kernel version of Puppy that LHPup 4.43G uses won't give me the screen resolution I need (always gives 1024x768) and I cannot get the firmware the wifi chip says it needs.
I've tried loading older versions of LHPup as far back as 3.01 gold but nothing solves the problems.
I loaded Ubuntu 10.4 onto this machine which uses the newer 2.6.32 kernel and it solves both problems - proper wide-screen resolution and no problems connecting the intel wifi card.
This new notebook comes with Windows 7 which also works correctly, but of course I would much prefer to use your LHPup if at all possible
B.

[turnip]

Did you remove the blacklisted cards within compiz? I figure the sfs are easy enough to remove that it wouldnt really matter if you whitelisted everything, and my intel 915gm doesnt work with compiz as it is.

[tazoc]

Hi TazOC,
I posted my problems here
http://www.murga-linux.com/puppy/viewto ... 649#405649
It's an Intel chipset problem. Just wondering if you could take a quick look and see if you have any insights to offer.
Briefly the 2.6.30.5 kernel version of Puppy that LHPup 4.43G uses won't give me the screen resolution I need (always gives 1024x768) and I cannot get the firmware the wifi chip says it needs...
This new notebook comes with Windows 7 which also works correctly, but of course I would much prefer to use your LHPup if at all possible
B.

Hi Barburo,
I wish that LHP would work on your new hardware, but it clearly doesn't, at least not yet. Have you tried MU's Alternative Xorg/xserver 1.6.3/Intel pet? Start with a clean pupsave and maybe it will give better screen resolution, though JWM icon rendering is buggy. I hope to update the kernel in LHP when there is one with working ATI and nVidia proprietary drivers or that has Xorg that works with Compiz. Solving the Intel Wi-Fi looks difficult, though if Ubuntu did it, then there might be a way in the next Puppy. I've ordered an inexpensive USB Wi-Fi adapter and hope that I can get it working in LHP or Puppy in the future. Barry announced plans for Puppy 5 today, including Lucid Puppy and he encourages us to test and submit bugs here. I see Jim1911 is testing it already! It looks promising.
-TazOC

[tazoc]

Did you remove the blacklisted cards within compiz? I figure the sfs are easy enough to remove that it wouldnt really matter if you whitelisted everything, and my intel 915gm doesnt work with compiz as it is.

How do you remove blacklisted cards within Compiz? I don't have any Intel graphics to test on but maybe others here have some ideas/experience.
TazOC

[edoc]

Any news re. Gu2?

[turnip]

generally in /usr/bin/compiz you can comment out the line where the graphic card is inserted in the blacklist. I've had to do it to fix my compiz and had no problems with it.

[tazoc]

Hi turnip,
I think I see what you mean here in /usr/bin/compiz-manager. There is a link to http://wiki.compiz-fusion.org/Hardware/Blacklist there too. Thanks for that tip. I'll look into it further.

Hi edoc,
Thank you for your interest. Gu2 is not quite ready yet--I've squashed some more bugs and it needs further testing. I'm attaching some tentative release notes.

My Dad is not doing well and I want to see what I can do from here to help him. He lives very far away and I can't afford to travel at this time.

Fortunately Dad has a very good friend nearby and he is there for him. Keep us in your prayers if you feel so inclined.
Thanks,
TazOC

[edoc]

My Dad is not doing well and I want to see what I can do from here to help him. He lives very far away and I can't afford to travel at this time.

Fortunately Dad has a very good friend nearby and he is there for him. Keep us in your prayers if you feel so inclined.
Thanks,
TazOC

That sure is a priority!

Sure will pray - it may be about the only helpful thing I can do here on the Forum!

[turnip]

Compiz wouldnt work for me but I got it to work albeit buggy.

Went to setup>xorg video wizard>edit xorg.conf and added:

Section "Extensions"
Option "Composite" "enable"
EndSection


to the bottom of the xorg.conf, now compiz boots up and works but I am getting bugs like desktop icons not working without reloading window manager, and I cant see the text im typing into google. Any ideas what to do with this? If I typed compiz or compiz --replace into the terminal I got a "no composite extension" error.

[turnip]

Oh I was using lxde for this, I am gonna try kde and xfce to see if it works a bit better.