Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 15 Dec 2017, 12:21
All times are UTC - 4
 Forum index » Taking the Puppy out for a walk » Announcements
woof-CE needs you
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 69 of 81 [1213 Posts]   Goto page: Previous 1, 2, 3, ..., 67, 68, 69, 70, 71, ..., 79, 80, 81 Next
Author Message
Billtoo


Joined: 07 Apr 2009
Posts: 3296
Location: Ontario Canada

PostPosted: Thu 03 Aug 2017, 09:03    Post subject:  

mavrothal wrote:
If X tried to start and failed should produce a /var/log/Xorg.0.log file. Also the /initrd/tmp/dmesg.txt file could be informative and maybe the /initrd/tmp/bootinit.log file


@norgo had success with his testing branch iso so I burned the one from
my new woof-CE testing branch (yesterday afternoon) to a DVD and tried
it on a pc with intel graphics (X wouldn't start on my HP ATI Radeon)
and it works.
I'm booting from the DVD with a save file on the hard drive.

# inxi -bw
System: Host: puppypc27878 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop Mobo: Acer model: Aspire X3950 serial: U02C120500059
BIOS: American Megatrends v: P01-A3 date: 05/05/2010
CPU: Dual core Intel Core i3 540 (-HT-MCP-) speed/max: 1333/3067 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 144x40 Advanced Data: N/A for root
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives: HDD Total Size: 532.1GB (4.0% used)
Weather: Conditions: 68 F (20 C) - Partly Cloudy Time: August 3, 8:46 AM EDT
Info: Processes: 179 Uptime: 3 min Memory: 288.0/5997.2MB Client: Shell (bash) inxi: 2.3.8
#
I'll try booting the DVD on the Gateway which has Nvidia graphics and
see how that goes.

EDIT: The DVD boots to the desktop on the Gateway but the resolution is wrong and the mouse is dead,ctrl-alt-backspace does nothing.

So recent commits have caused problems with Radeon and Nvidia graphics on my hardware.
screenshot.jpg
 Description   
 Filesize   31.78 KB
 Viewed   1299 Time(s)

screenshot.jpg

Back to top
View user's profile Send private message 
sc0ttman


Joined: 16 Sep 2009
Posts: 2548
Location: UK

PostPosted: Thu 03 Aug 2017, 10:44    Post subject:  

Have built a slacko pup (32-bit, kernel 4.4, which is number 24 in the list during woof build)

It boots from CD and USB, all the way to desktop on a Dell Optiplex GX-something, which has on-board Intel gfx, and also boots to desktop on my main PC (with AMD radeon 7750 gfx) ..

Am using it now.. Works very nicely..

This is from the /etc/DISTRO_SPECS
Code:
BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'


inxi - bw
Code:
System:    Host: puppypc28490 Kernel: 4.4.70 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slak Puppy 6.9.11
Machine:   Device: desktop Mobo: ASRock model: FM2A75 Pro4 serial: E80-37025800032
           BIOS: American Megatrends v: P2.40 date: 07/11/2013
CPU:       Quad core AMD Athlon X4 750K (-MCP-) speed/max: 1400/3400 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
           Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           tty size: 211x64 Advanced Data: N/A for root
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Drives:    HDD Total Size: 2016.6GB (4.9% used)
Weather:   Conditions: 68 F (20 C) - Mostly Cloudy Time: August 3, 3:58 PM BST
Info:      Processes: 190 Uptime: 1:26 Memory: 563.8/16171.5MB Client: Shell (bash) inxi: 2.3.8


For reference, the previous errors (now gone in 6e9bb39?) were "missing xorgwizard-automatic, line 113 of xwin" in one very recent build, and missing "FreeSans" font errors in a slightly older one... I had those errors on both machines mentioned above, and in a VM.

... Now some general observations..

1. Is the missing fonts message that prevented my desktop loading up (in previous builds) related to not including pTheme?

2. JWM is crap at working out 2 monitors, and moving them around is a real pain - compared to the drag and drop UI that Xfce provides.. Any way round this? Zarfy, maybe?

3. Does the Universal Pup Installer insist on overwriting the MBR of every drive/disk that uses GRUB? (or is it just me?)... Seems every time I try to use the Universal Installer, it insists I replace my MBR with mbr.bin (or other).. Can the Universal installer not work out I have a working GRUB, just leave the MBR?

4. IIRC, the Grub4DosConfig app doesn't backup the menu-adv.lst file, only the menu.lst file..

5. Where is the documentation about adding new petbuilds and pet packages to Woof? I want to create a new branch and make it build an Xfce pup (ideally... baby steps)..

6. I've noticed that none of the following keys works as they should in Urxvt: Crtl-Left, Ctrl-Right, Home key, End key ... Should this be fixed in /etc/profile, or ~/.bashrc? i'm pretty sure i've got a puppy bashrc with all these fixes in it somewhere if anyone would prefer them working in woof-built pups..

7. How does having an Fdrv and a Ydv affect the zdrv-cutter thing? .. It that still a thing? Can't find it in my newly woofed pup..

_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 3296
Location: Ontario Canada

PostPosted: Thu 10 Aug 2017, 09:38    Post subject: woof-CE needs you  

I did a fresh install of woof-CE testing branch then a new build:

# inxi -bw
System: Host: puppypc4675 Kernel: 4.4.80-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: laptop System: Acer product: Aspire 7740 v: Rev serial: LXPNX02012004098672000
Mobo: Acer model: Aspire 7740 v: Rev serial: LXPNX02012004098672000
BIOS: Phoenix v: V1.15 date: 12/25/2009
Battery BAT0: charge: 44.0 Wh 100.0% condition: 44.0/44.0 Wh (100%)
CPU: Dual core Intel Core i5 M 430 (-HT-MCP-) speed/max: 1199/2267 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470]
Display Server: X.org 1.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 131x37 Advanced Data: N/A for root
Network: Card-1: Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCIe driver: tg3
Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k
Drives: HDD Total Size: 540.0GB (1.9% used)
Weather: Conditions: 68 F (20 C) - Overcast Time: August 10, 9:25 AM EDT
Info: Processes: 187 Uptime: 1:22 Memory: 222.1/3902.9MB Client: Shell (bash) inxi: 2.3.8
#

