topic title: live-persistence on ntfs partition
Posts: 76
newbody
Joined: 28 Mar 2010
#16
anticapitalista wrote:
The boot code will always set the drive that one boot from as ro
read only and that it is busy and owned by the live boot session
and the only way to work around it would be to remaster the initrd
or some other code and there change it. Would be a big job that
none are motivated to do because so few need it and it is a PITA
to do it. Takes months of hard work.
That is exactly what BitJam has done to make it possible in antiX.
Wow he has? That would be precious indeed. But BitJam when I read your
instruction to me which I ahve copied and made a text file that I placed in
the antiX dir so I easily can find it then there is nothing in that text that indicate
that it should work and all my tests up to now has failed. But sure I want to trust
you guys So I will follow your instructions but some of it is way above my head.

AFAIK I ahve already done all in the text in the other thread. AntiX do boot frugally
but the drive get owned and are owned by the boot up script.

I tested that just a few minutes ago and cited the error text and the error text is
when one boot too but too fast for to be able to copy it. It says that it fails to
do the persist.

Quote
So all you need to do is copy the linuxfs file to a place on your ntfs partition and then tell us where to find it with boot parameters. Assuming you are in the LiveCD or LiveUSB environment, you need to:

1. mount the ntfs partition (if it is not mounted already),
2. create an antiX/ directory on the top level of the ntfs partition,
3. copy /live/boot-dev/antiX/linuxfs to the antiX/ directory on the ntfs partition
/quote ends here

I try to add a screenshot to show what is in my antiX dir on NTFS. The linuxfs and homefs and rootfs are there
and properties show them are what one expect from such.

I use this menu.lst grub4dos

title antiXl-ntfs-sda2
root (hd0,1)
kernel /antiX/vmlinuz noxorg bdev=sda2 vga=791 bdir=antiX antiX=LMXD persist
initrd /antiX/initrd.gz

So the antix dir is on sda2 and it is a ntfs formatted sata or scsi ata not sure.
I make a blkid to see what they say.
sh-4.1# blkid
/dev/sda2: LABEL="ACER" UUID="xxxxxx" TYPE="ntfs"
/dev/loop0: TYPE="squashfs"
/dev/loop1: UUID="xxxxxxx" TYPE="ext3"
/dev/sda1: LABEL="PQSERVICE" UUID="xxxxxx" TYPE="ntfs"
sh-4.1#

So antix is on label ACER but AFAIK it would make no difference for it does
boot the problem is that the sda2 is owned by the"live session user"
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#17
And, yes, it did take a lot of hard work. __{{emoticon}}__ I'm hoping that other distribution will be able to use what we've done to add a lot of features to their LiveCD/USBs without having to repeat all that work.

One important thing you should know to better understand what is going on is that all the this stuff happens before the Linux system is started so it doesn't much matter whether we are booting a Debian system or some other distribution. All the code and data needed to mount your ntfs partition comes from the kernel boot parameters and a tiny little filesystem in the initrd.gz file. This is why 3 files are needed to boot Live (or Frugal): the Linux kernel, the initrd.gz, and the linuxfs file that holds the entire Linux system.

There are only two binary programs in our initrd, busybox (which can act like all the common utility programs we need) and ntfs-3g which mounts ntfs partitions read-write. There are also some scripts. The most important one is linuxrc which is the first script that runs when a LiveCD/USB (or Frugal) system boots. When that script is done it prints out:

Code: Select all

The linuxrc bootstrap is done.
======================================================================
To help me better understand your situation could you post the output of"df -Th" on your Live ntfs system and also the output of the"mount" command? Please put the output between code tags.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/faq.php?mode=bbcode#f2r1"
linktext was:"here are instructions"
====================================
for doing that.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#18
I didn't see your most recent post before I made the post above.
newbody wrote:So antix is on label ACER but AFAIK it would make no difference for it does
boot the problem is that the sda2 is owned by the"live session user"
Everything in your post looks good. It would be great if you could fire up a browser after you boot antiX so that you can log in to these forums and post the output of the commands I asked you to run with copy and paste. A screen shot would also work. If it is easy, I would also like to see the /var/log/antiX/linuxrc.log file. Perhaps someone else can walk you through the steps needed to post this stuff on the forums.

