Duh!!nooby wrote:
Why would he write like that in their forum if it is not true and if it was wrong they would ahve corrected him would they not?
Try asking the people actually involved in the discussion.
Duh!!nooby wrote:
Why would he write like that in their forum if it is not true and if it was wrong they would ahve corrected him would they not?
lighthouse has this feature, when installing for example firefox.pet. it asks if you want to move it outside the savefie, and will install it in /mnt/home/lighthouse and symlink it back. a good idea for beginners.mikeslr wrote:
@ sszindian: You can create a series of empty folders -- with common, useful names like "downloads," "graphics" "documents" -- outside Puppy's SaveFile and include them in a Remaster, so Puppy can probably be created to do so when it's installed. However, the use of such folders from within the system without further human intervention would require that they be symlinked. I may be wrong, but I don't think you can establish symlinks until you have a working system. At any rate, I don't know. As it only takes me a couple of minutes to do so manually, I am currently not predisposed to spend several hours creating a test Remaster. Especially since, even were I successful I wouldn't know how to modify the "Installation choices" of the "install" module so that that choice would become generally available.
mikesLr
That was the full udev151-12 package.playdayz wrote:mavrothat, When you installed udev 151 from the ubuntu repo, did you cut it down or install the whole thing?Does that mean it is working in 256?
Also, you have installed udev-151 from the ubuntu lucid repo?
No and yes.
And then after you installed it, you were able to get sound on the XO?
Yeah saw that one Lobster.. what to do? Make the clock font bright green?Lobster wrote:Can not find the original link but someone mentioned the clock bottom right being invisible. I thought this was transparency - so turned that off with the fbpanel wizard
Nope . . .
the clock is displaying as white on pale tint (with some themes of Openboxt) - not sure where the error is?
Code: Select all
#!/bin/sh
#run mkfontscale and mkfontdir for Liberation fonts
#NOT to be used for other fonts as they may be installed in a different location,
#this script will work in a woof environment or as a normal installation
if [ ! "`pwd`" = "/" ];then
echo "installing Liberation fonts..."
mkfontscale ./usr/share/fonts/truetype/ttf-liberation
mkfontdir ./usr/share/fonts/truetype/ttf-liberation
echo "Liberation fonts installed"
else
mkfontscale /usr/share/fonts/truetype/ttf-liberation
mkfontdir /usr/share/fonts/truetype/ttf-liberation
fi
I wrote about an upgrade issue back on page 47. This was an upgrade of the pupsave file from luci254 to luci255. In retrospect this was not so much a general issue of the upgrade process as it was an oversight on my part. One needs to be extra careful to remove any old graphics driver before installing a new one. And secondly there seemed to have been a problem with 255 and playdayz changed promptly to 256.rerwin wrote:
I would also like to dig into some of the issues people have encountered while upgrading pupsave files. I have no special knowledge about how that works, but am willing to see what I can improve. Any of you with issues about updating from 254 to either 255 or 256: please contact me by PM pointing me to your posting about it, or post a new message here. Thank you.
Richard
Hi rerwin
i tried a remaster of luci256 with your modem-modprobe_fix_pack_to_43x-20110321.pet . When i booted it, i experienced the same problems as when i upgraded from luci 254 to 255. I couldn't start x, what ever i chose. An unusual thing though, after booting, you get to the xorgwizard, and instead of being in 800x600 resolution, xorgwizard was in a very high resolution, approaching HD (i have a HD screen) . This also happened when i did the upgrade from 254 to 255 (i had forgotten about it doing this)
666philb
Had the same (or similar) issue. My .jwmrctray has this lineCan not find the original link but someone mentioned the clock bottom right being invisible. I thought this was transparency - so turned that off with the fbpanel wizard
Nope . . .
the clock is displaying as white on pale tint (with some themes of Openboxt) - not sure where the error is?
Code: Select all
<Clock format="%a %d %b %H:%M">minixcal</Clock>
Code: Select all
<Clock format="%a %d %b, %H:%M" width="60">minixcal</Clock>
OkHow about a screeny
How come one would not use PupClockSet Manager to change the color of the clock font to whatever would work well with the background?Make the clock font bright green?
Yelp! Shocked
Probably a strong grey or deep cream will work with most themes and be a compromise? Smile
wuwei, I think it would be better to use PupClockset Manager, in case changing the code would confuse things.Had the same (or similar) issue. My .jwmrctray has this line
Code:
<Clock format="%a %d %b %H:%M">minixcal</Clock>
and it showed only "Th 24 M" in the lower right corner. When I changed the code to read
Code:
<Clock format="%a %d %b, %H:%M" width="60">minixcal</Clock>
Thanks mavrothal, I am posting luci-257 later today, with a cut down version of udev-151, cut down to match Barry's version file for file. I will also post the full version--that way we can see if the cut down version helps anyone, or if not, then if the full version does. Thanks.That was the full udev151-12 package.
I'll see if I can trim it down and still get sound going
booted live cd, added followingplaydayz wrote:Luci-257 aka Better Safe than Sorry is now posted in the first message of this thread.
Code: Select all
title Luci257 (Boot HD/Dir)
find --set-root /[your Luci_dir]/initrd.gz
kernel /[your Luci_dir]/vmlinuz pmedia=satahd pdev=sda1 pkeys=[your code here] psubdir=[your Luci_dir]
initrd /[your Luci_dir]/initrd.gz
I stand corrected, playdayz. Your advise is well taken.wuwei, I think it would be better to use PupClockset Manager, in case changing the code would confuse things.