Running from a 32gb SDHC card on Acer laptop.

Works good, thanks for the fix.
******************************************************************
EDIT:
Same woof-CE version,new build:

# inxi -bw
System: Host: puppypc12471 Kernel: 4.4.83-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: 163x30 Advanced Data: N/A for root
Network: Card: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Drives: HDD Total Size: 31.9GB (10.3% used)
Weather: Conditions: 75 F (24 C) - Mostly Cloudy Time: August 17, 11:49 AM EDT
Info: Processes: 193 Uptime: 51 min Memory: 690.0/8097.6MB Client: Shell (bash) inxi: 2.3.8
#

Works well so far.
screenshotaug17.jpg
 Description   
 Filesize   77.05 KB
 Viewed   859 Time(s)

screenshotaug17.jpg

screenshot.jpg
 Description   
 Filesize   94.62 KB
 Viewed   1054 Time(s)

screenshot.jpg


Last edited by Billtoo on Thu 17 Aug 2017, 11:56; edited 1 time in total
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1327

PostPosted: Thu 10 Aug 2017, 17:46    Post subject:  

sc0ttman wrote:
6. I've noticed that none of the following keys works as they should in Urxvt: Crtl-Left, Ctrl-Right, Home key, End key ... Should this be fixed in /etc/profile, or ~/.bashrc? i'm pretty sure i've got a puppy bashrc with all these fixes in it somewhere if anyone would prefer them working in woof-built pups..

