Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Josiah Carlson <jcarlson@macalester.edu>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] website
Date: Mon, 15 Jan 2001 21:01:06 -0800	[thread overview]
Message-ID: <200101160501.VAA11005@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 15 Jan 2001 20:25:15 PST." <3A63B10BBB.D2B5JCARLSON@smtp.macalester.edu>


Josiah Carlson wrote:
...
> 4. The fact that parisc-linux.org is overseen by the HP corporation, and
> that they are unwilling to change the layout and such of the web page.

Wrong on two counts: HP does not run the web site. AFAIK, HP helped
fund the parisc-linux site developement and approved it's current
layout/use of HP logo. No one said anything about future developement.
This issue is still under discussion and Mathew's input has been heard.

> Though we've got to remember
> that we're dealing with a corporation, with a structure, with
> supervisors.

Who are just people.
Some need to learn new things they don't yet know.

> If there's one thing that I've learned from working at any
> workplace, it's that supervisors sometimes know less than a 2 year old
> and sometimes are twice as stubborn.

Funny. None of my supervisors have ever fit that description.
Maybe I'm just lucky.

> not only am I not privy to the code,

Wrong again.
Source is visible at http://puffin.external.hp.com/cgi-bin/cvsview
or through CVS. Just like the linux kernel.

> but I doubt that HP would
> accept any changes if I had any. (more on that later)

You are right - HP won't. Mostly because HP doesn't "own" it.
Anyone with write access to the CVS repository can change it.
Only about 1/5th of the people with such write access are HP
employees.

> Currently there is not a whole lot of info on
> getting said machines running on the main site.

1) It's because owners of said machines haven't *written* a web page
   (or FAQ) specific to each platform.
2) Such a page would fairly quickly be stale.
   The long term goal is to have one process/kernel for all machines.
   (64- vs 32-bit kernels is the only issue that won't go away.)

> I have to document the steps
> required because someone in the future may have to do it again where I'm
> at, and it could also be posted to the parisc-linux.org site for other
> people.

Exactly. Post it here and people can find it by searching the
mail archive. (That's probably another FAQ, Alex?).

grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

  reply	other threads:[~2001-01-16  4:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06 12:26 [parisc-linux] website Matthew Wilcox
2001-01-15 15:20 ` Jane Vinet
2001-01-15 19:33   ` Stan Sieler
2001-01-15 22:24     ` Matthew Wilcox
2001-01-15 23:00       ` Josiah Carlson
2001-01-15 23:10         ` Matthew Wilcox
2001-01-16  2:25           ` Josiah Carlson
2001-01-16  5:01             ` Grant Grundler [this message]
2001-01-16  6:28               ` Josiah Carlson
2001-01-16  0:48         ` Stan Sieler
2001-01-15 22:50   ` Matthew Wilcox

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=200101160501.VAA11005@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=jcarlson@macalester.edu \
    --cc=parisc-linux@thepuffingroup.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