I have one more test I want you to run but we should probably wait until after I get the information I asked for above because that information might make the following test unnecessary.

Anyway, here is the next test. I want you to add the bp=2 boot code at the intial Grub or IsoLinux menu. This will create a breakpoint and cause the boot process to stop and let you enter commands. You can resume booting with either the"exit" command or by hitting <Ctrl>-d. You should get a prompt that looks like:

Code: Select all

antiX>
At that prompt, enter these two commands:

Code: Select all

antiX> mkdir /test
antiX> ntfs-3g /dev/sda2 /test
If this command works there should be no output. If it doesn't work, there should be an error message. Write that error message down on a piece of paper and post it here. If you want to continue booting then you should run these commands:

Code: Select all

antiX> umount /test
antiX> exit
Posts: 76
newbody
Joined: 28 Mar 2010
#19
I can do it in puppy now tonight it is 22.35 now and my body scream for bed
so I do for antiX tomorrow at about 10AM our local time.

Hm tags? Which tag do you want? it is not code is it.
It is terminal answers not code? Way above m,y knowledge
I got very little from that link. The reason I don't ahve tags now
is that the no script don't allow them. sorry.

df -Th I try to do it and copy result here from within frugal of puppy

Code: Select all

sh-4.1# df -Th
Filesystem    Type    Size  Used Avail Use% Mounted on
rootfs      rootfs    504M  154M  351M  31% /
/dev/sda2  fuseblk    139G   42G   97G  30% /initrd/mnt/dev_save
/dev/loop1    ext3    504M  154M  351M  31% /initrd/pup_rw
/dev/loop0
          squashfs    127M  127M     0 100% /initrd/pup_ro2
unionfs       aufs    504M  154M  351M  31% /
tmpfs        tmpfs    251M  104K  250M   1% /tmp
shmfs        tmpfs    225M     0  225M   0% /dev/shm
sh-4.1#
sda2 is the one everything boots from. WinXP too I ahve dual boot set up.
Grub4dos"chainload" to the boot.ini
What more did you ask me to tell I take a look.

Ah so I add bp=2 to the kernel line and it does not matter where on the line of code?
Fially somebody giving instruction that I trust in. I do this coming morning then.

So that test dir should turn up then when it is booted. Where do I look for it?

Ah it give the answer directly okay
quote If this command works there should be no output. If it doesn't work, there should be an error message. Write that error message down on a piece of paper and post it here /quote

okay I go to bed now
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#20
newbody wrote:df -Th I try to do it and copy result here from within frugal of puppy
That is the information I want but I need it from antiX, not Puppy. All of my instructions assumed you were able to boot antiX on your system that has the ntfs partition.

The"df" command tells me what file systems are mounted on what partitions. I want to know what my code in antiX is doing. I'm much less interested in what Puppy is doing. I want to see how we are mounting /dev/sda2. If the Type is"ntfs" that means the ntfs-3g program is failing. The bp=2 instructions should create the error message that tells us why it is failing. If it is not failing then /dev/sda2 should already be mounted read-write and the problem is elsewhere.
Ah so I add bp=2 to the kernel line and it does not matter where on the line of code?
Yes, and the position on the line does not matter. Just make sure there are spaces between different parameters and there are no spaces inside of bp=2. If you make a mistake and create a parameter that I don't understand, my program will issue a warning message.

You probably already know this, but just in case, you can add bp=2 during the boot process. You type it in at the first graphical screen. IIRC, it has a white border and a black background with stars. After you type it in you need to hit <Enter> for the boot process to continue. You don't need to edit any files.
Hm tags? Which tag do you want? it is not code is it.
It is terminal answers not code?
Yes, code tags. Terminal output should go inside of code tags because that will make the columns line up. Example:

Code: Select all

