public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: FabF <fabian.frederick@skynet.be>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHSET 2.6.7-rc2-ff3] Kernel webconfig
Date: Thu, 29 Jul 2004 22:41:10 +0200	[thread overview]
Message-ID: <1091133670.2334.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20040729131330.13accb5a.rddunlap@osdl.org>

On Thu, 2004-07-29 at 22:13, Randy.Dunlap wrote:
> On Thu, 29 Jul 2004 19:43:30 +0200 FabF wrote:
> 
> | Randy,
> | 
> | You're absolutely right ! I forgot to talk about that mandatory point :
> | 
> | Here's httpd.conf additions :
> | 
> | ScriptAlias /cgi-bin/ "/usr/src/linux-2.6.7-rc2-ff1/"
> | 
> | <Directory "/usr/src/linux-2.6.7-rc2-ff1/">
> |     AllowOverride None
> |     Options None
> |     Order allow,deny
> |     Allow from all
> | </Directory>
> | 
> | i.e. http://localhost/cgi-bin/wconf is mapped to wconf binary which is
> | generated in linux tree root.
> | 
> | Note that we could work another way around e.g. 
> | 	-Have CGI in apache original cgi-bin path
> | 	-Place some conf file with kernel tree.
> | ... That said, it's only in proto state :)
> 
> Hi again,
> 
> I still can't get it (the web server) to work, and I've spent
> too much time on it already, so I'll have to drop it for now.
> I think it's a neat idea, though.
You might want to look at apache log see if it's not access
relevant.wwwrun has to be linux-tree authoritative (eg brutal -R 777)

Regards,
FabF

> 
> Later,
> --
> ~Randy
> 


      reply	other threads:[~2004-07-29 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07 14:46 [PATCHSET 2.6.7-rc2-ff3] Kernel webconfig FabF
2004-07-28 16:52 ` Randy.Dunlap
     [not found]   ` <1091049074.7462.1.camel@localhost.localdomain>
     [not found]     ` <20040729100225.0e0b9aef.rddunlap@osdl.org>
2004-07-29 17:43       ` FabF
2004-07-29 20:13         ` Randy.Dunlap
2004-07-29 20:41           ` FabF [this message]

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=1091133670.2334.25.camel@localhost.localdomain \
    --to=fabian.frederick@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    /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