Posted: Thu 20 May 2010, 12:18
Would it be possible to sort out the gcc version problem for a bug release of 5.0 ?
thanks
DC
thanks
DC
READ-ONLY Archive
https://oldforum.puppylinux.com/
Integration is the key...stu90 wrote:I know 5.0 aim was to have the traditional puppy look / desktop layout but how about a new look/layout for 5.1?
Working on it.DC wrote:Would it be possible to sort out the gcc version problem for a bug release of 5.0 ?
thanks
DC
I think that is a good idea too. Be sure to check what is already there as a first step--just a general rule of thumb.I think Puppy needs some sound configuration wizard that runs alsaconf, alsamixer and adjusts volume levels. That could be a great thing for people that face problems with getting sound to work. Sort of a 1-2-3 wizard, no sound-alsaconf, still no sound- alsamixer, then it checks volume levels or something. Just an idea.
Yes. There are two update procedures in place. First, the Update feature in Quickpet--the first one will be in a week or so. Second,.a bugfix release 5.0.1 in a month or so, followed by a 5.0.2 if necessary. Concerning bugs that don't get fixed. Some bugs just can't be fixed by us--those are built into Xorg, for instance. We can only look for ways to work around such bugs as those. It might be interesting to look at all the threads since the beginning of uPup development to see what percentage of reported problems have been rectified.Before going off tilting at new windmills, maybe a bugfix release for 5.0 would make a little sense? We already have a 5.0 thread with 76 pages full of reported bugs; do we want to repeat that performance with 5.1? Why report bugs that never get fixed?
Upnorth's fix appears to work fine.playdayz wrote:Jim1911. The gparted that is in LP5 is the Ubuntu binary. In some earlier versions up to 113 or so, I'm not sure, it was the pet. I replaced it only out of a prejudice for Ubuntu binaries in LP--it was actually bigger. You might try the one in the Puppy Package Manager (the pet). Both gparted's were taking a long time on ntfs drives--eventually displaying them, but very fast on Linux drives. I see what you mean about the uuid's. Let us know if you find one please. Thanks.
upnorth wrote:gparted is working properly, displaying uuids here.
one thing different is that i dropped in /sbin/blkid obtained from elsewhere.
anyone with quirky could copy its /sbin/blkid to /sbin. it might help gparted.
That will never do. OK, here's one: it needs to be expanded. There should be a Word Processor Installer, comparable to the present Browser Installer; a Window Manager Installer too (for IceWM, at the very least); and maybe some other fairly big packages would be better as optional downloads rather than integral parts of the basic Puppy distro.01micko wrote:Look at Quickpet for example. It is an app that is about six weeks old.Not, even, 4/12/2010 is the date it was created. I haven't seen a complaint about it in the reviews, bug threads, anywhere.
haha! Who siad I was finished?pa_mcclamrock wrote: That will never do.
That is a point rarely made Jemimah. It has a big bearing on the importance of re-mastering, yet the re-master process is still very basic. Only Dougals re-master script produces a true copy, the included script borks most of the customisation, such as additional trays in .jwm.jemimah wrote:Not to mention that only the main SFS runs in RAM.
The filesystem also should be in ram?Not to mention that only the main SFS runs in RAM.
I dropped in /sbin/blkid from Quirky 018. Where am i supposed to see the uuids?gparted is working properly, displaying uuids here.
one thing different is that i dropped in /sbin/blkid obtained from elsewhere.
anyone with quirky could copy its /sbin/blkid to /sbin. it might help gparted.
Well, open programs and files are copied to ram by the operating system so they can run, but they live on disk in your save file unless they are in the main sfs. For instance opening a browser that you installed as a pet might take longer than one that's in the SFS, because the files are copied from the disk instead of from the ramdisk.playdayz wrote:The filesystem also should be in ram?Not to mention that only the main SFS runs in RAM.
The freely available .PET for TextMaker 2002, about 3.6 MB, is in the Puppy 3 repository, and also here: http://www.pa-mcclamrock.com/textmaker-2002_full.pet . Actually, I usually use TextMaker 2010 (in the SoftMaker Office 2010 package)--but unfortunately that's not available for free, and it's a lot more than 3.6 MB!01micko wrote:Now, i've only used abi and Writer (OOorg). Can we get hold of that one you like..is it Softmaker?
If it's a Word Processor/Desktop Publisher Installer, it could include Scribus, which (like any DTP program) can be used as a word processor. There's also Kword, for those who want their little Puppy to wag a massive KDE tail (although I don't know if it would be any more massive than OO Writer).What other WPs will be suited?
I hardly ever use them, so I don't know if Gnumeric has faults as bad as AbiWord's faults or not, and I don't know how OO Calc compares. There is a package for an old version of PlanMaker, the companion to TextMaker, in the Puppy 3 repository, but I think it may have limited functionality.While we're at it, what about spread sheets?
Yes--but, if they need to buy Puppy CDs, it would be possible to include a lot of extra .PETs on the CDs for optional installation.We do need to be careful what we take out, there are those that are still on dialup and those who don't even have net access
And am I right, this is also basically what a DVD Multi-session does???My Ramboot code does copy all the SFS files and the save file to RAM. My goal in writing the code was to make it possible to shut down the hard disks to save power.
You sound like Bondy mate!cthisbear wrote: I can't remember what Barry is using now.
Chris.