$ df -Th
Filesystem     Type    Size  Used Avail Use% Mounted on
rootfs         rootfs   31G   24G  5.8G  81% /
/dev/root      ext3     31G   24G  5.8G  81% /
rc-svcdir      tmpfs   1.0M  108K  916K  11% /lib64/rc/init.d
cgroup_root    tmpfs    10M     0   10M   0% /sys/fs/cgroup
udev           tmpfs    10M  344K  9.7M   4% /dev
shm            tmpfs   2.0G     0  2.0G   0% /dev/shm
/dev/sda7      xfs     1.1G  409M  633M  40% /usr/portage
/dev/sda8      ext3    452G  346G   83G  81% /data
so I do for antiX tomorrow at about 10AM our local time.
I'm in no rush. I don't know what time zone you're in. I'm on Mountain Time:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wwp.greenwichmeantime.com/time-zone/usa/mountain-time/"
linktext was:"http://wwp.greenwichmeantime.com/time-z ... tain-time/"
====================================
Posts: 76
newbody
Joined: 28 Mar 2010
#21
First things first!

I added the break point 2 and that failed with this error
mount: mounting /dev/sda2 on /test failed: Device or resource busy
Then I did the umount /test exit and it booted and I am in AntiX now
and like Anti suggested and trusted in the wallpaper did change to the
blue seashore that I told it to yesterday but I still are not allowed to
even see the sda2

here is the df-Th

Code: Select all

demo@antiX1:~$ df -Th
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sda2      fuseblk   139G   42G   97G  30% /live/boot-dev
/dev/loop0     squashfs  647M  647M     0 100% /live/linux
tmpfs          tmpfs     785M  1.3M  784M   1% /live/aufs-ram
/live/aufs     aufs      785M  1.3M  784M   1% /live/aufs
/live/aufs     aufs      785M  1.3M  784M   1% /bin
/live/aufs     aufs      785M  1.3M  784M   1% /boot
/live/aufs     aufs      785M  1.3M  784M   1% /etc
/live/aufs     aufs      785M  1.3M  784M   1% /sbin
/live/aufs     aufs      785M  1.3M  784M   1% /var
/live/aufs     aufs      785M  1.3M  784M   1% /lib
/live/aufs     aufs      785M  1.3M  784M   1% /opt
/live/aufs     aufs      785M  1.3M  784M   1% /root
/live/aufs     aufs      785M  1.3M  784M   1% /tmp
/live/aufs     aufs      785M  1.3M  784M   1% /usr
/live/aufs     aufs      785M  1.3M  784M   1% /media
/live/aufs     aufs      785M  1.3M  784M   1% /selinux
/live/aufs     aufs      785M  1.3M  784M   1% /srv
/dev/loop1     ext4       96M   45M   52M  47% /home
tmpfs          tmpfs     100M  368K  100M   1% /run
tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs      10M     0   10M   0% /dev
tmpfs          tmpfs     200M     0  200M   0% /run/shm
demo@antiX1:~$
And on iceweasel it does remember bookmark I made
but does not remember the startpage that I changed.
I had pointed it to a html file on the sda2

Does there exist two sda2? I mean is one of them"virtual"
and thus owned by the boot up and the other that you or
Anti described or referred to somewhere and I did not
make notes about it. Something about where one find it?

Somebody did mention that one have to reach for the drive
coming the right way? Sorry my poor memory
so it does remember something despite it says that it can not save.

And it failed to remember the passwords that I gave it.

it created a hidden file that I don't have permission to open.
I guess one have to be root to open it.
Posts: 76
newbody
Joined: 28 Mar 2010
#22
When I do Run rox /media and check the run as root
then it still say
Mounting /media/sda2
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
Mount failed

Done
There was one error.
so how do I use the fuser command.

It had enormous many options and I did not get a iota of it.
Posts: 76
newbody
Joined: 28 Mar 2010
#23
anticapitalista wrote:Ok, you have persistence working from your ntfs partition.
There is no need to go to the media. sda2 folder as you are already using it. You are in it as your antiX frugal folder is on sda2. (the windows partition).

Instead what you have to do is go to /live/boot-dev. All your windows stuff and anything else on the ntfs partition is there.
If you want to make changes while running frugal-antiX, you can save a file for example in your /home/demo folder and changes are saved so next time you use antiX-frugal it will be there is /home/demo.
If you want to access what you do in antiX eg a file when using windows, you must save it in /live/boot-dev.

Try this.

Run antiX frugal with the persist option.
When at the desktop, open the filer to /home/demo and in there create and save a file.
Use antiX control centre to change the wallpaper.
Reboot and you should boot into the new wallpaper and that file you created in /home/demo should still be there.
No need to use root (yet).

