X-Slacko-4.4 with Xfce

[rg66]

How about doing X-Fatdog64-7.0?

I'm able to compile xfce4-4.10 on Fatdog64 but unable to integrate it into fatdog properly since I don't know how to write the scripts that would be required (or whatever it would require).

It might be popular.

I've never tried fatdog, I guess I'll have to dl it and check it out. Not sure if I'm up to more frustration trying to get xfce working in a puppy though. If xfce compiled without too much hassle I might give it a go.

It was a lot of trial and error to get precise and slacko working, I should write all the steps down one day.

[gcmartin]

Hello @RG66

These are just some thoughts that may be consistent with the efforts you have been involved with over the past years with 32bit PUPs and the WM you support.

For 64bit, there are 2 PUPs which may be a little easier to tackle in th 64bit arena as the 2 I mention look and feel much like the PUPs you are accustomed to: Namely LightHouse64 and Slacko64. Both of these have dotted-line connections with PUPs and Slackware that you have been using and producing for the community.

Should you use LightHouse64, I would recommend you use the Mariner version for a start of the testing you will venture toward. Reason: I seem to remember that the author did some work and has some of the same WM and FM that you have addressed in recent items you have presented to us. So, it would give you a springboard for addressing your getting acquainted as well as bringing those older FMs and XFCE WM versions up to the latest using same efforts you use for 32bit distros.

Lighthouse also comes in a Base version without all of the ease of use incorporated in the Mariner version. The author has a website devoted to all of the understanding you would need to have a simple easy path to limited to none issues in its use. It is found ===> here in Puppy forum

The author combined the best of PUPs and expanded on the FATDOG plethora for the ease of use you will find.

Slacko64 is a good vehicle as well. As I remember here, 01Micko did present this just prior to heading back off to school. Much has been accomplished and will show up in teh next release, I'm sure.

FATDOG is excellent, but the learning curve start to finish is unique in both perspective and operation than a standard PUP experience. It is different from what is seen in 32bit PUP worlds.

Hope this helps you to have a low frustration step into a stable 64bit direction for the WMs, FMs and ISOs you present to all of us.

Thanks again for what you do.

[rg66]

@ gcmartin

Thanks for the suggestions, I've no real plans to anything at the moment. If I did, I guess slacko64 would be a good choice.

[gcmartin]

Confirmed! LightHouse64 Mariner has XFCE OOTB. Boot the ISO live, fill in FirstRUN, after desktop refresh, exit desktop to the prompt, start XFCE.

Nothing to install.

But, all packages in Mariner are over year old. But its operations is swift and the system is stable.

Hope this helps for evaluation.

[Billtoo]

@ gcmartin

Thanks for the suggestions, I've no real plans to anything at the moment. If I did, I guess slacko64 would be a good choice.

I took a stab at xfce4 in slacko64, I got this far but I don't know how to integrate it properly in slacko64.

Xorgwizard is broken in slacko64 so there's no way that I know of to compile the proprietary nvidia driver.

EDIT: The zarfy-0.1.0-x86_64-1.txz from Fatdog64-700 beta allows using 2 monitors.

[fixit]

I can not find out where the program is in X-Slacko that allows one to install it to a USB or hard drive.

[ttuuxxx]

I can not find out where the program is in X-Slacko that allows one to install it to a USB or hard drive.

I don't have slacko 2.2 but you should have this /usr/sbin/dotpup
ttuuxxx

[fixit]

Thanks.

[rg66]

I can not find out where the program is in X-Slacko that allows one to install it to a USB or hard drive.

If an app isn't in the menu then it's in app menu > Control Panel.

[starhawk]

Booting from USB on my Fujitsu thin client, PS/2 mouse doesn't work. Might be the mouse, not sure... it's an HP optical PS/2...

System is a Fujitsu Siemens Futro S400, specs here --> http://www.parkytowers.me.uk/thin/Futro ... ndex.shtml
I've upgraded it to 512mb RAM (won't take more ) and am booting from a Lexar 32gb flash drive, manual frugal install + grub4dos, no savefile.

Could very well be the mouse, it's lit up and all, tho, so I'm not sure. PS/2 keyboard works, as does a spare USB wireless mouse by Targus.

Not really interested in troubleshooting this one for now, I'm just seeing how the system runs with that OS and the built-in Firefox... casual tinkering, really... if it runs way better than I think it will, then I'll be more interested in finding out whether my mouse is broken or if it's X-Slacko. Main desktop uses USB everything so I'm not really worried there.

Mostly I just wanted to let you know that if you had the time and inclination it might be something worth looking into... maybe, maybe not, up to you

EDIT: confirmed to be the mouse itself that didn't want to behave. I've a local friend who does eWaste recycling in a responsible way, so I'll give it to him.

