| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
This way we lose the indentation -- but special characters are escaped
automatically. Also, the commands appear in monospace font (as <pre>
blocks) this way, which I think is better.
There might be some prettier option -- but I'm too lazy to check :-) The
formatting of the whole thing is not exactly good anyways...
|
|
Even if it should turn out this is not completely obsolete (which I'm
pretty sure it is), the specific cases are already covered in the
instructions; and if any new should pop up, the guide needs to be
updated accordingly. Making the user guess just doesn't fit with such a
step-by-step guide.
|
|
|
|
|
|
I don't see any use in that; it only creates potential confusion and
other problems.
|
|
Explicitely using "./" instead of just "." is necessary only in some
very special situations... This in not one of them. So use the simpler
and more familiar form.
|
|
Instead of just vaguely stating that things can be done as user,
explicitely suggest logging in as user.
More importantly, include the chown command necessary for this actually
to work...
|
|
Put stuff in an actual user home directory, rather than stuffing it
directly in /home/
|
|
Explain that it is only necessary to create a new driver if an
appropriate one isn't in DDE already; and mention which steps are
necessary only in this case.
Also be explicit about the fact that this guide only deals with
single-file drivers.
|
|
|
|
|
|
I'm pretty sure it is neither possible nor necessary with the apt
offline setup.
|
|
This has nothing to do with DDE; and I don't see why it would be
necessary here -- the DDE stuff doesn't need any recent packages to
build AFAIK.
|
|
|
|
|
|
Again, not the right place for this.
|
|
It's really out of place here.
Add a note in the intro.
|
|
|
|
|
|
|
|
hurd/dde: New.
hurd/running/dde_guide -> hurd/dde/guide.
|