What else is on your sda2 partition? You should see them when running antiX-frugal in /live/boot-dev
This is the post by Anti that I did refer to above.

First time I read about that way to access files.
what you have to do is go to /live/boot-dev
I try to look there now Jay there I ahve a my files. I guess I ahve to tell rox that I want to use Leafpad
for to edit menu.lst using the set run action? I edit the text file that is a copy of your text BitJam
and that actually did save to the /live/boot_dev/

But I had never heard of live boot dev before so had no idea one should use that one.
All the other 75 linux distros that I have tested made use of mnt/home/ and such designations.
So sorry. had no idea. So thansk Anti for mentioning the above.

But I still ahve no idea how to use it. I will reboot now and see if it survives.

Edit. 50% success

It still give the error when booting too fast for to write down. something about
Can\t umount live persist not valid argument
and then it ask me for the passwords again so it failed to remember them
and then it boots and show the new wall paper and it remember my bookmarks
and it kept the edit I made to the BitJam.txt on the itnernal HD so that is a success.

But it says that this is the first time I use persist so would I set it up ... so failure there.

So already now it is a huge help but No Cigar as we say.

So what could be missing? my boot looks like this now in grub4dos menu.lst

Code: Select all

title antiXl-ntfs-sda2
root (hd0,1)
kernel /antiX/vmlinuz noxorg bdev=sda2 vga=791 bdir=antiX antiX=LMXD persist
initrd /antiX/initrd.gz
should it have something that indicate the /live/boot_dev/ or does that one only
come to exist after boot maybe. And one need to find a solution to the error that it
can not umount due to live persist not valid
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#24
This is looking good even though it not fully working yet. It appears that /dev/sda2 is being mounted read-write as it is supposed to which can be seen from this line in your df -Th output:

Code: Select all

/dev/sda2      fuseblk   139G   42G   97G  30% /live/boot-dev
This means the linuxrc program was able to mount your ntfs partiton read-write even though you were unable to do so at breakpoint 2.

It looks like the only problem is that the changes to the linux file system are not saved back to the /live/boot-dev/antiX/rootfs file.
All the other 75 linux distros that I have tested made use of mnt/home/ and such designations. So sorry. had no idea. So thansk Anti for mentioning the above.
The du -Th output from PuppyLinux shows that your /dev/sda2 is mounted under /initrd/mnt. LivCD/USBs need to keep some things out of the normal Linux file system. Puppy is putting them under /initrd, we put them under /live. The entire Linux file system is contained under /live at least twice. If you tried to put this stuff under /mnt then it would try to contain itself which is impossible. To some extent the existence of the /live directory and what it contains is the major difference between a Live system and a full install. The other difference is the linuxrc script that runs and creates everything under /live.

Anyway, back to your problem with persistence.
it created a hidden file that I don't have permission to open.
I guess one have to be root to open it.
I won't be able to understand what you are saying here unless you tell me the full path to the file and the name of the file. Giving me some hint about *when* this file gets created would also help.

The problem you have seems to be that your changes are not being saved to the rootfs file which is why things like the new passwords get forgotten. If your bookmarks are saved that means the home directory is being saved in the homefs file. The best way to track down the rootfs error is to run the persist-save program which is supposed to save your changes to the rootfs file.

You can either run"persist-save" from the command line or navigate the menus:

Applications --> Other --> RemasterCC

and then select"Save root peristence". If this program is not run then your changes will not be saved. You are supposed to be able to select to have it always gets run at shutdown. That is the automatic setting. You could instead choose the semi-automatic setting where you get asked if you want to save your changes on shutdown. If you set it for manual then you will have to manually run the persist-save program as explained above or your changes won't be saved.

It might be best to run the program from the command line to ensure you see the error messages although all error messages should show up in /var/log/antiX/persist-save.log. We are playing the same game as before where either the program works or you get an error message exlaining why it didn't work.
It still give the error when booting too fast for to write down. something about
Can\t umount live persist not valid argument
It would have helped if you told us at least *when* this error occurs. Does it occur before or after it says:

Code: Select all