[outtaspam]

Anybody know the workaround to enter a password when making an encrypted save file in X-Slacko?

The process hiccups/stalls when I'm entering the password and the outcome is an encrypted save file with a blank password.

Thanks!

[rg66]

Anybody know the workaround to enter a password when making an encrypted save file in X-Slacko?

The process hiccups/stalls when I'm entering the password and the outcome is an encrypted save file with a blank password.

Thanks!

Looks like pupsaveconfig is broken, it wouldn't even wait for me to enter a password. Remove it with Control Panel > Software > remove builtin packages and install the pet below. Seems to work for me now.

[outtaspam]

Anybody know the workaround to enter a password when making an encrypted save file in X-Slacko?

The process hiccups/stalls when I'm entering the password and the outcome is an encrypted save file with a blank password.

Thanks!

Looks like pupsaveconfig is broken, it wouldn't even wait for me to enter a password. Remove it with Control Panel > Software > remove builtin packages and install the pet below. Seems to work for me now.

It worked for me as well Thank you

I enjoy this Puppy derivative very much.

[Marv]

Anyone had sucess swapping a newer kernel into X-slacko 2.2?

I'm updating old micro-ATX boxes to j1900 (Trail Bay-D processor) mobos (ASRock Q1900M) and USB support seems to be missing in pre 3.11/3.12 kernels. Surprisingly, everything else works well. The j1900 works perfectly in LxPupTahr (3.14.8 kernel) and in Carolina with either Battleshooters 3.17 swap or my 3.15.4 swap. Stock Carolina 1.2 also does not have USB support but runs otherwise. No options in the BIOS to fiddle with USB compatiblity. I've had a couple of goes at a swap to 3.15.4 but always end up with not being able to set up the layered fs and a kernel panic.

Nothing vital, just tinkering and trying to get my favorite triad up on these new boxes.

[rg66]

Hey Marv,

I've had success using the slacko-5.9.3 kernel, initrd.gz and vmlinuz. Haven't tested too much, but it would be nice to have the save folder option. Here's a screeny.

[Sage]

No options in the BIOS to fiddle with USB compatiblity

So far, at least, my strategy to stay with AMD (Kabini?) and avoid Intel has worked out well. The AMD board makers , esp. Gigabyte, seem to have been most cooperative in avoiding the unwelcome leverage of the DWintel cabal, providing flexible (if not always intuitive!) BIOS options. Not sure where we are with the newer BIOS makers. It used to be possible to switch on missing functions using a custom utility - the Legacy USB was one of those. I pity those guys, esp. on your continent who persist in buying ready-built boxes. They spoil it for everyone and encourage the cartel, of course. If you discover that it is still possible to interfere with the BIOS options I'd be glad to know of a suitable utility. I suppose the true gurus might be able to do that from the Linux CLI?!
Afterthought: it also used to be possible to reflash a BIOS to an earlier version from the same stable. Might lose a few options but gain what you need. Risky, sometimes, and it all depends on how big the technology jump for everything else. Not always as big as the hype would have us believe...
All this is/should be academic as far as Puppy is concerned? Anyone still pushing the boundaries with a K6/7-500 system? All this talk about 2Gb/2Gb surely misses the point?

[rg66]

After a few small edits and gyro's patches, save folder is working. Just compiled 3.14.22 kernel (I had the source already) and will test to see if it works tomorrow. If it does, I'll compile a newer one.

[yerc1]

After a few small edits and gyro's patches, save folder is working. Just compiled 3.14.22 kernel (I had the source already) and will test to see if it works tomorrow. If it does, I'll compile a newer one.

I would appreciate if you can revisit adding kernel support for Toshiba Chromebook touchpad. Please see my posts in:

http://www.murga-linux.com/puppy/viewto ... 598#784598
http://www.murga-linux.com/puppy/viewto ... &start=330
http://www.murga-linux.com/puppy/viewto ... start=1500

Thanks

[Marv]

Hey Marv,

I've had success using the slacko-5.9.3 kernel, initrd.gz and vmlinuz. Haven't tested too much, but it would be nice to have the save folder option. Here's a screeny.

I've run straight slacko 5.9 3 on the j1900 and no USB as the kernel is still prior to 3.11/3.12. Pretty sure any 3.14.x would fly. Tidying up both 'new' boxes and testing/swapping DVD players so not much software mucking. Both the 3.17 Carolite and the 3.14.8 LxPupTahr give nice stutter-free full screen playback on what video & DVDs I've tried so far. Having fun

[rg66]

I would appreciate if you can revisit adding kernel support for Toshiba Chromebook touchpad.

Thanks

Well, I can't seem to find a patch for that which is weird cause I'm sure I found one when you first posted about it. I'll keep looking.