Thanks, your fix works great.kirk wrote:No, it's included.Is it necessary in Puppy to load MP3 functionality?
Jim1911, is correct. I uploaded a pet package for BibleTime-2.8.1, It has a couple of bug fixes patched in. It requires the qt4, clucene, and sword packages installed. Please note the the qt4 package requires a reboot. Jim and Joe reported 'Install Works' wasn't downloading. That turned out to be a problem with the QT4 packages. I had some files in the qt4-dev package that should have been in the regular qt4 pet. I've re-uploaded the qt4 pets.
Fatdog64-520 Final
Sorry to be the spoiler Kirk, but after removing and re-installing the latest qt4 (rebooted), sword, clucene, and Bibletime, still nogo on being able to download via 'Install Works' feature. Again, while I have the modules I need (downloaded manually), just thinking about someone else who may need this feature. Thanks!Jim1911 wrote:Thanks, your fix works great.kirk wrote:No, it's included.Is it necessary in Puppy to load MP3 functionality?
Jim1911, is correct. I uploaded a pet package for BibleTime-2.8.1, It has a couple of bug fixes patched in. It requires the qt4, clucene, and sword packages installed. Please note the the qt4 package requires a reboot. Jim and Joe reported 'Install Works' wasn't downloading. That turned out to be a problem with the QT4 packages. I had some files in the qt4-dev package that should have been in the regular qt4 pet. I've re-uploaded the qt4 pets.
jg.fw.tx - Please lighten up. Kirk was just trying to help. Take care.
-
- Posts: 5
- Joined: Fri 23 Sep 2011, 15:19
-
- Posts: 5
- Joined: Fri 23 Sep 2011, 15:19
still no auto mount
kirk
sdb1 existed already in /mnt
so i copied your echo and pasted it in the terminal
a reboot still has non-mounted sdb1.
What am missing?
Thanks for your help.
-Jay
sdb1 existed already in /mnt
so i copied your echo and pasted it in the terminal
a reboot still has non-mounted sdb1.
What am missing?
Thanks for your help.
-Jay
uh...? oh...
i don't know what you are talking about, Eric, i wrote in the default font with a "large" font size (it says size=18) and that is NOT screaming in any kind of parlance i know of online.Caneri wrote:@jg.fw.tx ,
Please be kind.
There is no need to use bold fonts as it looks like you are screaming at kirk.
I will ask Murga to stop you if you continue to post in bold type.
Be kind-rewind
Eric
i am quite aghast at the misrecognition of attempted humor here, @joe0855 and @Caneri, but @frankly it doesn't matter. what matters are answers. from a perhaps verbose post directed @kirk, only HE gave me one.
my humor is sometimes too dry for a few people, i know. no need to apologize, i understand users, new or used. i guess that's why i often prefer computers to people, even though they don't chuckle at puns. yet.kirk wrote: Quote:
please, Kirk, that was unnecessary chastisement
I'm sorry, it wasn't meant that way. Most new users just don't notice the FAQs.
BootManager did not work before - it does not find or see the VirtualBox package, the 2 i d/l-ed, anyway. even moving them out of the spot folder. BootManager did see a LibreOffice i d/l-ed, but tossed the sfs error at me.kirk wrote: Quote:
LibreOffice won't load because it says sfs 3 is required and the package is sfs 4.
There's a fix for that on page three of this thread or better yet just use the BootManager. This will be fixed in 521, coming soon.
as for "page 3", on my widescreen i have 7 full pages and 1 partial page of this thread, arranged newest to oldest, and even going backwards i cannot find a fix for the problem. perhaps i am missing something...? wait, one more rewind to be kind and i see an sfs-load-fix.pet. is that it?
i might not have to just wait for 521, lemme reboot out of Puppy into Fatdog64 and try...
appreciate the answer, i'll give'er all i've got, cap'n. regards, jon
---------------
There are none so blind as those who choose what they want to see.
Ancient Optometrist saying
Click on /etc/rc.d/rc.local. It should look like this:a reboot still has non-mounted sdb1.
Code: Select all
#this file called from rc.sysinit
#you can edit this file
#When firewall is installed, will append lines to this file...
#
# If you need to change the scaling governor from the default "ondemand" uncomment le lines below
#modeprobe cpufreq_performance
#ONLINECPUS=$(cat /sys/devices/system/cpu/online | sed "s/-/ /")
#CPUPATH=/sys/devices/system/cpu/cpu
#for cpu in $(seq $ONLINECPUS); do
# CPUFREQ=${CPUPATH}${cpu}/cpufreq
# if [ -d $CPUFREQ ]; then
# echo "performance" > $CPUFREQ/scaling_governor
# fi
#done
mount /dev/sdb1 /mnt/sdb1
FATDOG Development ... Thanks for the MP3 acknowledgement.
Did you see @Shinobar's post re: FATDOG sfs_load?
I am wondering if adding his Pesonalize Settings to the Menu>Setup would have a positive or negative impact in FATDOG?
Hope this helps
Did you see @Shinobar's post re: FATDOG sfs_load?
I am wondering if adding his Pesonalize Settings to the Menu>Setup would have a positive or negative impact in FATDOG?
Hope this helps
No offense to anyone here with this offer.
@JamesBond helped me with an understanding of the steps REQUIRED to set up a VirtualBox on FATDOG several months ago.
I also understand the request being made here in this thread for VirtualBox guidance.
I also understand that when VirtualBox installs, it becomes one of subsystems similar as is CUPS or SAMBA or etc.
Question
Would it be appropriate to ask that someone start a new thread titled VirtualBOX discussion for the 64bit kernels that are now present in Puppyland?
I, for one, would also welcome an OTB VirtualBox (VB) solution that would use Puppy as a Host to exploit my 64bit systems and its RAM. I would consider this a new thread and a separate thread because of the additional elements that are unique in its use in a 64bit host.
In that forum thread we could discuss Host setup, Host assist, VM setup, VM assists, and specifically address the differing incarnations of Puppy Linux, (Live media-RAM based, Frugal based), Win8, Win7-Vista, XP, and other virtual machines that would run via the 64bit Fatdog/LightHouse64 Host(s). This has particular basis as the thread would certainly help in guiding and understanding some of the peculiarities within the host such that successful operations of the virtual machines, the network(s), and the internal operations of the peripherals that the individual virtual machines would see and attempt usage as they run under the auspices of the 64bit host.
The thread would allow everyone to contribute along the lines of VM Host and allow concentration(s) on the virtual machines that pose quirks when running in a VM host environment. Many of these things do not surface in the "normal non-VM" use.
Hope this helps. I don't feel that I have the skill level to start this AND IF IT IS STARTED, it WILL NEED THE ASSISTANCE of the 64bit Distro developers. The reasons for this need is obvious: Their distros will be host for the VM subsystems that will be added.
Lastly, before even going further, I have already reported to Kirk that there are remaining problems in the "hostname" implementation that SHOULD be fixed should progress with a thread like this move forward. This problem does NOT exist in the LH64 PUP implementation. This most certainly will need to be addressed at some point if for no other reason than the fact that using a VB host subsystem will allow any user to add multiple virtual machines to the LANs such that a means of being able to assign meaningful names to the virtual FATDOGs that may come into play will become even more necessary. Better to fix the problem now, than wait, I feel.
I am on record as highlighting the Great work of Kirk and Jamesbond on the product. I have been a user for quite a while. I believe that this continues to be a stellar within the Puppy Linux community And I again, applaud the work of everyone who has contributed items which have made this a great-great OS for our use.
Hope this help
@JamesBond helped me with an understanding of the steps REQUIRED to set up a VirtualBox on FATDOG several months ago.
I also understand the request being made here in this thread for VirtualBox guidance.
I also understand that when VirtualBox installs, it becomes one of subsystems similar as is CUPS or SAMBA or etc.
Question
Would it be appropriate to ask that someone start a new thread titled VirtualBOX discussion for the 64bit kernels that are now present in Puppyland?
I, for one, would also welcome an OTB VirtualBox (VB) solution that would use Puppy as a Host to exploit my 64bit systems and its RAM. I would consider this a new thread and a separate thread because of the additional elements that are unique in its use in a 64bit host.
In that forum thread we could discuss Host setup, Host assist, VM setup, VM assists, and specifically address the differing incarnations of Puppy Linux, (Live media-RAM based, Frugal based), Win8, Win7-Vista, XP, and other virtual machines that would run via the 64bit Fatdog/LightHouse64 Host(s). This has particular basis as the thread would certainly help in guiding and understanding some of the peculiarities within the host such that successful operations of the virtual machines, the network(s), and the internal operations of the peripherals that the individual virtual machines would see and attempt usage as they run under the auspices of the 64bit host.
The thread would allow everyone to contribute along the lines of VM Host and allow concentration(s) on the virtual machines that pose quirks when running in a VM host environment. Many of these things do not surface in the "normal non-VM" use.
Hope this helps. I don't feel that I have the skill level to start this AND IF IT IS STARTED, it WILL NEED THE ASSISTANCE of the 64bit Distro developers. The reasons for this need is obvious: Their distros will be host for the VM subsystems that will be added.
Lastly, before even going further, I have already reported to Kirk that there are remaining problems in the "hostname" implementation that SHOULD be fixed should progress with a thread like this move forward. This problem does NOT exist in the LH64 PUP implementation. This most certainly will need to be addressed at some point if for no other reason than the fact that using a VB host subsystem will allow any user to add multiple virtual machines to the LANs such that a means of being able to assign meaningful names to the virtual FATDOGs that may come into play will become even more necessary. Better to fix the problem now, than wait, I feel.
I am on record as highlighting the Great work of Kirk and Jamesbond on the product. I have been a user for quite a while. I believe that this continues to be a stellar within the Puppy Linux community And I again, applaud the work of everyone who has contributed items which have made this a great-great OS for our use.
Hope this help
VirtualBox et al...
@gcmartin
while my own interests in VirtualBox are aimed at 64 bit because it's the only platform that offers effective and full use of all the base computer hardware, more than 3 Gb of RAM, and 64 or 32 bit guests, i realize there's lots of 32 bit users who could benefit from VirtualBox. there's a lot of crossover commonality.
but on the subject of threads - and everybody should be aware i'm a newcomer to the Puppy Linux Discussion Forum and its established protocols - i can see distinct advantages in forming a new "Advanced Topic" that addresses 64 bit things (as opposed to Puppy's de facto 32 bit).
regardless of the possible preponderance 32 bit machines and OSs in the wild, the industry trend toward 64 bit was irreversibly established some years ago. sometimes backward compatibility is overemphasized - but i digress... 64 bit is here to stay. yea, even though only 3/8 of my machines here are 64 bit they're my main ones.
so a 64 bit VirtualBox thread is one thing, but a 64 bit (Puppy Linux) thread would be broader and could include a lot more. that's my 2 devalued American cents.
regards, jon
great idea, and yes, i'd be glad to contribute whatever tidbits i can glean from using any 64 bit Puppy in any host and guest environments. not that i'm by any standard an expert, more a lazy user. since i'm lazy i'm always trying to find the easiest, cheapest, fastest, least complicated way to do something.Question
Would it be appropriate to ask that someone start a new thread titled VirtualBOX discussion for the 64bit kernels that are now present in Puppyland?
while my own interests in VirtualBox are aimed at 64 bit because it's the only platform that offers effective and full use of all the base computer hardware, more than 3 Gb of RAM, and 64 or 32 bit guests, i realize there's lots of 32 bit users who could benefit from VirtualBox. there's a lot of crossover commonality.
but on the subject of threads - and everybody should be aware i'm a newcomer to the Puppy Linux Discussion Forum and its established protocols - i can see distinct advantages in forming a new "Advanced Topic" that addresses 64 bit things (as opposed to Puppy's de facto 32 bit).
regardless of the possible preponderance 32 bit machines and OSs in the wild, the industry trend toward 64 bit was irreversibly established some years ago. sometimes backward compatibility is overemphasized - but i digress... 64 bit is here to stay. yea, even though only 3/8 of my machines here are 64 bit they're my main ones.
so a 64 bit VirtualBox thread is one thing, but a 64 bit (Puppy Linux) thread would be broader and could include a lot more. that's my 2 devalued American cents.
regards, jon
md5 sum
i was loading LibreOfffice - thanks, kirk, the pet worked - and tried to double check the md5 checksum against the downloaded .sfs file, but couldn't find any app to do that in Fatdog64. am i missing something...?
anyway, it did install fine anyway but then protested strongly there wasn't any JRE loaded. uhm. more dependencies...
the only JRE i could find was in Fatdog64's ibiblio index, but it's an .sfs. i'm wondering how fast i'm going to reach the 5 .sfs limt...
nothing is showing up in package manager, so i'm going to reboot and see if they pop up.
regards, jon
anyway, it did install fine anyway but then protested strongly there wasn't any JRE loaded. uhm. more dependencies...
the only JRE i could find was in Fatdog64's ibiblio index, but it's an .sfs. i'm wondering how fast i'm going to reach the 5 .sfs limt...
nothing is showing up in package manager, so i'm going to reboot and see if they pop up.
regards, jon
Re: md5 sum
In a terminal window, Tryjg.fw.tx wrote: ... find any app to do that in Fatdog64....
Code: Select all
md5sum fn.sfs <=== The name of the d/l
This will check md5sum. Can also be added to right click menu.
Fixed the directory structure.
Fixed the directory structure.
- Attachments
-
- ghasher-1.2.1-x86_64.pet
- (18.5 KiB) Downloaded 376 times
Last edited by WillM on Thu 29 Sep 2011, 17:34, edited 2 times in total.
-
- Posts: 5
- Joined: Sat 10 Apr 2010, 03:35
just installed virtualbox from the binaries package on their website. it requires devx but I must say it's getting easier. In older puppy versions you had to track down kernel headers. any way just downloaded the one from the bottom of the list marked all distributions on the amd64 side(~70MB). I know a pet package would be much better but ...
Many thanks to WillM, going to try ghasher just as soon as I finish this post.
Many thanks to WillM, going to try ghasher just as soon as I finish this post.
md5 sum
thanks @WillM and @gcmartin, both check sums worked, although i have no idea how to add either of them to the right click menu despite a little searching - the search function on this BB forum won't let me do an enclose in quotes search and the AND function isn't exclusive, so i got hundreds of hundreds of posts/topics. i'll have to explore this phpBB's eccentricities a little more to hone in. the real problem, of course, is my incomplete knowledge of the organization of the Linux file system, et al. i'm workin' on it.
in the meantime setting up a VirtualBox has been set back by my swapping from a live CD which (seems to have run out of room and let all my additions/downloads perish in RAM on a reboot) to a pendrive. since my eventual goal is to have a minimal base OS host system and do most of my day-to-day computing chores in guests, the ever increasing size of the saved sessions is perplexing and eating up storage space. so i'm pulling back to learn how Puppy (and Bigdog64 or LIghthouse or ...) functions together. slowly, with interruptions.
more mind work than i anticipated but que sera sera...
regards, jon
------------
We are all related by DNA.
Old Simian saying
in the meantime setting up a VirtualBox has been set back by my swapping from a live CD which (seems to have run out of room and let all my additions/downloads perish in RAM on a reboot) to a pendrive. since my eventual goal is to have a minimal base OS host system and do most of my day-to-day computing chores in guests, the ever increasing size of the saved sessions is perplexing and eating up storage space. so i'm pulling back to learn how Puppy (and Bigdog64 or LIghthouse or ...) functions together. slowly, with interruptions.
more mind work than i anticipated but que sera sera...
regards, jon
------------
We are all related by DNA.
Old Simian saying
-
- Posts: 5
- Joined: Sat 10 Apr 2010, 03:35
Just tried ghasher, works great! also discovered phash while fooling around. how long has that been there? to think I've been typing md5sum at the Command Line all this time.
Oh by the way has anybody else noticed xterm adding "[C" (without quotes) to the end of the command when you use <alt-right arrow> for command line completion. Haven't noticed that before, kinda strange.
Anyway thanks guys for a great distro! Fatdog 64 is truly awesome! I've been using it since version 5.0.0 and have had no problems so far. Fatdog is definitely my favorite Operating System and it just keeps getting better. Please keep up the good work.
Oh by the way has anybody else noticed xterm adding "[C" (without quotes) to the end of the command when you use <alt-right arrow> for command line completion. Haven't noticed that before, kinda strange.
Anyway thanks guys for a great distro! Fatdog 64 is truly awesome! I've been using it since version 5.0.0 and have had no problems so far. Fatdog is definitely my favorite Operating System and it just keeps getting better. Please keep up the good work.
Since 520.Buck Huffman wrote:also discovered phash while fooling around. how long has that been there? to think I've been typing md5sum at the Command Line all this time.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]