Tiny Core Extensions > TCE Corepure64

QEMU for 64bit?

(1/10) > >>

flyingfishfinger:
Hi,
Looks like there was an extension request for this about 2 years ago, but the thread didn't answer whether there is one or not. The only other question about this was more about making our own extensions, and personally I don't think I have the skills for this.
Since there's a 64-bit KVM extension and they most often work together, I'm wondering if there is also a QEMU.
I got VMs working in the 32-bit version of TC, but I'd love to be able to address more RAM and install 64-bit guests in my TC64 install.
Thanks!

R

flyingfishfinger:
I managed to build it from source (not as an extension) and it works, but I don't know how to persist it through reboots. I tried adding the whole /usr directory to the backup, but apparently that's not enough. In particular, it complains about libbz2.so.1.0 not being available anymore post-boot.
Other than creating an extension, how can I persist builds of things across boots?
Thanks,

R

Also, backing up /usr seems to break Xorg. If I do that, startx is no longer available..

flyingfishfinger:
Never mind the X thing, it works.
Sorry for replying again, the edit icon seems to have disappeared.

R

Juanito:
Really the only sensible way to do this is to create an extension, but the good news is that it's not difficult  :)

You could try this:
--- Code: ---$ make
$ touch mymarker
$ sudo make install
$ sudo find / -not -type 'd' -cnewer mymarker | grep -v "\/proc\/" | grep -v "^\/sys\/" | tee files
[edit files with a text editor - it will be obvious which ones to delete]
$ sudo tar -T files --numeric-owner -zcvf myextension.tar.gz
$ mkdir /tmp/pkg
$ cp myextension.tar.gz /tmp/pkg
$ cd /tmp/pkg
$ sudo tar xf myextension.tar.gz
$ rm myextension.tar.gz
[edit out dev files from /tmp/pkg/usr/local]
$ cd /tmp
$ sudo mksquashfs pkg/ myextension.tcz
$ sudo chown tc:staff myextension.tcz
--- End code ---

Rich:
Hi flyingfishfinger
As a general rule of thumb, the only files under  /usr  that should be backed up are configuration files that you have
modified. Every time Tinycore boots it creates the  /usr  directory from scratch to allow you to recover if you messed
something up. Say a library file got altered accidentally. By backing up  /usr , every time you boot the altered library
file would replace the original. Wbar may also be affected. It has files that are dynamically updated and might not like
being changed to a previous state. The point here is, don't back up the  /usr  directory.


--- Quote ---Sorry for replying again, the edit icon seems to have disappeared.
--- End quote ---
You have about 30 minutes to go back and modify a post.

Navigation

[0] Message Index

[#] Next page