WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v3.7rc1  (Read 6648 times)

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: tinycore_v3.7rc1
« Reply #15 on: May 19, 2011, 02:14:27 PM »
Quote
Interesting that grub4dos is 324k versus syslinux 1.3 MB.

You could remove files that are not needed in syslinux for install-tools.gz.

Leave them in in syslinux.tcz, as someone may want them.
Many people see what is. Some people see what can be, and make a difference.

Offline hiro

  • Hero Member
  • *****
  • Posts: 830
Re: tinycore_v3.7rc1
« Reply #16 on: May 19, 2011, 02:17:07 PM »
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.
Shouldn't it be possible to umount the tce and then ntfs-3g mount it? With copy2fs I see nothing against it.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: tinycore_v3.7rc1
« Reply #17 on: May 19, 2011, 02:30:37 PM »
I will fix. Thanks!
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: tinycore_v3.7rc1
« Reply #18 on: May 19, 2011, 02:33:04 PM »
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.
Shouldn't it be possible to umount the tce and then ntfs-3g mount it? With copy2fs I see nothing against it.
You may be correct. ntfs-3g.tcz extension would then only need a startup script to call rebuildfstab.
10+ Years Contributing to Linux Open Source Projects.

Offline newbody

  • Full Member
  • ***
  • Posts: 109
Re: tinycore_v3.7rc1
« Reply #19 on: May 19, 2011, 10:50:29 PM »
Thanks to all of you for caring about my naive and inquisitive questions.
I am just very selfish that demands TinyCore to be there for my sake and personal needs.

I just felt very happy that finally TCL would be as easy to use as Puppy but it still differs too much for somebody on my too challenged level of using code.

But some of your comments does indicate that maybe one could tweak it to allow me to change a menu.lst even if it is a grub4dos such and not a isolinux.

So if I get it then the whole sda3 HDD is set to read only when I do a frugal install like I have described in this thread. So there is no way to log in as root to make it read write then even temporarily?
« Last Edit: May 19, 2011, 10:52:52 PM by newbody »
Acer D250, Snow Puppy, TinyCore and on HP SR5622, Snow Puppy,

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Many people see what is. Some people see what can be, and make a difference.

Offline newbody

  • Full Member
  • ***
  • Posts: 109
Re: tinycore_v3.7rc1
« Reply #21 on: May 20, 2011, 10:12:21 AM »
I am too different. We should make a new thread if we want to go on like this :)

This is my last post on this to not further derail the thread.

I am different. I only do frugal installs on NTFS. So the link you gave will help all those that accept to touch their HDD which I am very reluctant to do. Maybe some years from now when I have another new machine. or the hdd break down and me buy another one then maybe I do Ext3 on it.
Acer D250, Snow Puppy, TinyCore and on HP SR5622, Snow Puppy,

Offline genec

  • Full Member
  • ***
  • Posts: 240
Re: tinycore_v3.7rc1
« Reply #22 on: May 21, 2011, 04:25:28 AM »
Syslinux does not support NTFS and is targeted towards Linux file systems.

Yet.  It's currently a WIP that has been seeing progress in the last month.

Offline genec

  • Full Member
  • ***
  • Posts: 240
Re: tinycore_v3.7rc1
« Reply #23 on: May 21, 2011, 04:29:11 AM »
Quote
Interesting that grub4dos is 324k versus syslinux 1.3 MB.

You could remove files that are not needed in syslinux for install-tools.gz.

Leave them in in syslinux.tcz, as someone may want them.

What about a split, ie syslinux.tcz and syslinux-base.tcz?  syslinux.tcz would dep syslinux-base.tcz while syslinux-base.tcz would only include the essentials needed to perform an install.  The extlinux/extlinux installer can handle all of the file systems (as long as they're mounted) so linux/syslinux and mtools/syslinux are not needed.  A lot of the COM32 modules would _NOT_ be required for basic install but can be very useful.

edit to add _NOT_
« Last Edit: May 25, 2011, 01:57:58 PM by genec »

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: tinycore_v3.7rc1
« Reply #24 on: May 21, 2011, 06:19:45 AM »
Quote
2. Using back arrow also means you must reselect the partition, once done Mark Active should be enabled.

It is not

Fixed! Thanks for reporting.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: tinycore_v3.7rc1
« Reply #25 on: May 21, 2011, 03:23:32 PM »
I have spent some time looking at grub4dos and I am able to have an install program create a no-partition NTFS Tiny Core & Windows system without remastering. Now I must decide on how I am going to proceed for v3.7rc2  :-\
10+ Years Contributing to Linux Open Source Projects.

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: tinycore_v3.7rc1
« Reply #26 on: May 21, 2011, 04:03:44 PM »
You need to keep the ability to install on a Linux filesystem.

I like the extlinux bootloader.

It is just a matter of whether you also offer other options.

Is there any chance of malfunctions or problems when installed on ntfs?
Many people see what is. Some people see what can be, and make a difference.

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: tinycore_v3.7rc1
« Reply #27 on: May 21, 2011, 04:07:00 PM »
With Tiny Core installed on ntfs, I am concerned about children, and even adults, using Tiny Core and destroying Windows.
Many people see what is. Some people see what can be, and make a difference.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: tinycore_v3.7rc1
« Reply #28 on: May 21, 2011, 07:24:50 PM »
You need to keep the ability to install on a Linux filesystem.

I like the extlinux bootloader.

It is just a matter of whether you also offer other options.

Is there any chance of malfunctions or problems when installed on ntfs?
It, grub4dos, fully supports ext file system, you can still partition for linux native and have a Windows and Tiny Core boot menu.
« Last Edit: May 21, 2011, 07:26:36 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: tinycore_v3.7rc1
« Reply #29 on: May 21, 2011, 07:28:21 PM »
With Tiny Core installed on ntfs, I am concerned about children, and even adults, using Tiny Core and destroying Windows.
Tiny Core can run in a single directory on NTFS.
It would be an option and certainly not a default!
It would be up to the discretion of the user.
« Last Edit: May 21, 2011, 07:30:06 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.