Tiny Core Base > Release Candidate Testing
tinycore_v3.7rc1
Guy:
Some bugs in the installer
1. If Windows is already installed, and a user sets up a partition for Tiny Core, and makes it Active, before running the installer. Then runs the installer without selecting "Mark Partition Active (bootable)." The installer will not set up a menu for selecting Windows.
2. When running the installer. If a user does not select "Mark Partition Active (bootable)," but clicks the forward arrow. Then decides to change it, and clicks the back arrow. The option to "Mark Partition Active (bootable)" is no longer available.
roberts:
--- Quote from: newbody on May 19, 2011, 02:11:20 PM ---RobertS
interesting that it has ntfs now. Sadly I am computer challenged. Does this mean that it now will boot using this menu.lst on ntfs hdd?
snip...
--- End quote ---
I see several issues with regard to running Tiny Core entirely within NTFS.
Your posts suggest that you, or the remaster, is using grub4dos. Currently we use syslinux.
The reason for this is that grub4dos does not support ext4. grub4dos is primarily targeted towards supporting NTFS and DOS. Syslinux does not support NTFS and is targeted towards Linux file systems.
Let's say that you try to use the existing grub4dos with v3.7rc1 tinycore.gz. Since only the kernel module is in the base, you will only get read access to NTFS. While you boot loader grub4dos will read the kernel, bzImage, and the core, tinycore.gz, you should be able to boot Tiny Core. Tiny Core will seek the tce/ directory which will be read-only,
To get read write you need the ntfs-3g.tcz extension. But as an extension it is too late to change read-only to read-write. Even if you move ntfs-3g.tcz to be first in the onboot.lst and even if you flagged it as copy-to-fs (ram), and even if, a startup script were to be created which called rebuildfstab to update entry to rw, and callled mount -o remount,rw, I don't believe it would work.
I am surmising here as I have little access to NTFS to throughly test. Perhaps those with easy access to test will. Perhaps changing ntfs-3g.tcz into ntfs-3g.gz and specify that the boot loader, grub4dos, load ntfs-3g.gz? Can grub4dos even load multiple initialramfs?
The reason to include the kernel ntfs (read-only) module was to allow current Windows net access together with starter packs (being a single file) together with loadpack GUI as easy way to get started on a Tiny Core system with no net access.
roberts:
--- Quote from: Guy on May 19, 2011, 04:37:50 PM ---Some bugs in the installer
1. If Windows is already installed, and a user sets up a partition for Tiny Core, and makes it Active, before running the installer. Then runs the installer without selecting "Mark Partition Active (bootable)." The installer will not set up a menu for selecting Windows.
2. When running the installer. If a user does not select "Mark Partition Active (bootable)," but clicks the forward arrow. Then decides to change it, and clicks the back arrow. The option to "Mark Partition Active (bootable)" is no longer available.
--- End quote ---
1. By design, I don't assume to create a menu, unless Mark Partition Active is selected.
2. Using back arrow also means you must reselect the partition, once done Mark Active should be enabled.
roberts:
Interesting that grub4dos is 324k versus syslinux 1.3 MB.
Now that is food for thought.
Guy:
--- Quote ---2. Using back arrow also means you must reselect the partition, once done Mark Active should be enabled.
--- End quote ---
It is not
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version