Puduan-6.0.0-wmx-alpha1a
Congrats Musher0!
It must be mindbreaking fun to build a complete puppy.
Can you give a little more explanation on the what, why, how of your build?
Or did you already explain it somewhere on the forum?
I am tempted to try it; the wmx intrigues me. But I run on an old Palomino with geforce256 and I guess you use a new kernel and xorg?
I can run Tahr - not palemoon though, I got no SSE2 - and if I need something I always look in the repos of jessie. So why would you build this if there is already Tahr?
It must be mindbreaking fun to build a complete puppy.
Can you give a little more explanation on the what, why, how of your build?
Or did you already explain it somewhere on the forum?
I am tempted to try it; the wmx intrigues me. But I run on an old Palomino with geforce256 and I guess you use a new kernel and xorg?
I can run Tahr - not palemoon though, I got no SSE2 - and if I need something I always look in the repos of jessie. So why would you build this if there is already Tahr?
Last edited by foxpup on Sun 21 Aug 2016, 21:24, edited 2 times in total.
Hello, foxpup.
The discussion that led to this thread was:
http://murga-linux.com/puppy/viewtopic. ... ost#917394
As to why I built a Puduan Puppy while a TahrPup existed: keep this to yourself:
I wanted to create trouble!!!
Joking aside: Puppy has had the capacity to build a Jessie for a long time. People
were starting to make fun of us and discredit us on DistroWatch because we didn't.
(Nah. That may be just another [bad] joke!)
How about: a distro that can feed on many repos didn't. Now Puppy has one more
restaurant to choose from!
As to the technical aspects of your question, they will be better answered by a
real techie.
Edit: The kernel I chose for this Puduan is version 3.14.0. There are other kernel
options in the Woof-CE when you get to that item. For the record, as I am writing
these words, the last stable Linux kernel listed on kernel.org is version 4.7.2.
But I do encourage you to download the latest woof-CE and dive right in!
BFN.
The discussion that led to this thread was:
http://murga-linux.com/puppy/viewtopic. ... ost#917394
As to why I built a Puduan Puppy while a TahrPup existed: keep this to yourself:
I wanted to create trouble!!!
Joking aside: Puppy has had the capacity to build a Jessie for a long time. People
were starting to make fun of us and discredit us on DistroWatch because we didn't.
(Nah. That may be just another [bad] joke!)
How about: a distro that can feed on many repos didn't. Now Puppy has one more
restaurant to choose from!
As to the technical aspects of your question, they will be better answered by a
real techie.
Edit: The kernel I chose for this Puduan is version 3.14.0. There are other kernel
options in the Woof-CE when you get to that item. For the record, as I am writing
these words, the last stable Linux kernel listed on kernel.org is version 4.7.2.
But I do encourage you to download the latest woof-CE and dive right in!
BFN.
Last edited by musher0 on Sun 21 Aug 2016, 14:36, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
@01micko.
Yeah, it's wiggling!
It'll need to go through the usual paces (beta, rc) before final publication.
Thanks for taking it for a test drive! (And thanks for the initial push!)
BFN.
Yeah, it's wiggling!
It'll need to go through the usual paces (beta, rc) before final publication.
Thanks for taking it for a test drive! (And thanks for the initial push!)
BFN.
Last edited by musher0 on Mon 22 Aug 2016, 22:01, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Here's a link to the files, they are marked as puduan:musher0 wrote: About SMPlayer and SMTube: did you compile them on this Puduan? If so, is there a
possibility you can make them available (including the Qt) for the rest of us?
http://www.smokey01.com/Bill2/
Splendid! You're a champion!Billtoo wrote:Here's a link to the files, they are marked as puduan:musher0 wrote:About SMPlayer and SMTube: did you compile them on this Puduan? If so, is there a
possibility you can make them available (including the Qt) for the rest of us?
http://www.smokey01.com/Bill2/
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
I just tested them on a new puduan install and they work fine, however I installed smtube last and it caused the computer to freeze, after rebooting everything was fine.musher0 wrote:Splendid! You're a champion!Billtoo wrote:Here's a link to the files, they are marked as puduan:musher0 wrote:About SMPlayer and SMTube: did you compile them on this Puduan? If so, is there a
possibility you can make them available (including the Qt) for the rest of us?
http://www.smokey01.com/Bill2/
Maybe install the smtube pet first?
- Puppus Dogfellow
- Posts: 1667
- Joined: Tue 08 Jan 2013, 01:39
- Location: nyc
Puduan-6.0.0-wmx-alpha1a
Manual frugal install to a usb-3.0 SSD, pc is a lenovo desktop:
video-info-glx 1.5.3 Sun 21 Aug 2016 on Puduan 6.0.0 Linux 3.14.0 i686
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
oem: NVIDIA
product: GF108 Board - 1071v1p1 Chip Rev
X Server: Xorg Driver: nouveau
1920x1080 60.00*+
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVC1
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2003 1: @2003 MHz
It's working well on this computer.
video-info-glx 1.5.3 Sun 21 Aug 2016 on Puduan 6.0.0 Linux 3.14.0 i686
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
oem: NVIDIA
product: GF108 Board - 1071v1p1 Chip Rev
X Server: Xorg Driver: nouveau
1920x1080 60.00*+
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVC1
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2003 1: @2003 MHz
It's working well on this computer.
- Attachments
-
- Screenshot.jpg
- (80.54 KiB) Downloaded 390 times
Re: a mirror for the devx and alpha1a iso
Thanks for the archival space and thanks for the thanks, Puppus!Puppus Dogfellow wrote:Puduan-6.0.0-wmx-alpha1a.iso
devx_puduan_6.0.0.sfs
congrats on woofce build, musher!
Both are much appreciated. If that sounds recursive, then it is! (Ha! Devs!)
@Billtoo: Thanks again!
( I think that you can stop testing now! Unless you're doing it for the fun of it! )
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hi musher0.
So basically you just built it because it can be done.
Diving into woofCE would probably kill my dear old machine.
First I have to look for a more powerful PC.
For the moment I just dive into puppy.sfs (and pupsave.fs) to take out or put in as i like.
I will take a dive into your Puduan Puppy though. The kernel is allright. I just cannot use the nvidia driver.
I already had done some reading there. I liked it when you decide to try to get to X because otherwise no one is interested.musher0 wrote: The discussion that led to this thread was:
http://murga-linux.com/puppy/viewtopic. ... ost#917394
Who put this choice there without using it? And why? You ask something along these lines when you ask about "wanderer", right?It's one of the build choices offered in the woof-CE.
So basically you just built it because it can be done.
Diving into woofCE would probably kill my dear old machine.
First I have to look for a more powerful PC.
For the moment I just dive into puppy.sfs (and pupsave.fs) to take out or put in as i like.
I will take a dive into your Puduan Puppy though. The kernel is allright. I just cannot use the nvidia driver.
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
This conversation is making me hungry That "it's alive" picture cracks me upmusher0 wrote:How about: a distro that can feed on many repos didn't. Now Puppy has one more
restaurant to choose from!
Yes foxpup, having another repository to choose from (devuan jessie) is part of the charm and adds to puppy variety.
Nah, I turn off speedstep on my 2005 laptop and let woof-ce build at 800MHz. This way it is quiet and the CPU uses only 10.8W.foxpup wrote:Diving into woofCE would probably kill my dear old machine.
First I have to look for a more powerful PC.
For the moment I just dive into puppy.sfs (and pupsave.fs) to take out or put in as i like.
Not wanderer, no. Iguleder started the Devuan woof and then had tofoxpup wrote:Hi musher0.
(,,,)
Who put this choice there without using it? And why? You ask something along these lines when you ask about "wanderer", right?
(...)
leave for important reasons (such as earning a living IIRC).
3-4 years ago, wanderer provided the interim producing various Puppies, between
Barry's retirement and the constitution of the woof-CE. Wanderer played a vital role
during that period. We are not grateful enough towards wanderer. He helped maintain
Puppy's momentum at the time.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hello all.
Why I am on this thread this afternoon:
Ref.: davids45's post, bottom of page 2, item [4].
I have been working on the compatibility between the Puduan's special desktop and
Zigbert's pwidgets. A big part of the problem is Zigbert's use of conky 1.6 and my
use of conky 1.9.
I am still working on it, but basically, at this point, I can get my scripts out of the
way of the pwidgets, but not the reverse (if the user wanted to re-instate the
original Puduan desktop, for example). Zigbert's low version of conky squishes
my higher version. And my conky configuration needs the conky 1.9, in particular
to indicate the desktop number (2nd line, last item to the right).
Any ideas? BFN.
Why I am on this thread this afternoon:
Ref.: davids45's post, bottom of page 2, item [4].
I have been working on the compatibility between the Puduan's special desktop and
Zigbert's pwidgets. A big part of the problem is Zigbert's use of conky 1.6 and my
use of conky 1.9.
I am still working on it, but basically, at this point, I can get my scripts out of the
way of the pwidgets, but not the reverse (if the user wanted to re-instate the
original Puduan desktop, for example). Zigbert's low version of conky squishes
my higher version. And my conky configuration needs the conky 1.9, in particular
to indicate the desktop number (2nd line, last item to the right).
Any ideas? BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hello, "Puduanites"!
I gave it another try, this time trying to get conky to load its config file as
conky-1.6 or as conky-1.9.1. That would have made it very simple
-- for the Puduan desktop use conky-1.9.1
-- for pwidgets use conky-1.6.
But no, conky has to be identified as conky. Period.
So folks, unless one of you brilliant people has a stroke of genius, the user will
have to make a very final decision on 1st boot:
-- EITHER (s)he wants the Puduan desktop
-- OR (s)he wants the pwidgets
-- forever and ever, amen.
If you install pwidgets, you can't go back to the Puduan desktop. It's a point of
no-return kind of thing. Not in the same pupsave, anyway.
In practice, this means:
before installing the pwidgets, move Startup scripts (I mean in /root/Startup)
conky-2l.sh and rclock.sh to /root/Startup-NON. Then install your pwidgets. Then
reboot or, less drastically, restart X;
or do not install pwidgets.
The only thing left for me to write, then, is a one-way script for the empty PuppyPin
option, to move the weather and aemenu icons out of the pwidgets' way. (3/4
done, actually.)
If you want the Puduan desktop back after you've chosen the pwidgets, you'll
have to start the Puduan afresh with another pupsave.
BFN.
I gave it another try, this time trying to get conky to load its config file as
conky-1.6 or as conky-1.9.1. That would have made it very simple
-- for the Puduan desktop use conky-1.9.1
-- for pwidgets use conky-1.6.
But no, conky has to be identified as conky. Period.
So folks, unless one of you brilliant people has a stroke of genius, the user will
have to make a very final decision on 1st boot:
-- EITHER (s)he wants the Puduan desktop
-- OR (s)he wants the pwidgets
-- forever and ever, amen.
If you install pwidgets, you can't go back to the Puduan desktop. It's a point of
no-return kind of thing. Not in the same pupsave, anyway.
In practice, this means:
before installing the pwidgets, move Startup scripts (I mean in /root/Startup)
conky-2l.sh and rclock.sh to /root/Startup-NON. Then install your pwidgets. Then
reboot or, less drastically, restart X;
or do not install pwidgets.
The only thing left for me to write, then, is a one-way script for the empty PuppyPin
option, to move the weather and aemenu icons out of the pwidgets' way. (3/4
done, actually.)
If you want the Puduan desktop back after you've chosen the pwidgets, you'll
have to start the Puduan afresh with another pupsave.
BFN.
Last edited by musher0 on Mon 22 Aug 2016, 17:37, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Thanks.jlst wrote:it looks like it's working now
Hi jlst.jlst wrote:musher do you a have an updated DISTRO_PKGS_SPECS?, attach it here so i can update the file in woofce.
Euh, no. This is a remaster of the basic Puduan Jessie woof output you and
666philb led me to. Once I had that output I started remastering.
Besides, I'm not touching that database. It makes me anxious. I'm too afraid
I would introduce errors in it. Operating on a raw database is always clockmaker's
work.
Basically the packages I added/removed are:
-- the wget and its libraries. (See end of the other thread.)
-- I removed the vlc libraries I could find.
-- I added some libs so that an mplayer-1.3 sfs that I had compiled for the DPup
Wheezy I woofed last spring could work.
-- I added the series of colored wmx's I had compiled a while back.
The rest are my own scripts and aemenus, which I composed through the years
to respond to needs I had.
Edit, Aug. 22 2016: Also the full Sound eXchange suite (compiled on this Puduan)
and the most recent less (v. 481) with companion scripts and files.
Give me a day or two and I'll prepare a tree or ls list plus an archive of the added
packages. That's the best I can do, sorry.
BFN.
Last edited by musher0 on Mon 22 Aug 2016, 23:00, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Quick manual frugal install. All basics working on initial boot.
Loaded a Chromium sfs, updated the PPM database and installed a couple of packages.Getting used to the interface but seems to be working well so far.
Loaded a Chromium sfs, updated the PPM database and installed a couple of packages.Getting used to the interface but seems to be working well so far.
Code: Select all
[~]>inxi -Fxx
Resuming in non X mode: xdpyinfo not found. For package install advice run: inxi --recommends
System: Host: puppypc1039 Kernel: 3.14.0 i686 (32 bit gcc: 5.3.1)
Desktop: JWM 2.2.2 dm: N/A Distro: Puduan 6.0.0
Machine: Mobo: ASUSTeK model: M5A97 LE R2.0 v: Rev 1.xx serial: 150545593600028
Bios: American Megatrends v: 2601 date: 03/24/2015
CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB
flags: (lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 42140
Clock Speeds: 1: 1400 MHz 2: 3500 MHz 3: 1400 MHz 4: 1400 MHz
5: 1400 MHz 6: 1400 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0 chip-ID: 10de:0a65
Display Server: X.org 1.16.4 drivers: nouveau (unloaded: fbdev,vesa)
tty size: 80x6 Advanced Data: N/A for root
Audio: Card-1 NVIDIA High Definition Audio Controller
driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 10de:0be3
Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1002:4383
Sound: Advanced Linux Sound Architecture v: k3.14.0
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: d000
bus-ID: 02:00.0 chip-ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full
mac: 1c:87:2c:5a:bb:e2
Drives: HDD Total Size: 1120.2GB (5.1% used)
ID-1: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB serial: N/A
ID-2: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB serial: N/A
Partition: ID-1: swap-1 size: 8.60GB used: 0.00GB (0%) fs: swap dev: /dev/sdb5
RAID: System: supported: linear raid0 raid1 raid10 raid6 raid5 raid4
No RAID devices: /proc/mdstat, md_mod kernel module present
Unused Devices: none
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 133 Uptime: 20 min Memory: 238.6/16148.6MB
Init: SysVinit v: N/A runlevel: 5 Gcc sys: N/A
Client: Shell (bash 4.3.291 running in rxvt) inxi: 2.1.28
Code: Select all
[~]>free
total used free shared buffers
Mem: 16536188 1427208 15108980 0 114808
-/+ buffers: 1312400 15223788
Swap: 8396796 0 8396796
Great on ya', Musher, for stickin' with Woofin' up this Puduan Pup - congratulations!
I haven't had the time to try it out yet, but look forward to it (the WM and aemenu stuff in particular - neato!).
As far as the Pwidgets/conky version conflict issue, just a few thoughts that pop into my head - I haven't tried, but may be worth a try (David)...
1) Re-install Puduan's conky v1.9.1 after installing Pwidgets, in order to overwrite the "old" conky version from Pwidgets. In my tinkering, I've found later conky versions work mostly just fine over Pwidgets, but the Pwidget's config files will often require to be fiddled with in order to get them displaying properly again.
2) Conversely, unpack and manually install Pwidgets - everything but the included (old) conky, to keep Puduan's conky intact.
3) Those Pwidgets' unwanted window decorations can likely be eliminated by fiddling with the Pwidgets config files (in /usr/local/pwidgets/widgets/configs directory), maybe (ya - big maybe - but...) using something like -
Maybe try varying "own_window_type" between "normal", "roxdesktop" and "desktop".
Just some random ideas, if worth anything.
Again - congrats Musher! Go, man - GO! Very cool!
Bob
I haven't had the time to try it out yet, but look forward to it (the WM and aemenu stuff in particular - neato!).
As far as the Pwidgets/conky version conflict issue, just a few thoughts that pop into my head - I haven't tried, but may be worth a try (David)...
1) Re-install Puduan's conky v1.9.1 after installing Pwidgets, in order to overwrite the "old" conky version from Pwidgets. In my tinkering, I've found later conky versions work mostly just fine over Pwidgets, but the Pwidget's config files will often require to be fiddled with in order to get them displaying properly again.
2) Conversely, unpack and manually install Pwidgets - everything but the included (old) conky, to keep Puduan's conky intact.
3) Those Pwidgets' unwanted window decorations can likely be eliminated by fiddling with the Pwidgets config files (in /usr/local/pwidgets/widgets/configs directory), maybe (ya - big maybe - but...) using something like -
Code: Select all
background yes
own_window yes
own_window_type normal
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_transparent yes
Just some random ideas, if worth anything.
Again - congrats Musher! Go, man - GO! Very cool!
Bob
Last edited by Moat on Mon 22 Aug 2016, 02:59, edited 1 time in total.