Next: Scenario 2, Previous: Install, Up: How-to [Contents][Index]
First of all, initialise the default mdtx
server
(init-remove-purge (see init-remove-purge)).
Notice: this is already done by the DEBIAN package.
# mediatex adm init
You now have local access to the local meta-data history using
this url:
http://localhost/~mdtx
Add a new
PUBLISHER (see Who) user using an already existing user login (username1
).
Then, reload the Xsession or use su
to re-login in order
the
PUBLISHER belongs effectively to his new mdtx
group.
$ id uid=1000(username1)… # mediatex adm add user username1 $ su username1 $ id …groupes=…,122(mdtx),
When initialising, an out-dated mediatex
’s example support
was added.
$ mediatex ls supp
As PUBLISHER, please check the “message of the day”
a nd provide this wanted support.
$ mediatex motd Please provide theses local supports: … $ mediatex check supp ex-cd1 on /usr/share/mediatex/misc/logoP1.iso
MOTD will not complain any more about this support as it was seen recently.
Add a new support.
$ mediatex add supp ex-cd2 on /usr/share/mediatex/misc/logoP2.iso
Notice: As it works the same way, we are using here ISO files
instead of real supports (CD, USB key, …
from such /dev/sd[bc…]
peripheral files).
Add a new File.
$ mediatex add file /usr/share/mediatex/misc/logoP1.iso
Moreover, your final archive may simply be a file on your filesystem. In this case MEDIATEX can automatically access it without asking for, using the message of the day.
Notice: There is a 10 chars string you can use to put what you want in order to record a state for each support.
$ mediatex note supp ex-cd2 as what_you_want $ mediatex ls supp
Next: Scenario 2, Previous: Install, Up: How-to [Contents][Index]