he linuxrc bootstrap is done
======================================================================
?
If it happens before this is printed, you have several options:
  1. You could use the wait=10 boot parameter to have the system wait 10 seconds before going on to the next things.
  2. You could use the bp=9 boot code that will drop you to a shell when the linuxrc program is almost done. This too will pause the scrolling of the display. Use the"exit" command or <Ctrl>-d to continue booting.
  3. You could look at the file /var/log/antiX/linuxrc.log after the system boots which may (but may not) contain the error message.
The point of error messages is to help us track down what the problem is. Even if you can't catch the actually error message as it flies by, it helps a lot if you can give us an idea of *when* the error is occurring. Most (but not all) error messages for my programs will show up in one of the log files under /var/log/antiX/.
should it [the Grub entry] have something that indicate the /live/boot_dev/ or does that one only come to exist after boot maybe.
The user does not have control over the /live directory structure. As far as booting is concerned, the only information we need is how to find the boot device and how to find the linuxfs file on the boot device. Since your linuxfs file is in the standard location on the boot device (/antiX/linuxfs) all you need to tell us is how to find the boot device. You already do this with the bdev=sda2 entry. BW I don't think you need bdir=antiX because that should be the default value.
Posts: 76
newbody
Joined: 28 Mar 2010
#25
I am in puppy now for to be able to easily edit the picture my mobile camera took
of the bp=9 halted boot process.

To your question that error happen before the linuxrc is finished see blurred picture
I will now reboot into antix and reread your post and try to answer your questions.

I did the Menu Applications remaster as you described and saved a screenshot of
the errror message.

So most likely??? the rootfs file maybe is bad due to me not good at following instructions.

Can I make it again now when I ahve come this far. Anti described how to but
I have already forgotten all about it. I try to find that text again?

