Lighthouse 64 5.15 Final
@meeki,
thanks very much for your earlier post on XPDF - I hadn't tinkered with the config file for the fonts directory, from memory, but I've mucked around with it in the past regarding my preference for continuous scrolling, a4 pagesize for printing etc. (all this in pemasu's dpup exprimo 5X15, 32-bit). Thanks for the pointer on that. Sorry it doesn't appeal to everyone (or many!) with its spartan appearance and interface - I don't like the dot-matrix type font they chose for their interface, but for its size its quick and reliable with the cut'n'paste of text, which is what I need. I'm hoping that someone will write/volunteer a module to support hightlighted text saves in any of the pdf readers... if only Foxit Reader for Linux had that funcionality, as it does in windblows
P.S. and thanks for looking into PDF Shuffler - I'll reboot with LH 5.15 on the weekend, and have a look into those issues that you raised, Cheers!
thanks very much for your earlier post on XPDF - I hadn't tinkered with the config file for the fonts directory, from memory, but I've mucked around with it in the past regarding my preference for continuous scrolling, a4 pagesize for printing etc. (all this in pemasu's dpup exprimo 5X15, 32-bit). Thanks for the pointer on that. Sorry it doesn't appeal to everyone (or many!) with its spartan appearance and interface - I don't like the dot-matrix type font they chose for their interface, but for its size its quick and reliable with the cut'n'paste of text, which is what I need. I'm hoping that someone will write/volunteer a module to support hightlighted text saves in any of the pdf readers... if only Foxit Reader for Linux had that funcionality, as it does in windblows
P.S. and thanks for looking into PDF Shuffler - I'll reboot with LH 5.15 on the weekend, and have a look into those issues that you raised, Cheers!
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
PDF-Shuffler
http://sourceforge.net/projects/pdfshuffler/
PDF-Shuffler-0.6.0
SFS http://lhpuppetsfs.puppytune.org/sfs/pd ... x86_64.sfs
MD5 http://lhpuppetsfs.puppytune.org/sfs/pd ... 64.sfs.md5
NOTE!!! You must be running the devx.sfs ... PDF-Shuffler needs python.
Inside the SFS:
PDF-Shuffler-0.6.0 (python app)
pyPDF-1.13 (python app)
pypoppler-0.12.1 (linux lib for python)
-------------------------------------------------------------------------------------------------------------
Good news every one. More build pets came of this. You can find pyPDF-1.13 and pypoppler-0.12.1 as pets HERE ----> http://lhpuppetsfs.puppytune.org/pet/ if you need them for your own build needs!!!
http://sourceforge.net/projects/pdfshuffler/
PDF-Shuffler-0.6.0
SFS http://lhpuppetsfs.puppytune.org/sfs/pd ... x86_64.sfs
MD5 http://lhpuppetsfs.puppytune.org/sfs/pd ... 64.sfs.md5
NOTE!!! You must be running the devx.sfs ... PDF-Shuffler needs python.
Inside the SFS:
PDF-Shuffler-0.6.0 (python app)
pyPDF-1.13 (python app)
pypoppler-0.12.1 (linux lib for python)
-------------------------------------------------------------------------------------------------------------
Good news every one. More build pets came of this. You can find pyPDF-1.13 and pypoppler-0.12.1 as pets HERE ----> http://lhpuppetsfs.puppytune.org/pet/ if you need them for your own build needs!!!
Game:
M.A.R.S. – a ridiculous shooter
http://mars-game.sourceforge.net/?page_id=10
http://mars-game.sourceforge.net/?page_id=10
mars_a_ridiculous_shooter-0.7.4-x86_64.sfs
SFS http://lhpuppetsfs.puppytune.org/games/ ... x86_64.sfs 71MB
MD5 http://lhpuppetsfs.puppytune.org/games/ ... 64.sfs.md5
M.A.R.S. – a ridiculous shooter
http://mars-game.sourceforge.net/?page_id=10
http://mars-game.sourceforge.net/?page_id=10
Features
awesome 2D-graphics with an unique style and shader support
a stunning amount of particles
single- and multiplayer-support
artificial intelligence using an aggro-system, which reacts differently upon varying situations and uses inter-bot communication via jobs
many impressive weapons and specials
customizable ships
a very sexy GUI
support for many different languages
mars_a_ridiculous_shooter-0.7.4-x86_64.sfs
SFS http://lhpuppetsfs.puppytune.org/games/ ... x86_64.sfs 71MB
MD5 http://lhpuppetsfs.puppytune.org/games/ ... 64.sfs.md5
Game:
Seven Kingdoms Ancient Adversaries
http://7kfans.com/
Strategy Guide
http://www.7kfans.com/wiki/index.php/7K_Strategy_Guide
http://www.7kfans.com/wiki/index.php/Main_Page
SFS http://lhpuppetsfs.puppytune.org/games/ ... x86_64.sfs 69MB
MD5 http://lhpuppetsfs.puppytune.org/games/ ... 64.sfs.md5
Seven Kingdoms Ancient Adversaries
http://7kfans.com/
Strategy Guide
http://www.7kfans.com/wiki/index.php/7K_Strategy_Guide
http://www.7kfans.com/wiki/index.php/Main_Page
seven_kingdoms-ancient_adversaries-2.24.3-x86_64.sfsSeven Kingdoms Ancient Adversaries was open sourced under the GPL in 2009. This includes the game source code, graphics, and audio, except the music.
SFS http://lhpuppetsfs.puppytune.org/games/ ... x86_64.sfs 69MB
MD5 http://lhpuppetsfs.puppytune.org/games/ ... 64.sfs.md5
Lost X input while installing monodevelop-2.8.1
Greetings.
i was hoping to get mono installed onto this LH64 final version, and needed monodevelop-2.8.1.
While installing monodevelop-2.8.1, there's the lvm2 dependency that needed to be installed.
While it was installing, X crashed, and was continually printing onto stdout/err console "cannot exec: /bin/bash ..."
After shutdown and reboot into X using the same savefile, the usb mouse and usb keyboard refuses to work. We couldn't even use the CTRL-ALT-F<key> combination to get into the text consoles.
All we could do was press the power button, listen for the bark, and shutdown the system.
Is there a fix for this? especially losing mouse and keyboard in the xwin desktop?
i was hoping to get mono installed onto this LH64 final version, and needed monodevelop-2.8.1.
While installing monodevelop-2.8.1, there's the lvm2 dependency that needed to be installed.
While it was installing, X crashed, and was continually printing onto stdout/err console "cannot exec: /bin/bash ..."
After shutdown and reboot into X using the same savefile, the usb mouse and usb keyboard refuses to work. We couldn't even use the CTRL-ALT-F<key> combination to get into the text consoles.
All we could do was press the power button, listen for the bark, and shutdown the system.
Is there a fix for this? especially losing mouse and keyboard in the xwin desktop?
Were you building them yourself???? or installing them from a Slax package?
Also if your a builder make a few save files. One for build one for run etc so you can boot from a mistake like this. Also back them up from time to time.
LVM2 (logical volume management) not a good Idea to play with this unless you know what your doing. I build stuff all the time and will not touch it with a 10foot pole.
Also if your a builder make a few save files. One for build one for run etc so you can boot from a mistake like this. Also back them up from time to time.
LVM2 (logical volume management) not a good Idea to play with this unless you know what your doing. I build stuff all the time and will not touch it with a 10foot pole.
Can anyone help mrbulldog with his problem here:
http://www.murga-linux.com/puppy/viewtopic.php?t=82136
or here:
http://www.murga-linux.com/puppy/viewtopic.php?t=82178
He seems not able to understand how to add posts to the end of this thread!
(I think he is clicking 'New Topic' instead of 'Post Reply')
http://www.murga-linux.com/puppy/viewtopic.php?t=82136
or here:
http://www.murga-linux.com/puppy/viewtopic.php?t=82178
He seems not able to understand how to add posts to the end of this thread!
(I think he is clicking 'New Topic' instead of 'Post Reply')
LVM in LH64
Hi @Edwardb
LVM2 is not so bad. It has some great and distinct advantages especially for those who of us who expect to maintain data over both time and spacial. Its been around so long that most all issues have been cleared long ago.
You may want to PM him or search past FATDOG threads for his LVM mention.
Here to help
i think JamesBond did some work with LVM2 on a 64bit platform back in the FATDOG 5.2x days. He may still have the utilities he provided for this somewhere in his arsenal. I seem to remember a PET that addressed dependencies,....I think.Edwardb wrote:... there's the lvm2 dependency ...
LVM2 is not so bad. It has some great and distinct advantages especially for those who of us who expect to maintain data over both time and spacial. Its been around so long that most all issues have been cleared long ago.
You may want to PM him or search past FATDOG threads for his LVM mention.
Here to help
gcmartin:
My original comment was out of fear. Having broken things many times Its ok to be scared now and then.
Ok let me justify my first comment. I don't know a thing about Multipath and storage in Linux besides a very general Idea about how they work. I use LVM groups on my server. But besides knowing how to basically manipulate my storage settings I would have no clue how to compile the sucker with correct depends in my current kernel.LVM2 is not so bad.
My original comment was out of fear. Having broken things many times Its ok to be scared now and then.
Last edited by meeki on Wed 14 Nov 2012, 00:01, edited 1 time in total.
Re: Lost X input while installing monodevelop-2.8.1
There are somethings that just simply dont work well to compile into the very environment you are using. Some things (like lvm), you need to either A) edit your ./configure script or make install destdir; and install them somewhere else to build a package out of them. If you try to just do a normal install you will be overwriting or changing files you system is actively using. In those cases it's best to build the package, and then manually place it in the base SFS (if you're sure you got everything working right) and then reboot using that SFS.edwardb wrote:Greetings.
i was hoping to get mono installed onto this LH64 final version, and needed monodevelop-2.8.1.
While installing monodevelop-2.8.1, there's the lvm2 dependency that needed to be installed.
While it was installing, X crashed, and was continually printing onto stdout/err console "cannot exec: /bin/bash ..."
After shutdown and reboot into X using the same savefile, the usb mouse and usb keyboard refuses to work. We couldn't even use the CTRL-ALT-F<key> combination to get into the text consoles.
All we could do was press the power button, listen for the bark, and shutdown the system.
Is there a fix for this? especially losing mouse and keyboard in the xwin desktop?
Another example of this is that you have to usually compile proprietary x.org drivers from command line with x not running.
Can you compile it for us since you're more aware of it than the rest of us are.gcmartin wrote:LVM2 is not so bad. It has some great and distinct advantages especially for those who of us who expect to maintain data over both time and spacial. Its been around so long that most all issues have been cleared long ago.
Here to help
It'd be a big advantage as you've stated if it was available for everyone.
Thanks Q5sys for your comments on PET and SFS building.
Beyond what Q5sys is sharing, I would like to give a little more insight. As I remember, JamesBond (or someone) added LVM support via a PET such that the booted system would be able to recognize and work with an existing LVM filesystem. The benefit that he produced was not to take Puppy into a new direction, but rather, to give it intelligence to recognize and use an LVM if it were present. FATDOG and other PUPs with this are excellent distro to manipulate data/files/etc "outside" of the primary distro that built the LVM. That's the beauty of Puppies. Fast, and robustly featured.
This was an attempt to be helpful.
Q5sys, I know you have great skills and insights in the LH64 build process. I would trust what you produce as I'm sure you would thoroughly test it. Your effort would be an addition to the PPM effort, I would assume.
Here to help
I had made my comments because, I thought that another member in the community has already addressed this and I thought that it may be compatible with current LH64.Q5sys wrote: ... Can you compile it for us since you're more aware of it than the rest of us are.
It'd be a big advantage as you've stated if it was available for everyone. ...
Beyond what Q5sys is sharing, I would like to give a little more insight. As I remember, JamesBond (or someone) added LVM support via a PET such that the booted system would be able to recognize and work with an existing LVM filesystem. The benefit that he produced was not to take Puppy into a new direction, but rather, to give it intelligence to recognize and use an LVM if it were present. FATDOG and other PUPs with this are excellent distro to manipulate data/files/etc "outside" of the primary distro that built the LVM. That's the beauty of Puppies. Fast, and robustly featured.
This was an attempt to be helpful.
Q5sys, I know you have great skills and insights in the LH64 build process. I would trust what you produce as I'm sure you would thoroughly test it. Your effort would be an addition to the PPM effort, I would assume.
Here to help
Video issue on a new PC
There is a community member who has a very new PC and is running into difficulty trying to get to LH64-515 desktop. He has enclosed a Hardinfo report.
Question
Any additional suggestions to that thread?
Question
Any additional suggestions to that thread?
Re: LVM in LH64
Hi @ gcmartin.gcmartin wrote:Hi @Edwardbi think JamesBond did some work with LVM2 on a 64bit platform back in the FATDOG 5.2x days. He may still have the utilities he provided for this somewhere in his arsenal. I seem to remember a PET that addressed dependencies,....I think.Edwardb wrote:... there's the lvm2 dependency ...
LVM2 is not so bad... [snip]
Here to help
i've dumped lvm2 for btrfs.
i only mentioned lvm2 because the mono package seemed to have a dependence on something in the lvm2 "pet" package...
But thank you anyways.
Re: Lost X input while installing monodevelop-2.8.1
Hi @ Q5sys,Q5sys wrote:There are somethings that just simply dont work well to compile into the very environment you are using. Some things (like lvm), you need to either A) edit your ./configure script or make install destdir; and install them somewhere else to build a package out of them. If you try to just do a normal install you will be overwriting or changing files you system is actively using. In those cases it's best to build the package, and then manually place it in the base SFS (if you're sure you got everything working right) and then reboot using that SFS...edwardb wrote:Greetings.
i was hoping to get mono installed onto this LH64 final version, and needed monodevelop-2.8.1.
hehe... one thing at a time. i haven't even gotten to the point of building ANYTHING in this environment, yet; this is just setting it up first...
However, thank you for explaining the damaging nature of the .pet files i install using the Package Manager. What you said makes sense. Up to now, i assumed installing .pets were guaranteed SAFE for the system. i guess i'm sorely mistaken.
This then brings up a few things:
1) if .pets are so damaging to the system, why are they allowed to continue to exist and be referenced by the Package Manager when "damage" *is* being done to the system that installs them? (this goes with just about anything file-system related... at least with what i've experienced...)
2) With that being said, why don't the creator of the .pet opt for the .sfs route *IN THE FIRST PLACE* to spare the user the grief of a ruined system? (especially when the though of backing up the .savefile came as an afterthought, too late...)
3) Is there a restore feature via CLI that undoes the damage the .pet has done? In my case, i cannot enter into X, so i'm left with doing the repairs in console mode...
BTW, feel free to split up and move this thread if it doesn't belong here. i'm still a noob and am feeling my way around here...
Re: Lost X input while installing monodevelop-2.8.1
i think you misunderstood me. PETS are fine. thats why we use them.edwardb wrote:Hi @ Q5sys,Q5sys wrote:There are somethings that just simply dont work well to compile into the very environment you are using. Some things (like lvm), you need to either A) edit your ./configure script or make install destdir; and install them somewhere else to build a package out of them. If you try to just do a normal install you will be overwriting or changing files you system is actively using. In those cases it's best to build the package, and then manually place it in the base SFS (if you're sure you got everything working right) and then reboot using that SFS...edwardb wrote:Greetings.
i was hoping to get mono installed onto this LH64 final version, and needed monodevelop-2.8.1.
hehe... one thing at a time. i haven't even gotten to the point of building ANYTHING in this environment, yet; this is just setting it up first...
However, thank you for explaining the damaging nature of the .pet files i install using the Package Manager. What you said makes sense. Up to now, i assumed installing .pets were guaranteed SAFE for the system. i guess i'm sorely mistaken.
This then brings up a few things:
1) if .pets are so damaging to the system, why are they allowed to continue to exist and be referenced by the Package Manager when "damage" *is* being done to the system that installs them? (this goes with just about anything file-system related... at least with what i've experienced...)
2) With that being said, why don't the creator of the .pet opt for the .sfs route *IN THE FIRST PLACE* to spare the user the grief of a ruined system? (especially when the though of backing up the .savefile came as an afterthought, too late...)
3) Is there a restore feature via CLI that undoes the damage the .pet has done? In my case, i cannot enter into X, so i'm left with doing the repairs in console mode...
BTW, feel free to split up and move this thread if it doesn't belong here. i'm still a noob and am feeling my way around here...
I was talking about compiling from source code and building things that way. when you are compiling something it 'can' cause issues when in the process you overwrite something thats being used to run the system.
if you use pets you shouldnt have anything to worry about.
Here's an example of how a comment can have un-intended consequences.
PET development produces the same functionality within the distro where its REPO presents it via PPM. And, PETs understanding is built-into the PUPs in each's PPM.
For the most part, excepting for one recent occasion in all of my Puppy years, I have had no issues in PET use. Further, in all cases where a developer has produced a PET and an SFS, I have never had a problem. This doesn't address which to use. Its just one experience.
There are concerns on both sides of the fence for either of these 2 approaches that add functionality to a running distro. But, Puppy's PPM has a long history with PETs in system integration, while the SFS have had 2 specific tools added to Puppyland to assist understanding users in SFS manipulation(s).
I don't think Q5sys intended to alarm users in their use of PPM/PETs or anything of such.
None of us should shy away from PET development in fear because i don't believe he intended such.
All developers should take into account that both PETs (used in PPM) and SFS (used by 3 other system facilities) add functionality to a given distro (assuming you are using its DEVX). And, also, its easy for any one of us to see that a PET's size and a SFS's size is not "dramatically" different. (I have a specific example where a distro developer made both a PET and an SFS and the PET is actually smaller that the SFS. And, there are other sizings where the PET and SFS are of equal sizing)
We are all here to try to help each other.
I'm sure that Q5sys was attempting to share a reason why one developer might prefer to use a SFS versus using a PET. Namely, if a SFS is used, it reduces the system effort that a developer would need to address in testing of the product that is being added to the running system. Simply SFSs can be installed in a layered fashion, while PETs are installed via PPM and insert directly into the OS. Problems do NOT ALWAYs occur and in some very-rare occasions, a module may get misplaced. (Without going into particulars, something similar could, again rare as well, could happen with SFS use which would require the developer to do research to understand.)edwardb wrote:... for explaining the damaging nature of the .pet files i install using the Package Manager. What you said makes sense. Up to now, i assumed installing .pets were guaranteed SAFE for the system. i guess i'm sorely mistaken ...
PET development produces the same functionality within the distro where its REPO presents it via PPM. And, PETs understanding is built-into the PUPs in each's PPM.
For the most part, excepting for one recent occasion in all of my Puppy years, I have had no issues in PET use. Further, in all cases where a developer has produced a PET and an SFS, I have never had a problem. This doesn't address which to use. Its just one experience.
There are concerns on both sides of the fence for either of these 2 approaches that add functionality to a running distro. But, Puppy's PPM has a long history with PETs in system integration, while the SFS have had 2 specific tools added to Puppyland to assist understanding users in SFS manipulation(s).
I don't think Q5sys intended to alarm users in their use of PPM/PETs or anything of such.
None of us should shy away from PET development in fear because i don't believe he intended such.
All developers should take into account that both PETs (used in PPM) and SFS (used by 3 other system facilities) add functionality to a given distro (assuming you are using its DEVX). And, also, its easy for any one of us to see that a PET's size and a SFS's size is not "dramatically" different. (I have a specific example where a distro developer made both a PET and an SFS and the PET is actually smaller that the SFS. And, there are other sizings where the PET and SFS are of equal sizing)
We are all here to try to help each other.
edwardb
What you installed was not a pet
I made a video showing what happened to you and how not to download slax packages in the future.
VIDEO SHOWING WHAT I THINK HAPPENED
http://youtu.be/JfaL9nI_K8s
Most people that make pets dont have depends.
Hope this helps
What you installed was not a pet
I made a video showing what happened to you and how not to download slax packages in the future.
VIDEO SHOWING WHAT I THINK HAPPENED
http://youtu.be/JfaL9nI_K8s
Most people that make pets dont have depends.
Hope this helps