search for: tinycorelinux

I've been using linux:TC from a USBstik in order to not break the M$ capability, as previously always happened. Since TC runs in RAM, it has many extra problems; like reinstalling all the apps and your private settings at each boot. The sample isolinux.cfg which I've been emailed by the oficianado is very unfamiliar and worrying. Where is the official syntax ? -- Without knowing if/how

Trying to build xapian+omega on tinycorelinux. I followed the install guide and get pass configure/make/make install/omindex, but when I try to run omega "P=search term", I received the following message: # ./omega.cgi 'P=small' Content-Type: text/html; charset=utf-8 Illegal instruction # Attached is the config.log . Ma...

Per http://forum.tinycorelinux.net/index.php/topic,14323.0.html I can confirm: 1) Specifying an MBR ID results in an error due to the lack of a "use" statement. 2) Specifying a non-decimal value may result in $id being undefined. I have a patch for the first however should #2 abort operation, attempt to translate 4...

...rid on this > .iso image will give me what I want. If the ISO is built that way AND the kernel/initrd know how to find the ISO. Just because it's there doesn't imply that the kernel/initrd have the logic to perform your goals. On the otherhand, also look at TinyCore Linux ( http://www.tinycorelinux.net ). > If it does, I have a second question. My USB drive actually has two > partitions, the first of which is a small FAT partition that contains > persistent data, and is visible if the drive is ever plugged into a > Windows system; and a second partition which is the boot partitio...

I've got an embedded x86 system built with Yocto, which boots from a USB flash drive. It uses a loop mount to give access to an ext3 root file system contained within a FAT16 file, which means it has persistent storage. What I want is something that boots from the flash drive, but copies everything into a large RAM disk, and runs from there, so that it doesn't touch the flash drive once

Hi, Didier Spaier wrote: > The issue is the inability of booting of a *physical* (not virtual) optical > media, like for instance a DVD or a CD, using syslinux.efi. Actually firmware cannot find any UEFI specified booting starting points in an ISO 9660 filesystem that was created with mkisofs -b and -hard-disk-boot, but without a boot image which was marked as EFI System Partition. The