If Ctrl-Left and Ctrl-Right are the keys that switch you to a different virtual window I've always found that shortcut just annoying. I'll be playing a game and the desktop will randomly switch to a different one where my game isn't on instead of doing what it's suppose to inside the game. I think it was Tahrpup that had this issue, as I remember the "pink square" moving left and right when my screen disappeared. Might have been Alt-Left/Right though, haven't experienced the issue for a while now.
Back to top
View user's profile Send private message 
belham2

Joined: 15 Aug 2016
Posts: 1362

PostPosted: Thu 17 Aug 2017, 11:16    Post subject:  

The Slacko64-6.9.9.9 frugal-install the I use a few times a week has started to display helter-skelter behavior (freezing screens, programs randomly refusing to open, etc) . Don't understand as everything was running great for a few months, with no new add-ons (or anything) have been applied to this latest release. Only thing that has changed is that I like to plug the USB drive that has all these frugal-installs into many of my different machines here-----and this new Slacko64-6.9.9.9 does not like this one bit.

Sure is a stark contrast on things when I throw Sailor E's slacko 5.7 build (into any machine) and everything just stinking runs like wildfire, no matter what I've thrown at it, I can't even get it to hiccup (and I've been doing crazy qt stuff with it, lol). Maybe I need newer systems to reliably run all of Micko's later creations; makes me sad Crying or Very sad Wife won't be having any of that soon, unfortunately. My newest hardware is 6 yrs old (i3 laptop), and the others are 8-19 yrs old (the oldest being a Pentium 2.0 I try to keep going, lol, and it does have a 1GB of ram, in its defense of staying relevant).
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 3296
Location: Ontario Canada

PostPosted: Sat 19 Aug 2017, 11:02    Post subject: woof-CE needs you  

I did a new build using the Aug 10th woof-CE:

# inxi -bw
System: Host: puppypc21732 Kernel: 4.9.44 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 1600/2500 MHz
Graphics: Card: Intel 82G33/G31 Express Integrated Graphics Controller
Display Server: X.org 1.18.3 driver: intel tty size: 139x36 Advanced Data: N/A for root
Network: Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 500.1GB (10.8% used)
Weather: Conditions: 70 F (21 C) - Mostly Cloudy Time: August 19, 10:51 AM EDT
Info: Processes: 158 Uptime: 4 min Memory: 262.1/4025.6MB Client: Shell (bash) inxi: 2.3.8
#

It wouldn't boot to the desktop on a computer with radeon graphics but
it did on this pc with intel graphics.

Seems that the fix only applied to the 4.4 kernel and not the 4.9
kernel.

It's working okay apart from that.
screenshot.jpg
 Description   
 Filesize   127.29 KB
 Viewed   746 Time(s)

screenshot.jpg

Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 3296
Location: Ontario Canada

PostPosted: Sun 20 Aug 2017, 03:02    Post subject: woof-CE needs you  

I did a fresh install of woof-CE rationalise branch (aug 20th) and a
new build:

# inxi -bw
System: Host: puppypc32216 Kernel: 4.4.83-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 2000/2500 MHz
Graphics: Card: Intel 82G33/G31 Express Integrated Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 162x40 Advanced Data: N/A for root
Network: Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 562.5GB (9.9% used)
Weather: Conditions: 63 F (17 C) - Clear Time: August 20, 2:53 AM EDT
Info: Processes: 162 Uptime: 1:17 Memory: 685.1/4026.6MB Client: Shell (bash) inxi: 2.3.8
#

Fewer things to update when Updates notices - Slackware bugfixes is
run.
Firefox 52.3.0 ESR is included and works well.

No problems so far.
*************************************************************************
EDIT: I've done a fresh install of woof-CE testing branch (aug 20th) and a build:

