As usual, alpha and beta releases of Puppy are not for general release, only for our band of Puppy-testers.
The live-CD is 75.4MB. Get it from here, also the ‘devx’ file and patched kernel source:
ftp://ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.00alpha1
This is the first alpha of what I have been referring to as ‘RawPup’. I decided that it is a significant jump forward to warrant calling it the version-4 series. This puppy has been redesigned from the ground up for smallness. Packages were compiled from source using T2, for minimum dependencies. As it is a complete rethink, I made some very tough decisions, that will not please everyone. Puppy has grown over a number of years, and all sorts of stuff has been included. Anyway, if something is not there, Tcl/Tk for example, it can be made available as PET packages. There may be some things that aren’t there simply due to oversight.
I have released alpha1 today simply because tomorrow I won’t have broadband2 access, not until the following Sunday evening when I plan to be back in Perth. I still have a longish to-do list. Here are some release notes:
1.
I haven’t put the volume control in the taskbar yet.
2.
No PET packages on ibiblio yet. I plan to create a new directory on
ibiblio for these. So, the PETget package manager won’t be able to
download anything yet.
3.
The Universal Installer is partly broken. I used it to do a full hd
install, then found no modules at all got installed in /lib/modules. It
is easy to fix though, just click on zdrv_390.sfs (and devx_390.sfs)
and ROX will mount it, then open a terminal and run ‘cp -a
–remove-destination ./* /mnt/xxx/’ where ‘xxx’ is the install partition.
There is also a problem with Flash installs as ‘mtools’ is missing and
Puppy has the version of syslinux that does not use mtools, which may
require script changes.
4.
Do not, I repeat, do not, attempt to upgrade an existing pup_save file.
There are some issues to sort out. Boot with ‘puppy pfix=ram’ and at
shutdown you can create a new pup_save.
5.
You might be somewhat taken aback by the color scheme! Especially if
you prefer blue/grey themes. I’ve just been looking at it, and I think
those icons don’t look quite right …maybe if they went back to
transparent or semitransparent color fill. In fact, transparent fill
would blend with any theme. Note, the live-CD also has zigbert’s theme
and icons. Anyway, it’s just an experiment and likely will be different
in the final release.
6.
I chose the 2.6.18.8 kernel as it is the last one that uses the
traditional upport for IDE drives. The 2.6.19 kernel introduces a
unified SCSI emulation layerfor all IDE drives, which although it is
optional, there are hardware compatibility issues whether you decide to
adopt the new system or decline. I intend that this version4 series
will also be available with a more recent kernel. However, there is a
problem, see point 10.
7.
Xvesa only. There will be a PET package soon with the full Xorg drivers.
8.
The Roaring Penguin PPPOE package is there, but no GUI as it is based
on Tcl/Tk. I never use this, so know very little about it, but I am
wondering… the ppp package has a PPPOE plugin which is code taken from
Roaring Penguin, so couldn’t ordinary dialup GUI programs be made to
use PPPOE?
9.
Kernel 2.6.18.8: I compiled a heap of extra modules, including the
‘tifm’ driver required for many SD card readers. But, I failed to
compile at76c503a, Intel 537ep and rtl8180 drivers. I obtained the
latest of these, but perhaps what I need are older source packages —
this was the case for the tifm package, where v0.8 would not compile,
v0.6 did.
10.
And now for something weird. I have been happily using SeaMonkey 1.1.5
with various alpha builds of RawPup for the last couple of weeks. Now I
have just uploaded the alpha1 and when I went to login to my blog,
SeaMonkey crashed. And kept crashing whenever I hit the login button.
Worked every time before. Only error message is “Segmentation fault”.
There are some odd messages in /var/log/messages and /tmp/xerrs.log
about dhcpcd not running, although ‘ps’ shows that it is.
There is one thing different though, the 2.6.18.8 kernel, whereas before I used the same 2.6.21.7 kernel as in pup3.
…so, I built pup 4.00alpha1 with the 2.6.21.7 kernel (from pup3, not recompiled) and SeaMonkey logs into my blog ok. Hmm, I wonder if the old dhcpcd from Puppy 2.16 would work? (it has the 2.6.18.1 kernel). This will need to be sorted out.
Anyway, both puppies have been uploaded. If the 2.6.21.7 kernel in
Puppy3 worked for you, then go for that kernel. If you had problems
with the 2.6.21.7 kernel then try the other, bearing in mind that you
might have the above-mentioned network problem.
….well, this is an alpha!
We need to start a forum thread for feedback on this new pup.





Puppy developer news:


Sage
Monday, November 5, 2007, 09:58 AM
“And now for something weird”. Opera might kill two stones with one bird? Dillo is the fallback, either way.
Sage
Monday, November 5, 2007, 10:22 AM
Everything except ‘Play’ in ..21 works for me - including the ‘munster. HardInfo is a distinct improvement, although SystemStats may be smaller and has dmesg OP.
Henry
Monday, November 5, 2007, 11:02 AM
Truly impressive, Barry,
I have upgraded more or less successfully from 3.01 with k21.
Temporarily of course. The Halloween color is a bit unnerving!
Lobster
Monday, November 5, 2007, 11:17 AM
desktop background can not be changed with wallpaper changer
processor system info much better
Have added a thread in forum under cutting edge
wii info and Puppy 4 page added
A lot to explore
Is there any way to get the res in xvesa higher? I am stuck at 800*600 I am sure there is but have not figured it out yet . . .
Lobster
Monday, November 5, 2007, 11:19 AM
wii=wiki - oops . . .
vern72023
Monday, November 5, 2007, 12:26 PM
in order to get icewm to work I had to impoprt an earlier version of IMLIB apart from that and the wallpaper changer issue that Lobster mentions wine46 works okay so taht is my largest concern
magerlab
Monday, November 5, 2007, 12:31 PM
will the packages from raw pup work in puppy 3.01?
Bob Bagwill
Monday, November 5, 2007, 12:32 PM
Will gslapt be include in the standard rawpup?
mdisaster2
Monday, November 5, 2007, 02:15 PM
What about Slackware compatibility ?
linuxcbon
Monday, November 5, 2007, 04:59 PM
It’s great, just testing the new beta.
So far I am very pleased with all your changes, colors are cool, menu is simpler, xvesa works good (screen refreshing rate is not high but this can be changed).
Still some bugs to be corrected like chat icon doesn’t work or mplayer not displayed ?
It is on the good way to be a terrific 4.0
BarryK
Monday, November 5, 2007, 06:19 PM
Sage, ah, yes, the ‘play’ icon. You have to edit /usr/local/bin/defaultmediaplayer and change “mplayer” to “gmplayer” — that was a bug.
Lobster, ah, the wallpaper setter assumes the existence of directory /root/.config/tmp — manually create it, then wallpaper setter works. But, it still has issues — is supposed to know the current setting at startup but doesn’t. Anyone a wiz at setting up ROX-Filer and can fix this?
Lobster, regarding higher resolution, have you run the Video Wizard (in the Setup menu)?
magerlab, packages from RawPup may not work in 3.01 as they use the very latest versions of libraries. Also answering mdisaster2, the reverse is probably okay, Slackware packages will work in RawPup, except maybe some missing dependencies. Bob, no, Gslapt will be a PET package, at least in the main ‘official’ Puppy, at least that’s my thinking for now. Gslapt should work fine, and should automatically determine any extra dependencies that would need to be installed.
linuxcbon, see above note about mplayer. The chat icon: RawPup has Pidgin and that should be working. Hm, I just tried ‘pidgin’ in a terminal, and it crashed with a segfault and a message to report this to the developers. Well, I did have pidgin working before, so I’ll look into it. Perhaps I left something vital out of the PET package. Sometimes, just leaving out an icon causes an app to crash at startup. RawPup has pidgin version 2.2.1.
…of course, if you’re keen, you could compile it.
BarryK
Monday, November 5, 2007, 06:41 PM
Note, I have fixed the old blog, existing comments were not displaying.
cthisbear
Monday, November 5, 2007, 08:28 PM
Barry:
You never cease to surprise and amuse me.
Do we call this Sandy Desert colour?
No this is good.
Shock the hell out of the detractors.
Strangely couldn’t mount C:\ Drive to delete Windows temps etc.
Other drives OK to delete recycle bin etc.
Maybe just a one off…I will reboot and see.
And you are still King of the Castle.
Have a good day…………………….Chris
cthisbear
Monday, November 5, 2007, 08:54 PM
” Strangely couldn’t mount C:\ Drive to delete Windows temps etc.”
Now testing on a HP Pavillion 772a….never a favourite.
NTFS has the same problem as my regular computer.
Sees Fat32 and writes to them
Sees NTFS and it’s Red Alert….cannot write to the drive.
Is it a newer version….because since Puppy 2.10,
fixing hard drives is a pleasure with Puppy….but not today.
And of course this is where Puppy shines.
Why I use Puppy to tuneup XP
http://www.murga-linux.com/puppy/viewtopic.php?t=20312
Chris
cb88
Monday, November 5, 2007, 10:23 PM
I wonder how this version of puppy will compare to say 1.9 or 2.02 and 2.12 as far as speed and efficiency…. would be nice to see some numbers
Lobster
Tuesday, November 6, 2007, 01:21 AM
“Lobster, regarding higher resolution, have you run the Video Wizard (in the Setup menu)?”
Yes I have. Not used xvesa in a long time. The max resolution offered in the wizard is 800×600 24 bit It is possible that 1280×1024 is not possible in xvesa with the Nvidia Geforce I am using. I might try the inbuilt graphics card on this board. In the early xvesa you could manually set with options such as #0×011a - not sure if that is possible? After trying to config varous ‘x files’ I had to reboot and run “puppy pfix=purge” - enabling me to boot up again into xvesa.
I am glad this has turned from an ‘Experiment’ into a full ‘Alpha 4′ (I am using the code name PAL (Puppy Advanced Linux) for Puppy 4. That should bring in some interest
In particular the use of SVG is welcome and may even be possible to use
icons, superimposed or shadowed or blurred to generate infinite
background abstractions with very little code . . .
What tools are used to generate SVG? Ah . . . inklite . . . built into Puppy. Onward to the magic castle . . .
Raffy
Tuesday, November 6, 2007, 05:21 AM
That high resolution is supported by default in my test PC - this is SiS600+ integrated graphics card.
PAL - Beware, Lobster, ‘coz PAL could stick and finally make the connection between Puppy’s name and the advanced features of Linux. Good thinking out of the blue (ocean, that is).
(To the script: No, am human - timeout did not go away with this new version.
Dougal
Tuesday, November 6, 2007, 08:37 AM
Wasn’t this blog supposed to be commentless?
Anyway, RE: volume applet.
If you are referring to AbsVolume, then, the way I understand the README, it’s not a volume applet — just a volume control app that’s supposed to be launched from a panel-button.
Sage
Wednesday, November 7, 2007, 04:58 AM
Big problems with network connection on full install, reported here:
http://www.murga-linux.com/puppy/viewto
- and, yes, timeout defect remains on this board!
Sage
Wednesday, November 7, 2007, 06:22 AM
BK list No.3 :”just click on zdrv_390.sfs”
Failed mounting or unmounting
Is this related to the network failure?
Whatever, dumbos like me would need an expanded explantion of the above proposed fix (if it were working!)
Sage
Thursday, November 8, 2007, 12:30 PM
vide supra - just lobbed the /lib/modules from the (pfixed) liveCD onto the HD install and entered the addresses manually. Amazing - it worked. Guess this is what BK will do for alpha2, anyway?
Reporting here as John’s board is down again.