dCore Import Debian Packages to Mountable SCE extensions > dCore X86

dCore and Grub4DOS on a NTFS partition...

(1/6) > >>

sbaguz:
Dear all,

recently I managed to build a beautiful customized dCore system, I have spread it over several USB keys and PCs and finally I've been able to install grub4DOS on my company laptop without even touching the Windows MBR to have dCore always with me even at work...
Now the problem: the PC have a Windows 7 system installed on a NTFS partition.
This partition, where the tce folder reside, is mounted read-only during dCore boot and I can't use ntfs-3g afterwards to be able to save my changes while shutting down.
I have already tried the manual procedure (cat core.gz ntfs-3g.gz > mycore.gz) suggested in http://forum.tinycorelinux.net/index.php?topic=6246.0 without success (it seems the system doesn't load any extension).
Since I have no more time to try to port the script provided in that thread to dCore and even to well understand it (e.g.: the sed part is quite frightening...  :o ) do you have any suggestion/workaround to make me reach my goal?

Thanks in advance.

Jason W:
Though dCore supports *.gz initrd files as a part of a remaster in /tmp/builtin, remasters of the main initrd are a last resort to me as that inhibits keeping with updates.  If you have an ntfs-3g.gz, then you can place it the chosen /boot directory and specify it as another initrd in the boot loader, below is what I used with grub2 to have ntfs-3g available as if it were in the main dCore-*.gz image, and hopefully similar works with grub4dos:


--- Code: ---
insmod ext2
set root='(hd0,msdos7)'
linux /boot/vmlinuz-wily quiet max_loop=256 tce=sda7/tceimport-wily showapps user=jason nozswap desktop=startlxde
initrd  /boot/dCore-wily.gz /boot/ntfs-3g.gz


--- End code ---

In fact, I a have created an sce2gz tool that is available as an extension that can create a *.gz out of an SCE in the SCE directory or one of one's choosing.  Works much like sce-load.  This is mainly to support ntfs-3g and perhaps wireless, but should work in any case.  Startup scripts in the extra *.gz are processed as usual and added to the list of installed packages.  It is assumed sce2gz is used to create the extra initrd's, convert raw Debian packages at your own risk. 

Please try booting with the extra initrd and let me know how it goes. 

sbaguz:
Hi Jason,

thanks for the quick answer.
Everything went fine... apparently.
I easily created the ntfs-3g.gz, I added it to the menu.lst of grub4dos (by the way: it works exactly like grub-legacy), the boot process gave no problems and the ntfs-3g package was up and running after the boot... but the NTFS disk was loaded read-only as before!
To be honest, I already had this problem even with the ntfs-3g.sce in sceboot.lst: I always had to manually load NTFS partitions when needed with the ntfs-3g command, but it was not so different from using the Mount Tool, so I was not so much worried about it. Now the situation is obviously different.
What do you suggest?
Another (probably stupid) question: since dCore should load everything in RAM, why I can't simply manually umount the partition where tce folder resides (the device is busy) and then mount it again with ntfs-3g command?

Misalf:
Extensions are loop mounted to /tmp/tcloop.
if a file  /etc/sysconfig/tcedir/copy2fs.flg  is present at boot time, everything is copied to RAM and the boot device can be un-mounted.

sbaguz:
Thanks for the hint Misalf: as said, it was a stupid question... now I understand, nevertheless I would like to avoid the Copy Mode, but I will consider it as the last resort if we weren't able to make ntfs-3g work as expected.  ;)

Navigation

[0] Message Index

[#] Next page