Page 44 of 191 [2854 Posts]   Goto page: Previous 1, 2, 3, ..., 42, 43, 44, 45, 46, ..., 189, 190, 191 Next
Author Message
RSH
PostPosted: Tue 18 Dec 2012, 17:49    Post subject:

der-schutzhund-at-german-forum wrote:
Hi all,

I got a strange effect on a Notebook Fuijtsu LifeBook!
It looks like the Fn Key is activated constantly and deactivated by pressing the Fn Key. Exactly the opposite, as it should be. I can write this post only by pressing the Fn key constantly !

Do you have any idea/solution?

It is about the Lucid 528-4 / Lazy.

Greetings

Wolfgang
bigpup
PostPosted: Sun 16 Dec 2012, 22:46    Post subject: Re: Instant updates??

Barkingmad wrote:

I have Lucid and have added update 002 as a pet package but can't remember where I got that from. Is it possible to go to 005 or do I need to whole ISO from the top of this thread?

Thanks

Will

You will need the Lupu 528.005 iso

Depending on how Lucid is installed determines how to do the upgrade.
mikeslr
PostPosted: Sat 15 Dec 2012, 20:55    Post subject: Thanks for luciddc10,2.jpg Wallpaper

Hi futwerk,

Thanks for the new wallpaper. I wonder if anyone else realizes how much hard work you put in to create your artwork and the vision that had to precede it. Just wanted you to know it was appreciated.
Although I keep Lupu as a fall-back/work-horse, most of the time I currently run one of the precise-pups. Pemasu just came out with a new version that I thought could be better reflected by a more powerful and abstract wallpaper. So your work appeared just in time. A little editing in gimp eliminated the Lucid+ moniker.
And then, having gimp opened, I got carried away. The result was my new upup desktop (jpg attached), a new drive48.png and a new xonclock clock-face. I've also attached them if anyone wants them. Instructions for replacing the drive48.png --which shows up as the desktop drive icons-- can be found here: http://www.murga-linux.com/puppy/viewtopic.php?p=668562&sid=def2de8e3a0cff1737c1451528348104

How to change xonclock's face can be found here: http://www.murga-linux.com/puppy/viewtopic.php?p=602304

None of which would have been possible if you hadn't created the wallpaper for me to cannibalize.

mikesLr
futwerk
PostPosted: Fri 14 Dec 2012, 18:49    Post subject:

backgrounds.
chrome307
PostPosted: Fri 14 Dec 2012, 13:58    Post subject:

Have you checked your 'package manager' for an update or alternatively look here:

http://ftp.nluug.nl/ftp/pub/os/Linux/distr/puppylinux/pet_packages-lucid/

I didn't come across it myself though
Barkingmad
PostPosted: Fri 14 Dec 2012, 11:55    Post subject: Instant updates??

Hello

Hello

Having neglected Puppy for a while I find that Lucid is up to update 005.

I have Lucid and have added update 002 as a pet package but can't remember where I got that from. Is it possible to go to 005 or do I need to whole ISO from the top of this thread?

Thanks

Will
ASRI ├ęducation
PostPosted: Sun 09 Dec 2012, 16:02    Post subject:

I would (again) thank the contributors for this great Puppy Lucid.
Today, this distribution has allowed me to free a MacBook.
http://www.murga-linux.com/puppy/viewtopic.php?t=82841
otropogo
PostPosted: Fri 16 Nov 2012, 14:31    Post subject:

bigpup wrote:
otropogo,

Some of this speed difference could be caused by the different storage devices read speeds.


I thought of that initially, because the 256MB CF card is older than the 500MB SD, and would likely be a bit slower to read into RAM. But I dismissed that as an insignificant factor because:

1. I assume the entire loader code is read into RAM before the boot process begins, ie. before the boot prompt, after which all activity takes place strictly between RAM and the hard drives. And this is the interval in which the speed differences were noted.

I've just tested this assumption, and it proved WRONG. The card needs to remain in the card reader until the matching 2fs and sfs files have been located on the hard drive, or the load process will fail.

2. even if the assumption above is mistaken, the amount of code to be copied from the CF card is so small, that it couldn't account for any of the speed difference recorded.

I tested this by copying all of the Puppy files on the CF card in question to a test folder on one of my hard drives, using my slowest card reader.

