woof-CE needs you

Message

Sailor Enceladus · #991 Post by **Sailor Enceladus** » Mon 03 Jul 2017, 04:12

belham2 wrote:P.S. Nobody liked our thread about "memory lane" projects . Thought for sure others would post and talk about whatever old pup they still keep around & running. Oh well, what's that saying: "Those who forget the past are doomed to repeat it"

Well said belham2.

greengeek · #992 Post by **greengeek** » Mon 03 Jul 2017, 07:18

belham2 wrote: Nobody liked our thread about "memory lane" projects . Thought for sure others would post and talk about whatever old pup they still keep around & running. Oh well, what's that saying: "Those who forget the past are doomed to repeat it"

Hi Bedlam - can you post a link to that thread please? cheers!

James C · #993 Post by **James C** » Mon 03 Jul 2017, 07:39

greengeek wrote:
belham2 wrote: Nobody liked our thread about "memory lane" projects . Thought for sure others would post and talk about whatever old pup they still keep around & running. Oh well, what's that saying: "Those who forget the past are doomed to repeat it"
Hi Bedlam - can you post a link to that thread please? cheers!

http://www.murga-linux.com/puppy/viewto ... 481#958481

greengeek · #994 Post by **greengeek** » Mon 03 Jul 2017, 08:03

Ta JC - much obliged.

Sailor Enceladus · #995 Post by **Sailor Enceladus** » Mon 03 Jul 2017, 18:41

I tried another "slacko-current" woof-CE build with Seamonkey (it didn't need gtk3). The adrv adds some missing libs from 14.2

https://www.mediafire.com/folder/kldh509odczdb/current (Mirror)

BarryK · #996 Post by **BarryK** » Sat 08 Jul 2017, 14:24

Hi guys,
Someone might want to consider this insertion for 0setup:

http://barryk.org/news/?viewDetailed=00589

Note, I don't commit to woof-CE, as since I retired from the frontline of Puppy development, I don't want to be seen as interfering, or as trying to get back behind the drivers wheel, so to speak.

So, the link has a suggestion, for anyone who wants to investigate it.

belham2 · #997 Post by **belham2** » Sat 08 Jul 2017, 17:10

BarryK wrote:Hi guys,
Someone might want to consider this insertion for 0setup:

http://barryk.org/news/?viewDetailed=00589

Note, I don't commit to woof-CE, as since I retired from the frontline of Puppy development, I don't want to be seen as interfering, or as trying to get back behind the drivers wheel, so to speak.

So, the link has a suggestion, for anyone who wants to investigate it.

Dam#, I am slapping my forehead reading Barry's link....suddenly, some of the un-explained "why didn't the correct package get built- in" when using the Ubuntu-based woof-CE builds now makes sense. I am going to do a few new ubuntu-woof-CE-builds after first inserting Barry's code in 0setup--will try the insertion where he suggests and also in a couple of different places in the script, and see what happens. Thanks, Barry!

BarryK · #998 Post by **BarryK** » Sat 08 Jul 2017, 23:46

belham2 wrote:
BarryK wrote:Hi guys,
Someone might want to consider this insertion for 0setup:

http://barryk.org/news/?viewDetailed=00589

Note, I don't commit to woof-CE, as since I retired from the frontline of Puppy development, I don't want to be seen as interfering, or as trying to get back behind the drivers wheel, so to speak.

So, the link has a suggestion, for anyone who wants to investigate it.

Dam#, I am slapping my forehead reading Barry's link....suddenly, some of the un-explained "why didn't the correct package get built- in" when using the Ubuntu-based woof-CE builds now makes sense. I am going to do a few new ubuntu-woof-CE-builds after first inserting Barry's code in 0setup--will try the insertion where he suggests and also in a couple of different places in the script, and see what happens. Thanks, Barry!

While you're at it, here is another one to consider. I posted about a bug in /etc/rc.d/0setup that on certain hardware can cause a hang at bootup, or a delay:

http://barryk.org/news/?viewDetailed=00586

woof-CE still has the offending line, or what I think is the cause, at line 761:
https://github.com/puppylinux-woof-CE/w ... rc.sysinit

rufwoof · #999 Post by **rufwoof** » Wed 12 Jul 2017, 22:08

I used WoofCE for the first time since quite a while ago (with little success back then). This time, first run failed as I tried to be clever and opt for likely inappropriate choices. Second time I used the example 'defaults' choice and built tahr 32bit pae which is running great (I went for one of the oldest kernels for that ... so a bit outdated). Today I've build tahr 6.0.6 amd64 with a 4.1.11 kernel. That's also running as well, initially the fonts were a bit 'off' (not as clear/smooth as the 32bit version, but after a lot of trying different things they came good). Todays WoofCE run took around 40 minutes total build time running on a 10 year old amd phenom 4 core with 2GB (internet down link speed of around 80Mb/sec). The final folder content size is showing just under 6GB of disk space used that includes the iso and devx sfs.

Really neat. And simple enough for the likes of me to use. Thanks.

mavrothal · #1000 Post by **mavrothal** » Thu 13 Jul 2017, 08:07

rufwoof wrote:Really neat. And simple enough for the likes of me to use.

You might be interested in the woof-next branch of woof-CE.
Is building a "puppy" much closer to upstream (with apt-get and everything!) which you may prefer.
Currently is at alpha/early beta stage as Jamesbond stopped working on it a couple of years now. However, if someone shows interest and asks informed, constructive questions, I think he may be willing to help.

Sailor Enceladus · Fri 14 Jul 2017, 03:21

I tried making a template for squashfs-tools (3), but every time I run ./2createpackages and type squashfs-tools, woof-CE ignores my template and just extracts the pet without running it. I tried both using FIXUPHACK and an executable pinstall.sh. The packages-slacko/squash-tools_manual shows what it's supposed to do, does anyone know why the template is ignored?

(the reason why I made this is because sfs-converter expects mksquashfs3, unsquashfs3, mksquashfs4, and unsquashfs4 all to exist to work - see /usr/local/sfsconvert/func. At some point it looks like there was a script that fixed this in 3builddistro).

Sailor Enceladus · Fri 14 Jul 2017, 14:55

I got the template to work, by copying lines 854-871 into line 278 in 2createpackages. Guessing there is a better way though..

rufwoof · #1003 Post by **rufwoof** » Fri 14 Jul 2017, 16:21

mavrothal wrote:You might be interested in the woof-next branch of woof-CE.
Is building a "puppy" much closer to upstream (with apt-get and everything!) which you may prefer.

Thanks mavrothal. Only just got woof-CE to work for me for the first time (tried some years back with no success). Tahr 6.0.6 is working great and looking good for me so I'm content to stick with that. I had been trying out freebsd where you can build everything from source or just download pre-build binaries using pkg install (which is like Debian's apt-get install), but I'm ditching that as its just too time intensive to get things going (lots of reading, nothing pre-configured after you install ...etc.). Very nice looking though and works great when it is all running ok.

