thanks mark I'll look at it_Mark_ wrote:Hey ttuuxxx
Found a bit of a typo in the logout screen you missed a c out of switch, on the switch to jwm button
ttuuxxx
thanks mark I'll look at it_Mark_ wrote:Hey ttuuxxx
Found a bit of a typo in the logout screen you missed a c out of switch, on the switch to jwm button
Only as I usually do:ttuuxxx wrote:...Hmm I never had rox look like that, are you sure you didn't reconfigure it?
Yes, there is no other 214 pup_save on this machine. I named it specifically, "pup_save-214xtop6.3fs". All other pup_save's are within psubdir's. boxpup-421-retro's pup_save is the only other pup_save the 214x-top6 init sequence detects the presence of. There are 27 other pup_save's in this partition, besides 214x-top6's and boxpup's, but 214x-top6 evidently stops looking after it finds boxpup's, which is the next Puppy alphabetically.Are you sure you don't have a pupsave from 2.14R?
Menu -> Desktop -> Set date and timeefiguy wrote: 1 Just noticed clock is wrong and no menu way to set it
Easiest, non-destructive, way to stop it from starting at every boot is to remove Exec-permissions of /etc/rc.d/init.d/hiawatha.run:efiguy wrote:1b ..., also looking at loaded modules Hiawatha had started on initial load
Code: Select all
chmod 644 /etc/rc.d/init.d/hiawatha.run
I'm still working on it, but I was just going to add it to the next release, Probably in a day or two , well a new Firefox is out and The default layout bugs me so I'll revert it to the older look.MinHundHettePerro wrote:Nice one, ttuuxxx !
Care to share the gtk theme-hack ?
Cheers /
MHHP
Hooo-eeey, I don't suppose you could transplant that into l0wt3ch's MyCrossover icewm theme, as supplied in Puppy Studio 3.3?ttuuxxx wrote:I've took one of the backgrounds in 2.14x made a system link, added lots of code to the gtk theme and came up with menu background in the menu. do you guys like it?
Hi MHHP,MinHundHettePerro wrote:
To answer your question:
I've been thinking about how to upgrade the kernel to sfs ver. >=3.1 (proper, 214 has some 3.1rc[1|2]), and also whether it would be feasible to upgrade the kernel to 2.6.18.8. Kernel 2.6.18.1 that was used for 214[-|r|X], 216(1) and 217(1) were patched by BK and all the links to the original, complete, sources, patches and all, seemed dead (puptrix.org, e.g.); I had some patched sources of K2.6.18.1 stashed away, and ttuuxxx provided some more at his smokey01 repo.
Regardless, I wanted to (at least in the first go at it) keep all the original BK-patches to the kernel, so as not to risk loosing any support for older hardware that was working, thus I manually patched BK's K2.6.18.1 (already patched with sfs-3.1rc?) with sfs-3.4.
AFAIK, BK's K2.6.18.8 was compiled way later than the K2.6.18.1 used in the original 2-series puppies, in a woof attempt at pup218, and judging from the file name of the patched sources, there could be some patches omitted from this later version.
I have started looking into how to upgrade the kernel in 214X to K2.6.18.8, while ensuring all the original patches are preserved (comparing the patched sources of kernels used in 214/216 and BK's 2.6.18.8 with vanilla sources of 2.6.18.1 and 2.6.18. - might have a go at it in a week or two.
OTOH, if someone has a link to (or can provide) the complete kernel sources of K2.6.18.1 (of puppy 214 or 216), patches and all, I would be very much obliged .
Cheers /
MHHP
Hello !sinc wrote:Hey ttuuxxx, since the topic of how to boot 214x on a frugal install seems to appear over and over again maybe you can add MHHP's example GRUB to the first post where your download files are. Bc PSUBDIR doesn't work people who are used to using current versions are not sure how to boot. Just a thought to clear up some confusion that keeps happening.... Or else get psubdir to work..
#
title Puppy 214X
rootnoverify (hd0,4)
kernel /puppy_214XRC5P/vmlinuz root=/dev/ram0 PMEDIA=idehd PDEV1=hda5 PUPMODE=12 DEV1FS=ext2 SFSFILE=ext2,hda5,/puppy_214XRC5P/pup_214X.sfs ZDRV=ext2,hda5,/puppy_214XRC5P/zdrv_214X.sfs PUPSAVE=ext2,hda5,/puppy_214XRC5P/pup_save-214XRC5P.rfs
initrd /puppy_214XRC5P/initrd.gz
#
Hello, clarf !clarf wrote:Hi MHHP,
I agree that's the right approach to achieve maximum compatibility with old hardware and keep the 214X kernel original essence.
I also tried to find the individual kernel patches by their name, but I had no luck. I could not find the loglevel, via, dpath or ksize patches.
I just found newer unionfs releases for 2.6.18.X but as I described in the upgrade process I have to test those versions, and hope the Unix socket problem is solved and track any other inconsistency.
Did you have any luck with the patches sources? How is the compare process going on?
Greetings,
clarf
ttuuxxx
added lots of code to the gtk theme and came up with menu background in the menu. do you guys like it?
Please don't use that kludgey Windows-driver workaround. It's quite unhelpful to the Linux community.Foroweb wrote:i have the driver for windows but am a noobie in linux world and i do not know how to install.