|
Puppy developer news:  Older news |  Later news |
Puppy Linux version 2.12 releasedThe release notes are here: http://www.puppylinux.com/download/release-2.12.htm The download page is here: http://www.puppylinux.com/download/index.html A few extra minor points to append to the release notes (please do read the Release Notes first!): This Puppy has JWM window manager version 1.8rc4, which is very much a compromise. It fixed some bugs that were in 1.7 but unfortunately introduced some new ones. Display of the applets in the taskbar is a bit quirky, and you will have to live with that for now. For Unleashed enthusiasts, it's all there on Ibiblio, but note that the 'createpuppy' script is not properly modified for creating a iso without the 'zdrv' file. It gets to a point where it states that it has executed 'pickmodules.sh' but doesn't do so. What you have to do, is after running 'createpuppy', do this: # ./pickmodules.sh 2.6.18.1 # ./complete2sfs # ./burn2dvd2iso Anyway, have fun! Do note the closing comment in the Release Notes: v2.12 has established a new base system that we will stick with for sometime. That is, we will stay with the same kernel version and we will keep refining the "zdrv" meachanism. So look toward the next few releases of Puppy as being consolidation of the status-quo and focussed on refinement and improvement of the user experience. kirk
Probably should upload the devx file to ibiblio or put a link on the download page.Downloading 212 now! Thanks Barry! Raffy
Great - thanks, Barry!John Doe
Yahoo!!Great work Barry! Jeff
Good job Barry!Thanks for all the work you put in! Is the USB Networking driver included in the larger release here? -Jeff Caesirian (hernan.garbarino<at>gmail.com)
hey there, congrats Barry!i'm downloading it now.. i really like your work and the work of the other guys who help and colaborate with puppy and the apps greetings from Argentina and please.. take some vacations! :P aussie
Well done Barry, connected to internet couple of clicks no problems, Puppy is number one in my book debernardis
OK the first thing I am doing Sunday morning is downloading this new and refined Puppy. Barry, you're great Sage
What
a tonic! Your commitment to the v2.12 baseline is most wise and will
appeal to a wide range of converts. If it is possible to make
subsequent fixes, patches and updates a simple, seemless, one-click
operation it will draw in even more support. Linux has a unique window
of opportunity until 30th January (pun intended). Let's use it to put
the word around. PR could never be more important.marksouth2000
Good
news Barry. Thanks for all the hard work you've put in on 212, and for
all the fun we've had with the betas the past couple of weeks.Mark Bill St. Clair (billstclair<at>gmail.com)
Mirrored:puppy-2.12-seamonkey-zdrv.iso puppy-2.12-seamonkey-zdrv.iso.md5.txt puppy-2.12-seamonkey.iso puppy-2.12-seamonkey.iso.md5.txt zdrv_212.sfs zdrv_212.sfs.md5.txt devx_212.sfs devx_212.sfs.md5.txt puppy-unleashed-core-2.12.tar.gz puppy-unleashed-core-2.12.tar.gz.md5.txt data
Downloaded and installed it on its own partition and grub on a floppy disk.Ut when I reboot it gives me this error....ERROR:INVALID or Unsupported executable format What does this mean? I dont want to install Grub on MBR instead I used floppy option and booting via another bootloader(by PCLinuxOS) It happened with any and all of your versions. Any help would be appreciated. GuestToo
you should ask your question on one of the forums that is up and runningit sounds like Grub can't find the kernel, vmlinuz ... check to see that it is where menu.lst says it is feri
212.very good job! rez 1200x800 wide ok on DELL laptop, ipw2200
wireless too! PureFTPd up/download anonymous/user OK, but have an
security problem: in anonymous login limit the upper directory to
/root/ftp and symlinks from this dir are inactive--OK, but on user
login ftp client have read/write acces to the whole / directory tree...Jeff
Is
it possible for the base ISO to activate the ethernet interface(s) if
present and try to DHCP on them like other live CDs do? To avoid the
need to run the connect wizard in vanilla DHCP environments (ie a lot
of home broadband networks today)?I think that would move things a bit closer to the perfect out of the box experience. Just a thought... -Jeff Bill St. Clair (billstclair<at>gmail.com)
There are links to all my mirrored versions, along with torrents, at:http://s3.amazonaws.com/puppy/index.html It's working for me so far, with the xfce window manager. natonzor (nathan.abussi (gmail))
hey.. i have an idea for the redistribution of the zdrv file.It is most likely that many computers (if not most) will only need some of the drivers. Would it not be possible that an app could be created, where it takes the information gathered at the autodetection at boot, find the relevant drivers, and dispose of the parts of the zdrv file that it doesnt need? Or, maybe.. have a web app where the user will submit the "Autodetect information" file (if one does not exist, one could be created), and all the processing happens on a server somewhere, so that the user does not need to download the whole zdrv file? Just a thought... Nathan MU
another mirror:http://puptrix.org/isos/Puppylinux-official/ I also moved all older isos from dotpups.de and htb65.de there, too. Mark nyu
I am trying to install a dotpup package butnothing works. The wget is trying to point to www.murga.org's old address which is 66.181.212.120 instead of the new address which is 208.109.22.214. Am I doing something wrong? nyu GuestToo
no, there are 2 problems1) the IP address for murga.com has probably changed, and it will take a few hours (or days) for the DNS servers to get the new address 2) the old address of John's Puppy forum was http://www.murga.org/~puppy/ ... it is now http://www.murga.org/puppy/ (without the tilde ~) ... that will break any link that points to the old forum, including all the links to download dotpup packages that are hosted on the forum you can copy the url and remove the tilde character if you like ... for example, on my dotpups page: http://puppylinux.org/wikka/DotPups copy any url link, for example, by right clicking the link ... use the link, for example, paste it in Seamonkey or Firefox's address box ... delete the tilde, that is, change ~puppy to puppy ... press enter or click the go button, or use wget to download the link ... then click the dotpup to install it Sage
It didn't work for me, but :http://208.109.22.214/puppy did. GuestToo
yes,
if the ip address for murga.org has been changed, it will take time for
the DNS servers to be updated ... until then murga.org won't workbut maybe the forum will have a different domain name, then murga.org won't work anymore, ever in either case, the /~puppy/ part is different in any case, to download a dotpup file from a link like: http://www.murga.org/~puppy/download.php?id=112 you can change it to this: http://208.109.22.214/puppy/download.php?id=112 and it should work F M Lynch (flynch1<at>se.rr.com)
I
reset my /etc/puppyversion file to 211. I also deleted the old zdrv
212.sfs file. I then ran Puppy 2.12 from CD. Modprobe prism2_usb did
not return an error, but the folder WLAN was still not created in /etc
with the needed files. I ran the manual install of the prism2_usb
driver. Still no /etcWLAN folder. However, on impulse, I clicked on the
Linux-wlan-ng pupget package (linux-wlan-ng-0.2.5.pup) I had previously
downloaded from the http://dotpups.de/dotpups/Wifi/ web site to get my
onboard prism2_usb module to work in Puppy 2.01, and had previously
copied to the Ver 2.12. root directory. To my amazement, it installed
the WLAN folder and all needed files in /etc. I used the
linux-wlan-readme.txt script, also downloaded from the same web site,
to configure and activate my prism2_usb module. It also worked. Now my
prism2_usb wifi is automatically detected, configured and activated on
boot. of Puppy 2.12. Hopefully, this process might work for other
folks, if they encounter wifi configuration problems.Spell check in Abiword does not work for me. It reports that the EN dictionary cannot be found. The Abiword documents I copied from ver 2.01 to ver 2.12 needed some minor formatting. The new improved fonts likely caused this situation. Simply adding and removing tabs in the appropriate places fixed those documents. I also noticed the right hand sidebar in puppylinux.com/news/ has some minor distortions, at least on my computer. The calendar dates overrun the column width. Some of the other notes also overun. Font change issues, must likely. I am not yet ready to replace my old reliable HD install of Puppy 2.01, but I am seriously considering the possibility. Thanks Barry , and all you other very talented contributors to this magnificent project. aussie
I have posted a similar message on the Developers forum, however will repeat it here in case somebody has more info. Tried to access the main forum received the following message "Critical Information You have been banned from this forum Please contact the webmaster or board administrator for more information" As a long time user and promoter of Puppy and contibutor as "aussie" can someone enlighten me as to the reason for the above message. I hope it can be sorted quickly Thanks BarryK
aussie,John Murga is the owner and administrator of the main Puppy forum. If he was going to ban you, for whatever reason, he would have notified you beforehand. There is a process that John follows, I think a first then second warning if anyone misbehaves. Congratulations on your excellent os. I just installed 2.12 as an upgrade and all went extremelly well with one little exception. The only problem is that the DotPups which I had installed previously are no longer on the "Start" menu. I can access them from rxvt. Is there an easy fix? Jeff
I
don't think this got enough attention... Barry the new fonts really are
a massive step forward in the visual polish of the interface. Good
work, and saving space too!-Jeff Sage
Who could possibly criticise?! But was hoping for the scsi drivers in the zdrv package! Maybe next time?Nick
Love 2.12~Rdesktop links to the wrong location.... aussie
BarryReceived no notification from John Murga re this "banning" fiasco. I am under a bit of pressure from the group I am associated with who are miffed by this "banning". I have posted a statement in the Developer's forum, under "General discssion about Puppy" sub heading "John's board". I sincerely hope this incident does not lead our group to leave Puppy for another distro, being West Australian's we regard Puppy as number one, however at the moment not a happy crowd. Thanks Raffy
aussie, Beem was also affected (cant login), so he registered again in
the forum ("back to square one", he says). there are a lot of spammers
lately and some deletion accident can happen. aussie
RaffyTried to re register still no joy, the last resort left is for me to email John Murga, to try and get it sorted, I realise things can go wrong, but the group I associate with feel a bit let down by this incident. Thanks BarryK
aussie,Yes, email John and ask him. This developer news blog is not the best place to be discussing this. You need to get feedback from John, then if there is still something unresolved you can send me a p.m. aussie
BarryAll resolved have been in email contact with "flash", some misunderstanding had occurred, everything back to normal, sorry about using the developer news blog, was under some pressure to get the "banning" unbanned as quickly as possible. Thanks |
More bugfixes: NTFS, USB, keyboardGuestToo pointed out that vfat/msdos partitions can be mounted with the 'shortname=mixed' option to get around that, but the ntfs-3g driver does not have that option. So for Linux, pup_212.sfs and PUP_212.SFS are different. I fixed the problem in the 'init' script by detecting the upper-case filename and renaming it. Here is the thread that discusses it: http://www.puppylinux.com/forum/azbb.php?1163546272 Leon discovered a bug with keyboard language settings. When you boot Puppy and get the text-mode dialog window to choose keyboard layout appropriate for your country, if you choose "slovenian" then you do get the correct layout for the text-mode console, but when X graphics mode starts, the "sk" layout is used. That was my ignorance -- "sk" is Slovakian, the correct choice is "si". The script that was fixed is /usr/sbin/xorgwizard. Many people discovered a problem with USB after installing Puppy to a h.d. (full install, not frugal). USB drives were detected as present, but could not be mounted. I have isolated the problem, and we do have a manual workaround. I need to do a bit more work on the 'modprobe' script to fix it properly though. Discussion of this problem in this thread: http://www.puppylinux.com/forum/azbb.php?1163431099 Raffy
+About the keyboard choices, as Puppy is English by default, would a "us" keyboard be appropriate as first choice? Thanks!GuestToo
actually, in this case, on a vfat fs. the default shortname=lower would
automatically fix the problem by lowercasing short names ... mixed
would display the names "as-is", that is, all uppercase, which would
mean the file would not be foundthe thing is, depending on the options used when mounting the file system, and whether it is vfat or ntfs, short names will be stored differently (they may be converted to all uppercase, or all lowercase, or stored "as-is") and they will be displayed differently too ... so renaming a shortname file may not do what you think it should do ... you might want to try a few test cases to be sure what you are doing is actually working and it's not just Linux ... Win 9.x and Win 2000 and Win XP each have their own way of storing shortnames one workaround would be to make sure all such file names have more than 8 characters ... long file names should not have case problems this is not a problem if you only use LInux file systems like ext3 ... but Puppy does not have that luxury BarryK
Well, I mounted a NTFS partition (Pmount uses the same options for
ntfs-3g as does the init script) and created a short filename all
uppercase then used Rox to rename it. It then appeared lowercase and
passed a test in a terminal window as being lowercase.Changing the subject, I pinpointed the cause of the hanging when trying to mount a usb drive in full h.d. installation. My modprobe script executes 'sync' and this is what hangs. I tried the non-busybox sync, same thing. When the kernel calls modprobe to load a module, it will not work if sync is there. I removed the sync and it worked. I also redesigned modprobe script to allow reentrancy. BarryK
Raffy,yeah I gotta do that one of these days... Jeff
Is
it possible to pass your keyboard choice to and video settings as
kernel options at boot time so we can bypass the menus if we know what
we want?-Jeff BarryK
Currently the boot option 'PKEYS' is accepted, for example:PKEYS=us To see the 2-letter choices, go to Setup -> Mouse/Keyboard Wizard and choose the "old 2-letter method" for keyboard layout. PaulBx1
I had run into the problem of filename case on USB flash drives:http://www.murga.org/~puppy/viewtopic.p This ugly issue promises to bite over and over again. |
New drivers, various improvementsJason (plinej) made a couple of improvements to the Pmount drive-mounter script. For BETA2 I "fixed" a bug in the pupget script, which it turns out causes another bug. So, I have undone the bugfix, will revisit that one sometime. Dougal's enhanced CD-remaster script has been updated for 2.12 and will be in the live-CD. I have recompiled the acx driver (for Texas Instruments ACXxxx wireless chips), using the latest source, 20060521 snapshot. Jason fixed a small rendering problem with MUT. The new fonts are a bit wider and didn't fit quite right. cthisbear
Puppy 2.12 Beta 2 finally booted my next door neighboursproblem computer....all others would not work. Great work from you and all the Puppy trailblazers. I have distributed quite a few puppies this week. I even left one at John Howards electoral office today at Gladesville - Sydney. Expect a few G-Men types at your door soon brother. Maybe Helen Coonan might enable broadband to you sooner. Regards Chris. Jeff
Great work guys.I see the development cycle is as fast as the OS! -Jeff BarryK
I have also solved the USB problem for a full h.d. installation. It is discussed in this thread:http://www.puppylinux.com/forum/azbb.php?1163431099 Let's see if I can copy my last post: Okay, I found the problem. I installed the latest Puppy to h.d. on my laptop, probedisk and probepart recognised a usb pen drive, but Pmount hung when I tried to mount it. So, I used 'KP' to see what processes are running, and saw this: [pre]/bin/sh /sbin/modprobe -q -- nls_cp437[/pre] The kernel or the vfat driver will have issued this as the vfat/msdos filesystem requires the nls_cp437 character set. The '-q' is okay, it just means "quiet". However the '--' seems to have flumoxed my 'modprobe' script. I don't know what purpose it serves, it isn't in the docs for modprobe. A quick fix is to mount nls_cp437 manually: [pre]# modprobe nls_cp437[/pre] I also found that running the original modprobe executabel directly like this: [pre]# modprobe.bin -q -- nls_cp437[/pre] works fine. So, the '--' is supposed to mean something. I will have to modify my modprobe script not to hang at least. Marcos (marbimba<at>gmail.com)
Umm barry youre the best!!!! dont leave this magnific project please!!!
|
Small bug fixed in Xorg WizardDougal found an interesting utility program that could be helpful in improving Xorg Wizard and I will check that out for v2.13. There is a lot more work to be done with this Wizard, targetted for 2.13. The main problem is widescreen LCD. I popped into a local PC-parts discount shop last week to buy some DVDs and saw many of the desktop LCD monitors on display are widescreen -- so, this seems to be a trend and has to be solved. I have partially solved it for the Intel video chips, but a more general solution using modelines is required. The Xorg auto-probe and edid utility return modeline information for the monitor, but getting Xorg to use it has been the problem when I previously tried. BarryK
A few people have commented that the new fonts are rendering too big. This can be adjusted downwards by reducing the value inControl Panel --> Set global font size Then restart X. The default is 84. ...should I tweak the default setting down a bit for 2.12final? Jason Pline
I prefer 72 but it's easy enough to change it yourself.kirk
I like 78. At 84 the extract button on Xarchive is hidden.PS: Betaftpd seems to be broke. I posted an alternative at: http://www.puppylinux.com/forum/?1163553598 And GuestToo posted one at: http://www.murga.org/%7Epuppy/viewtopic.php?t=12691 Raffy
Reducing the default font size can perhaps solve the MUT labels getting
outside their boxes (?):
http://www.murga.org/users/puppy/viewtopic.php?t=12733 The current font size is O.K. for 1024x768 display, but is too large for 800x600 display. Maybe a tip about how to adjust the default font size should be placed in the first-boot splash page. GuestToo
ftp servers do not seem to like unionfs mounts ... they will work if the file dir is in /initrd/pup_rw, or a mounted driveJeff
Hi Guys,Something I wanted to mention. Ubuntu 6.1 seems to have the XOrg modelines issue sorted out. I haven't looked under the hood to try and figure out how they do it, but the final release CD correctly detects on all the PCs I've tried it on. It picks up my Radeon X800XL card and my 1280 X 1024 Samsung flat panel. Its the only distro that has properly. It also works properly on my work widescreen laptop which is an HP with 1280x768. Since its all open source, perhaps we can figure things out by looking at what they do? Also, is it possible to have all available ethernet interfaces dhcp by default at boot, like most distros? That way if you have naked DHCP you'll have connectivity from the outset. The new release is working amazingly well on my machine. I can't wait to dig my teeth in to it and customize it. Great work! -Jeff Jeff
A
few additional questions... Is FireFox 2.0 available as a DotPup
anywhere? I'm also looking for SKype and aMsn. I've seen them in screen
shots but not sure where to find optimized ones for Puppy.Also, I think XFCE has gone to version 4.4. Has Dougal or anyone else had any luck with the latest version? Thanks! -Jeff PS - On an unrelated note. Audio works properly on a dell with AC97 that I test. It worked on my wife's Acer laptop but she had no volume control (soft or via hardware). It does NOT work on my main desktop which has an Audigy 2 ZS. It is identifying as an EMU10K1 chip which sounds right to me, as it works with that driver on PCLOS and UBuntu, but I'm not getting any audio even after I re-run the ASLA script. Any ideas? Dougal
Jeff: look at the XFCE-4.2.3.2 thread on the forum, I mentioned the new release there and why I haven't packaged it yet.Flash
FWIW, I have a widescreen HDTV (1360 x 768) LCD which I use as a
monitor. Puppy doesn't use the whole screen. There doesn't seem to be
an option for that resolution in the Xorg wizard. Since this is the
standard resolution for HDTV, perhaps it should be included in the Xorg
wizard.MU
Firefox:http://www.toddrichardson.com/archive/ http://dotpups.de/dotpups/Internet/ aMSN: http://www.murga.org/%7Epuppy/viewtopic.php?t=4657 http://www.murga.org/~puppy/viewtopic.php?t=8737 Mark kirk
In 210 I could get betaftpd to work outside of the union, but not in
212. The pure-ftpd I compiled in 212 works in or out of the union.Leon
Barry,Please include a patch for Slovenian keyboard layout in next version of xorgwizard. I described it on Puppy Linux Discussion Forum. http://www.murga.org/~puppy/viewtopic.php?t=12772 Jeff
Very impressed.I installed Dougal's XFCE pup against the 2.12 Beta 2 build, and did some customizing, then cut my first remaster. Wow. Boots in 55 seconds, gives me a nice XFCE desktop. My network is working now without the need to run the connect script. However, and Dougal does warn about this, my resolution came up as 640x480 and I could not get the XVesa server to work at all at my native 1280x1024. I did discover a very fast way to get to the proper res, if someone can explain why or if this helps, that would be great. If I run the XVesa/Xorg chooser wizard and then choose the XOrg server followed by the Resolution Changer, I can then select 1280x1024 even though I thought I was still in Vesa mode. Poof, nice 1280 desktop. However, it did not persist on the CD burn, even though I selected persistence after it happened. A minor issue. I can't believe how fast this is. And the 55 second boot time is damn impressive. If I put my switches on properly I think that includes moving it all to RAM as well. I'll be continuing to customize and adjust for a few weeks but I think I can achieve most of what I want. Thanks so much and I will be donating as mentioned before. -Jeff Craig
On the Skype question just unzip the version with static qt libraries and it works great.Dougal
Jeff: I think I know why it does that: XFCE doesn't know how to "listen" to Xvesa, that's why it has problems with it.So maybe when you select the Xorg resolution, XFCE gets that info and uses it? You should mention it on the forum thread, I think Flash never managed to solve the Xvesa problem, either.. Jeff
Dougal,Will do later today, just heading out the door. Here is the strange thing. I didn't actually SWITCH to Xorg, I just run the "within X" resolution changer. So I'm technically still on XVesa as far as I know, all I think it did (especially given how fast the res change) was poke a register I think. Does this sound possible? -Jeff Dougal
Jeff: we should be having this discussion on the forum, but since we're
here... I understood you were still in Xvesa, but I don't think it
matters to XFCE... maybe it just behaves according to what it's told...As for keeping the settings when you remaster: when you get the option of looking into /tmp/root, go and copy the (hidden) directory /root/.cache into /tmp/root/ and if you're using Barry's script, also /root/.config. |
Various networking issuesSo, I have just written a script that automatically generates the /etc/networkmodules file. This script is part of Puppy Unleashed and is executed by the 'createpuppy' script. Entries in /etc/networkmodules look like this: 3c589_cs "pcmcia: 3Com 3c589 series PCMCIA ethernet driver" The description now identifies whether the interface is a pcmcia, pci or usb. This improved /etc/networkmodules file will be in 2.12 final. There was a response that the firmware for the Linux-wlan-ng driver did not install when 'modprobe prism2_usb' was executed. I tested, it installs okay. Testers need to be sure that they have followed the upgrade instructions given in the release notes. In particular, get rid of any 'zdrv_212.sfs' file that may have been copied to the h.d. when testing BETA1. The Texas Instruments acx driver is missing its firmware. This was because I didn't know it needed any. Fortunately I have a PCI card with this chip, so I am just about to download the firmware and test it. Caesirian (hernan.garbarino<at>gmail.com)
hi,
a few days ago i tried that beta and i had problems with the network
wizard, it didnt load any module for my ethernet card... i was going to
report this error but i wasnt sure if it was a bug or my mistake during
the upgradei havent tried more things because without internet i couldnt download any package... well.. id like to have this 2.12final version by the way.. why it is so hard to install the C compiler?(i have 2.11) could i compile my favorite apps without having any problem in 2.12? excuseme if this was already answered before.. i dont have that time to read the forum and the whole release notes BarryK
Caesirian, I presume you are running the live-CD?A normal PCI ethernet card should have been autodetected and driver loaded. C compiler? ...running live-CD it's the simplest thing in the world. Download devx_xxx.sfs file to same place as the pup_save.3fs file, then reboot. That's it. BarryK
Okay, I've downloaded the firmware for the acx driver.My Netgear WG311 v2 card seems to be working, it has a ACX111 chip. I don't have any wireless signal here though. One thing, in Rutilt when I clicked on the "Scan" button it returned: "An error occured: can't trigger scanning. code: 11" Puppy has acx driver dated 20051003. I've downloaded the most recent, dated 20060521, I'll try that. BlackAdder
Barry,The firmware for the TI acx100/111 adapters is not quite straightforward. The required radio file differs according to the adapter type (there are three radio files AFAIK). My limited experience with the network wizard in the wireless context is that it needs a bit of a nudge at times. BTW the new fonts make Puppy look really great. all puppyes not only 212: if installed without pup_save.3fs it doesn't search for other xxx.sfs files like devx_212.sfs.So for testing I gave an hole partition like /dev/hdb1 for puppy (formatted reiserfs ) put there ok the hole directory tree , after that I copyed Puppy_212.sfs an evrything works fine , exept it doesn't look and load other sfs files.I presume for using them remains only to decompress them also to /dev/hdb. I shall prefer in future to work with pup_save.3fs file because I like the modularity with xxx.sfs files Puppy is centered on easy root use,and I agree with the idea, but for testing BetaFTP I had to create an usual user, it works Ok the download too.With this non root user I tried to launch xorgwizard but failed of course haven't enough right to acces /tmp and /etc for errlog and some config file.Maybe it is not to difficult to modify the script to have X for non root users? BarryK
I
have installed all the different firmware files. The driver knows which
one to load, it seems. I have a ACX111 chip and the driver loads the
tiacx111c16 firmware file.Warren S Carl (websafecomputers<at>yahoo.com)
RLT8150.c drive for BPI usb 10/100 Ethernet Adapter- I use it on old
laptops that have 16bit PCMCIA slots to get data off. I would like to
use puppy( is this driver going to be in final release. Will be test
2.12 beta2 todayCaesirian (hernan.garbarino<at>gmail.com)
actually i havent tried the live cd yet, i just downloaded the iso,
then extracted the vmlinuz, puppy_212, zdrv_212 and initrd and put them
in the same location where the old files was..then rebooted, it did the upgrade, it took lake 5 minutes replacing the files and then started.. and like i said before it didnt load the module for my ethernet card.. anyway.. ill just wait for the final 2.12 about the C compiler.. i dont use the live cd, i got puppy installed, and i always had problems with the compiler, i put the devx_xxx file (i also changed the number to my puppy version) and nothing happened motalaat (motalaat<at>yahoo.co.uk)
Warren S. Carl. I am looking everywhere for that driver you use for
your BPI USB LAN adapter. Can you please tip me on where to get it from?
|
Puppy version 2.12BETA2 availablehttp://www.puppylinux.com/test/ Please do read the release notes: http://www.puppylinux.com/download/release-2.12.htm Lobster
Looking forward to it. Quite slow download - so a faster mirror will be good wiki update http://puppylinux.org/wikka/Puppy212 perreando (perreando.linux<at>hotmail.com)
I
just booted from the CD and try to setup the wireless USB but when I
modprobe zd1211b it gives a "fatal error - module not found". Did
zd1211b made it to version 2.12?Thanks for all the great work! Jason Pline
Unfortunately I have the same problems I did with the first beta. My
audio is choppy and when I play the 2barks.au it just plays in a
continuous loop.# aplay /usr/share/audio/2barks.au I also need to remove the ehci module so my usb drive can be recognized. # rmmod ehci_hcd # modprobe uhci-hcd The fonts look great though. I guess I'll have to keep using 2.11 for now. Bill St. Clair (billstclair<at>gmail.com)
Mirrors at:http://s3.amazonaws.com/puppy/puppy-2.1 http://s3.amazonaws.com/puppy/puppy-2.1 http://s3.amazonaws.com/puppy/devx_212.sfs http://s3.amazonaws.com/puppy/devx_212.sfs.md5.txt http://s3.amazonaws.com/puppy/linux-2.6 http://s3.amazonaws.com/puppy/linux-2.6 .md5.txt I was getting 500 KByte/sec download rates from puppylinux.com, to my web service provider's machine. Still waiting for my copy to come down over my DSL line. I checked the MD5's after download, but I haven't checked them from s3.amazonaws.com yet. I'll test 2.12 beta 2 on my laptop later today, God willing. Have to leave this morning before the downloads complete. Bill St. Clair (billstclair<at>gmail.com)
Got the last link wrong:http://s3.amazonaws.com/puppy/linux-2.6 gdcrane (gdcrane<at>bellsouth.net)
Looks good so far Barrydid my usual thing - remove xorg and seamonkey, added opera and wine and everything works seamlessly so next I will reboot in ram and rebuild my pup_save Ted Dog
Using the problemaic VIA C3 motherboard, with RT2500 wireless card,
everything works out of the box (or DVD) Thanks! got a winner, gxine
full screen works, clean looking fonts - THNKSsugestion use xxmc verses xvmc, it works better on unichrome & other cards that I use. Revolutionist (klh<at>klh.org)
Mime-Types !Be sure to add MU: OpenOffice mime-types please. Great Work, nice to see T2 has 2.4 kernel... F M Lynch (flynch1<at>se.rr.com)
Modprobe of Prism2_usb did not return an error, but wlan folder in /etc
was not created. Therefore the wlanctl-ng configuration commands are
not recognized. ??The new fonts are very sharp. Thanks!! Bill St. Clair (billstclair<at>gmail.com)
My ipw2200 wireless interface now works out of the box.Everything else I've tried works good. I'm set for doing my work tomorrow in Puppy 2.12 beta 2. Emacs, Firefox, Thunderbird, my VPN client, Gnumeric, XChat, Gaim, J-Pilot (haven't synched yet), Ruby, rsync, sshd. All appear good. The free memory applet was scrunched when I first booted. Restarting X fixed it. marksouth2000
Works well so far, like the fonts although they default to huge on 800x600.Ralink 2570 (D-Link GWL122 rev B1) not yet detected out of the box, module not listed to load, either. Can be loaded with modprobe. Network wizard does not succeed in setting up rausb0 interface, however it can be done by hand using ifconfig, iwconfig, and rutilt to choose network and connect. Mystifying? Now to test frugal install and upgrade... tempestuous
Regarding F M Lynch's problem: unlike most other wifi drivers,
linux-wlan-ng does not use the hotplug subsystem to load its firmware.linux-wlan-ng has its own firmware loading utility, prism2dl, which should be located in /etc/wlan along with the firmware files and a few other standard configuration files. alienjeff (alienjeff<at>charter.net)
2.12beta2 reflectionsRan from Live CD on both desktop machine and lappy. Desktop: Tyan mobo, 600MHz Pentium-III, 384M RAM. Lappy: Gateway Solo 5150, 233MHz Pentium-II, 288M RAM, 3Com ethernet and wifi cards Observation: from the cli, top reports that 2.12beta2 uses nearly 15% more RAM than v2.11 does, regardless of running from Live CD or from a full HD install. Though not an issue for the 1Gb RAM crew, it [i]will[/i] matter to the older, less robust systems. Gxine: this seems to be a holdover from 2.11 and perhaps earlier -- the brightness control does nothing, nor do the other "video" adjustments in Gxine. Full screen seems to have been fixed somewhere between 2.11 and 2.12beta2, though. MUT: for some odd reason, the box borders around the word "mount" are smaller than needed. The right edge of the border box covers the letter "t" of "mount." Also, when I clicked mount of an external HDD, the system locks up tighter than Fort Knox ... seems to render the mouse inoperable. This is particularly odd, as this is unique to the 2.12 version; all other versions I've tried, numbering about 10, have not had this problem. NETWORK: though 2.12beta2 "sees" my wifi card when booting up, there's still no driver support for a very popular 3Com card (3CRWE62029A). Configuring the 3Com ethernet card went well, though several false hits showed during config. BTW, no luck compiling a driver for the wifi card under 2.11. Sigh. Haven't given up yet, though. That's it for now. Perhaps more later after further testing. Best regards. Bill St. Clair (billstclair<at>gmail.com)
Running Puppy from the Parallels Virtual Machine inside a MacBook
running OSX. Works well, and is about as fast as my Dell laptop running
Puppy on the bare metal.tempestuous
alienjeff, I presume you mean the Swallow/Poldhu driver from http://www.xs4all.nl/~bvermeul/swallow/This is not a standard kernel module, so you need to lobby Barry if you want it included. But it's quite an old driver, and won't compile under the latest kernels. I see here http://forums.gentoo.org/viewtopic-t-13 that someone wrote a patch for this driver back in the days of the 2.6.3 kernel, but there have been significant changes to the kernel since then, especially in the area of PCMCIA devices ... so you will have to wait until someone writes an updated patch. Hi, Have been running Puppy 2.10 (HD install) on Pentium 651 MHz desktop machine with 515 M Ram & upgraded to Puppy 2.12 without a hitch. Love the look, but when I try to access flash drives, Mut and Puppy drive mounter both freeze up. I have to kill Mut/Puppy drive mounter, but then I can't re-boot or shut down, have to turn the machine off. Before I turn the machine off, everything else still seems to work okay.Note: I could access the flash drives with Puppy 2.10. I use a generic USB 4 port hub - USB version 1.10 (Alcor) and the flash drives are a Lexar Plug drive - USB version 1.10 (128M) and an unnamed 512M USB storage device with USB version 2.0 (from Trend PC-Cillin promotion). Rob BarryK
I'm
puzzled, if you had typed "modprobe prism2_usb" it should have also
loaded all the firmware and executables from the zdrv file, including
/etc/wlan....okay, I have discovered a bug in the modprobe script that is messing this up, won't even load the module. BarryK
rob2306,perhaps you need to examine if there are different usb modules loaded compared with the earlier Puppy. In 2.12 you can use 'PupScan', in older Pups you can use 'lsmod' in a terminal. This thread is a bit long, individual bug reports will need to be continued in one of the forums. John Murga
Off topic ...Forum is down currently as my hoster has suspended my account due to a DOS attack. They have also suspended all my e-mail accounts. Hopefully it'll be resolved soon and we'll be on a new server. Cheers JohnM BarryK
John, sorry to learn about all your hassles with the host, DOS, etc.For anyone reading this, please continue feedback on 2.12BETA2 on the Developer Forum: http://www.puppylinux.com/forum/ To post, you have to register, and it requires email verification -- sometimes people have spam filters that bounce the verification email, so you may need to set an email from 'bkaulerATgooseeDOTcom' in the filter whitelist. Just a little extra note, I'm working on the 'createpuppy' script in Puppy Unleashed. It will be easy to choose to build a iso file without a zdrv file and with a usable set of modules like before, if you are into building small puppies. The zdrv file can still be provided later on the h.d. and Puppy will automatically find it, for extra modules if needed. BarryK
Jason and others, I would like to work on your problems, much easier if
you can start individual threads in the Developer Forum thanks.John Murga
Forum is backBut will be offline soon as we move it to a whole new server ... Hopefully it'll improve things dramatically. Cheers JohnM Brad C (Coulthard<at>ieee.org)
THANK YOU! EVERYTHING WORKS like a charm.i810 ipw3945 usb and touchpad at same time toshiba_acpi..... This one is a work of art.. Barry Kauler
Yeah, it's a funny thing, i810-family video was always troublesome, now for widescreen lcd it is working the best.pakt
Just shows how important good feedback is on non-working hardware. If
Barry doesn't have the hardware, how else can he add Puppy support for
it? bodigi
Hi, good job.Works perfect just fonts too big and during using cdrecord losing fonts at some places. reidi
Is anyone else having trouble with USB thumb drive installations (using
the Puppy wizard) and 2.12beta2? I'm getting kernel module errors early
on in the boot process, and then the usb device cannot be found so the
OS load hangs.
|
The shortlist is shrinkingThere was a bug in PupGet, I'm surprised noone reported it. I chose to install 'opera-9.02_STATIC_QT' package, but PupGet installed two packages, 'opera-9.02' and 'opera-9.02_STATIC_QT'. The script looked for packages of the correct name and accepted any name with a subset of the full string. Fixed. When I release 2.12BETA2 I will also release 'devx_212.sfs' and the patched 2.6.18.1 kernel source, so if anyone wants to try and compile the rtl8180 driver then go for it. Though probably the kernel source will not be required as the 'devx_212.sfs' module has the kernel header files and config files. Raffy
I
got to play with the tarball of openoffice_cutdown.tar.gz because it
won't install via pupget (in 2.10+ ?), and MU was kind enough to help
me with installing it directly - the result is an openofc.sfs that I
used with barebones 2.00 (that in turn has Opera9.02_static_qt on it). marksouth2000
Barry, a couple questions:1. Is there a way that Puppy could get to use the vanilla kernel sans patches? 2. Exactly which version of the r8180-sa2400 driver did you have your bad experience with? You didn't accidentally type "make disaster" did you? BarryK
The kernel in Puppy has the minimum number of patches and Puppy will
not work without those patches. Well, the squashfs patch anyway. There
are only two other patches, adjustment of the default loglevel and a
shutdown fix for Via chips and these are extremely minor patches. So,
the kernel in Puppy is virtually pristine.As I commented, I tried the same rtl8180 version as provided on the forum, exactly same tarball filename except that I downloaded it from somewhere else. marksouth2000
Thanks Barry, when you make the devx_212.sfs available I will see if I have any luck building the r8180-sa2400 driver.Regarding the patches, it would be reasonable to expect that squashfs and the VIA patch will make it into the kernel tree at some stage, not so? And the loglevel can be set at boot instead of in the kernel. Cheers, Mark Since you mention Opera when I install it the fonts in the bar on top of the screen with File Edit etc are ugly. That got anything to do with version or anti-aliasing or anything you can do? Which version and from where do you recommend? By the way, thanks for Puppy. Fiddling with it takes up a lot of my spare time and has almost become an obsession... Ted Dog
As
to kernel question. I found it easy to upgrade kernel in a full install
of 2.11 to HD. I was testing patches to fix UDF packet writing on
2.6.19 RC3 - mm version. Puppy init scripts only needed a single
correction. I think the new ideas Berry has like the zdrv.sfs are as
genuis as the multisession to CD-R was to the early 1.01 series. I
currently can switch back and forth between bleeding edge but plain
kernel (no unionfs or squashfs: no need on full HD install) and kernel
for 2.11Dougal
Barry, in the past I had problems of PupGet removing some of my
packages that had similar names to built-in packages and I remember
Nathan pointing out that PupGet searches for a string and doesn't
expect a full-word match. That means that "my-program-1.0.0" would have been found when searching for "my-program" I assume this is what you fixed? One request for the new Puppy: please add the application "paste". It was there in 2.00 and is gone in 210! BarryK
I can't even remember what 'paste' is. Something to do with the clipboard I suppose. But, where did I get it from?jorma p (jorma.piiroinen<at>danpat.fi)
Driver for Intel 3945 wlan?Dougal
I think "paste" is one of the core-utils. It takes two files and outputs them as one file with two coloumnsBarry Kauler
I
don't recall putting 'paste' into an earlier puppy... maybe it got into
a "devx" file? ...yeah, probably that is what happened, as the old
pre-T2 devx file was constructed in an ad-hoc fashion, mostly just
heaps of files dragged from Vector.Whatever, yes, it is in core utils and it is only 15K, so why not... it will be in 2.12final. MrPerson
Test post, using HV3 alpha13.waaahhh... |
More kernel modules compiledThe sis7019 driver is needed for the Norhtec MicroClient Jr. The chip is 1039:7019. Note, there is already an ALSA driver, snd_trident, for chip 1039:7018 and I wonder if that would work on the 7019 chip. The Linux-wlan-ng and rt73 are wireless networking drivers and they also have associated firmware and executables that I have included in the "zdrv" file. I attempted to compile the rtl8180-sa2400 driver, but failed. It was weird, running 'make' caused the entire source directory to self-destruct -- totally erasing itself -- I breathed a sigh of relief that it's destructive urge was contained. Mr Doolie
While you are compiling, please add support for Core Duo CPUs (i686?).I read that using a 386 kernel will burn out the motherboard because only one CPU will be taking all the load. Thanks kirk
I've posted the source for the rtl8180-2400a here:http://www.murga.org/~puppy/viewtopic.php?p=77595#77595 I compiled it in 200 and 202. BarryK
Note, the 'modprobe' script in 2.12BETA has a few bugs. It should not
matter if you do 'modprobe -vn snd-trident' or 'modprobe -vn
snd_trident' -- modprobe treats the '-' and '_' as equivalent. The
'modprobe' script in 2.12BETA does not have that independence, so you
have to type the exact module name, in this example:# modprobe -vn snd-trident ...this will fetch the module and all it's dependents and you can then load it and find out if it works for the Norhtec PC. BarryK
kirk,The tarball that I tried to compile has the same filename as your download. marksouth2000
Barry, you wrote:"I attempted to compile the rtl8180-sa2400 driver, but failed. It was weird, running 'make' caused the entire source directory to self-destruct -- totally erasing itself -- I breathed a sigh of relief that it's destructive urge was contained." This sounds ultraweird. I've built this driver under stuff like Vector before now, and taken no casualties in the process. It's also bad news, masses of wireless cards use the RTL8180 and RTL8185 - I have 3 here. I would be sooo delighted to have them working "out of the boot" with Puppy. Aside to Mr Doolie (if that is your real name : I have often run Puppy on single processor machines without burning out the motherboard, sounds like someone has been pulling your leg. |
|
Interesting 'feature' of echo
I am still debugging the full h.d. installer.The /etc/rc.d/rc.sysinit script has this line: mount /proc But at bootup it causes an error message that /etc/mtab cannot be written to as it is a read-only filesystem. So, I changed it to this: mount -n /proc The '-n' option tells mount not to write to /etc/mtab. But, I still got the error message. Hmm. /bin/mount is my script, a wrapper for the normal 'mount' executable. So, I examined the script, and that was when I discovered something that astounded me... How often I have put 'echo "$@" | ' into a script to pipe the commandline through for further processing. What is the commandline in the above example: '-n /proc'. Create a little script to test this, call it 'test.sh' and put this in it: #!/bin/sh then run it like this: # ./test.sh -n /proc ...what output do you expect? ...compared with what you get? Now modify the script: #!/bin/sh And test again: # ./test.sh -n /proc ...hmm, can you explain this? It works the same for Busybox echo and full echo. Okay, I fixed the bug for my 'mount' and 'umount' scripts, but I wonder how many other scripts are potentially broken. echo has other options, '-e', '-E' (and the full echo also has '--help' and '--version') -- can these also potentially cause trouble? Ted Dog
-n is for drop the newline.echo "$USER's current directory is $PWD" verses: echo -n "$USER's current directory is $PWD" SYSV3 environmental variable controls this behavior in some unix versions http://www.in-ulm.de/~mascheck/various/echo/ Ted Dog
#!/bin/shif [ "X$1" = "X-n" ]; then echo " $@" else echo "$@" fi Ted Dog
That should be:if [ "X[i][b]$[/b][/i]1"= Ted Dog
#!/bin/shif [ "X[b]$[/b]1" = "X-n" ]; then echo " $@" else echo "$@" fi Bill St. Clair (billstclair<at>gmail.com)
echo "$*" does the trick.With echo "$@", your command line is equivalent to: echo "-n" "/proc" With echo "$*", it's the same as: echo "-n /proc" The former has two args, the first of which is -n, which is interpreted by echo as "do not output the trailing newline". The latter has one arg, the entire string that you want echoed. See: http://www.gnu.org/software/bash/manual/bashref.html and http://www.die.net/doc/linux/man/man1/echo.1.html I always wondered what the difference was between $@ and $*. Now we all know. GuestToo
i'm
not exactly sure what you are trying to do, but i think in your
example, you are trying to make test.sh behave like echo ... in other
words it is a wrapper scripti would expect #!/bin/sh echo "$@" to work most of the time ... what "$@" does is the same thing as "$1" "$2" "$3" etc etc, normally delimited by spaces, and the variables are processed so that unnecessary leading and trailing spaces are removed in other words, test.sh -n /proc would be the same as echo "-n" "/proc" or echo -n /proc #!/bin/sh echo " $@" would probably not work this would be the same as typing echo " -n" "/proc" because the space is in a quoted string, ash/bash thinks that the space is significant and does not strip it out, so the string " -n" gets printed as a string #!/bin/sh echo "$*" would not work either ... this is the same as echo '-n /proc' if you want to be really really sure that the variables are working the way you think they should, you could write the script like this: #!/bin/sh p1="$1" p2="$2" p3="$3" p4="$4" echo "$p1" "$p2" "$p3" "$p4" this does about the same thing that "$@" does it can really help to run a script with the debug option: sh -x test.sh or bash -x test.sh (sh and bash behave slightly differently) that's how i found out that gettext was converting utf-8 strings to iso-8859-1 strings in my dotpup script there probably should be a wiki page created for tips and tricks for example, Busybox's pidof, killall, and which, do not work properly if there is a file or dir in the working dir, with the same name as the executable you are trying to find/kill ... this can cause bugs that are hard to find GuestToo
ok, where you see "" "" "" etc etc i wrote "dollar-sign1" "dollar-sign2" etc etc ... and p1="dollar-sign1" etc etcBarry Kauler
Yes
guys, I fully understand what '-n' means to 'echo. G2 came the closest
to ansering the question, which was why it made a difference doing
'echo " <dollar>@"' or 'echo "<dollar>@" -- that is, with
or without the space. Still, I'm really bothered by this.Also, G2, your solution does not work. The same problem exists. 'echo "<dollar>P1" "<dollar>P2" etc' will still treat the first param as a option for echo if it is '-n'. I think we need a wrapper for echo that makes it behave "properly". The error is in the bash interpreter when it does the substitution of "<dollar>@" -- you can do 'echo "-n /proc"' in a terminal and it behaves properly. The double-quotes should be telling Bash to treat everything within as a string and not behave differently if there is a leading space or not. Barry Kauler
Hey, Bill is right! $* fixes it!PaulBx1
You have two options, right? Make a wrapper to globally modify the behavior, or find every one and fix it?You can always delay the release if you want, to ferret these things out. I looked for "$@" with Turma , found 13 items in /bin with it (Busybox had 91 instances). In etc there were piles of them, at least Turma said so. Problem with changing "$@" globally, is there may be some scripts where "$@" is used legitimately. Another thing to do would be to leave it for a 2.13 project. We've survived a long time with this; should be able to go one more release. BarryK
Here is the official info, from the Advance Bash Scripting Guide, http://tldp.org/LDP/abs/html/internalva[pre]$* All of the positional parameters, seen as a single word Note "$*" must be quoted. $@ Same as $*, but each parameter is a quoted string, that is, the parameters are passed on intact, without interpretation or expansion. This means, among other things, that each parameter in the argument list is seen as a separate word. Note Of course, "$@" should be quoted.[/pre] But, this still does not anser the question why that space makes a difference. Anyway, it looks like I will have to fix some scripts, replace $@ with $*. GuestToo
[quote]this still does not anser the question why that space makes a difference[/quote]as i said, "-n" is treated as an echo parameter option ... "<space>-n" is treated as a string to be printed ... the leading space makes bash think that it is a string, not a parameter that is: "-n" = -n = a parameter " -n" = ' -n' = a string whether you would use "<dollar>@" or "<dollar>*" depends on whether you want "-n" to be treated as a parameter or as part of the string '-n /proc' running sh -x test.sh shows you what bash is thinking as it expands variables BarryK
Thanks G2, yes, that '-x' is helpful.Ken Yap
The solution is simple, in your wrapper script, when you echo $@ to a pipeline, do:echo '' "$@" | ... This makes the empty string the first argument to echo and prevents any interpretation of leading hyphens in $@ PaulBx1
That
guide noted, "The $* and $@ parameters sometimes display inconsistent
and puzzling behavior, depending on the setting of $IFS."I tried to see what $IFS defaulted to with "echo $IFS|cat -vte" but got nothing. Same result if I set it to " ". |
Release schedule for 2.121. I have improved the h.d. install, need to test it. 2. A few more kernel drivers to compile for "zdrv" file. 3. *Maybe* recompile kernel with Ted Dog's Via patch. 4. Bill's hotplug fix to make some drivers work. 5. Update Jason's apps to latest versions. 6. Apply Dougal's patch for man script. 7. Improve edid handling in Xorg Wizard. 8. There's a bug in pupget, fix that. This morning I worked on the full h.d. installer, fixed a couple of bugs. Also fixed a subtle bug in rc.shutdown that pakt discovered -- thanks for that. Anything more than that will be targetted for v2.13. If no serious hiccups, the above should take me another 3 - 4 days, so expect 2.12BETA2 by the end of the week. I would like to get the final out promptly, so I propose we do a very quick testing of BETA2, just a couple of days ...if nothing serious is discovered then 2 - 3 days after, we can release 2.12final. GuestToo
well, if you like, you could put my latest dotpuprox.sh script in 212
beta2 ... i only changed MSG=gxmessage to MSG="gxmessage -encoding
utf-8", and added a couple of quote marks that i thought should be
there, so i don't think i introduced any bugsif Puppy does not come with gxmessage already installed, it would not matter much anyway, because it could be installed when the language files were installed (so far, just de and fr) the only thing i changed was the dotpuprox.sh script ... i have a package for translators here: http://www.murga.org/~puppy/viewtopic.php?t=12540 the package installs gxmessage in my-applications/bin, but it also installs (without registering with pupget) /usr/local/share/pixmaps/gxmessage.png and /usr/local/share/locale/*/LC_MESSAGES/gxmessage.mo so you might prefer to just unzip the dotpup package somewhere, instead of clicking it to install the package or i can upload just the script somewhere John Doe
I don't know if anyone has mentioned this, but I noticed the gxine/mozilla plugin was broken.test: http://www.c-span.org/watch/cspan_rm.as GuestToo
i
found that the dotpup handler script was cheerfully converting UTF-8
text to ISO-8859-1 ... so i had to put this line in the script:export OUTPUT_CHARSET="utf-8" so i uploaded a new version with this change ... it seems to work properly it might be easier to use "MU's method" of sourcing homemade lang files to import message translations ... it's not as powerful a tool as gettext, but it would be easier, and would require no dependencies the dotpup script with gettext support was an experiment ... so far, it's seems to work properly, but it hasn't been extensively tested ... it should work in English anyway archwndas
Barry,the connect icon which launches the dialup modem utility doesn't work for me. I tried both a Lucent modem (using the ltserial driver) and a serial external modem. While wvdial works (at least it can connect) the gkdial doesn't work. It cannot connect and I can't hear the modem dialling. I do not know any alternatives other than kppp I used to use under SUSE. The other problem with wvdial is that 6-7 seconds after it gets connected it hangs up saying connection lost exit code -2, examine files in /var/log and it tries to dial once again. But it can't stay connected. Hope there is really a bug in there, and it is not a problem related to my hardware! Cheers! GuestToo
i
added [b]export OUTPUT_CHARSET="utf-8"[/b] because it seemed to be
necessary to prevent gettext from converting text from utf-8 to
iso-8859-1then it occurred to me that this might cause trouble for the dotpup.sh script in the dotpup package when it is run ... or not ... so just to be safe, i unset the varariable before calling dotpup.sh then it occurred to me that maybe, that variable might be set to something, and that unsetting it might not be a good idea ... so i unset it, then i export the original value, but only if there was one so i think that should work ... i have only made minor changes to the script to get it to display utf-8 text properly ... the changes should not have affected English (ascii/ansi) text so if you want to put the newest version in 212beta2, i uploaded it to the forum ... and there are de, fr, es, ja, and it translations, if you want them [a]http://www.murga.org/~puppy/viewtopic.php?t=12540[/a] if you don't want to put in the newest version, it's easy to install from a dotpup package, so it's not really important "it might be easier to use "MU's method" of sourcing homemade lang files to import message translations ... it's not as powerful a tool as gettext, but it would be easier, and would require no dependencies" May I say that this was music to my ears? After Stormix, SuSE, RedHat, Debian, and others I grew impossibly frustrated with endless dependencies. The degree to which Puppy avoids dependencies at every possible turn is the degree to which it remains a) more easily understood and maintained, b) less vulnerable to obsolescence because of changes elsewhere, c) less complex to the new or less-technical user, d) smaller, e) more stable, ... Just had ot say that and THANKS! I sure appreciate all of you and wish I had the technical skill to assist other than via testing and breaking things! I will load 2.12BETA on a desktop here, frugal of full HD install as you prefer, and try to break it. Lemme know. doc in Florida BarryK
Wait for BETA2, it will be out soon.
|
Refined handling of NTFS partitionsAnyway, the ntfs-3g driver can be forced to mount a 'dirty' f.s., so I have done this as a fallback in my mount script, but a warning message will popup. My 'Pmount' drive mounter utility (see File managers menu) uses 'mount' to mount partitions, so you will get the warning. A 'dirty' NTFS f.s. is a problem at first shutdown when choosing a partition in which to create the pup_save.3fs file. previously, a dirty f.s. was rejected, but now it is available but a warning message is displayed, advising not to use it and to fix it first. The rc.shutdown script in /etc/rc.d has been modified. Barry Kauler
Just a little note about my new Acer Aspire laptop: it came with XP
Home preinstalled, but ...and this is what really surprised me... it is
a FAT32 filesystem.cthisbear
I too noticed this on 2 Acer laptops earlier this year.My belief is that Acer may have had warranty problems,from XP being harsh on hard drives, so they went Fat32. Anyway it makes it simpler for ordinary bods to boot a Win98 bootdisk and fix things if there is a problem. The great thing with recent Puppys is being able to copy files from the first hidden partiton if needed. Chris krumpli
I have purchased two Acer [b]desktops[/b] earlier this year. Both had similar configurations. Must be current Acer policy.Paul M Ted Dog
How does multisession DVD work on the laptop? laptops are very problematic with older HW and DVD (CD) multisession on reboot.Barry Kauler
I haven't tried multisession on my laptop yet.One thing though, the DVD-burner drive is specified to handle dvd+r, dvd+rw and dvd-rw, but [i]not[/i] dvd-r. All of my testing so far has been dvd-r's as that's what I bought a bulk pack of. Now I have got as far as purchasing 50 dvd+r's but not yet done any multisession testing with them on my laptop. |
Gxmessage now in PuppyI did look at it way back, don't recall when, but I think that I wasn't entirely happy with it. But, the latest version 2.6.2 looks really good. It's a GTK2 clone of 'xmessage' (which just uses the XLIB library) and has a very high degree of compatibility plus some extra features. It's very small and the antialiased fonts plus the enhanced features really do mean it's the way to go. In other words, take it that from Puppy 2.12 onwards gxmessage will be there, so scripts can be written assuming that. There will also be a help document, just type "man gxmessage". Looking at the gradually improving appearance of Puppy, now with JWM and GTK2 apps using the Bitstream Vera fonts, and the possibility of migrating xmessage-based scripts to gxmessage, the one thing on the desktop that is starting to stand out as lagging behind -- is Rox-Filer. The most immediately noticeable thing is the non-antialised text underneath the desktop icons. Well, I won't do anything about Rox-Filer for 2.12 as that is really frozen now. But for 2.13 I am prepared to take a look at upgrading Rox-Filer -- is there are recent DotPup and notes on installation and caviats for Puppy anywhere? Has anyone tried IDesk in Puppy? Lobster
Pizzasgood did extensive testing of 2.4 of Rox for Puppy 1.09CEhttp://forum.puppylinux.com/viewtopic.php?t=19 . . . as expected it was too slow MU
Note there also is a "hacked for Puppy" (by Nathan Fisher and others) version of Xdialog2.Forum is down, but program available: http://dotpups.de/dotpups/System_Utilit Works with PupGet! I use it as default in Muppy, seems to be very stable Mark GuestToo
for
simplicity, i used xmessage/gxmessage to display messages in the
dotpups script ... i added language translation capability (as an
experiment) using gettext, but xmessage does not seem to support utf-8
... so i would either need to use gxmessage for translated messages, or
rewrite the script to use gtk-dialog or similar program that does
support utf-8i don't remember whether i said anything about MS core fonts or not ... i think they were created by Bitsteam anyway http://corefonts.sourceforge.net/ http://corefonts.sourceforge.net/faq8.htm http://corefonts.sourceforge.net/eula.htm i think the license allows them to be used for public use, but i don't know if the license allows them to be included in a distro in a ready-to-use form ... it would be easy to write a simple "import fonts" wizard ... KDE has an import fonts wizard the latest stable version of Rox filer is 2.5 ... there's a dotpup package on my dotpups page ... http://puppylinux.org/wikka/DotPups but it is hosted on John Murga's forum, which is down right now ... i have a copy of the package on my hard drive, if it's needed Rox 2.5 is prettier, with antialiased fonts for menus, file names, and desktop icons ... the desktops fonts are more configurable (size, type, colours) and are antialiased ... the wallpaper is easy to configure ... you can click anywhere on the icon, including the invisible background (with Rox 1.2, you have to click on the foreground of the icon) ... the menus are antialiased ... there are extra features, but Rox 1.2 has most of the basic functions that 2.5 has ... Rox 2.5 displays recently modifed files and dirs in bold text, which makes them easy to see and find ... app dirs have more features, like support for translated menus and Summary (tool tip) and About (properties) etc etc ... for example, in the Rox 2.5 menu (right click the icon) you can enable/disable the pinboard: <Item option="-p=/root/Choices/ROX-Filer/PuppyPin"> <Label>Enable pinboard</Label> <Label xml:lang="hu">Pinboard engedélyezése</Label> <Label xml:lang="es">Habilitar el pinboard</Label> etc etc another feature is that desktop icons can be add/removed from a script using SOAP (simple object protocol) in short, Rox 2.5 is prettier and has many nice features, and is not much bigger than Rox 1.2 ... i have Rox 2.5 installed on Puppy 212B, the executable is 192k, Rox 1.2's executable is 312k, but i upx'ed the 2.5 executable so that is not a valid comparison but Rox 2.5 requires the shared-mime-database ... the entire database does not have to be distributed with Puppy, just the package configuration files, because the database can be built from the config files ... the config files are about 673k, but gzipped they are about 99k so Rox 2.5 is bigger, but not as big as you might think Rox 2.5 is a little slower than 1.2, but not much slower ... there is very little difference in speed on my 900mhz machine, hardly noticeable ... maybe a 1/4 second slower popping up a Rox window when clicking on the Home icon, and no noticeable difference when actually using Rox one caveat ... Rox 2.5 has a nice easy-to-use and very configurable background setter ... but it takes over the desktop background, and you can't disable the feature ... it uses a higher level than the root display for the background, so other wm's or programs might set the wallpaper, but you will only see Rox's wallpaper, and if you run aterm with pseudo transparency, it will show the root background, not Rox's background ... this can be confusing, especially to a newbie ... i think MU's wallpaper setter automatically sets the root display and Icewm's background and Rox 2.5's background all to the same wallpaper anyway, to avoid confusion bottom line: Rox 2.5 is nicer and has some useful features ... it's a bit bigger, but not as large as you might think (my dotpup package is about 596k) ... a little slower but not significantly slower (well, i haven't tried it on a 33mhz 386) my dotpup package installs to my-applications and /root (shared-mime-info), is easy to uninstall (right click the icon to uninstall) and does not interfere with Rox 1.2 (you can use them both at the same time, for example to compare windows) ... my package is hosted on the Murga forum, so is not available while the forum is down, but i have a copy of the package if you want to try it if you compile your own, i hacked the source slightly, 2 trivial changes ... i disabled the Running As Root message, and i disabled the window that pops up complaining if you use the -o option GuestToo
also, Rox 2.5 supports UTF-8 text, for file system names and icons and
menus ... and it has built into language support for a lot of languagesMU
yes, my backgroundsetter sets:1.) the rootwindow (that is visible if you use JWM/Rox 1.2) 2.) it also saves the background inclusive all modifications like scaling/tiling as /root/Choices/ROX-background.jpg and restarts Rox 2.x to force it to use it. Rox 2x has a less "brutal" method of setting the background from external programs, but afaik that requires Python. 3.) If available, it runs wmsetbg with this saved picture. This is required by fluxbox or xcompmgr (shadows for windows). Rox2x would be a good choice because of UTF, so that it could display vietnamese/russian etc. The cons are that it uses a clientwindow as background, covering tools like Torsmo (though there are hacks I think, but they also might require Python, don't remember exactly). But while there might be hacks for some programs, it gets problematic with other windowmanagers like Enlightenment, that uses its own clientwindow. So for Muppy, I will stay with 1.2, but add a program that allows to Rox 2.5 from GuestToo in the Toolbox, with hints about the pros/cons. So anybody who wants to tweak his desktop is not hindered by Rox 2x, but all users depending on UTF have a easy way to update, if they think the standard desktop (Icewm) is ok for them. Mark MU
btw., the combination of setting rootwindow and then using wmsetbg is
the only way I know to use xcompmgr without a clientwindow.All other backgroundsetters fail here, because xcompmgr seems to have timingproblems, displaying the background totally distorted. Desktops like KDE simply work around this issue by covering the rootwindow with a clientwindow. ---------------- Concerning idesk: I think it has no utf-support, and displays only icons. You have no drag'n'drop or integrated filemanager, so it is out of discussion for me (because of the last 2 points). I think one of the advantages of Puppy is the easy to understand drag'n'drop mechanism. In this point it has even advantages over KDE, that internally uses .desktop files for Icons, making it very hard to understand for people, that switched from windows (though that concept has advantages, too). Mark GuestToo
no,
SOAP does not require Python, just a few lines in a script ... read the
Rox manual for the features that are supported (Rox 1.2 supports SOAP
too)yes, rox 2.5 takes over the background whether you like it or not, and whether you use the pinboard or not ... and this can interfere with other programs (wms especially) that try to control the background too ... this is Rox 2.5's most annoying feature i don't use Torsmo, and i usually run Icewm, so i have don't have problems with Rox 2.5 the Rox developers really should allow you to configure Rox so it will not try to take over the desktop, but there seems to be no political will to do that GuestToo
Rox
2.5 and Rox 1.2 can be installed at the same time, and can even run at
the same time (you can have a Rox 1.2 window and a Rox 2.5 window on
the screen at the same time), if anyone making a Puppy flavour wants to
include both versions in their iso ... they should not interfere with
each other (but i've never tried running both pinboards at the same
time ... i think Rox 2.5's pinboard would just cover the 1.2 pinboard)MU
that's interesting.In the past, I had problems, that Rox 2.x converted some XML-files to a newer version, breaking v1.2. I will try to add it to Muppy in the next days in addition to 1.2. Now off to work. Thanks, Mark gdcrane (gdcrane<at>bellsouth.net)
My vote would certainly go to Rox 2.5 Dougal
I
usually like to use a newer Rox (used ro be 2.4, now 2.5) especially
because of the UTF support, but also since it gives you some more
config options (like setting the number of items at which display
changes to small icons).However, I must disagree with G2 and admit it's much slower -- it's just unnoticed when it doesn't have to do a lot of work... On my 450MHz machine entering /usr/lib can leave me waiting for 5-10 seconds before I can do anything. I'm not saying this is unbearable, especially since you don't normally have to go to directories like that, but it's a matter of what your priorities are... Barry: A few weeks ago I had the idea of possibly improving pupRox. I thought of looking for the versions where various options were implemented and trying to insert them into pupRox and see if I can make them work. I haven't gotten around to it (downloaded a whole lot of changelogs from sourceforge though...), but maybe that's an idea to use? Maybe you can't implement the antialiasing without GTK2 or something, I don't know, but it might be worth looking up. What about porting other GTK1 apps in Puppy to GTK2? I think maybe 2.13 could be named "face-lift" or something and have us concentrate on making Puppy look better. Better idea: maybe WE will handle those kind of things and make you suggestions and you (Barry) just sit back and choose what you want to add? (If MU cooperates with me we might have something for you soon.) I'm sure Barry's Famous Notebook has plenty of things listed in it that need to be taken care of... Raffy
Hey, Dougal, this shows in Barry's dictionary: "sit back - not found". Am excited though by the new Guten printing (formerly gimp-print). As to alternative to Rox, will Emelfm2 be good? http://www.murga.org/~puppy/viewtopic.p rarsa
Last
time I looked at IDesk it was not activelly developed. I liked it, it
is light and out of your way but as was mentioned no drag'n drop is a
big drawback.As for Rox look and feel, with some minor modifications It looks quite better: - Change the Icons - Change the GTK theme (fonts and colours) These changes should not add to much to the base Puppy size and may be worth it. GuestToo
Rox
1.2 puts the config files in /root/Choices ... Rox 2.5 puts the config
files in /root/.config/rox.sourceforge.net ... so they play well
together nowthey both use PuppyPin in /root/Choices (called from .xinitrc), but that seems to be ok if you put both versions in Puppy, they should probably both be put in /usr/local/apps/ ... maybe renamed ROX-Filer2 or something it's /usr/local/bin/rox that controls which Rox would run by default (my Rox 2.5 program reinstalls /usr/local/bin/rox everytime it runs) it's quite possible that Rox 2.5 is noticeable slower on slower machines ... i suspect there is a point where an increase in cpu speed will not have much effect, because the bottleneck is no longer the cpu speed but something else, like the hard drive speed also, i usually run Rox with thumbnails disabled, which is faster if there are many pictures in the dir ... with Rox 2.5, you can just right click the Show Hidden icon to see the thumbnails ... with Rox 1.2 you can just press the T key anyway, John's forum seems to be back online, so you can try my dotpup package for yourself if you like ... just edit /usr/local/bin/rox to make Rox 1.2 the default rox again ... or uninstall my package by right clicking the roxapp icon ... or just rename the roxapp temporarily Dougal
Something worth checking:I was just looking through the Rox 2.5 code, thinking of maybe hacking it to solve the backdrop problem, when I discovered the following comment (line 2474 in pinboard.c): "Also update root window property (for transparent xterms, etc)" Could it be that they've fixed the problem we had with 2.4.1? Rarsa: I've been working on improving the looks of GTK1... ;) Pizzasgood
A
consideration about to speed: Anything you install will not be in the
ramdisk. Rox 1.2 is. That means it has an automatic advantage over
anything you're testing. When you remaster with the newer Rox it makes
a noticeable difference (or at least it did with 2.4 in 109CE). In
addition to anti-aliased fonts, it also has much much better icon
support. It can use more formats, and they anti-alias nicely.The conflicts with some programs are the only reason I'd discourage it. I don't know if it would be worth including in the standard Puppy because of that. That said, one of the first things I do when installing Puppy is install the newer rox package, even on my old 450MHz system. Pizzasgood
I
don't know if updating everything to GTK 2 would be wise. From what
I've heard, GTK 2 is much slower than GTK 1. There are themes for GTK 1
that look quite nice. I usually use smooth-peachy-clean, which has a
version for both and gives my system a very unified and slick
appearance.Jason Pline
My 2
cents on the patched gtk2 xdialog and gxmessage, I've been using both
for at least a month now. I made xmessage into a symlink to gxmessage
and haven't noticed any problems. The only potential problem with the
patched gtk2 xdialog that I've noticed is the directory selector
records the directory as /path/to/directory and the gtk1 version
records the directory as /path/to/directory/That shouldn't be a problem unless you have a script that selects a directory and then later has a file selector from within that directory. When the script would be executed in the gtk2 version it could be in a line like this: some-command `cat selected-directory``cat selected-file` Which would turn into: some-command /path/to/directoryselected-file Which would of course cause errors in the script due to the missing slash. I haven't ripped a dvd with pupdvdtool since I've started using the gtk2 version of xdialog but I think at least one of my scripts would have that issue. It wouldn't be hard to fix those sections in the scripts though. All you'd have to do is change the line to: some-command `cat selected-directory`/`cat selected-file` BarryK
Dougal,You might be able to solve a problem. PupRox is Rox-Filer v1.2.2 with support for Xft, so it has some antialised font display. This was done for me by that Japanese guy "Teki" who also added Xft support to Dillo. You can see the antialised fonts in the icon labels in pupRox windows. Teki also added Xft support for the pinboard so the desktop labels display antialised, however Teki did not know how to get a transparent background -- so, I replaced his modified pinboard code with the original. The source for pupRox should be at puptrix.de, where all Puppy's source is. I put both pinboard sources in it, the original and teki's modified file, I think, so it would be easy to try his. If you can solve that transparent background problem, then we are back in business with Rox 1.2.... The other more ambitious thing would be to upgrade Rox to GTK2. The next release of Rox after 1.2.2 was a migration to GTK2 but they also migrated to that enormous MIME databse thing. If we could do the GTK2 migration but not the MIME migration... GuestToo
the
only part of the shared-mime-database that is necessary is 99k
compressed ... uncompressed and built into the full database, it is
1368k ... that's how i get Rox 2.5 in a 500k packagethe database replaces the 6k file /usr/local/share/Choices/MIME-info/Standard ... there are advantages to doing this, but simplicity is not one of them BarryK
Ah, the pupRox source is here:http://puptrix.org/sources/alphabetical/r/ It is version 1.2.2.1 -- I added the extra '.1' and the official Rox-Filer that it is based on is 1.2.2. You compile it like this: [pre]# cd ROX-Filer/src # ./configure --enable-rox --with-platform=Linux-ix86 --build=i486-pc-linux-gnu # make[/pre] Nathan Fisher
Well I misses quite a lot in the last couple days, now didn't I? I'm
really glad about gxmessage being included as I have quite a lot of
scripts that were written with it (has been in Grafpup for a while
now). As for ROX, I wish I could have chimed in earlier. I hacked the
source of ROX-2.5 a while back, including all of GuestToo's changes and
a few of my own. This version doesn't give the message about runnning
as root, doesn't pop up the warning about 'the -o option is no longer
used', and changes all references about 'Send To' to 'Open With',
including the directory path, messages, and manual. This is already
going into the next Grafpup. A source tarball has been posted here for
at least a month now. About ROX-2.5, it IS slower on an older machine, but not painfully so. I am running it on a 333mhz right now and it does OK. The more files in a directory the slower it will go. The big reason for the switch, for me anyway, is that they did fix the issues with transparency. I have it runing right now in Slackware alongside Fluxbox and all transparency works. It also works with a transparent RXVT and Aterm. There is still a problem with Torsmo, but I have had enough other issues with Torsmo that I no longer use it anyway. All in all I like it better and think now would be a good time to give it a serious look. Dougal
Barry: I could look at the pupRox code, but I doubt that I can fix it if Teki couldn't...I think, now that Nathan has confirmed that transparency is fixed in 2.5, that you should go with it. It also occured to me that there's another important advantage in using it: coupled with the new fonts, Puppy will now be very easy to use with UTF-8 locales! All a user will have to do is add a .utf8 locale and they'll immediately be able to see filenames with non-Latin characters (unless they're Chinese, Vietnamese etc. which I don't think those fonts support...) I'm working on code for the xorgwizard to allow adding additional keyboard layouts, so together with the new Rox and fonts Puppy will be much more language-friendly... GuestToo
unicode does support Chinese and Japanese and other charactersBarryK
Do
any of you guys recall some discussion awhile back on the forum about
unicode fonts? It may have involved Hacao. There were some smallish
unicode fonts proposed for inclusion in Puppy, but at the time I didn't
follow it up as I thought the base Puppy already had too many fonts --
but now that I have reduced the scalable fonts down from 5M to 2M |