I have been booting both debian jessie and freebsd as my main primary boot choices. Debian Jessie's a long term keeper for me, however tahr pup is so neat that its tending to becoming the grub4dos menu.lst default boot

(Especially since I've now managed to get woofce to work for me as expected).

BarryK · #1004 Post by **BarryK** » Sat 15 Jul 2017, 02:07

Sailor Enceladus wrote:I tried making a template for squashfs-tools (3), but every time I run ./2createpackages and type squashfs-tools, woof-CE ignores my template and just extracts the pet without running it. I tried both using FIXUPHACK and an executable pinstall.sh. The packages-slacko/squash-tools_manual shows what it's supposed to do, does anyone know why the template is ignored?

(the reason why I made this is because sfs-converter expects mksquashfs3, unsquashfs3, mksquashfs4, and unsquashfs4 all to exist to work - see /usr/local/sfsconvert/func. At some point it looks like there was a script that fixed this in 3builddistro).

I don't know if it is still the case with woof-CE, but the templates only work on packages from the host distro, not on PETs.
PETs are expected to be already optimised and split up into _DEV etc.

Billtoo · #1005 Post by **Billtoo** » Sun 23 Jul 2017, 19:20

I did a build yesterday, burned the iso to a DVD and booted from it.
Used the puppy installer to a 32gb flash drive.

# inxi -b
System: Host: puppypc20509 Kernel: 4.4.78-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: ACER product: Aspire M5620 v: R01-A4 serial: PTS860X0348050CF642700
Mobo: ACER model: G33T-AM v: 1.0 serial: 00000000 BIOS: American Megatrends v: R01-A4 date: 12/19/2007
CPU: Quad core Intel Core2 Quad Q6600 (-MCP-) speed/max: 1603/2403 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.org 1.18.3 driver: nvidia tty size: 150x41 Advanced Data: N/A for root
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 31.5GB (10.7% used)
Info: Processes: 180 Uptime: 1:17 Memory: 274.9/8097.6MB Client: Shell (bash) inxi: 2.3.8
#

Updated PPM,applied the update notices with PPM,installed latest
Firefox and others with PPM + added Smplayer and Smtube.
Added proprietary Nvidia driver.

Working well so far.

*****************************************************************
EDIT: I did a second build with a different kernel.
# inxi -b
System: Host: puppypc21521 Kernel: 4.9.39-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: Hewlett-Packard product: HPE-410f serial: MXX0370KF3
Mobo: FOXCONN model: 2AB1 v: 1.00 BIOS: American Megatrends v: 6.02 date: 07/21/2010
CPU: Hexa core AMD Phenom II X6 1045T (-MCP-) speed/max: 800/2700 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570]
Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 161x36 Advanced Data: N/A for root
Network: Card-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 1126.5GB (0.8% used)
Info: Processes: 195 Uptime: 6:31 Memory: 321.9/8091.6MB Client: Shell (bash) inxi: 2.3.8
#
It works well.

