public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Karel Kulhavý" <clock@twibright.com>
To: Michael Still <mikal@stillhq.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make htmldocs
Date: Tue, 14 Oct 2003 16:41:24 +0200	[thread overview]
Message-ID: <20031014164124.A2600@beton.cybernet.src> (raw)
In-Reply-To: <Pine.LNX.4.44.0310142106220.16081-100000@diskbox.stillhq.com>; from mikal@stillhq.com on Tue, Oct 14, 2003 at 09:16:39PM +1000

> http://freshmeat.net/projects/docbook-utils/

Tried this. It wants jade. Installed jade. jade is a X Window
System appliaction. During compilation of
docbook-utils-0.6.13 I got a message:
Gtk-WARNING **: cannot open display:

I am doing this on a router where I have no X server. How can
I view Linux Kernel HTML documentation on a router where I have got only
an ssh access and no X server?

I suggest considering replacing the DocBook bloatware for something
more sane in the kernel tree. You could maybe generate the html
docs yourself and simply put them somewhere into the Documentation/
directory into the kernel sources. Or at least on the web, but then
the people offline couldn't even read the instruction manual for their
kernel.

> Dude, he was just trying to ask what distro you use, in order to help you 
> out. Of course how you install it changes based on the distro you're 
> using.

I don't use any distro. I have compiled my operating system from scratch.

> 
> > If there doesn't exist any distribution-idependent installation process
> > for "DocBook stylesheets", then "DocBook stylesheets" is not portable,
> > and transitively, "Linux Kernel" is not portable.
> 
> Given than most Linux distros are open source themselves, and that the 

Your talk about distros is OT. I don't have any distro. I have built my
system from the source. I just
want to know how to build the kernel HTML docs.

I have built Gnome, Qt, Xfree86, gcc, glibc, j2sdk1.4.1 and mozille from
sources, but haven't used dpkg or rpm yet.

If Linux Kernel is package-only, please tell me. I will do a cat /dev/zero >
/dev/hda then and move on to OBSD then.

> web? For example, a bunch of the kernel API man pages can be found at:
> 
> http://www.stillhq.com/linux/mandocs/
> 
> > Could you please
> > recommend me some other open-source free operating system where I don't
> > need to have a "distribution" to be even able to read it's enclosed
> > documentation? I have been using Linux Kernel for 7 years but can't anymore
> > because I am unable to read it's manual.
> 
> FreeBSD? OpenBSD? NetBSD? Minix? I recommend you look through the list at 
> http://mirror.aarnet.edu.au if you really feel the urge to move on.
> 
> Cheers,
> Mikal
> 
> -- 
> 
> Michael Still (mikal@stillhq.com) | "All my life I've had one dream,
> http://www.stillhq.com            |  to achieve my many goals"
> UTC + 10                          |    -- Homer Simpson
> 

  parent reply	other threads:[~2003-10-14 14:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 16:55 make htmldocs Karel Kulhavý
2003-10-14  9:46 ` Erik Mouw
2003-10-14 10:09   ` Karel Kulhavý
2003-10-14 10:48     ` Clemens Schwaighofer
2003-10-14 11:04     ` Erik Mouw
2003-10-14 12:57       ` Karel Kulhavý
2003-10-14 11:16     ` Michael Still
2003-10-14 13:44       ` Karel Kulhavý
     [not found]         ` <200310140842.57178.shawnfu@willden.org>
2003-10-14 15:06           ` make htmldocs -- docbook-utils Karel Kulhavý
2003-10-14 19:50         ` make htmldocs Michael Still
2003-10-14 14:09       ` Karel Kulhavý
2003-10-15 19:37         ` Thomas Horsten
2003-10-16 19:26           ` Pavel Machek
2003-10-14 14:41       ` Karel Kulhavý [this message]
2003-10-14 19:55         ` Michael Still
2003-10-14 21:53         ` Michael Still
2003-10-14 12:51     ` Pavel Machek
2003-10-14 17:29     ` Guy
2003-10-14 17:52     ` Sam Ravnborg
2003-10-15 19:30     ` Thomas Horsten
2003-10-15 11:01 ` Jean Charles Delepine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031014164124.A2600@beton.cybernet.src \
    --to=clock@twibright.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikal@stillhq.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox