Tiny Core Linux
General TC => Tiny Core on Virtual Machines => Topic started by: deodion on August 17, 2017, 12:43:34 PM
-
I have read around,
So how can I install it when I only have SCSI HDD?
I use HP ML350 G6
-
I use VMware Paravirtual SCSI Controller, looks like installed successfuly,
but when I boot, it says: failed in waitforX
Please help
-
If your VM is not compatible with Xvesa, try Xorg or Xfbdev with a vga= bootcode.
-
If your VM is not compatible with Xvesa, try Xorg or Xfbdev with a vga= bootcode.
Hello, you mean something like this:
http://forum.tinycorelinux.net/index.php?topic=17844.0
could you elaborate the updated command for that please?
That link is from 2014,
Thank you very much
-
It should work with Xorg and vmware video and vmmouse drivers. You will also want to use the open-vm-tools.tcz and open-vm-tools-desktop.tcz. This will let time sync, mouse (if you're accessing the VM via VMware player), and window resize work. For console only you wouldn't need open-vm-tools-desktop.tcz.
-
So you mean there are 4 tcz?
Is giving my hardware details will help tcz required?
-
Your hardware list isn't required, because all VMware VM's have the same virtual hardware for a given version. In onboot.lst all you should need is:
open-vm-tools-desktop.tcz
Xlibs.tcz
Xprogs.tcz
flwm_topside.tcz
wbar.tcz
The open-vm-tools-desktop.tcz.dep file will take care of all the other .tcz files.
Try:
tce-load -iwl open-vm-tools-desktopfrom the command line (while X is not running). Check to be sure that they all downloaded before you reboot.
-
If your VM is not compatible with Xvesa, try Xorg or Xfbdev with a vga= bootcode.
Just come out my mind,
If its not compatible how come I can live-boot the GUI in the first place with this Xvesa?
Thank you guys,
-
Xvesa is 32-bit only, CorePlus is 32-bit
-
tce-load -iwl open-vm-tools-desktop
pangomm.tcz MD5 sum didnot match
Xvesa is 32-bit only, CorePlus is 32-bit
thanks for the info
-
How big is your virtual disk? Can you post the output from 'fdisk -l'?
-
pangomm.tcz MD5 sum didnot match
I checked the server and there is no problem with the pangomm md5sum.
Perhaps your download was corrupted, could you remove open-vm-tools-desktop/pangomm and try again?
-
Im going forward with core 8.0 x64 (hdd install) instead,
I have been looking around
And would like to know quickly how to:
- Auto run service
- Setup static ip address and related like dns
- Ntp setup
- Ftp or similar setup to upload/download files
- Setup account and password
- Setup ssh if not installed
- Setup recommended remote desktop(for tcl with desktop)
Thank you very much for ur support,
-
For these you need to add commands to /opt/bootlocal.sh, and for accounts you need to add account related files to /opt/.filetool.lst. Read up on these in the Wiki. I can't recommend a remote desktop, and since this isn't Windows I don't know why you would need one. That's what SSH is for.
-
http://distro.ibiblio.org/tinycorelinux/concepts.html
If I want to use the "mount mode"
with Core 8.0 x64 (console only)
Is that mean I must follow this?:http://distro.ibiblio.org/tinycorelinux/install_manual.html
and there is no cfdisk in: http://distro.ibiblio.org/tinycorelinux/8.x/x86_64/tcz/
Sorry after I read the Wiki, I have not even success with this "persistence" feature,
-
It's not totally clear what you're asking, but you can use the tce-install extension to both install in a vm and on real hardware.
Persistence can be as easy as running the command "filetool.sh -b"
-
I use ISO to load, then run tc-install and choose CDROM option, it runs well,
was select from running OS, but it didnt success, maybe i forget something,
thanks anyway,
-
Once you've booted the vm from the iso, it would be better to choose the install to hd (the vm hd) option
-
I use ISO to load, then run tc-install and choose CDROM option, it runs well,
was select from running OS, but it didnt success, maybe i forget something,
thanks anyway,
Try the download from web option. ([N]et)
It'll install a clean core-only on your virtual disk (whole disk)
The "select from running OS" is for migrating a existing installation,
when you manually select the path to your local kernel.