sc0ttman · #1006 Post by **sc0ttman** » Tue 01 Aug 2017, 21:04

I've tried to build a 32-bit Slacko 6.9.9.9, using kernel 4.4 (choice number 24 in the Kernel chooser)..

I simply tried to build a Slacko 6.9.9.9 RC3, by using the latest Woof snapshot, with al ldefault options.

I also used an older one from a few weeks back.. Both times I have not been able to boot to X .. I get a 'no screens found message'..

The latest Woof-CE snapshot gave me a 'xorgwizard-automatic not found' error (line 117 of xwin I think), and the second and third builds I did using slightly older Woofs did not have this error message, but they still could not boot to X ..

I tried every option in xorgwizard, and am able to get a desktop on other pups on the same hardware..

Any ideas?

Billtoo · #1007 Post by **Billtoo** » Tue 01 Aug 2017, 21:24

@sc0ttman

Try the rationalise branch, it's the one that I used last.

sc0ttman · #1008 Post by **sc0ttman** » Wed 02 Aug 2017, 09:28

Billtoo wrote:@sc0ttman

Try the rationalise branch, it's the one that I used last.

ok will do, cheers

mavrothal · #1009 Post by **mavrothal** » Wed 02 Aug 2017, 09:31

sc0ttman wrote:I simply tried to build a Slacko 6.9.9.9 RC3, by using the latest Woof snapshot, with al ldefault options.

6.9.9.9 was build with woof 126 commits earlier than the current snapshot.
It shouldn't, but something may have broken the slacko build since.
Try to clone the entire git repo and then

Code: Select all

git checkout 762210b829267e394fe69ae109adf9587dcdf39a #the commit 6.9.9.9 was build from

Or if you do not want to clone the entire git browse to the said commit and download from there.
If this builds OK file a bug in github
BTW, rationalize is just 14 commits behind testing. No other difference. If this works that narrows down the bug a lot.

norgo · #1010 Post by **norgo** » Wed 02 Aug 2017, 10:12

The day before yesterday I built a Slacko 6.9.9.9 RC3 too ( testing branch of 2017-07-31 ) and also chose kernel 4.4.70 PAE

Everything went without problems and Distro is working great.
Thanks for this awesome work.

# inxi -b
System: Host: puppypc28875 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: ASRock model: H87 Pro4 serial: M80-xxxxxxxxxxx
BIOS: American Megatrends v: P1.90 date: 12/06/2013
CPU: Quad core Intel Core i7-4770S (-HT-MCP-) speed/max: 800/3101 MHz
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 163x52 Advanced Data: N/A for root
Network: Card: Intel Ethernet Connection I217-V driver: e1000e
Drives: HDD Total Size: 2000.4GB (0.1% used)
Info: Processes: 190 Uptime: 1:17 Memory: 505.5/15863.1MB Client: Shell (bash) inxi: 2.3.8

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

woof-CE needs you

woof-CE needs you

trying woof

Re: trying woof