virtualbox-4.1.4-2-slacko.sfs works on slacko 5.3/5.3++.difedepe wrote:I am looking forward for the Virtualbox for Slacko puppy 5.3
http://www.murga-linux.com/puppy/viewto ... 32&start=2
You can apply SFS by using the SFS-loader on slacko.
virtualbox-4.1.4-2-slacko.sfs works on slacko 5.3/5.3++.difedepe wrote:I am looking forward for the Virtualbox for Slacko puppy 5.3
thank you very much shinobarshinobar wrote:virtualbox-4.1.4-2-slacko.sfs works on slacko 5.3/5.3++.difedepe wrote:I am looking forward for the Virtualbox for Slacko puppy 5.3
http://www.murga-linux.com/puppy/viewto ... 32&start=2
You can apply SFS by using the SFS-loader on slacko.
Hi Shinobar,shinobar wrote:@difedepe
If you have ever installed another or older PET/SFS, remove them all and delete '/lib/modules/*/misc/vbox*.ko', if they are exists, before loading the new.
that's very clearshinobar wrote:virtualbox-4.1.6.sfs for Puppy 4.3.1 and most of Puppies 5.x.
as for Slacko, use virtualbox-4.1.6-slacko.sfs.
http://www.murga-linux.com/puppy/viewto ... 055#481055
If you have ever installed another or older virtualbox PET/SFS and trying new, remove old ones and delete '/lib/modules/*/misc/vbox*.ko', /opt/VirtualBox, if they are exists, before loading the new.
difedepe wrote:that's very clearshinobar wrote:virtualbox-4.1.6.sfs for Puppy 4.3.1 and most of Puppies 5.x.
as for Slacko, use virtualbox-4.1.6-slacko.sfs.
http://www.murga-linux.com/puppy/viewto ... 055#481055
If you have ever installed another or older virtualbox PET/SFS and trying new, remove old ones and delete '/lib/modules/*/misc/vbox*.ko', /opt/VirtualBox, if they are exists, before loading the new.
I'll let you know
Thanks in advance.
Hi Shinobar... this is your answer to my question????shinobar wrote:Add kernel module for Wary-5.2.2 ((2.6.32-uni):
virtualbox-4.1.6-1.sfs
http://www.murga-linux.com/puppy/viewto ... 055#481055
If I remember correctly, you can't increase its available storage once the disk image is created.difedepe wrote:Sorry, do you know if it is possible to increase the "C:/" space in a windows vdi file? Or do I have to install one more time another virtual windows?
From what I have seen, you have been a great help in this community by making it easy for users to run a VM host and run VM guests.TheAsterisk! wrote: ... just feel like I should float the idea to make sure it won't cause any more difficulty or confusion than what I'm doing now. Suggestions, feedback, requests, etc., would be appreciated.
Thanks!
Kind words! Thank you!gcmartin wrote:From what I have seen, you have been a great help in this community by making it easy for users to run a VM host and run VM guests.
Well, my view is that anyone who uses the packages I build is qualified to address the issue. My main concern is whether or not the new method would introduce any (extra) confusion.I am NOT a system builder. so I am probably not the best for offering an answer.
Actually, an ISO like that might not be a bad idea, but I'd be clueless where to begin. I've never built or trimmed a Puppy before, but I'd think a somewhat cut-down Puplet would be ideal, to give the VM some more breathing room on whatever hardware gets used. In any case, that would be a bit beyond my scope.Since I deal with Objectives, then reviewing the success of the objectives, you may want to access whether there is a method/methodology that would be foolproof in having someone go from your PET to a running VB host and guest. That would be one view from my perspective.
Another view is an ISO that is a complete running Puppy VB host. This could be extremely useful to the many newbies who want to dip the toe in the water, but, have a tendency to make mistakes using even the most elementary of HTML instructions.
My main idea is that keeping the drivers separate from the base package might allow easier upgrades from one Puppy version or kernel to another. You just download a few hundred KB driver package, use your old VBOX_base package, assuming you've kept it somewhere local, and that's that. The smaller total file size is a bonus of sorts, and having been on dialup for several years, I can also appreciate that lesser filesizes to download can be very nice, even if it might not affect me anymore.Lastly, I have to ask if the problem you are addressing is one on having bandwidth when you product a PET(s) or one where your workload and the support you give, would diminish should you change to this newer strategy.
Unfortunately, I don't have any 64-bit hardware to work with, so any efforts there would have to come from somebody else, unless Curbside Christmas come a few hours early this year! :pHopefully this helps as I, for one, would appreciate a 32bit or a 64bit "OOTB Live media Puppy VB host ISO" that could be deployed without ever having touch a DEVX, or PET or source or drivers or... Further, this ISO would have considered where I can store my VM guests. As I understand, I might have KVM considerations that could be brought into play to assist performance of the VM guest that are assigned KVM booting vs para-virtualized. This would allow a Puppy implementation that would match what we get from other VM host vendors And, it would make everything so, so easy to start into the VM realm with Puppy. Also, a 64bit version would make so much sense, because most have the resources to easily support the Puppy desktop as well as a VM guest which is actively doing something useful (this would kinda insure some user doesn't try this on a 256MB platform, and then, complain). LightHouse (both versions) come to mind as an easy desktop for newbies to work from with the resources you would need. Maybe you could work with TaZoC or produce a copy of his effort for a mainstream VM host.
Yup! This was pretty much what I meant when I asked for feedback. I can't promise much, but it doesn't hurt to think about these things.Hope this helps.
JamesBond and TaZoC (I believe) are regular users of your VB. They possess skill that us motals may not posses at this time. Might be worth a PM asking for advice or assistance.Actually, an ISO like that might not be a bad idea, but I'd be clueless where to begin. I've never built or trimmed a Puppy before, but I'd think a somewhat cut-down Puplet would be ideal, to give the VM some more breathing room on whatever hardware gets used. In any case, that would be a bit beyond my scope.
This is a very forward-thinking addition for the 32bit PCs PAE is not only fast, but also supports all RAM that can be thrown at it.TheAsterisk! wrote:Added a package for the PAE kernel (2.6.39.4) version of Slacko.
No VirtualBox version change.