Is there a download link to try those two pups?LateAdopter wrote: e.g. slacko64 and a trusty64 built with jamesbond's woof-ce-next..
tahrpup64 6.0.5 CE
Re: Woof-CE savefile - shutdown bug
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
Re: Woof-CE savefile - shutdown bug
Hello stemsee
The slacko64 stuff is still here:
http://distro.ibiblio.org/puppylinux/test/slacko64/
For the woof-next-james stuff go here:
https://github.com/jamesbond3142/woof-CE
and here
http://www.murga-linux.com/puppy/viewtopic.php?t=94101
I had never built anything before, but jamesbond's instructions are so clear that I didn't have much difficulty building a more-or-less working puppy.
It's a year ago that I tried it, and I deleted the ISO long ago, but it only takes 10 minutes to build a puppy using jamesbond's woof-ce-next.
The only requirement, not mentioned in the readme is a real dpkg not the busybox one. I built it using a fatdog kernel.
I don't know anything about how puppies manage savefiles and shutdown, so I couldn't attempt to debug it.
jamesbond has been too busy with fatdog 7 and "other things" to develop it further since then.
This is a bit of a timewarp!stemsee wrote:Is there a download link to try those two pups?LateAdopter wrote: e.g. slacko64 and a trusty64 built with jamesbond's woof-ce-next..
The slacko64 stuff is still here:
http://distro.ibiblio.org/puppylinux/test/slacko64/
For the woof-next-james stuff go here:
https://github.com/jamesbond3142/woof-CE
and here
http://www.murga-linux.com/puppy/viewtopic.php?t=94101
I had never built anything before, but jamesbond's instructions are so clear that I didn't have much difficulty building a more-or-less working puppy.
It's a year ago that I tried it, and I deleted the ISO long ago, but it only takes 10 minutes to build a puppy using jamesbond's woof-ce-next.
The only requirement, not mentioned in the readme is a real dpkg not the busybox one. I built it using a fatdog kernel.
I don't know anything about how puppies manage savefiles and shutdown, so I couldn't attempt to debug it.
jamesbond has been too busy with fatdog 7 and "other things" to develop it further since then.
a few backgrounds.
- Attachments
-
- tahrmr6a.jpg
- https://www.mediafire.com/folder/x4v77bi1p58ox/puppy2013
- (39.73 KiB) Downloaded 1515 times
-
- tahra16t.jpg
- https://www.mediafire.com/folder/x4v77bi1p58ox/puppy2013
- (10.96 KiB) Downloaded 1528 times
I too tried this.stemsee wrote:... But the biggest problem for me was the inability to connect to the internet, and I tried a lot ways to get it working, so I put it on hold! I thought you had cracked it!
This BUG problem was reported to @Jamesbond many months ago. He says that there is no problem. I have shown evidence that there is. This was introduced as they went to FD7. I think he is attempting a targeted effort that has reduced both functionality and introduced this bug. In fact, no explanation has been given, yet, to the reason he changed the manner of LAN/WAN operations as he did. We are left to "live with it" ideology versus acknowledgement and reversal even though all other PUPs continue proper operations when booted. I consider him an excellent developer, but, in this instance for this problem, additional consideration should not have been taken as "him making a mistake". Instead the "hoped" behavior was addressing this.
I have asked if he would consider reversing the change and using the logic in all of the prior FDs or the logic present in Lighthouse or @Dry Fall's JustLighthouse or @01Micko's Slacko64 or @BarryK's April64 or Simplicity64 or ...
FD7 is the ONLY PUP distro (no, the only modern distro or OS) that has this dilemma in its OOTB boots on several PC networks. No other released PUP is built with this strategy or has this dilemma.
I believe @01Micko has a build process for WOOFCE that does NOT conclude with this BUG.
woof-next does not build FD it has nothing to do with fd . Fd is built with LFS.
Woof-next method is new and very fast. It can be configured so that packages for the build are installed using the default package handler, true dpkg or synaptic. ~He delivered woof-next as is'hoping' the community would do the rest of the work debugging it and finding solutions. Saintless reported a finding, I also reportedd a few findings and I had tried all three build possibilities. Anf I had a plan of action but I knew my scripting ability was not skilled or knowledgeable enough to tackle the tasks. But now I am interested again.
Woof-next method is new and very fast. It can be configured so that packages for the build are installed using the default package handler, true dpkg or synaptic. ~He delivered woof-next as is'hoping' the community would do the rest of the work debugging it and finding solutions. Saintless reported a finding, I also reportedd a few findings and I had tried all three build possibilities. Anf I had a plan of action but I knew my scripting ability was not skilled or knowledgeable enough to tackle the tasks. But now I am interested again.
finally i'm getting around to working on tahrpup64 again i've done one build already and the two major bugs of the previous one seem fixed .... so the important symlinks in /lib & /usr/libs are no longer being overwritten and setting the wallpaper now sticks.
i should be posting a new iso (hopefully beta quality) next weekend
i should be posting a new iso (hopefully beta quality) next weekend
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
- xanad
- Posts: 400
- Joined: Fri 28 Feb 2014, 14:56
- Location: 2 locations: MonteRosa Alp and Milano
- Contact:
Hi 666Philb,
Kernel uptated from 3.4.17 to 4.1.3EmSee
Any modification.
tahr64-6.0.2_k-4.1.3-EmSee-64
https://copy.com/06nSm2lJNhtKKbZz
Experimental italian version. Switch Language, Country and Time Zone after the boot. Some bugs fixed.
Thar_Media-64-k_4.1.3-EmSee_x86-64
https://copy.com/zBisCcKH7EwKYQ7r
Thar_Light-64-k_4.1.3-EmSee_x86-64
https://copy.com/pUycFpHzgv8Vv0KS
Patch CUPS n.1 by Watchdog https://copy.com/Fj8Q2io21YOHrJDh
Patch CUPS n.2 by Watchdog https://copy.com/cHkF0Fe6D3ICcZ7a
A little fun around T64.
EDIT: links updated
Kernel uptated from 3.4.17 to 4.1.3EmSee
Any modification.
tahr64-6.0.2_k-4.1.3-EmSee-64
https://copy.com/06nSm2lJNhtKKbZz
Experimental italian version. Switch Language, Country and Time Zone after the boot. Some bugs fixed.
Thar_Media-64-k_4.1.3-EmSee_x86-64
https://copy.com/zBisCcKH7EwKYQ7r
Thar_Light-64-k_4.1.3-EmSee_x86-64
https://copy.com/pUycFpHzgv8Vv0KS
Patch CUPS n.1 by Watchdog https://copy.com/Fj8Q2io21YOHrJDh
Patch CUPS n.2 by Watchdog https://copy.com/cHkF0Fe6D3ICcZ7a
A little fun around T64.
EDIT: links updated
Last edited by xanad on Sun 23 Aug 2015, 15:18, edited 4 times in total.
[url]http://www.xanad.tk[/url] Html5 Parallax
- James186282
- Posts: 270
- Joined: Tue 08 Sep 2009, 19:14
- Location: Minnesota
Yea!! So glad your back onto Tahrpup 64. I've had it running for a little while on my "free" Dell Dimension E521 and its going pretty good so far. I upgraded to the 6000+ CPU at 3 GHz at the same time so I'm probably going to have too many new things going at once. But so far it works and from the Benchmarking I've done 64 Bit shows improvements in some areas such as 40% faster Raytracing, 14% Blowfish but slower on some of the others. Probably the choice of the Benchmarking software and how it was compiled.
If anyone is interested in a working Module (aka Device Driver) for those AE3000 Cisco / Linksys pods I figured out how to do it. *A real pain to follow a dozen threads all with one piece of the puzzle. If I can figure out how to upgrade GCC to the version used to make this distro I'm going to give the Nvidia Driver a try for my new "box"
I'm running the 64 Bit Firefox and other then problems with extensions it seems to be working ok. And the problem is the folks making the extensions.
I have an actual project (software) and it has to run on a 64 Bit Linux box so THANKYOU!!! for your work. If you have any need for testers and a overall script don't be afraid to shout. Thanks again...
If anyone is interested in a working Module (aka Device Driver) for those AE3000 Cisco / Linksys pods I figured out how to do it. *A real pain to follow a dozen threads all with one piece of the puzzle. If I can figure out how to upgrade GCC to the version used to make this distro I'm going to give the Nvidia Driver a try for my new "box"
I'm running the 64 Bit Firefox and other then problems with extensions it seems to be working ok. And the problem is the folks making the extensions.
I have an actual project (software) and it has to run on a 64 Bit Linux box so THANKYOU!!! for your work. If you have any need for testers and a overall script don't be afraid to shout. Thanks again...
Science is what we understand well enough to explain to a computer.
Art is everything else we do.
[i]Donald Knuth [/i]
Art is everything else we do.
[i]Donald Knuth [/i]
I haven't had success with the chroot in a 32bit filesystem which is an alternative way to use 32bit code in a 64bit filesystem. I think that the kernel should be compiled with this feature (once upon a time there was a flag to be set for ia32-libs in the compilation of the kernel...). The bash shell of this alpha release can't execute the chroot in a 32bit filesystem.
Chroot 32 bit jail in tahr64 using a tahr 6.03 filesystem
Success launching skype in a chroot jail using the xanad's light tahr64 with kernel 4.1.3-EmSee. I have booted tahr 6.03 32 bit, I have unloaded any unwanted sfs and copied on a sdb1 linux formatted usb stick /bin /boot/ /etc /lib /opt /root /sbin /usr /var dirs. I had installed skype by pulseaudio in that filesystem. Then make dirs /dev /proc /sys /mnt /tmp /tmp/.X11-unix on the usb stick and symlink the /run dir to /tmp. Then boot tahr64 with kernel 4.1.3 EmSee. You can launch skype4.3 by the following script (give it execute permissions):
Code: Select all
#!/bin/sh
mount /dev/sdb1 /mnt/sdb1
mount --bind /dev /mnt/sdb1/dev
mount --bind /proc /mnt/sdb1/proc
mount --bind /sys /mnt/sdb1/sys
xhost +
mount --bind /tmp/.X11-unix /mnt/sdb1/tmp/.X11-unix
chroot /mnt/sdb1 skype4.3
umount /mnt/sdb1/tmp/.X11-unix
umount /mnt/sdb1/sys
umount /mnt/sdb1/proc
killall dbus-launch
sleep 10
umount /mnt/sdb1/dev
umount /mnt/sdb1
xhost -
Last edited by watchdog on Sun 30 Aug 2015, 15:08, edited 1 time in total.
Thar_Light-64-k_4.1.3-EmSee_x86-64 by xanad has a misconfiguration of gconf. Edit /usr/share/dbus-1/services/org.gnome.GConf.service to match the following content:
Code: Select all
[D-BUS Service]
Name=org.gnome.GConf
Exec=/usr/lib/libgconf2-4/gconfd-2
new iso uploaded see first post....
the devx and kernel sources are currenly uploading and will be done in about an hour from when this was postedhttp://murga-linux.com/puppy/viewtopic.php?t=96748
the devx and kernel sources are currenly uploading and will be done in about an hour from when this was postedhttp://murga-linux.com/puppy/viewtopic.php?t=96748
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Quick manual frugal install...... no obvious problems yet.
Code: Select all
root# report-video
VIDEO REPORT: tahr64, version 6.0.3.5
Chip description:
VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768x16
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri2 exa extmod fb glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1440x900 pixels (381x238 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
Code: Select all
root# free
total used free shared buffers
Mem: 8065272 960900 7104372 0 96204
-/+ buffers: 864696 7200576
Swap: 8396796 0 8396796
Code: Select all
-Computer-
Processor : 6x AMD FX(tm)-6300 Six-Core Processor
Memory : 8065MB (420MB used)
Machine Type : Physical machine
Operating System : Puppy Linux
User Name : root (root)
Date/Time : Sun Aug 30 17:02:52 2015
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Gallium 0.4 on NVA8
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA ATI SB
Audio Adapter : HDA-Intel - HDA NVidia
Audio Adapter : PC-Speaker - pcsp
tahrpup64 6.0.3.5 beta
I did a manual frugal installation to a 32gb usb 3.0 flash drive, pc is
an HP desktop.
Computer
Processor 6x AMD Phenom(tm) II X6 1045T Processor
Memory 8165MB (294MB used)
Machine Type Physical machine
Operating System Puppy Linux
User Name root (root)
Date/Time Sun Aug 30 19:54:08 2015
Display
Resolution 3840x1080 pixels
OpenGL Renderer Gallium 0.4 on AMD REDWOOD
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA ATI SB
Audio Adapter HDA-Intel - HDA ATI HDMI
Audio Adapter PC-Speaker - pcsp
OpenGL
Vendor X.Org
Renderer Gallium 0.4 on AMD REDWOOD
Version 3.0 Mesa 10.1.3
Direct Rendering Y_es
I added a few applications from PPM.
It's working well so far.
Thanks
an HP desktop.
Computer
Processor 6x AMD Phenom(tm) II X6 1045T Processor
Memory 8165MB (294MB used)
Machine Type Physical machine
Operating System Puppy Linux
User Name root (root)
Date/Time Sun Aug 30 19:54:08 2015
Display
Resolution 3840x1080 pixels
OpenGL Renderer Gallium 0.4 on AMD REDWOOD
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA ATI SB
Audio Adapter HDA-Intel - HDA ATI HDMI
Audio Adapter PC-Speaker - pcsp
OpenGL
Vendor X.Org
Renderer Gallium 0.4 on AMD REDWOOD
Version 3.0 Mesa 10.1.3
Direct Rendering Y_es
I added a few applications from PPM.
It's working well so far.
Thanks
- Attachments
-
- screenshot.jpg
- (74.63 KiB) Downloaded 970 times
Hi Phil
Mostly running ok. Good job.
Nice to see netmon_wce make an appearance.
Some oddities though. Why the ancient version of dir2pet? The current one supports xz compression, this one doesn't. (BTW, the advancecomp bug was squashed ages ago).
JWM themes need to be updated. The xslt method in Joe's docs works. I did have a script somewhere but can't find it at the moment. Will post when found.
I notice a few library conflicts, jpeg v8 and v9.
png v1.2.50 and v1.4.17beta
This might cause other issues, can't be sure.
@james C. I see your retrovol doesn't show up (coz it's black and bg is black). I have patched retrovol so that you can choose the icon colour from the 'Config Window'. Once chosen the first time retrovol needs to be restarted. After that the colour will change in an instant. This is because it writes the icons to $HOME instead of /usr/share/retrovol. I did this so it is multiuser friendly. Source is at my github https://github.com/01micko/retrovol/tree/speaker.
I'll attach a pet compiled in tahr64.
Mostly running ok. Good job.
Nice to see netmon_wce make an appearance.
Some oddities though. Why the ancient version of dir2pet? The current one supports xz compression, this one doesn't. (BTW, the advancecomp bug was squashed ages ago).
JWM themes need to be updated. The xslt method in Joe's docs works. I did have a script somewhere but can't find it at the moment. Will post when found.
I notice a few library conflicts, jpeg v8 and v9.
Code: Select all
gcc -O2 -Wall -pipe -lXpm -ljpeg -lpng12 -ltiff -o xonclock xonclock.o placement.o cache.o parse.o image.o pmdesktop.o png.o jpeg.o tiff.o -lpthread -lXpm -ltiff -ljpeg -lpng -lXft -lXext -lX11 -lXrender -lm
/usr/bin/ld: warning: libjpeg.so.8, needed by /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../x86_64-linux-gnu/libtiff.so, may conflict with libjpeg.so.9
Code: Select all
root# ./xonclock
xonclock-0.0.9.3: parse.c:117 Unable to open config file: /root/.xonclockrc
libpng warning: Application was compiled with png.h from libpng-1.2.50
libpng warning: Application is running with png.c from libpng-1.4.17beta02
libpng warning: Incompatible libpng version in application and library
xonclock-0.0.9.3: loaders/png.c:101 libpng error catched
Segmentation fault
@james C. I see your retrovol doesn't show up (coz it's black and bg is black). I have patched retrovol so that you can choose the icon colour from the 'Config Window'. Once chosen the first time retrovol needs to be restarted. After that the colour will change in an instant. This is because it writes the icons to $HOME instead of /usr/share/retrovol. I did this so it is multiuser friendly. Source is at my github https://github.com/01micko/retrovol/tree/speaker.
I'll attach a pet compiled in tahr64.
- Attachments
-
- config-tray_tab.png
- (34.63 KiB) Downloaded 963 times
-
- retrovol.png
- (6.79 KiB) Downloaded 961 times
-
- retrovol-14.1-1-x86_64.pet
- for tahr64 only
- (38.42 KiB) Downloaded 219 times
Puppy Linux Blog - contact me for access