Posted: Sat 14 Feb 2009, 07:56
All squared away, Chris. Check the Beta release coming soon.cthisbear wrote:Well most things seem nice and smooth.
But the drive icons.
This has to be addressed as well as unmounting.
READ-ONLY Archive
https://oldforum.puppylinux.com/
All squared away, Chris. Check the Beta release coming soon.cthisbear wrote:Well most things seem nice and smooth.
But the drive icons.
This has to be addressed as well as unmounting.
Hey, I've got the 4.1.1 version of Remaster Express done except for a bit of needed testing; it just ejected a completed live-CD for me as I was typing this. (Right after I get done with this message, I'll put up links to the completed set of screenshots in the "Remastering remastering" thread.) [EDIT: And here they are: http://www.murga-linux.com/puppy/viewto ... 765#274765] Can I have the 4.2 versions of packages.txt and 0pkgs_db, so I can work up the 4.2 version of Remaster Express really fast?WhoDo wrote:Check the Beta release coming soon.
I compiled the full version last week, I have it on file here, the one which rarsa provided didn't contain any dev files for compiling so it made it useless for me when I wanted to compile the latest amsn, but by then the 2 packages weren't compatible, So it messed everything up, When i'm done of printing and icewm, I'll move over to tcl and build a release, with the dev files available for the devx or to download.pa_mcclamrock wrote:Hey, I've got the 4.1.1 version of Remaster Express done except for a bit of needed testing; it just ejected a completed live-CD for me as I was typing this. (Right after I get done with this message, I'll put up links to the completed set of screenshots in the "Remastering remastering" thread.) Can I have the 4.2 versions of packages.txt and 0pkgs_db, so I can work up the 4.2 version of Remaster Express really fast?WhoDo wrote:Check the Beta release coming soon.
Also, there's still a problem with the Tcl 8.5.6 .PET (the "clock" command doesn't work, and apps that invoke it won't start). I PM'd rarsa several days ago, but I haven't received any notice that he's corrected the problem, if he has. I appreciate the fact that he slimmed Tcl and Tk down considerably, but I can't help wondering if he may have cut out too much in addition to the "msgcat" package that's needed to make "clock" work. I hope you can either (1) successfully beg him to fix Tcl 8.5.6 really soon or (2) bring yourself to cram in my somewhat fatter 8.5.5-runtime .PETs straight out of Slackware, unless and until the problem with 8.5.6 is fixed. (They still amount to a lot less than the 4 MB you were originally considering for Tcl and Tk!)
Both my desktops are AMD athlon's 64x2 and I never Had a issue with cpu's.If that helps, I never needed SMP enabled to run Puppy, Would be nice to have it, but the size difference is a lot if I remember right:)ferikenagy wrote:As i had reported time ago(and some other members too on different dell), the last puppy that boots the kernel on Dell laptop 1526 was puppy alpha 406 with kernel 2.6.25.15.,next kernel 2.6.25.16 after writing "booting kernel." it stops,hangs.
Initially I supposed some drive/modules change in kernel from 2.6.25.15 to 2.6.25.16, or some changes in <init> script from "initrd" , for my surprise the only difference between them where some encrypting modules,so not there was the difference.
the answer to this bug seems to be in kernel compile configuration, because for my surprise 2 experimental puplets with the same kernel 2.6.25.16 but with different configuration from standard, both with SMP enabled (to run on multicore enviroment) boots & runs with no problems ,on my Dell 1526, these are:
galipup : g_pup-1.2.iso, (with MU SMP kernel for 4.1.2) and lxde-pup411-k2.6.27.5-dillo-v01.iso
Now there is still some question: if the difference is in enabling SMP only or there was some other difference in configuration that makes it to work on my dell (processor is AMD Turion 64x2 TL60)
Great--thanks! (Hang on, WhoDo!)ttuuxxx wrote:When i'm done [with] printing and icewm, I'll move over to tcl and build a release, with the dev files available for the devx or to download.
2. One of the first things I do with each new "I think I'll keep this one" installation is to edit rc.shutdown (in /etc/rc.d) and add an 'eject' statement at the bottom. This enables me to remove the CD I forget was still in the tray. Otherwise I have to power up just to take it out which often means aborting a boot-up. Is this A Bad Idea for deep and mysterious Linux reasons, or is it An OK Idea? If it's the latter could it go into the release?I checked my e-mail with Claws and got the mail, but I also got an error message saying "The Bogofilter plugin couldn't filter a message. The command `bogofilter -T -b` couldn't be run."
@ttuuxxx I've just printed OK from Abiword with your CUPS packages. No intervention was required; I choose the 'Generic Postscript' printer and it went to the printer I set as Default in CUPS.ttuuxxx wrote:I just printed with abiword, Keep in mind I never used Linux printing before yesterday really, so this is all new to me, But on the other hand I'm pretty good a compiling and getting things to work, so feel confident Anyways How does Abiword print, the way I did it was create a PDF and saved it, then opened the pdf and printed it, when I tried 'Generic Postscript' Abiword Crashes, and when I ran it via command line, and tried it again I got this message
# abiword
** (abiword:9606): WARNING **: Can't g_module_open /usr/lib/libgnomeprint/2.18.2/modules/libgnomeprintcups.so
lpr: Error - no default destination available.
Broken pipe
So was the Generic Postscript always broken in Abiword ?
I'll look for a fix
ttuuxxx
yes nic I set the printer the way you described and it worked.nic2109 wrote:@ttuuxxx I've just printed OK from Abiword with your CUPS packages. No intervention was required; I choose the 'Generic Postscript' printer and it went to the printer I set as Default in CUPS.ttuuxxx wrote:I just printed with abiword, Keep in mind I never used Linux printing before yesterday really, so this is all new to me, But on the other hand I'm pretty good a compiling and getting things to work, so feel confident Anyways How does Abiword print, the way I did it was create a PDF and saved it, then opened the pdf and printed it, when I tried 'Generic Postscript' Abiword Crashes, and when I ran it via command line, and tried it again I got this message
# abiword
** (abiword:9606): WARNING **: Can't g_module_open /usr/lib/libgnomeprint/2.18.2/modules/libgnomeprintcups.so
lpr: Error - no default destination available.
Broken pipe
So was the Generic Postscript always broken in Abiword ?
I'll look for a fix
ttuuxxx
It "just worked" - praise be.
It would eliminate some confusion if the words 'Generic Postscript' could be replaced by 'Default CUPS Printer' (or something to that effect), but I have no idea if that's something that you can influence in the compilation, or if it's too deep down in the code to be accessible.
hi nic,nic2109 wrote:1. Has this problem been fixed? I still get it.
I checked my e-mail with Claws and got the mail, but I also got an error message saying "The Bogofilter plugin couldn't filter a message. The command `bogofilter -T -b` couldn't be run."