Hi All,
I have printed and studied many 'remastering guidance, also I have searched in the internet (the trouble is, I found much guidances - but there are some differences I do not understand - options that I not found in the manpage - errors known, where I not understand what is the solution - and I found posts in this or other places for same questions which are older and have no answer).
I would like to thank you in advance for your effort.

--options I not found in the manpage--
Code:
mount -rw /dev/hda1 /mnt/hda1
I found the option '-rw' in all guidances.
In the manpage I found :
-r Mount the file system read-only. A synonym is -o ro.
-w Mount the file system read/write. This is the default. A synonym
is -o rw.

So I don't understand why '-rw' should be used when '-w' is the oppsite of '-r'.
(is interesting for learning something - even though it seems to work correct)

--differences--
most guidances told to make directories
Code:
mkdir /mnt/hda1/knx
mkdir -p /mnt/hda1/knx/master/KNOPPIX
mkdir -p /mnt/hda1/knx/source/KNOPPIX
one told to make
Code:
mkdir -p /mnt/hda1/knxmaster/KNOPPIX
mkdir -p /mnt/hda1/knxsource/KNOPPIX
question:
has this difference any effect of the further remastering process?
(of course used the made directories in the following statements)
Is there a difference because some used statements/scripts
only exept one of these directory structures?
For example in the second case the swapfile is made
/mndt/hda1 (changed in the directory before creating)

because I yesterday in the evening had stoped remastering
with reason of huge problems now I start remastering from Knoppix CD 3.51
with hard disk where are the Knoppix-Files already copied on
so after starting Knoppix from CD - mount -rw /dev/hda1 mnt/hda1
- starting the swapfile new -
I worked on with setup the envoronment for chroot and chroot
I thing this should be possible ???

--known errors with chroot and differences in sequential order and options --
1st version
Code:
mount --bind /dev /mnt/hda1 /knx/source/KNOPPIX
chroot /mnt/hda1/knx/source/KNOPPIX
- message seems to be known:
see http://www.knoppixforum.de/knoppix-f...dvd-5-3-1.html
http://www.knoppixforum.de/knoppix-f...3-1-zu-cd.html
- message for 'mount --bind /dev /mnt/sda4/knx/source/KNOPPIX/dev'
mount: wrong fs type, bad option, bad superblock on /dev,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so (here I have not seen anything which gives me an idea)
- info to this message:
The manpage of mount in knoppix version 5.3.1 says
--bind Remount a subtree somewhere else (so that its contents are
available in both places). See above.
-> bind is a known option so I think the version 5.3.1 should support
this option?

- my understanding: option bind is mainly needed for already mounted
subtrees???

2nd version
Code:
chroot /mnt/hda1/knx/source/KNOPPIX  
mount /dev/hda1 /mnt/hda1
-option why is there no bind-option used?
is it because the /dev is mouted before
and /dev/hda1 should not be mounted before?

questions:
Is the sequential order of mount and chroot important?

information found to this question:
http://www.knoppixforum.de/knoppix-f....html#post9133 from Schock dated 'Montag, 3. Juli 2006, 18:13' in German language
he says 'Hattenhauer' says in his book 'Linux-Livesysteme' at page S. 355
for the error
to chroot-environment with <Strg> <D>
and after that to do:
mount -o remount,dev,suid /dev/hda1 /mnt/hda1
chroot ...

eventually for another error but you see that mount should be
done outside chroot??? - is this correct?????

why is mount --bind /dev ... in the HowTo
listet under
'14. setup the environment for chroot'
I think this is not visible while im in the chroot environment?


Has anyone an idea of the reason of my error messages:
if I start chroot befor mount it works without any error
after that: mount /devhda1 /mnt/hda1
message: mount point /mnt/hda1 does not exist
if I only type mount for getting information
message: /dev on / type nore (rw,bind)



When I then stop chroot with ctrl+D
mount for checking wheather hda1 ist locked
message:
/dev/hda1 /media/hda1 type ext3 (rw,data=ordered)

---> is there a problem with type 'ext3'?
---> what means 'data=ordered' - where comes it from -
is that normal vor ext3? is it a problem for remastering?

some time I don't exactly can say at what point - I got the message:
mount: /dev/hda1 alrady mounted or /mnt/hda1 busy
mount: according to mtab, /dev/hda1 is mounted on /media/hda1
I think this was before I disconnected hda1 on the desktop (not Root Shell)
using the context menue of hda1
- is this essential if I have to continue remastering, after I have broken
the process and shut down the system as described above.

I think this will be enough for tonight. I'm very hopeful for helping ideas.

Greats

Your very bothered idealist.
100 % where very good - I know I will never get it -
but if you not start with searching 100 % - how
much you are able to get?
[/code]