The total Byte count of the files (since lupu_528.sfs isn't on the card) is only 4085K, and it took less than 2 seconds (1.5 by my stop watch) to copy all of these files to the hdd. Presumably, reading them into RAM would be no slower.

The same read from the SD card (an early "Pro" level 500MB SD) took a bit less than a second to complete.

I then repeatedly compared the time from reset to presentation of the hard drive's 2fs options (at which point the card is no longer a factor, and can be removed) took 58 seconds with the SD card, and 60 seconds with the CF card.

So assumption #2 seems to be correct. The "professional" 500MB SD card does read demonstrably faster than the 256MB CF card, as indicated in the first test above. But that doesn't translate into any significant difference in loading Puppy.

So why adding
Code:
 psubdir=pupsave
to the syslinux.cfg file should save 42 seconds of loading time with the CF card, but only 10 seconds with the SD card remains a mystery.
rincon155
PostPosted: Fri 16 Nov 2012, 12:27    Post subject: Keep offerring Lucid Puppy 5.2.8

This is just to say that Puppy Linux 5.2.8 is so reliable and 5.2.8 005-2 so complete. I appreciate your keep offering this version with further improvements.
I am also user of Slacko 5.3.3, Puppy Linux Precise Pangolin 5.4.1, and Lighthouse64 Mariner 5.15 in several PCs and Laptops at home and in my father┬┤s home, with very good experience, but I consider Puppy 5.2.8 a classic that deserves keeping it up.
Thank you.
otropogo
PostPosted: Fri 09 Nov 2012, 13:07    Post subject:

greengeek wrote:
otropogo wrote:
However, I wonder whether more than a handful of us care about this.
Sometimes only one person digs deep enough to discover new information, but it is still very helpful. This sort of thing is always useful information. It adds to the overall knowledge pool and helps us understand the finer points of what is going on. Good research.


Thanks for your encouragement, greengeek.
bigpup
PostPosted: Fri 09 Nov 2012, 12:37    Post subject:

otropogo,

Some of this speed difference could be caused by the different storage devices read speeds.
ETP
PostPosted: Fri 09 Nov 2012, 05:29    Post subject:

Hi greengeek,
Please access your PMs. (I need feedback on MK5 & MK7) Smile
greengeek
PostPosted: Fri 09 Nov 2012, 04:11    Post subject:

otropogo wrote:
However, I wonder whether more than a handful of us care about this.
Sometimes only one person digs deep enough to discover new information, but it is still very helpful. This sort of thing is always useful information. It adds to the overall knowledge pool and helps us understand the finer points of what is going on. Good research.
otropogo
PostPosted: Fri 09 Nov 2012, 02:26    Post subject:

bigpup wrote:
Quote:
And the message makes no sense, since the lupu_528.sfs file is in a folder in the root directory of sda1. And this message still displays if I add the argument

/pupsave

Try making this
Code:
psubdir=pupsave


Yes, bigpup. That worked. I timed the interval from hitting ENTER at the puppy boot prompt to the moment the 2fs files were displayed at

81 seconds without the spsubdir argument, and
38 seconds after it was added

A substantial speed-up, thanks.

Interestingly, I then added pdev1=sda1 psubdir=pupsave to the SD card's syslinux.cfg file also, but the gain was much smaller in that case, a mere 10 seconds shaved off.

49 vs 39 seconds.

My guess is that the loader on the CF card was searching further than the one on the SD card before the psubdir argument was added. But I can't imagine why.

Presumably pmedia=atahd automatically sets the SD loader to search the root directory of the first partition of disk0 first, followed by the the folders in that directory.

But the argument that the CF card required to find the same directory would have set it to do exactly the same thing, since sda1 is the first partition of disk0.

I'm tempted to experiment further by putting extra 2fs files elsewhere on the hard drives, including in folders within folders, where they're not supposed to be found at all. I know that when I boot from a LiveCd (I don't have one burned at the moment), the loader searches all storage devices on the system for 2fs files, and the partition on which the chosen 2fs file is located becomes "home" and can't be unmounted.

However, I wonder whether more than a handful of us care about this.

I couldn't resist moving one 2fs file into the root directory of sda1 and removing all but the pmedia=atahd argument from the SD card's cfg file. The loader then showed only the two 2fs files remaining in the pupsave folder.

So I conclude that it takes the loader 10 seconds to examine the 21 files and 99 folders (or as many of the latter as precede "pupsave' in its search order) in the root directory of sda1 looking for lupu_528.sfs. And this explains the time saved by adding the psubdir=pupsave .
argument.

But why it takes the loader launched from the CF card 32 seconds longer to do exactly the same thing remains a mystery to me.
bigpup
PostPosted: Thu 08 Nov 2012, 22:44    Post subject:

Quote:
And the message makes no sense, since the lupu_528.sfs file is in a folder in the root directory of sda1. And this message still displays if I add the argument

/pupsave

Try making this
Code:
psubdir=pupsave
Display posts from previous:   Sort by:   
Page 44 of 191 [2854 Posts]   Goto page: Previous 1, 2, 3, ..., 42, 43, 44, 45, 46, ..., 189, 190, 191 Next

Powered by phpBB © 2001, 2005 phpBB Group