# inxi -bw
System: Host: puppypc6136 Kernel: 4.9.44 i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 1600/2500 MHz
Graphics: Card: Intel 82G33/G31 Express Integrated Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 158x35 Advanced Data: N/A for root
Network: Card: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 562.5GB (10.2% used)
Weather: Conditions: 73 F (23 C) - Partly Cloudy Time: August 20, 1:34 PM EDT
Info: Processes: 152 Uptime: 1:53 Memory: 208.5/4025.6MB Client: Shell (bash) inxi: 2.3.8
#
The result is pretty much the same as the rationlise branch, it's working well.
screenshot.jpg
 Description   
 Filesize   94.78 KB
 Viewed   639 Time(s)

screenshot.jpg

screenshot.jpg
 Description   
 Filesize   104.2 KB
 Viewed   687 Time(s)

screenshot.jpg

Back to top
View user's profile Send private message 
sc0ttman


Joined: 16 Sep 2009
Posts: 2548
Location: UK

PostPosted: Mon 21 Aug 2017, 08:20    Post subject:  

Hi guys,

Is it the expected/desired behaviour that the ~/.packages/builtin_files/pkgname files ONLY contain dirs (not the actual files of the package) whenever the pkg is in ADRV?

Example, I built a woof Slacko with Abiword and Gnumeric in the ADRV... and now their respective ~/.packages/builtin_files/* contain only this:

# cat ~/.packages/builtin_files/gnumeric
/usr
/usr/bin
/usr/lib
/usr/share
/usr/share/applications
/usr/share/icons
/usr/share/icons/hicolor
/usr/share/icons/hicolor/16x16
/usr/share/icons/hicolor/16x16/apps
/usr/share/icons/hicolor/22x22
/usr/share/icons/hicolor/22x22/apps
/usr/share/icons/hicolor/24x24
/usr/share/icons/hicolor/24x24/apps
/usr/share/icons/hicolor/32x32
/usr/share/icons/hicolor/32x32/apps
/usr/share/icons/hicolor/48x48
/usr/share/icons/hicolor/48x48/apps
/usr/share/icons/hicolor/scalable
/usr/share/icons/hicolor/scalable/apps
/usr/share/pixmaps


Is that a bug?

Also, why don't the built-in pkg file lists contain full file paths on each line, like in the ~/.packages/*.files of user installed packages? Is there a reason?

Seems very "pre-woof" .... Would make more sense if user pkgs and built-in pkgs listed their files in the same format...

I'm trying to write a command line package manager for puppy, and finding out the contents of built-in packages becomes very messy indeed because of these 2 problems -> when a file is in two packages (/usr/bin/gnumeric and /etc/file/gnumeric), trying to work out which pkg the file comes from starts to be a real pain if any of those files come from a pkg that lives in the ADRV..

(Sorry if this is the wrong place to post! ... And thanks for all the great work on puppy and woof-CE!)

EDIT: BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'

_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search

Last edited by sc0ttman on Mon 21 Aug 2017, 14:04; edited 1 time in total
Back to top
View user's profile Send private message 
sc0ttman


Joined: 16 Sep 2009
Posts: 2548
Location: UK

PostPosted: Mon 21 Aug 2017, 13:24    Post subject:  

On my woofed 32-bit slacko ... BUILD_FROM_WOOF='testing;6e9bb39;2017-07-31 17:43:50 +0800'


Youtube-dl fails as it can't find Python3 interpreter after install .. PPM reports no missing deps.. (as does my pkg manager).. the repo db dependency entries might need fixing..?

Code:
#  youtube-dl
bash: /usr/bin/youtube-dl: /usr/bin/python3: bad interpreter: No such file or directory


Package file: youtube-dl-2016.08.22-i586-1salix.txz (2.1MB)
From salix repo

_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1327

PostPosted: Tue 22 Aug 2017, 13:34    Post subject:  

belham2 wrote:
Sure is a stark contrast on things when I throw Sailor E's slacko 5.7 build (into any machine) and everything just stinking runs like wildfire, no matter what I've thrown at it, I can't even get it to hiccup (and I've been doing crazy qt stuff with it, lol).

Thanks Belham! I'm using it as my main OS too. I tried making another 14.0 build at commit 5506 with kernel 3.18.66. Might upload it later, although this one is missing a few more deps that will probably need to be resolved or re-added to adrv first.

sc0ttman wrote:
Seems very "pre-woof"

I think that's a little harsh since the adrv feature is still pretty new. Your feedback is possibly useful though.

P.S. Are you planning on making a new Puppy Arcade? That seems to be a quite popular puppy still and a neat concept. Smile
Back to top
View user's profile Send private message 
sc0ttman


Joined: 16 Sep 2009
Posts: 2548
Location: UK

PostPosted: Thu 24 Aug 2017, 11:01    Post subject:  

Quote:
sc0ttman wrote:
Seems very "pre-woof"

I think that's a little harsh since the adrv feature is still pretty new. Your feedback is possibly useful though.

P.S. Are you planning on making a new Puppy Arcade? That seems to be a quite popular puppy still and a neat concept. Smile

I'm one of the worst offenders for producing 'pre-woof' mess... So no offence intended obvs..

And I will possibly do it, If I make a new one, I will use some sleek frontend like EmuStation as a frontend to my frontend (Rom-Loader) ... That will do away with the old-school, clunky GTK interface, but will retain all the features of Rom-Loader (custom configs per ROM, etc) .. Just needs better bluetooth gamepad support for PS3, PS4, XBOX360 etc ... But I doubt anyone is interested by now and I'm waiting on a job application, so dunno whats next .. Depends.. We will see..

_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9682
Location: Charleston S.C. USA

PostPosted: Thu 24 Aug 2017, 12:27    Post subject:  

belham2 wrote:
The Slacko64-6.9.9.9 frugal-install has started to display helter-skelter behavior (freezing screens, programs randomly refusing to open, etc) . Don't understand as everything was running great for a few months, I like to plug the USB drive that has all these frugal-installs into many of my different machines here-----and this new Slacko64-6.9.9.9 does not like this one bit.

Maybe I need newer systems to reliably run all of Micko's later creations. My newest hardware is 6 yrs old.

The newest Linux 4 series kernels do seem to be a little buggy.
Finding one that is well bug fixed is an issue.
01micko has said, it has been one of the issues, he has been trying to overcome, in final releasing Slacko 7.0
Linux kernel 4 series seems more about providing support for the newer or newest hardware and not trying to support old hardware.

Example:
I have a very new computer with latest hardware.
Any of the Puppies using kernel 3 versions just do not have full 100% support for the hardware.
Kernel 4 versions do give me 100% hardware support.

The latest Puppy versions including Slacko 6.9.9.9 can easily change to using a different (older) kernel.
The ability is built in.

In a console enter:
Code:
change_kernels

This is the program to use to change to using a different kernel.

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 3296
Location: Ontario Canada

PostPosted: Thu 24 Aug 2017, 13:48    Post subject: woof-CE needs you  

I did a build from the woof-CE testing branch of Aug 20th, it's running
on my Acer touchscreen laptop:

# inxi -bw
System: Host: puppypc27047 Kernel: 4.4.83-pae i686 (32 bit) Desktop: JWM 2.3.2 Distro: Slacko Puppy 6.9.9.9
Machine: Device: laptop System: Acer product: Aspire V5-571P v: V2.17 serial: NXM49AA03531512EC36600
Mobo: Acer model: Aspire V5-571P v: V2.17 serial: NBM491100831501E946600
UEFI [Legacy]: Phoenix v: V2.17 date: 02/27/2013
Battery BAT0: charge: 20.1 Wh 99.0% condition: 20.3/25.0 Wh (81%)
CPU: Dual core Intel Core i3-3227U (-HT-MCP-) speed/max: 800/1901 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.org 1.18.3 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 113x35 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Broadcom Limited BCM43228 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 500.1GB (6.7% used)
Weather: Conditions: 66 F (19 C) - Mostly Cloudy Time: August 24, 1:29 PM EDT
Info: Processes: 180 Uptime: 1:28 Memory: 218.6/5865.7MB Client: Shell (bash) inxi: 2.3.8
#

The touchscreen works, no problems so far.
screenshot.jpg
 Description   
 Filesize   109.29 KB
 Viewed   327 Time(s)

screenshot.jpg

Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 375
Location: not Bulgaria

PostPosted: Sat 26 Aug 2017, 10:20    Post subject:  

Single script to auto-build an official woof-CE pup:

http://www.murga-linux.com/puppy/viewtopic.php?p=965541#965541

wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 375
Location: not Bulgaria

PostPosted: Wed 30 Aug 2017, 05:44    Post subject:  

saintless wrote:
peebee wrote:
I'm not sure it's that simple (but that may be my lack of understanding) as I think the kernel has to be built with all the patches for aufs - this is what kernel-kit in woof-ce does to build the Puppy kernels.......

Hi peebee.

The standard Debian/Ubuntu kernel should have all patches needed to boot with aufs. Debian-live also uses aufs (and also options to boot with unionfs and now overlayfs).
But seems someone already did this in woof-ce even without aufs:
https://github.com/puppylinux-woof-CE/woof-CE/commit/d8c8b865cc3ead465fd54fcf9e4d1381958a516e


Yes, the woof-CE 3builddistro-Z script sources support/kernel_pkg.sh if kernel provided comes packaged as a pet, deb, tgz, or txz:

Code:
case "$KERNEL_TARBALL_URL" in *.pet|*.deb|*.tgz|*.txz) KPKG=yes  ;; esac

if [ "$KPKG" = "yes" ] ; then
   # kernel pet/deb/txz/tgz
   . ../support/kernel_pkg.sh


and the controlling _00build.sh contains:

Code:
## Kernel tarball URL
## avoid being asked questions about downloading/choosing a kernel
#KERNEL_TARBALL_URL=xxx


where xxx can be a link to say a debian package kernel such as:

http://http.us.debian.org/debian/pool/main/l/linux/linux-image-4.9.0-0.bpo.3-686-pae_4.9.30-2+deb9u2~bpo8+1_i386.deb

The contents of that end up being copied into Puppy z drive (which I presume can be read by Puppy initrd (I haven't checked that). However, the initrd-progs/0initrd/sbin/not_a_huge_kernel_stuff code you refer to doesn't seem to be sourced by the 3builddistro-Z script as yet so aufs will not be working with such a kernel (the kernel contents are themselves extracted in kernel_pkg.sh and moved into the z drive):

Code:
case $KERNELPKG in
   *.pet)
      rm -f $KERNELPKG
      KERNPKGNAMEONLY="`basename $KERNELPKG .pet`"
      rm -rf $KERNPKGNAMEONLY
      cp ../kernel_pkgs/${KERNELPKG} ./
      pet2tgz $KERNELPKG
      tar -xf $KERNPKGNAMEONLY.tar.?z
      rm -rf zdrv/
      mv -f $KERNPKGNAMEONLY zdrv/
      ;;
   #*.txz|*.tgz) #TODO
   *.deb)
      dpkg-deb -x ../kernel_pkgs/${KERNELPKG} zdrv 1>/dev/null
      ;;
esac

mv -f zdrv/etc/modules/firmware.dep zdrv/etc/modules/firmware.dep.${KERNELVER}


I haven't actually tested if what I say is correct, but that is my reading of the current woof-CE-testing scripts situation. I'm certainly looking forwards to the code currently being stored in not_a_huge_kernel_stuff being implemented since woof-CE stretch building users seem to do a lot of fluffing about finding kernels to use when it would be so much more convenient (and secure maybe) to be able to simple use a stock kernel in Puppy like you have suggested Toni.

wiak
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 69 of 81 [1213 Posts]   Goto page: Previous 1, 2, 3, ..., 67, 68, 69, 70, 71, ..., 79, 80, 81 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Taking the Puppy out for a walk » Announcements
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1234s ][ Queries: 15 (0.0322s) ][ GZIP on ]