|
Puppy developer news:  Older news |  Later news |
Puppy version 2.14 releasedRelease notes here: http://www.puppylinux.com/download/release-2.14.htm Download links: http://www.puppylinux.com/download/index.html jnd
Oh my, so many news! Good work, keep going :)Carmen
where is the checksum file numbersBarryK
Md5sum file is on the ibiblio website, alongside the iso file. But, here it is also:5012d1fd6d9bb5907ea358ecfd865153 puppy-2.14-seamonkey-fulldrivers.iso zygo
I
had a crazy idea to download it at home -- on dialup. It took six hours
-- wget is brilliant. I'm also glad to see I downloaded the latest
upload. I'm using it now. BarryK
Forum member "Previously known as guest" has kindly mirrored Puppy here:http://pkagfiles.net/puppy-current-release/ Jason Pline
Nice work Barry (and everyone else)! I was going to mention something
about TKdvd before you put out 2.14 but I forgot. Maybe a note for 2.15
though. The main window needs to be enlarged to see the Burn button on
the bottom and so the Excluded files button is scrunched and
unreadable. There's a line that sets the window geometry in the TKdvd
script. wm geometry . Should be set to 750x650 (I'm using a 1024x768 screen) Also 4.0.5 is now out. Carmen
Thanks Barry I just burned it & it seems fine,I really like it.My only slight hasle is sound,must modprobe sb in console, doesnt seem to have drivers for awe 32 or 64 like the version 1.0x did. Also cant get wireless to see network, but using ethernet anyway. Great job so far. P/S after seeing the md5 number mine matched after all. Keep up the good work you & your crew. Craig
Looks good but neither of the remaster scripts will run for me. I get
the first dialog box press okay and I then get a full screen with
instructions on how to run xdialog.everything else looks good. Craig tempestuous
Various firmwares for wifi drivers still didn't make it into 2.14.But there's a need to make available additional/alternative wifi drivers anyway (especially Zydas) so I will put together a "wifi Service Pack" shortly. Dougal
Craing: are you running on a machine with only NTFS partitions? That
could be the cause of the problem and the latest version of my script
solves that (it's available on the community forum, on the last page of
a thread named "Testing: improved remaster script").Bill St. Clair (billstclair<at>gmail.com)
Mirrored:http://s3.amazonaws.com/puppy/puppy-2.1 http://s3.amazonaws.com/puppy/puppy-2.1 http://s3.amazonaws.com/puppy/devx_214.sfs http://s3.amazonaws.com/puppy/devx_214.sfs.md5.txt rarsa
Well, This puppy is working almost flawlessly. It's now booting in 30 seconds from a sata drive (starting up from the LiveCD) and is correctly setting mode 12. The 30 seconds include the wait time for WPA association!!! that is fast. I've found a single issue with puppy (incorrectly?) associating the wireless card with the bcm43xx driver. http://www.murga-linux.com/puppy/viewto I've applied a workaround so my puppy 100% healty right now. Craig
The remaster script from the forum worked great is there a reason it hasn't been included in 2.14?jpi
Very very fine! Wpa, speed! Yet Avi in Gxine and support to Photosmart 7760. So Puppy would be all i need.jpi BarryK
Craig, a few things got missed out, for one reason or another. We can put together a Service Pack with the fixes/improvements.I propose that 2.15 be a "consolidation" release, especially to include the excellent work that Dougal and Rarsa have been doing with various scripts. In fact, instead of doing a 2.14CE, why not make it a 2.15CE and I'll host it on ibiblio, as well as all the required PET packages? In other words, Dougal, Rarsa, Lobster, and anyone else who wants to be in it, get together and make 2.15 "your" release. I want to go back to T2 and work on that, plan for Puppy 2.20 (but I think there will be a 2.15 and a 2.16 before that). I want to work on fully automating souce --> final-puppy-live-cd. Craig
Just
noticed something else. I cannot play a regular dvd in gxine. and
strangely cannot get my dell broadcom wireless working with ndis
wrapper If I use a vanilla 2.14. It says it loads the driver and then
is unable to load ndiswrapper. It did work for me initially and
continues to on that remaster so I am trying to figure out what I did
different.Craig BarryK
Craig, did you upgrade from 2.14alpha or beta? I tested Gxine in a pristine 2.14-final and it played a DVD okay.Sage
How
general might that last comment be, Barry? I am having a whole bunch of
issues with 2.14 upgrades, including a serious network no-go which
rarsa is helping me with, the 'missing icons syndrome' which is
afflicting Henry from Oregon as well as myself, mouse freezing, and
various other stuff reported elsewhere. If the upgrade is not working
as it should at present, maybe this could be flagged more prominently
until it's fixed?craig
BarryI deleted my pup save file off the hd and burned a pristine 2.14 still no go. I also have trouble playing some avi's that I have burned to disk but I will try all of this on another machine first just to make sure it is not a machine specific anomaly. I will get back to you tommorow got to go to bed now. Thanks Craig Sage
Can't believe my eyes! I've been using cfdisk from a terminal ever
since I discovered Puppy. This morning, I get "Opened disk read-only -
you have no permission to write" !!! [After a week's discussion on the
Forum about root/user protocols!] It then takes a few <Enter>
keypresses to get to the partitioning screen, with a couple of pages of
switches listed along with the author's name, but no indication that if
you keep going you will get the set-up you might've needed (this only
occurs at the first attempt). But when/if you get there, it shows the
incorrect disc size and parameters, so the whole thing is useless.
First time round I just deleted the terminal! One step forward, two
steps back....Fortunately, GPartEd came to the rescue, except it wanted to label the single HD as hdc ?? So is there any good news? Yes! Cleaning out the HD and doing a completely fresh install has solved my network connection issue (I'll advise rarsa), my mouse freezing issue, but, alas, not only are my d/l icons gone, but I've got to reinstall all the apps as well. That just leaves Craig's problem to sort out. Sorry, Barry, just too many features turning up in 2.14. ..and the time-out for these comments is still too short if one needs to check stuff and write it in the box as one progresses (or regresses?!). Cuaz
thanks....... I have Puppy 2.12 in my HD, how upgrade to 2.12?Cheers!!!!!!!! Cuaz
Sorry to 2.14..............Devildog
Congratulations to Barry and the many gifted and talented contributors
in making this wonderful release possible. Puppy Linux 2.14 is truly
remarkable. I am a newbie when it comes to using Linux, and have found
Puppy Linux to be the most intuitive and easy to use Linux Live CD
Distribution that I have used to date. The only difficulty I had was in
setting up my HP Officejet 5610v All-in-One, but resolved the problem
with installing the Dotpup for CUPS installation.Thank you again for providing us Puppy Linux 2.14. Sandwichbutton (sandwich<at>sandwichbutton.com)
Hello Puppy Team!Congratulations on what appears to be a very successful release! I have always defaulted to puppy because I can't find any other OS (including the Win9x and NT family) on my Dell Latitude C800 Laptop. Unfortunately this new release appears to have introduced several bugs to the hard drive install (via the IDE/ATA method 2). Following installation, when booting for the first time, the screen would fill with an input/output error when accessing line 70 of the keybdlist.txt file. I fixed that by control+c'ing my way to the root command line. where i deleted the contents of /tmp. Upon reboot I managed to boot into the graphical mode just fine. Except the network driver for my wireless card was not loading like it had on the live cd. Well a quick glance at the dmesg output had more of the input/output errors encountered with problem #1. So I erase the contents of the /lib/modules/2.6.18.1/kernel/sound directory. and copy the same folder from the live CD's ramdisc(or whatever its called when installed into volatile memory from cd) to the same folder i deleted the contents of. Yay! My ornioco_cs driver is loaded and i have wireless internet. I then traveled to youtube.com to test the flashplayer installer from mozilla, and it worked first try, I WAS REALLY IMPRESSED! So without restarting my browser or anything I see a video play... but there is no sound. So I run alsamixer, because I'm certain the snd-maestro3 driver is loading into memory, it did on the live CD ("bark, bark"). Well apparently it didnt load the sound like it did on the live cd, dmesg gives me a bunch of snd_maestro3: Unkown symbol snd_ac97_write or snd_maestro3: Unkown symbol snd_XXXXXXXXXX errors. OK, so I reboot into the livecd and copy the sound drivers from the live cd onto the drive, because, on my cd sound works just fine. Booting from hda1 however, doesn't load the driver. Well after replacing the driver and booting back into my hard drive install, the exact same errors return. Now I'm not complaining, I realize I have relatively obscur hardware, but given the fact that puppy had traditionally worked so well on my crap laptop, that this 'step forward' isn't quite so great for me. I really like the release, it is very fast. Had I not tried this and seen the same results over 3 consecutive clean installs, I would think this a fluke or a sign of hard drive corruption. Seeing as win98's scandisk utility, and debian 3.1 see no problems with the disk. You guys are doing great, but it might be time to slow down with the radical changes and focus a release on house cleaning. kjoe
Fantistic work, I really like Puppy which I have been playing around
with for about a year now. Thanks to Barry and everyone contributing to
this distribution.I just wanted to mention two things I discovered concerning Puppy 2.14, as maybe I am not the only one: I think it was mentioned before that the pfix=ram option doesn't prevent Puppy from mounting pup_save.2fs when booting from USB-stick. It is the same problem booting from harddisk. Is there a simple fix to that? One reason I like Puppy is its small size, so that I can also run it on older hardware. Up to 2.13 it really worked fine. Since 2.14 I am not able to boot any more, it seems that vmlinuz interrupts boot process in a very early stage. Booting stops by rebooting without warnings immediately after grub writing some lines on the screen. I ran into the same problem 2 weeks ago using the latest mandriva live-cd. That's why I think, that the troubles are caused by the kernel. Any ideas? I am really not complaining, as 2.13 works find and is ok for me. Maybe I could help i.e. by testing fixes (although my Linux and English knowledge is (very) limited). Thanks again for sharing your work with others. Cheers from Austria (yes, without "la") kjoe kirk
WOW,
looks Great! Big thanks Barry and the rest of the kennel. Extra thanks
to Rarsa, network wizard is very nice now. I used it today to connect
to a WPA network, easy. Sata drive boots up pupmode 12 too. Fonts look
real sharp.Craig
Okay
more on my DVD playing problem. I was able to duplicate on another pc
although it would play at least one dvd it would not play others. On
the dell Laptop if I switched to the xvesa driver the dvd's would play
but too jerky to watch. The dell is a 2 month old model with a gig of
ram so i don't think it is a horsepower issue.Any one else seeing an issue on laptops? Thanks Craig JohnRoberts
Craig, Hiabout the remaster script issue...are you running on a machine with pure NTFS partitions (W/o VFAT at all). If so it is a known problem (check the forum for script updates...) or plug in a USB flash and it should work... Craig
remaster worked great with the script off the forum. Jeffrey
2.14 looks great. Everything that I've tried so far works.Cosmetic issue: xorgwizard's test screen doesn't show the tiled shark image but the dialog asks if the image is OK. A new user might look at the grey background and say no. Marion (mari.koch<at>web.de)
Where is the MTools-File Manger in 2.14 ?I can't find him, so I work with 2.12. Thanks BarryK
It seemed that nobody was using MToolsFM, so I removed it.Marion (mari.koch<at>web.de)
That's hard. I like MtoolsFm because my camera only work with windows, but with the MtoolsFM I can copy them to Linux.BarryK
Marion, the two mount applications MUT and Pmount will mount any msdos
of windows partitionand Rox can access them. MToolsFM is not needed.However, if you want MToolsFM, what's the problem? It's a PET package, just use the PETget package manager and install it. Marion (mari.koch<at>web.de)
Hi Barry, you're great, thanks a lot. sometimes it is easier than it seems to be.I don't know very good Puppy because I'm a beginner and a german. So in English it's a little bit difficult. But I try the MUT and it works. Fantastic. Only my printer with usb doesn't work. Maybe you have an idea. It's Epson DX 4050. Thank you very much, Puppy is great. whine
nforce2 ethernet no module ):whine²
puppy 2.14beta works fine |
Late news before 2.14 releasehttp://www.puppylinux.com/download/index.html I have about half a dozen Unleashed CD orders, but holding them until Puppy 2.14 is released. Please excuse the delay, but it is better than receiving 2.13 CD in the mail just after 2.14 release is announced! Dougal has done some very good work improving the 'init', 'xorgwizard' and 'rc.d' scripts, but this will be helod over for consideration for inclusion in 2.15. Preliminary feedback is that Dougal's xorgwizard is very fast. Rarsa: Network Wizard upgraded to 2.14.8. NOTICE: I have uploaded Puppy 2.14 to ibiblio, however just after doing so have received many upgrades from Rarsa and Nathan. Network Wizard to 2.14.9, Grafburn to 0.9 (fixes a critical bug in 0.8), a couple of invalid menu entries. As well a couple of other things that can be postponed. Well, okay, I'll rebuild the iso and reupload it tonight. So, although 2.14 is currently at ibiblio (and the mirrors!), just ignore it. -- in fact, I'll delete it now, which will take awhile to ripple through to the mirrors. pakt
Don't mean to stress you Barry, but the boot option 'pfix=ram' doesn't
work when booting from a USB stick - pup_save.2fs loads anyway.Paul Leon
Barry,please include bug fix for Chooselocale script that now works properly, thanks to Pakt. http://www.murga-linux.com/puppy/viewto Edit /usr/sbin/chooselocale as follows: Code: on line 197, change if [ "$LOCSRC" = "download" ];then to if [ "$LOCSRC" = "zdrv" ];then BarryK
Or perhaps that should be (on line 197):[pre]if [ "$LOCSRC" = "download" -o "$LOCSRC" = "zdrv" ];then[/pre] I've already re-uploaded Puppy 2.14, so this fix and any others will have to be a service pack. Eric (caneri) (ericmulcaster<at>gmail.com)
just installed the newest 2.14. Rarsa...your new wireless with wpa
support is a think of beauty THANKS....worked and saved first shot on
my HP nx9420 with Intal pro nic(ipw3945 driver). The pet package
manager seems very fast now... I'll keep trying to break this version a
call back later. Again thanks to the puppy people!!Barry Kauler
Eric, check that you got the right iso file, as the first one I
uploaded to ibiblio was there for a couple of hours, then got removed,
then later on replaced. The ibiblio mirrors may have also temporarily
had the wrong one. Md5sum is: 5012d1fd6d9bb5907ea358ecfd865153 puppy-2.14-seamonkey-fulldrivers.iso roger
bug in connection tkpppoe after use pet install tkpppoe not starting
|
Improved recognition: SATA at bootup, 1920x1080 HDTVForum member 'thegoldenstrand' requested support for 1920x1080 monitor, which is a HDTV LCD panel. I have put this into the Xorg Wizard. Forum member 'mternus' reported that when 1680x1050 resolution was chosen in the Xorg Wizard, the color depth got set to '1200' in /etc/X11/xorg.conf, whereas it should be '16' or '24'. I examined the code but cannot see why this would occur. Anyone else get this behaviour? Leon
As I
already reported for Pup 2.14ALPHA Xorg Wizard still display only two
resolutions available for ATI SAPPHIRE RADEON 9200SE ATLANTIS 128 MB
graphics card and Sony SDM-M51, LCD, 15" monitor:640x480x16 640x480x24 http://www.puppylinux.com/forum/?1169851092;2 http://www.puppylinux.com/forum/?1169851092;3 That was not the case prior to Puppy 2.13. BarryK
Leon, there is a problem with your monitor. The 'ddcprobe' program
probes your monitor and it returns only those resolutions. Or, it could
be a problem with 'ddcprobe'. You could try this alternative monitor
probe (these progs are in Puppy):[pre]# get-edid | parse-edid[/pre] ...see if that returns more sensible resolutions. |
More bugs fixed in PETget package managerNeverMore
that's so greati cant really wait to try this new release!!! if 2.14 will work on my laptops it will became the principal OS in my home!! at now 2.11 is the most used in my home :D Firefox
Hi Barry,I found whilst running Petget Manager that if i chose to install a local package and clicked on it the entire menu disapeared!.I`m wondering if this is what has been fixed. Firefox |
Firmware added for zd1211rw modulerarsa
I'm testing WPA with hidden ssid with the zd1211rw using a USB GigaFast
WF748-CUI adapter and the zd1211rw seems flaky. Sometimes it starts,
sometimes it does not. Sometimes after I cannot connect the only
solution is to do a cold boot. Using the alternative "older" driver seems to work better, comes up every time. PaulBx1
I wonder if we can put both drivers in there. Clumsy, but then users will have two shots at getting it running.Does the firmware Barry mentions work with both drivers? tempestuous
There are so many Zydas variants it gets confusing.To clarify: the older (community) driver was already included in Puppy 2.12 ... but only the "A" version, not the "B" version. Summary - Community version = zd1211 & zd1211b From http://zd1211.ath.cx/download/ The "B" version requires a simple modification to the Makefile. These 2 modules do not require separate firmware. The zd1211 (but not zd1211b) was compiled by Barry and included in Puppy 2.12. "rw" (rewrite) version = zd1211rw Included in kernel source from 2.6.18. Requires ieee80211softmac module. Requires separate firmware in /lib/firmware/zd1211 This driver supports both A and B versions of the Zydas chipset. There is also a vendor version, upon which the community version is based. BarryK
I've
frozen 2.14. It only has the zd1211rw driver, which is the way to go,
if it can be made to work properly. If anyone needs the other zd1211
driver, I suppose it can be supplied separately.
|
Gxine playing avi filesThings keep changing all the time, I'll never get 2.14 released.... perhaps I'll just leave in the original Gxine 0.5.9, Xine_lib 1.1.1 and FFmpeg-2005-10. Recompiling a library in isolation has repercussions. Soon I plan to revisit T2 and recompile everything anyway. Leon
Thank you.PrairieDog (janitorofgod<at>yahoo.com)
Many Thanks Here too!Barry Kauler
Well, the problem is that FFmpeg was recompiled for a reason, to add
extra features that are being used by other applets. If I fall back to
using the old FFmpeg for v2.14, will those other applets still be
functional?tempestuous
I
don't wish to confuse the issue too much, but I have experienced
problems with Gxine which I believe may be related to ffmpeg.Using XvMC video output, for example, with an nVidia graphics card results in strange colours, but XvMC output is OK with VIA Unichrome graphics cards. And I have also experienced extreme picture contrast, but again, only with certain graphics cards, and certain video out options. The reason I suspect these problems relate to ffmpeg is that I have compiled MPlayer and VideoLAN in recent times, and discovered that trying to compile them against a shared ffmpeg library fails. In fact, the semi-official build instructions for VideoLAN actually advise to compile VLC with ffmpeg configured statically. So I would venture a guess that Gxine might behave better if compiled with internal ffmpeg. Of course, this would make Puppy larger. Jason Pline
What
will fail will be support with no add ons in PBcdripper & Grafburn
for wma & ogg support. If you still have that old source of ffmpeg
try to re-compile it with --enable-libogg=system so we can at least
have ogg support (since Puppy already has libogg). Shouldn't make it
that much bigger. Obviously the newer versions of ffmpeg have support
for many other formats so everyday it'll probably get a little bigger.
I could really care less about the wma support but ogg would be nice to
have.Jason Pline
I
should've mentioned in PBcdripper it will first look for oggenc to use
as an ogg encoder since it does a better job than ffmpeg (you get to
choose a bitrate other than a quality setting). I compiled a version of
oggenc with no flac support and it works with the standard libogg
already in Puppy. It's pretty small and would be nice to have in the
base iso. That is if you don't want to re-compile ffmpeg and don't want
to break PBcdripper. http://www.murga-linux.com/puppy/viewto BarryK
Too late! V2.14 was dragging on too long, so I did some final tests
than released it -- up on ibiblio now. using the original FFmpeg
2005-11 as used in Pup 2.13.If necessary, a little PET or DotPup can be applied to add whatever extra Pbcdripper and the others need. wolfie (valko<at>yotov.biz)
Hi All,maybe it worths to have a look at http://www.videolan.org/vlc/ it supports all the codecs and it will be the perfect solution for playing multimedia. |
Gxine media-playing improvedhttp://www.nasa.gov/multimedia/nasatv/index.html To play the RealPlayer or Windows videos requires the 'xine_extra_codecs' PET package. This is a problem that comes up again and again, so I have modified the wrapper script /usr/local/bin/gxineshell that is used to launch Gxine, so that if a codec file fails to load, a message will come up recommending to install the 'xine_extra_codecs' PET package. However, the RealPlayer file ( extension .ram) played with video only, no sound, whereas before installing the extra codecs it played with sound only!!! The Windows video file (extension .asx) was not recognised by SeaMonkey, so I added the mime-type 'video/x-ms-asf' to /etc/mime.types and /etc/mailcap -- now SeaMonkey offers to launch Gxine to play it. But, although the extra codecs are installed I only got video, no sound. I found out that the sound is encoded in WMA format instead of MP3, and requires another audio decoding file, 'divxa32.acm'. I downloaded this file and added it to 'xine_extra_codecs' package. Now the Windows .asx video plays with video and sound! The modified /etc/mailcap & mime.types will be in the 2.14-final, and I'll upload the improved xine_extra_codecs PET package later today. The RealPlayer .ram file lack of audio remains unsolved. Barry Kauler
Okay, I've uploaded the new 'xine_extra_codecs' PET package to Ibiblio, that has the 'divxa32.acm' WMA audio decoder in it.Eddie Maddox (greatnessguru<at>gmail.com)
Barry, Good job. Good News!I used the "PET install" PETget Package Mgr to install that new 'xine_extra_codecs' PET package. Then I tried SeaMonkey on the NASA-TV Media Channel Windows feed, which didn't know yet about the MIME-type, as you know already. So I "Choosed" /usr/local/bin/gxine. It Works! My box is really not up to the job (but I do have DSL-512), so it was intermittent, but both video and audio were there, in short snatches. I Quit gxine and used SeaMonkey again, this time to pick the NASA-TV Media Channel RealPlayer feed (my preference). It Works, Too! Both video and audio. I Quit SeaMonkey to save cycles and RAM, and set View>WindowSize to 200%. Not Too Bad! It says: "NASA-TV - Media Channel (NASA Headquarters) Real 320x240 Real Video 4.0 117 kBit/s 22 kHz 32kBit/s Cook" Thanks much, Barry! Eddie zygo
Barry, Couldn't xine extra codecs go into the zdrv sfs? Lobster
The extra codecs if not loading is a great idea - could something similar be offered with the flash 9 final? I think Flash 7 is in SeaMonkey? There is a dotpup of 9 J_Rey
Unfortunately some of those codecs/demuxers may have
licensing/copyright issues where they couldn't be included with Puppy
but I don't think it'd be a prob if a disclaimer pops up along with
installing the extra codecs package.Also, for 2.15 could try again to upgrade xine-lib, gxine, & xine plugin to the latest [i]together[/i]. Craig
Am I the only one that has a problem with 2.14beta playing avi's using gxine. I get audio but no video.Craig Leon
> Am I the only one that has a problem with 2.14beta playing avi's using gxine. I get audio but no video.> Craig Gxine won't play my AVI files too. It plays sound but no picture: Error from the xine engine Error loading libray: mpg4ds32 This worked in Puppy prior to version 2.14a without the need to install additional codecs. Reports about this problem: http://www.murga-linux.com/puppy/viewtopic.php?t=14981 http://www.puppylinux.com/forum/?1169851092;2 BarryK
The Gxine situation is not satisfactory. I've been communicating with
one of the Gxine developers, trying various patches to try to get
v0.5.11 to work, but no go so far. The suggestion that I upgrade to the
latest xine libs may be worth trying.Other than that, go for something else? ...MPlayer? ...not for 2.14 though. BarryK
I wonder how well the other xine-based players work? There's XFMedia, Xine-ui, ...and more.Actually, I did compile XFmedia awhile back, it's a PET pkg. Jason Pline
The thing with various video not working properly is that there's too
many formats that have no standards. Just because you can play one avi
file doesn't mean you'll be able to play another. They could be encoded
differently with different audio. If you want to play everything you'll
need to install all those extra codecs. For your videos that don't play
you could go to the command line and see what the audio/video codecs
are for the file. For example:sh-3.00# ffmpeg -i test.wmv FFmpeg version SVN-r7400, Copyright (c) 2000-2006 Fabrice Bellard, et al. configuration: --prefix=/usr --libdir=/usr/lib --mandir=/usr/man --disabl e-debug --enable-mp3lame --enable-a52 --enable-gpl --enable-shared --enable- pp --enable-libogg --disable-decoder=alac --disable-decoder=tta --disable-de coder=wv --disable-encoder=flac --disable-decoder=flac --disable-audio-beos --enable-small --enable-pthreads libavutil version: 49.1.0 libavcodec version: 51.28.0 libavformat version: 51.7.0 built on Jan 3 2007 13:14:09, gcc: 3.4.4 Compiler did not align stack variables. Libavcodec has been miscompiled and may be very slow or crash. This is not a bug in libavcodec, but in the compiler. Do not report crashes to FFmpeg developers. Seems stream 1 codec frame rate differs from container frame rate: 1000.00 ( 1000/1) -> 29.97 (30000/1001) Input #0, asf, from 'test.wmv': Duration: 00:39:20.1, start: 5.000000, bitrate: 496 kb/s Stream #0.0: Audio: wmav2, 48000 Hz, stereo, 96 kb/s Stream #0.1: Video: wmv2, yuv420p, 320x240, 29.97 fps(r) Must supply at least one output file ---------------------------------------------- As you can see this file has wma audio and wmv video. If ffmpeg recognizes the audio and video you could always re-encode to a format that should play in gxine. sh-3.00# ffmpeg -i test.wmv test.mpg That will re-encode to mpeg. I know that's not the best solution but you're always going to run into these problems unless you have all codecs installed. Eddie Maddox (greatnessguru<at>gmail.com)
Tried NASA-TV Public Channel "Watch with Quicktime":"Choosed" /usr/local/bin/gxine "The xine engine failed to start. No input plugin was found. Maybe the file does not exist or cannot be accessed, or there is an error in the URL." Eddie |
Puppy version 2.14BETA availableUPDATE, ABOVE LINK NOT WORKING, DOWNLOAD FROM HERE: http://distro.ibiblio.org/pub/linux/dis ... inux/test/ Release notes: http://www.puppylinux.com/download/release-2.14.htm Some extra notes: Plinej: Pbcdripper upgraded to v2.1. Jesse: elspci upgraded to v0.0.6. jb4x4: told me about a bug installing Slackware pkgs converted to PETs. Fixed. I removed MToolsFM from the 'standard' live-CD. Who uses it? GuestToo
well, i can't download iti don't use MToolsFM, but i seem to remember some program(s) use it for something ... i think Syslinux might need mtools ... maybe gparted, maybe others JB4x4
I can't upload it either. Using wget, it is saying it is trying to connect to "media-nf.puppylinux.com"tronkel
Also cannot download it. Site seems to be down for some reason. Will try later.J_Rey
Most
of the files at http://www.puppylinux.com/test/ are being redirected to
http://media-nf.puppylinux.com/test/ which isn't even ready/setup for use.
I've just sent Barry a PM about this, also.BarryK
I've submitted a ticket to my host, netfirms.com.In the meantime, I'm uploading to another site, will let you know when the upload has completed. BarryK
MToolsFM is a GUI for MTools. I have left MTools in Puppy.Barry Kauler
Okay, download from here:http://distro.ibiblio.org/pub/linux/dis Billcnz
My download was corrupt, only got 33 MB saved, don't know if problem was my end will wait a while before retrying.Henry
2.14beta is working just great!Thanks, Barry and congratulations. Henry Billcnz
Downloaded fine on 2nd attempt and running smooth. Font sizes in
Seamonkey looking good apart from fields where you type in data like
this comment being a little small.Barry Kauler
Billcnz,The files that can be used to customise stuff like font sizes are userChrome.css and userContent.css, to be found in the /root/.mozilla/ ... chrome/ directory. I didn't find out how to make this form edit box text bigger though. There must be some setting for it. Perhaps the knowledge we seek is somewhere here: http://www.mozilla.org/unix/customizing.html zigbert
I
welcome some new icons. "ok.xpm" and "error.xpm" are both small (around
3k), but "info.xpm" is huge (8k). I've tuned it down to same size as
the others.http://www.murga-linux.com/puppy/viewtozigbert
I forgot the question icon. It is now also fixed to 6-bits colordepth.Nathan
Runs
really slick, but I'll have to give it more of a test drive and then
report. There's at least one thing I'm really pleased with, the package
manager has sped up considerably. Seamonkey is also much faster now,
usable with my 533mhz whereas before it was just too sluggish to bear.archwndas
Barry,it seems impossible to download the devx_214.sfs. Could you upload it to the same folder as the new puppy 2.14? Thanks in advance. MooDog
Hi, Barry -Testing Out 2.14 beta - Gxine is not working I think, I got audio but no video when playing a .avi file. Probably testing 0.5.10 broke it? BTW - how is the PEDV1 parameter supposed to work? I tried to run with PDEV1=hda8, but it still tried to update my puppy 2.11 in hda5. Is it _not_ supposed to do this? Thanks! Bill St. Clair (billstclair<at>gmail.com)
Mirrored:http://s3.amazonaws.com/puppy/puppy-2.1 http://s3.amazonaws.com/puppy/puppy-2.1 I couldn't get the devx to download either. Haven't tried it yet. pakt
2.14beta works great so far from CF card on eBox-3851 thin
client(800MHz VIA CPU). Xorg 'via' module, 'snd_via82xx' sound module
and 'via_rhine' network module all loaded automatically.Nice work, Barry & Co Downloaded fine and runs nicely EXCEPT that I still can't print properly on my HP 1610. Just as before it strta off printing well but ends up as though the ink had ran out on the cartridge. The same item prints perfectly under windows. Otherwise 14 Beta seems to work well and looks good though I haven't tried every last program Eddie Maddox (greatnessguru<at>gmail.com)
2.14.BETA problem: NASA-TV videoFrom SeaMonkey: + NASA Home > Multimedia > NASA TV http://www.nasa.gov/multimedia/nasatv/index.html Media Channel: + Watch with RealPlayer http://www.nasa.gov/ram/145591main_Digital_Media.ram Error from the xine engine Error loading library: drv4.so.6.0 No video. Audio may work. Not sure. Note: Public Channel: + Listen with RealAudio Works just Fine. Thank you, Eddie jozl
Hello Barry,Are you sure you included elspci 0.06, as you mentioned in the release notes? I think the old version 0.0.3 is still in Puppy 2.14 beta, because it hangs at the same spot as where Puppy 2.13 hangs. Also, if I run elspci from the prompt (without the -l option) its mesage says that it is version 0.0.3. jozjl Billcnz
Jozjl, it says ver 0.0.6 for me:sh-3.00# elspci pci module loading help - compiled on Feb 1 2007. Version 0.0.6 Written by Jesse.Liley for PuppyLinux BarryK
MooDog, hmmm, no it's not supposed to do that. What are you booting off?Jozjl, oh dear, I made a mistake. I put in the 0.0.6 elspci then forgot to build the new 'inird.gz'. It is in the main part of Puppy, hence the conflicting reports. If you do "chroot /initrd" then try "elspci" (if you have a running Puppy) then you will see it is only v0.0.3 in the initrd. I'll fix that, upload it again a bit later today. Here is a forum thread for reporting bugs: http://www.puppylinux.com/forum/azbb.php?1171323163 Matt
USB hotplugging is still broken in 2.14B :(Bill St. Clair (billstclair<at>gmail.com)
Working for me in a Parallels VM on my iMac. Had to run the ALSA sound
wizard to get sound to work. This was not necessary in 2.12.BarryK
Matt,Can you give a specific example of the problem? Matt
Hi Barry,I had similar problems to this post ... http://www.murga-linux.com/puppy/viewto Chris
Barry,Truly was the slowest download of Puppy ever. But the dog ran out of the kennel so quickly that I got left at the GATES. cthisbear When I upgraded from 2.13, the menu didn't display properly. It only had the Shutdown and Help menu. The only thing above that are the two seperators that go between sections. Also, it would be nice to have the bootloader tell me the partition-selection flag. When I tried to connect to my WPA network, the connection failed the first time. I looked at the settings again (changed nothing), and then it connected. However, the time it takes to connect and then to activate DHCP is really slow. Brian C (spiffytech<at>gmail.com)
I've had several bouts of application instability with the 2.14 beta. 1) Firefox has closed on me twice while I'm browsing my Gmail account. This did nothappen in 2.13 2) The Network Setup wizard will occasionally refuse to connect to an access point, but will connect when I try a moment later. Also, I tried to save a profile, and it kept flashing "saving" with a progress bar. I had to restart X Brian C (spiffytech<at>gmail.com)
More stuff (I'm sure you're getting tired of it; I'm just making sure the next Puppy grows up strong!)1) When installing the Python interpreter, the PETget manager stayed at "checking dependancies" for ~30-60 seconds. That's a lot longer than the other steps, and seems like it should be short. I don't know if it's a rea problem, though. 2) The dialog for PETget progress is kinda annoying in the middle of the screen. It would be nice if I could put other windows on top of it, or if it defaulted to one of the screen edges. 3) The "Advanced" settings button under the JWM configuration just puts an entry in the taskbar saying "Sorry...", with no window or anything. Brian C (spiffytech<at>gmail.com)
OK,
firefox is crashing a lot. It usually happens when I open/close a tab.
I know FF isn't a part of Puppy 2.14, but this didn't happen in 2.13.
Could a change to Puppy have broken FF?zygo
Barry, Opera 9.10 (from the site) works fine as it did in 2.13 -- without the need to install qt! Thanks. Sage
Barry: Just reported serious mouse and apps issues with 2.14beta
upgrade to full install over on your own Forum. Seems OK on liveCD.
|
Various upgrades and fixes2.14BETA will have TkDiff to play with, replacing Gtkdiff. I'm not sure if it's that much better, but will evaluate. Rarsa has upgraded the Network Wizard to v2.14.5. John Doe provided a fix for the 'alsaconf' script to handle usb sound. Plinej has upgraded Pbcdripper to v2.0. Zigbert has developed 'Pfind' a new simple file finder, v0.5. Plinej has upgraded Pupctorrent to v0.4. I've partially ported the 'init' script to new code for scanning drives, but for the 2.14BETA this is only done for booting from USB Flash, IDE Flash, and IDE HD. Dougal has done some major rewriting of the 'init' script also and has created an alternative and smaller 'initrd.gz' file. I'll have a look at that after the BETA is released. jozjl (joz<at>lycos.nl)
Hello,Are you also going to put the newer version of elspci in Puppy 2.14? See: http://www.puppylinux.com/forum/?1168632391 jozjl Jaon Pline
I
just updated PBcdripper to 2.1. This version will allow you to tag your
mp3 files. If you have faac installed you can rip and tag m4a files. If
you have oggenc installed you can tag your ogg files. I think I'm done
with it for the time being unless someone finds a problem or asks for
another format or feature to be included.http://www.murga-linux.com/puppy/viewtopic.php?t=12088 Jason Pline
I
lied, I just updated PBcdripper to 2.2. This time I added tagging
abilities to wma and added support for ape and shn as long as mac and
shorten are installed.Nathan
Dang
it all Jason! I just upgraded my Grafpup package about six hours ago. I
even went in and changed all the icons. Now I have to do it all over
again In all seriousness good work, and thanks for it. zygo
How about PDEV1=none(and pfix=noramsfs) zygo
Sorry I just posted to the wrong thread somehow.
|
'init' boot script currently being rewrittenSo, although it means delaying the 2.14BETA a bit, last night I got stuck into the rewrite. This time, I am attempting to make the drives scan much more thorough and systematic. So far, so good. It is implemented in parallel with the old scan code, meaning that both sets of code are in the 'init' script, so I can port to the new code gradually. I have ported the boot from USB Flash drive, and that works fine. Next I'll port the boot from frugal h.d. installation, to fix the problems with that. Then perhaps will leave it as a mix of old and new and release 2.14BETA. While testing a USB Flash install, I discovered another bug, now fixed. For a msdos filesystem, the pup_save.2fs file got created as PUP_SAVE.2FS, which wasn't recognised at bootup. I think someone mentioned this capitalisation problem on the forum, but I think it was in relation to NTFS and I fixed that one awhile back. From the user's point of view, 2.14BETA should work as before, except the boot from USB Flash and from frugal h.d. install should both work properly. Raffy
Thanks for looking at this, Barry. A related discussion is here:http://www.murga-linux.com/puppy/viewtopic.php?t=15113 I wonder if you have an advise about this matter to users of version 2.02. Many "office pro" builds have used that version. Thanks and regards. menno (menno<at>fwn.rug.nl)
"this capitalisation problem"Mount a vfat with '-o shortname=mixed' . donald_duck
Hoppfully you can also have a look at the problem with the Iomega zipdrives as mentioned here:http://www.murga-linux.com/puppy/viewto Thanks in advance Andreas BarryK
I read through the zip forum thread, but not logged in there right now, so posting a question here:donald_duck and cdevidal, can you also report the result of running the 'test-eide' program. craftybytes
To
possibly assist in 'future' and 'on-going' fault-finding/fixing with
the "init" boot script - may I suggest that you 'sectionise' (if that
is a word) the main script areas - e.g.. script for locating &
mounting any 'vfat' (msdos) partitions/drives be in 'separate' section
to script for 'ext2/3' or script for 'ntfs' ... etc.... Also script for
locating & 'writing' to such drives as separate to other script ....Just my 2 c's worth towards making such tasks as "fault-finding" hopefully easier for all concerned .. BarryK
I've added support for the 'PDEV1' boot parameter. For example:PMEDIA=idehd PDEV1=hda1 It is preferred to leave the PMEDIA there, but PDEV1 can tell Puppy to search only a particular drive or partition. This can speed things up during booting, maybe also avoid finding components of Puppy on other drives and partitions. Sage
Would that include sda1 ?!ferikenagy
can
you also modify the init script to search and load aditional .sfs files
(like winexxx.sfs or officexx.sfs ) from same partition where main
pupxxx.sfs and zdrvxx.sfs files are located (in frugal hd install)?
these should also work (search&load additional sfs) in case we
don't have pup_save.2fs file (we haven't created yet or we have in
place of pup_save.2fs file an complete ext2 or ext3 partition) That
should be great.... thanks Dougal
Barry,I actually rewrote the init script a week ago. I didn't modify the way it scans partitions too much, but have modified quite a few things. I was actually wondering about the problem with upper-case names -- thought it might be best to do for vfat, too. You can find it in my modified initrd.gz: (only 810k) http://dotpups.de/incoming/dougal/tmp/initrd213.tar.gz rarsa
Another thing to consider is, even for SDA devices when booting from
the live CD, if it finds the pup_xxx.sfs and the zdrv_xxx on the Hard
drive where the pup_save.2fs file is, use them to boot and to find
drivers respectivelly.That is the way it works on HDA devices and I don't see a reason why it shouldn't be the same for SDA. Boot times are dramatically improved by just kickstarting from the CD and continuing from the HDD. J_Rey
Now I
know if Puppy finds more than one personal storage file in the same
directory then it'll prompt to pick which one to use, but does it or
will you have Puppy look at all of them on all the different media
types or just stop when it finds the first location? Same question
probably applies for .SFS files as well.donald_duck
Hi Barry,as requested here the result of 'test-eide': /dev/hdc - cdrom - 4x4x32 /dev/hda - floppy - IOMEGA ZIP 250 ATAPI Regards Andreas zygo
How about PDEV1=none(and pfix=noramsfs) |
Network Wizard now has WPA support, Grafburn upgrade, SeaMonkey font sizes fixNathanF has upgraded Grafburn, his simple CD/DVD burner, to version 0.8. I have been experimenting with setting font sizes in SeaMonkey. The menu font was a bit too big, causing the Edit -> Preferences dialog window to be too big for a 800x600 screen. I fixed that by editing /root/.mozilla ... chrome/userChrome.css. Text in the Mail and News module was to small. I created chrome/userContent.css and was able to fix that. Note, if all goes well, Puppy 2.14BETA will be released in a couple of days. rarsa
Barry,For the Beta please use the network wizard 2.14-5 2.14-4 was purely a test version and I found a really bad bug with scanning that rendered scanning useless. I am quite comfortable with 2.14-5 to be a candidate for release. http://www.murga-linux.com/puppy/viewtopic.php?t=15180 andrei
For some reason, the "Find Text As You Type /" is disabled in SeaMonkey,at least I was not able to turn it on. It is in the Edit menu, but I was not able to activate it. Perhaps, it is some sort of an extension which should be included at the time of compilation? I found these links: http://www.mozilla.org/access/type-ahead/ http://lxr.mozilla.org/seamonkey/source but I could not understand how it is supposed to work BarryK
andrei, it seems to be an extension, that was not compiled-in. I can't
do anything about it for now, but I've made a note of it. Probably will
upgrade SeaMonkey in Pup 2.15 and will see if I can compile it in then.Buri
I had a problem with cookies in Seamonkey (Puppy 2.13). I could not erase them.Lobster
I wonder if we have room for Pfind ... (10k)http://www.murga-linux.com/puppy/viewto |
Qtwvdialer, Firelog, Inotify Tools, removing invalid shared-library symlinksNoobieDoobieDo (Forum name!) has created Firelog firewall monitor, version 1.1. Quite intriguing, I've put it into the live-CD for us to play with. Note, the v1.1 script had a small bug with the path to load the results page in the web browser. Inotify Tools is a couple of utilities to enable the inotify feature of the kernel to be used scripts. I have created a Unleashed package with the 'inotifywait' utility in it. Jesse suggested that as Puppy does not have 'ldconfig', it would be a good idea to add some code to the version update script to check for invalid shared library symlinks. Done. This is in /etc/rc.d/rc.update. |
Various improvements, bugfixes, appletsAs requested, I have added 1680x1050 and 1360x768 LCD screen resolutions to the Xorg Wizard. Billcnz reported a bug in the PETget package manager. When the dialog window displayed to choose an alien package and the 'Cancel' button was pressed, it didn't quit. Fixed. I compiled Gxine 0.5.10, the latest. Unfortunately it did a segmentation fault as soon as it started. So, still on 0.5.9. I compiled Ctorrent version dnh2.2 and this is now an Unleashed package. I will put it into the 2.14BETA live-CD. Plinej (Jason) has written a GUI for Ctorrent, called Pupctorrent. The version is 0.4. Looks good, I'll put that into the live-CD also. Note, Jason has also developed a torrent tracked GUI app called Puptracker -- see the forum. The 'new2dir' script in PET-Tools had some problems. I found, when using it to create directories of the Pupctorrent and Puptracker DotPup installed files, that some files and directories got missed out. In particular, new empty directories got ignored. Fixed. Rarsa has added another improvement to the 'rc.network' boot script, suggested by PaulBx1. See previous post. Lobster
With a Firefox front end, the calls for Firefox in Puppy might be lessened - see herehttp://www.murga-linux.com/puppy/viewto From a subjective point of view I have found the Navigator part of Seamonkey in Alpha (still using it) to be more stable than previously. Any chance of using Sylpheed but keeping the upgrade to the latest Seamonkey? Perhaps more controversially going right back to Dillo with mods or Hv3 both with links to more advanced browsers. Another thing is the flash 9 final is available and I hope can be included in the Seamonkey route Barry Kauler
SeaMonkey 1.1 was a big upgrade, so bound to have some issues. Probably
the next release will be improved, and will reconsider for Puppy 2.15.Eddie Maddox (greatnessguru<at>gmail.com)
> ..SeaMonkey 1.1, so I have rolled back to 1.0.6.SeaMonkey 1.0.7 is the latest in the 1.0 lineage... Eddie Dougal
Barry,did you try running the new Gxine from gdb? The fragmentation error can be something as simple as an image missing -- which it'll tell you. Buri
Gxine 0.5.9 is very buggy in Puppy 2.13. Have you tried to compile the newest version 0.5.11 ?Billcnz
Talking about Seamonkey, I notice that on a slow cpu the puppy build of
SM-1.1 is still very slow to load long web pages compared with the
official binary or firefox, which seemed strange since it's using
firefox's engine. For example times for loading this developers blog
page on a pentium 2 400 MHz:Seamonkey-1.1 puppy-2.14alpha build: 35 seconds Seamonkey-1.1 official binary: 9 seconds firefox-2.0 8 seconds Note: for a fair comparison I remastered using the official binary so they were both running from the sfs. I did another comparison on a computer with a fast cpu and the difference is much less noticeable (down to a couple of seconds). Bill Standard8
What issues do you have with SeaMonkey 1.1? Have you actually checked there are filed bugs? Why not post a list of them?BarryK
Bug reports, and some followup discussion, were posted on the SeaMonkey developer's and user's forums.
|
Improved network detection at bootuphttp://www.puppylinux.com/forum/azbb.php?1170527918 rarsa
Barry,I've uploaded an improed version based on your suggestions and PaulBx1's suggestion. Now the script only waits the minimum it needs to wait. BarryK
I would like to throw in another suggestion. 'joki' posted this:http://www.murga-linux.com/puppy/viewtopic.php?t=13130 That is, we background rc.network and keep booting. I'm wondering though, if we would have to wait for rc.network to finish at the end of rc.local0, as perhaps user code in rc.local, or the firewall, would want the network to be up (?) -- or, could we just ignore whether rc.network has completed or not, continue on and start X? HairyWill
Please don't just background it. At the moment once X starts I know
everything is running and I can use it. It really irritates me that you
can never quite tell when XP has finished booting with loads of
important things starting after the desktop has been made visible.Once the user interface is there it should be useable, very often the first thing I do after booting is start my browser. That being said sometimes I'm hunkered over my machine waiting to play a local mp3, being able to CHOOSE to background the dhcp call during boot would be fine. In that case I'd know I was starting without full network support. Will |
Kernel recompiled, Wireless Tools upgradedI then recompiled the source with these changes, as modules: 1. Bluetooth support 2. Software MAC addon to ieee80211 stack 3. Wireless bcm43xx, zd1211rw drivers I did not turn on SMP support, as the docs warn that the kernel may not work with some uniprocessor PCs. For SMP, I will have to do a separate compile of the kernel and offer that as an alternative for those who create their own Puppies. I also compiled the Dazuko device driver. This is used by some virus scanner and intrusion detection software, and the source package has examples that show how someone can write their own software to use it. I configured with '--mapfile=/usr/src/linux-2.6.18.1/System.map --enable-syscalls --disable-local-dpath' -- the latter option means that the device driver will use the '__d_path' function exported from the kernel rather than its own inbuilt function, which apparently is required for an SMP kernel (the inbuilt __d_path function is unsafe with a SMP kernel). I have upgraded Wireless Tools to version 29.pre10, as this has improved WPA support. From comments on the forum and sent to me, it seems WPA is the way to go. rarsa
"That's the way to go".I started this week implementing WPA support on the network wizard. I've finished the interface and with great support from Tempestuous I'm finding my way around all the options for WPA. Just yesterday I was able to connect to my home network using WPA. After the problem loading the configuration at boot, WPA was the next most requested feature for the network wizard. PaulBx1
Rarsa's on a roll! I can't wait to give that a try... debernardis
Thanks for the BT drivers. Hope that I or someone else succeed with openobex. I am longing for the beta! Ted Dog
Darn, I should have spoke-up on the last of a few DVB modules left out of the mix. CONFIG_VIDEO_CX88_VP3054=m CONFIG_VIDEO_CX88=m CONFIG_VIDEO_CX88_ALSA=m CONFIG_VIDEO_CX88_BLACKBIRD=m CONFIG_VIDEO_CX88_DVB=m CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=y & check ONFIG_DVB_OR51211=m CONFIG_DVB_OR51132=m This is for a popular North American linux-only HD card, pchdtv hd3000. Just watched the Superbowl on my puppy basic machine Barry Kauler
Ted Dog,It's a lot of work recompiling the kernel, as I also compiled all the extra modules (just in case there's a symbols problem with the previous modules), and I have to manually reconstruct the Unleashed kernel hierarchy in Unleashed. But, I've written down your request and will include those DVB modules next time round. Ted Dog
I
found the kernel compile easy but long process, the repackaging of the
modprobe, & all the rest, finding disappearing firmware directory,
etc was difficult. It also needs firmware and /DEV changes. I'll
package up all changes and give you a link. I have a package of very
small HDTV tools, but am debugging a very small video recorder software
which should be a good match with puppy before I post a testing iso. rarsa
I've just uploaded a test version of the network wizard with WPA support:http://www.murga-linux.com/puppy/viewtopic.php?t=15180 |
Locale files now in "zdrv" moduleI have modified the 'createpuppy' build script to include the locales in the 'zdrv_xxx.sfs' file, and I modified 'chooselocale' to recognise this. That is, if the "zdrv" file is present, 'chooselocale' will fetch the locales from there. If not, the fallback is the Internet download. What is the point of doing this? For one, locale can now be chosen without having Internet access. Which means that we could have it as one of the questions asked at first bootup -- currently Puppy only asks about keyboard layout, but the correct locale setting is also required to truly internationalise our Puppy. We do want to minimize the questions asked at first boot. Most things are autodetected, but there is a dialog window that asks keyboard layout (country of keyboard) and at least two windows for setting up the X server. To keep it at the minimum, I was wondering if the keyboard layout and locale could be combined into one simple dialog window? I don't know if this is too difficult or not ...for example, a user could choose "French Canadian" from the dialog and from that we assign an appropriate locale and a keyboard layout. Lobster
I am wondering if there is a simple way of finding the keyboard. For example my UK keyboard has a £ above the 3there is also a euro sign around the 4 . . . Can a keyboard be pinged? klhrevolutionist
I was kinda hoping that you would bring back the questions at boot-up.Actually it would be nice if alsa ran by itself and auto-magically setup any cards/chips found w/out need for user input. Is it at all possible that when the keyboard layout/country is selected that it could auto-magically "insert" the locale chosen for the same keyboard ? I hope that made sense... Keep up the great work ! Sage
Lob: A keyboard is just a simple signaling device - it has no [i]a
priori[/i] knowledge of what is written on the keys; that is down to SW
interpretation once you have instructed it which look-up table to use.
Indeed, you can remap any key to do just about anything you wish -
useful if one key fails on your favourite keyboard. As for establishing the locale, even (!) 'doze needs to have this input during installation - hence the world map and timezone selection options. For live-CD s, other than in multisession mode, it will always be necessary to re-enter this info each time, so it is entirely appropriate, albeit irksome, that this should appear in the boot sequence. PaulBx1
You
can combine the two, but there will be the occasional case where locale
and keyboard are not the same. Perhaps the keyboard question can be
used to select the *default* locale in the next question, rather than
giving the user no choice.In most cases, it is no burden whatever to answer a few questions on first boot, because Puppy is still WAY more easy to "install" than windows or a big distro. And it's not done every day. The only case I can see where this is not true, is when someone has to manage multiple machines and uses Puppy for maintenance when Windows is broken. In that case, can a remaster cause those those questions like locale to be already set? A little more irritating is when booting into ram only, which is occasionally done by many people even if it's on the same computer one always uses. Perhaps Puppy can look for a file on the hard drive called "puplocale" for keyboard, locale and monitor information (maybe just "xvesa" for that), in the case of not using a pupsave? rarsa
Paul,When using "load to RAM" my main intention always is NOT to use the HDD, so going to the HDD to load something is self defeating. sir.rainbow
In
case of a ram-loaded puppy, you could add an option on the boot
command-line like locale=en_US or keyboard=it_IT, because you anyway
also have to write "puppy pfix=ram" and it wouldn't add to the number
of questions during the boot.Leon
When choosing Slovenian locale all this settings could be set at once:Locale: sl-SI Keyboard: Slovenian Timezone: GMT+1 Barry Kauler
klh,On most PCs Puppy does automatically detect and setup sound. It's just the odd one, notably isa-bus types, that need manual intervantion. Yes, that's what I want to do, the user just has one dialog window, chooses the country or whatever, and keyboard layout, locale and timezone all get automatically assigned. Hmm, as most people have Windows installed on the PC, or another Linux distro, I wonder if we could just pick up the information, then be truly automated. We would need someone with deep Windows know-how to find out how do that! Sage
Not
sure that 'most people have Windows installed on the PC, or another
Linux distro'. Most users I know are using a second, or more probably
an n th. machine! It would inadvisable to tangle with Windows for any
reason whatsoever on account of excessive bloat and an unusually poorly
shoehorned assemblage of OBEs rather than a coherently written OS. To
extract info from another Linux distro already present might prove more
of an intellectual exercise than a useful procedure to avoid one or two
keypresses?pakt
I
agree with Sage that Puppy should *not* assume Windows or another Linux
distro is present. This is bound to lead to complications The best idea so far is PaulBx1's: "Perhaps the keyboard question can be used to select the *default* locale in the next question, rather than giving the user no choice." Paul nyu
Berry, would you please include East Asian locales as well?Thanks in advance. PaulBx1
"When
using "load to RAM" my main intention always is NOT to use the HDD, so
going to the HDD to load something is self defeating."Yeah, I kinda guessed something like that would be true. Just thought I'd throw that out there though, to see if it would get knocked down. I once took on a task at work to read/write the Windows registry. It was one of the most disgusting bits of work I've done, and frustrating as hell. Don't mess with Windows unless you are a masochist. The more I think about it, on this ram boot question, the more I think the policy should be "leave well enough alone" and "don't concern yourself about a question or two". I mean, add the locale as a separate question, who cares? It's just not that difficult or irritating to deal with. klhrevolutionist
I
only use puppy on my hd.. I don't see why it cannot check for an
existant pupfile or hd install of puppy and use the defaults for that.As for using windows, I believe puppy can make use of windows fonts if windows exist on hd & not many people seem to mind that.. So long as puppy does not make use of the bad/ugly stuff installed on a windows box I see no troubles. Buri
It
would be nice to have the possibility to switch from one keybord-layout
to another with a mouseclick working with a text editor/control.
|
2.14ALPHA HD frugal install bugfixHowever at bootup Puppy was unable to find one of the files. The guys found that they had to shuffle files around in different partitions to get Puppy to find them. This problem did not exist in Puppy 2.13. Actually, there was a bug in 2.13 kind of similar, and Dougal fixed it, but now we have a new bug. Anyway, Dougal has now fixed that too. Forum thread: http://www.murga-linux.com/puppy/viewto ... 4488#94488 |
Unionfs "bug" workaround and filesystem purgeThe .sfs has its attributes changed to 766 so will not trigger the scan at future boots. But, if the partition containing the .sfs file is mounted read-only then the scan will happen at every boot (normally extra .sfs files are in the same place as the pup_save.2fs file and the partition is mounted read-write, so this problem won't occur). I have also added a new boot parameter, "pfix=purge", which is like "pfix=clean" (the simulated version upgrade) but more radical. The intention of this "purge" is to fix a system that is broken in some way. A normal version upgrade will make sure all 'official' files override any user-created files, but only if the official files have a newer modify date -- the purge option will override regardless, meaning that you will loose some customisations, like the desktop layout. The purge also forces a total scan of .sfs files for bogus Unionfs whiteout files. Basically, the idea of "purge" is to give your Puppy a good bath, get him back to a pristine (and functional) state. PaulBx1
I
like this purge idea; I had been wondering how to get back to a
standard Puppy after miscellaneous mods such as we often try from the
forum.Does your purge save the "purged" files in /tmp like the upgrade process does? That would seem to be a good idea. Also, this raises the question, what files can we modify and not have them get purged? For example, is rc.local still safe from a purge? I'd like a list of files that are "user territory"... BTW it occurred to me, after suggesting using the devx file permissions for a flag, that there is a slight risk that someone might change the permissions manually and inadvertently start a purge. The use of permissions for a flag is non-standard after all. The risk is pretty small though. If the purged files are saved, maybe it doesn't matter. Puppy developers are the best! It just keeps getting better and Puppy is my favorite distro. The unionfs issues have crossed my mind often but for now I am content with GuestToo's idea. This may seem drastic but here's the workaround I've used successfully since at least Nov19. I created a script based on GuestToo's 2006.10.15 post on PuppyForum. I execute it at the start of rc.shutdown every time: #========= /etc/rc.d/rm_un_wh ================= echo -ne "Executing /etc/rc.d/rm_un_wh... (clean up pup_rw 'wh.*' whiteout files)" sync usleep 300000 # the following is all on one line: #find /initrd/pup_rw -noleaf -name '.wh.__dir_opaque' > /tmp/wh.txt find /initrd/pup_rw -noleaf -name '.wh.*' > /tmp/wh.txt WH_CNT=` expr 0 ` cat /tmp/wh.txt | while read J do echo -en "." WH_CNT=` expr $WH_CNT + 1 ` echo rm -f \"$J\" &>/dev/null [ -r "$J" ] && rm -f "$J" &>/dev/null done echo $WH_CNT "files cleaned." sync #========== end rm_un_wh ======================= I first tried G2's original which only rm'd '.wh.__dir_opaque' files, but still noticed odd things not working, files missing, but were in the .sfs. I've used this clean 'em all approach in Puppy 2.02, 2.12, Muppy05, Muppy06, JWM, IceWM, KDE full desktop (xwin startkde) both with and without mupp212.sfs, KDE355mini_212.sfs, OpenOffice-204_212.sfs and both frugal installed CD boot and Grub mbr boot on two PCs, one heavily used everyday. Also set up a friends HP Vectra PIII-500/128MB with Muppy06, (and rm_un_wh) in Dec. My reasoning is this: I'd rather have a few extra files reappear after being deleted--generally system files from the orig .sfs's, than to have missing files or folders that should be there! I've only had two minor problems that may be related to cleaning all '.wh.*' files at every reboot. First MU's my-roxapps/autostarter-MU runs scripts in the folder /root/autostart. When I deleted a couple of his entries, they of course reappeared and were executed on reboot. So I just modified them with comments so that they would no longer execute as I want, in effect modifying instead of removing the files. AFAIK the only other problem is that the rm_un_wh script above echoes a '.' for every deletion, often a screen full or more if Puppy's been running several hours, but my attempt at displaying a count always displays "0 files cleaned"! I think it's a usage/syntax error, I'm not experienced with this kind of script. The only other gotcha I can think of is the decidedly remote chance that a user's/apps' file happened to be named '.wh.my-important-file'... which would get deleted and have to be restored from a backup pup_save file. But there's probably a way to prevent that, or not? P.S. Sorry for the long-winded post. If anyone can point me in the right direction to fix the zero count bug in my script, thank you in advance. -- John (TazOC) In keeping with the Puppy theme maybe the purge ought to be called a 'Dip'. Like what the vets do to get rid of all the fleas... :) TazOC
JohnMc,Yeah, Puppy Dip, I like that. 
I renamed the shutdown .wh.* scan on my PC pup_dip instead of rm_un_wh.
I also fixed the counter, refined the scan to exclude /tmp, ~/autostart
directories and log all changes to /var/log/union/pup_dip.log.It appears unionfs prevents user creation of files that begin with .wh.<anything>. Creating files or folders in rox and/or command line fails with "Operation not permitted." So I'm more confident this dip won't hurt Puppy! |
Unionfs "bug"Actually, it isn't a bug, it's a "feature". Let me quote from Unionfs docs (Aufs has this same "feature"): Namespace unification requires that there is a way to mark a directory "opaque" - meaning that lookup/readdir should not merge the objects of this directory with those of a directory of a lower priority. When one creates a new, empty directory using mkdir, the new directory should be empty according to POSIX/UNIX. To prevent contents of directories on lower priority branches from appearing in this newly created directory, the directory is made opaque. I tried an experiment. Without the "devx" module present, I installed the "qt" library package, which goes into /usr/lib/qt. It also created /usr/lib/qt/.wh.__dir_opaque and /usr/lib/qt/lib/.wh.__dir_opaque (in the top layer, these files cannot be seen at the merged "/"). This means that when I later added the "devx" module, which is a new bottom layer in the union, all of the directories and files that it has inside /usr/lib/qt are missing. Back at Puppy v2.11, I did implement a fix for this, as reported here: http://www.puppylinux.com/blog/comments.ph ... 011-062015 However, this only operates on the pup_xxx.sfs layer (the guts of Puppy) upward and makes sure that all of the directories and files in pup_xxx.sfs are visible at the top. What I did not think about at v2.11 was the "devx" module. We can't delete whiteout files while,the union is running, as that can screw things up mightily, it has to be done at bootup in the 'init' script before the union of the layers is created. So, at this stage it looks like I will have to modify the 'init' script to detect if the "devx" module is present and perform an analysis to clear out any higher level whiteout "opaque" files that might block its visibility. Puppy v2.11 and later only do this whiteout cleanup at a version upgrade, or for the boot parameter "pfix=clean" (a simulated version upgrade) as it takes some time to do. Unfortunately, this means that if you add the "devx" module to your Puppy system then you will have to do the "pfix=clean" -- unless I can get the 'init' script to detect that "devx" has just arrived and not there before, then do a forced cleanup. This is a progress report, to let you know of the issue and that I'm onto it. Note, I think that those "opaque" files get generated in other circumstances also that are unnecessary, and that really is a bug. Nathan
I've witnessed this behavior too, and am hoping there will be a fix for
more than just the official pup_XXX contents and the devx module, but
for other modules also. I've created several addon modules now and
experienced the glitch under various circumstances.More severe, I had a bit of a lockup on my computer recently and when I rebooted the entire /usr/X11R7 directory was gone. It turned out to be this same problem, unionfs created a whiteout file there in the top layer. This was Puppy-2.14 so apparently under certain conditions the bug still occurs on the 'official' Puppy files and directories. PaulBx1
"...unless I can get the 'init' script to detect that "devx" has just arrived and not there before, then do a forced cleanup."This is easy to do, assuming you can create a file somewhere at this stage of the boot. At the end of the detection process, create the flag file. At the beginning of the detection process, look for devx and this flag file. If devx is there but not the flag file, it is the first time and cleanup is required. If both are there, then cleanup has already been done. Of course the flag file would have to be revision-specific, just like the devx file. The "flag" could be something else too, like a change in the permissions of devx. You probably have figured something like this out already. It is a common sort of thing in hardware design, detecting leading edges of signals. pakt
Not to throw a wrench into the works, but from Linux Magazine, March issue, refering to Knoppix 5.1.0 with kernel 2.6.19.1:"The unionfs file system has given way to the newer aufs, an entirely redesigned and reimplemented unionfs. This provides Knoppix 5.1.0 greater stability and performance." Would aufs help the situation with Puppy? Paul BarryK
In
the Aufs docs it states that it has the same behaviour, creating a
"opaque" whiteout file when a new directory is created. So Aufs will
have the same problem that I had in my experiment with the "Qt" package.Other conditions in which Unionfs creates unnecessary "opaque" files may have been fixed in Aufs though -- but I'm speculating. BarryK
Paul, no, I hadn't got that far. The idea of changing the attributes of a file is good.Nathan, yes, I think I know how to do it so that it will cleanup all mounted .sfs layers. I was going to code a solution last night, but went off on a tangent investgiating 'inotify' and other systems that can notify whenever a file or directory has been created/accessed/changed/opened/closed/renamed or whatever -- I was thinking of another way to solve the "opaque" whiteouts problem, but it didn't work out. So I'm back on "Plan A" today. SunBurnt
I
suggested an advanced SFS file that automatically adds/removes menu
items & desktop icons when the SFS file is added/removed.The basis of it's functioning was to copy up to the Save file all the dirs. in the SFS file except the /usr dir, NO WHITE OUT PROBLEMS !!! Unless the white out happens to the SFS files /usr dir. Upon removal, the copied files are deleted from a list in the SFS file. Now I know Puppy-2 can't add/remove SFS files while running like Puppy-1 can, but very soon we hope that this'll be fixed, & it will be. ================= A fix I suggested for Puppy-2 swapping SFS files made 2 unions, one for the Save file that's unioned on / that never swaps, & another union for the /usr dirs. inside all the SFS files that're unioned on /usr. So the loop devices & SFS file mount points are outside the /usr union. This should allow UnionFS to swap SFS files reliably in Puppy-2, & it wouldn't change the file system structure so installs etc. fail. |
Network Wizard and 'createpuppy' bugfixeshttp://www.puppylinux.com/forum/azbb.php?1169956636 I'm not sure if I fixed the particular reported bug, but what I did find is that /etc/networkmodules was missing. This file is a list of all available network modules and is read by the Network Wizard. So, where did it disappear to? ...rarsa had such a file in his Network Wizard package, however I had deleted that before creating 2.14ALPHA, as the file gets auto-generated when the live-CD is created. I then discovered the autogeneration of networkmodules did not work properly, so we ended up with no networkmodules file. So, first thing. Rarsa, remove /etc/networkmodules from your package, as it is autogenerated. Secondly, I fixed the autogeneration. I have posted the correct 'networkmodules' file at the above forum thread. Just download, gunzip and place at /etc. In Puppy Unleashed, the 'createpuppy' script builds the live-CD iso file. This script now correctly creates /etc/networkmodules in the iso file, or more exactly in the pup_214.sfs file. Then I looked further at the 'createpuppy' script and found a related bug -- the script offers a choice to create a basic set of drivers built-in to pup_214.sfs rather than have the complete set in a separate zdrv_214.sfs file. The "built-in" option is the same as Puppies before we had the "zdrv" file. Anyway, the "built-in" choice wasn't working, all the supposedly built-in modules weren't there in the final pup_214.sfs. The cause of this was the same reason the 'networkmodules' got left out. So, it's fixed. rarsa
The Network wizard package I provided does not include that file. I don't even have that file in my development folder. I've always considered it part of the base puppy, not part of the network wizard. I've provided a dotpup of the package, maybe someone else included that file when converting to a pupget. Do you want me to start providing the updates as petgets? Barry Kauler
rarsa, apologies. I had an old 'networkmodules' file in the Unleashed
package that I had created from your latest DotPup, and I used an older
Unleashed Network Wzard package as the template and accidentally left
the file in -- so, it is my error.For Network Wizard updates, if you want to cater for current Puppy users then probably stick with DotPups. Probably when 2.14 is released then we can standardise on releasing new packages as PETs. |
Package and menu management improvementsThe technique I am using for generating the menu from XDG specification files (including the .desktop files) uses a script called 'fixmenus' that is called by petget, rc.update and createpuppy scripts, that is, whenever the menu configuration file needs to be updated. I have now created separate template files that 'fixmenus' reads. These are located at /etc/xdg/templates/ and look very much like the configuration files that rarsa developed earlier. For example, /etc/xdg/templates/_root_.jwmrc is the template file for /root/.jwmrc, the configuration file for JWM. Now, if anyone wants to directly edit this file, edit the template file as the actual .jwmrc configuration file gets autogenerated -- it's pretty straightforward as the template file looks very close to the final product, and you can easily see the bits of it that are going to get modified. So far I have it setup so the the menu configuration files for JWM, Fvwm95 and IceWM are autogenerated. Nathan gave me some advice about how to speedup /usr/sbin/indexgen.sh, the script that autogenerates the master help index. I have made it faster plus added a few extra features. basically what happens with this script is that if a package is installed (or removed), if it has any help files they are automatically added to (or removed from) the main help index page (the Help icon on the desktop or in the menu). Nathan also suggested that if someone clicks on a PET package from ROX-Filer, there should be an initial confirmation window, rather than just install the package. I've implemented a basic window, and intend to add some bells and whistles to it later. debernardis
This
is very good news because I was quite worried - my carefully hand
crafted .jwmrc I was so happy about had already been killed once by the
new scripts (luckily I had a copy).Nathan
Thanks
|
Updated PETget for 2.14ALPHAhttp://www.puppylinux.com/forum/azbb.php?1169966166 Please also read the recent posts on this News Blog about PETget. |
More updatesRarsa: remotedesktopcl |