the error show up as you told me also in that persist-save.log
--------------------------------------------------------------------
NTFS signature is missing.
Failed to mount '/dev/loop2': Invalid argument
The device '/dev/loop2' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
/usr/local/lib/antiX/antiX-common.sh: line 562: g[f]/live/persist-root[/]t_ac: No such file or directory
persist-save [0;31merror[0;39m:

2012-03-08 13:40:23: [0;35mCleaning up ...[0;39m
2012-03-08 13:40:23: Removing lockfile [0;32m/live/config/locked[0;39m
When I run from Run being root then it show same error message as in the first picture
So what would be the most logical thing to do now? Give the NTFS drive a signature?
Would that not destroy it for WinXP later? Why does the OS need a NTFS signature
whatever that is?

Did not Anti tell me that I could copy a rootfs file from somewhere? I need to find that instruction again
I have found it and tried to follow the instruction but felt unsure of if Idid make it right.
I reboot now and see if rootfs works better now
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#26
Thank you for the error messages!

I agree the problem is most likely a bad rootfs file. My program did not deal with this error condition gracefully so I will fix that to make it more clear.

You can check the rootfs file with these commands. If you change the directory name you should be able to run them in antiX or in Puppy. First, either log-in to a terminal as root or change to root with the"su" command. It will ask you for the *root* password. Then:

Code: Select all

# cd /live/boot-dev/antiX
# script
# ls -l rootfs
# mkdir /mnt/rootfs
# mount -o loop rootfs /mnt/rootfs
I believe you will get an error message when you try to do this. The next step is to create a new rootfs file. The seek number sets the size. The 2000 will give you a 2 gig rootfs which is what I would suggest.

Code: Select all

# rm rootfs
# dd if=/dev/zero of=rootfs bs=1M count=0 seek=2000
# mkfs.ext2 -q -m 0 -F rootfs
Now you should check it again with:

Code: Select all

# mount -o loop rootfs /mnt/rootfs
# df | grep /mnt/rootfs
# umount /mnt/rootfs
Thank you for putting up with this process. I hope we will be able to make things much easier for those who follow in your footsteps.

The"script" command at the very beginning will log everything you enter and all the output in a file called"typescript". Use the"exit" command when you are done to turn this off.
Posts: 76
newbody
Joined: 28 Mar 2010
#27
Thanks. It looked good and when I booted then it seems to mount rootfs without
the error that I made a picture of but when I do this in terminal as root then it says

Code: Select all

root@antiX1:/live/boot-dev/antiX# mount -o loop rootfs /mnt/rootfs
mount: mount point /mnt/rootfs does not exist
root@antiX1:/live/boot-dev/antiX#


I have to find the command that showed the other error. What was it?
Run rox /media then it give same error but when I run this
persist-save then it works. So that is a huge progress.

I test again if I can edit things on the live boot-dev Jay that works too.

The rox /media what is that about then? what could that be about?
10.00PM here now so I tutn in within one hour most likely.
BitJam much thanks for being this patient with an old fool like me.
I am incredibly bad at following instructions. But I want Linux to work
so sometimes I don\t want to give up.

Now I will go and set the language to Norwegian or to do the setxkbmap se
and see if that survive a reboot. Maybe I need to do the homefs like you
described I did the rootfs? Does home take care of keyboard?

anyway Much appreciated you cared.

Can I ask. If I want to run as Puppy do. To boot as root and not boot as demo?

What boot code do I use then? Can I use something like this?
noprompt autologin username=root password=root on the kernel line?
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#28
newbody wrote:

Code: Select all

root@antiX1:/live/boot-dev/antiX# mount -o loop rootfs /mnt/rootfs
mount: mount point /mnt/rootfs does not exist
You just have to make the directory first:

Code: Select all

# mkdir /mnt/rootfs
# mount -o loop rootfs /mnt/rootfs
# ls /mnt/rootfs
The ls command should show at least a"etc" directory. You should run"umount /mnt/rootfs" when you are done.
I have to find the command that showed the other error. What was it?
I need more hints.

The important thing is to make sure the persist-save program runs. If it does, you can repeat the steps above (omitting the mkdir) and you should see a lot more when you ls.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#29
newbody wrote:BitJam much thanks for being this patient with an old fool like me.
I am incredibly bad at following instructions. But I want Linux to work so sometimes I don\t want to give up.
The fault was 100% mine. If all my programs were working properly then you would not have run into any rootfs error. I thank you for your help and your persistence.
Now I will go and set the language to Norwegian or to do the setxkbmap se
and see if that survive a reboot.
I *think* you might need to do this before enabling persistence. Just use the lang=no boot code. Anti can tell you for sure. If lang=no does not work when persistence is enabled then delete the file /etc/live/protect/persist and try again. You will have to delete that file as root.
Maybe I need to do the homefs like you described I did the rootfs?
No. I don't think so. The fact that your bookmarks were saved shows that homefs is working. This is also seen in this line from you df -Th:

Code: Select all

/dev/loop1     ext4       96M   45M   52M  47% /home
Unfortunately, your homefs is way too small and you are going to run out of space on it very soon.
Does home take care of keyboard?
No.
If I want to run as Puppy do. To boot as root and not boot as demo?
Yes you can and no you shouldn't. There is no boot code to do this, instead you need to edit the /etc/slim.conf file and change the default_user from"demo" to"root". You should be able to do this from the antiX Control Center. I suggest that you do not make this change.
Posts: 76
newbody
Joined: 28 Mar 2010
#30
Swedish seems to work now using the code lang=se so that is cool.
Seems I did not need to delete the persist file for that.

What was that Run /mnt/media not allowing me to see sda2?

Did Anti or you forgot that I should look at live boot-dev instead?
I did not even know such directories could exist. I had not happen
to meet those terms before.

Okay about the root thing. Yes I know that most Linux Devs don't want
us to be root. Future will tell how I decide on it.

Now a questions you don't have to answer. All the other derivates or forks
or pure Debian OS existing can they learn from you how to do this then
as long as you get recognitions with your name in the code?

Sickgut over at Puppy him trying to make a 100% compatible Debian OS
most likely want to learn it too.

As I remember you told me the file that makes it possible to save on NTFS
is rather small even if making it where rather difficult which explains nobody
has done it before on Mepis varieties??? Okay Knopper has done it for Knoppix
but that is not 100% Debian maybe?

So congratulations to having accomplish this. I've been waiting sine AntiX 8.5
for to be able to do this. So happy you made it possible.
Most things seems to work now.

I only lack Adobe Flashplayer so I need to learn how to get that going.
Now I go to bed.