[parisc-linux] Question for the Faq

[parisc-linux] Question for the Faq

[Phillip D. Beal]

Hey,

I thought I'd post this to be added to the faq, as I was stumped on this
problem for a while, and I think some people might hit the same problem.

Q: The system boots up on the sTI Console but no "login:" prompt appears,
what do I do?

A: Uncomment the tty0 in /etc/inittab.

Just a thought....I spent a couple of days trying to figure out why the
console didn't completely work and I found that the tty's were commented
out under /etc/inittab.  


-- 
Phillip Beal                           ___           _               _   
Electrical and Computer Engineering   | _ ) ___ __ _| |___  _ _  ___| |_ 
pdbeal@louisville.edu                 | _ \/ -_) _` | |_ /_| ' \/ -_)  _|
http://www.bealz.net/                 |___/\___\__,_|_/__(_)_||_\___|\__|

Administrivia and a question was: [parisc-linux] Question for the Faq

[R P Herrold]

On Sat, 20 Jan 2001, Phillip D. Beal wrote:

> I thought I'd post this to be added to the faq, as I was stumped on this
> problem for a while, and I think some people might hit the same problem.

<snip good 'hint and kink type' contribution>

1. The submission got me thinking.  I just examined
http://parisc-linux.org/faq.html --- and there is no listing
of a formal role-address for an 'editor' of FAQ content.  So
it will probably be lost in the essectially unsearchable
archive at:
http://puffin.external.hp.com/mailing-lists/parisc-linux/


2, I was going to address the question of who is responsible
for making sure these gems to not get lost to the
administratative contact on the mailing list, so I checked
http://parisc-linux.org/lists.html -- no mention of the
role-address for parisc-linux-owner@thepuffingroup.com or
owner-parisc-linux@thepuffingroup.com.

Of course the first entry on that page, for the announce
archive is a dead link ...
http://parisc.thepuffingroup.com/mailing-lists/parisc-linux-announce


3. So I checked the mailer headers -- nope- the list
namagement headers are not there, of this sort from another
list:

List-Help: <http://www.suncoastlug.org/lists.html>
List-Unsubscribe:
     <mailto:majordomo@owlriver.com?body=unsubscribe%20slug>
List-Subscribe:
    <mailto:majordomo@owlriver.com?body=subscribe%20slug%20YourName>
List-Owner: <mailto:owner-slug@owlriver.com> (Human contact
    for the list)
List-Post: <mailto:slug@owlriver.com>
Sender: owner-slug@owlriver.com

Nope, no help there.


4.  In getting to the project webpages, I pasted
parisc-linux-owner@thepuffingroup.com, and editted that down
to www.thepuffingroup.com -- which went through two redirects
to get to: http://parisc-linux.org/

A one line trailer might be useful:

See the website: http://parisc-linux.org/


-------------------------------

I don't see problems so much as too much work for too few
hands, resulting in the technical side getting done first (as
it must be a priority, lest the project be Yet Anither Dead
Open Source Project [tm]).  Pollyanna would say they were
'opportunities'.

I can file a good bug report describing what I see -- I can
follow documentation with the best of them -- I stand in awe
of Alex, Grant and the rest of the coding team on the depth of
their knowledge in getting the port up and running.

So my question is: How may one contribute at an editorial and
project infrastructure level?  I wish to do so, and bet others
on the list do too.

-- Russ Herrold

Re: Administrivia and a question was: [parisc-linux] Question for theFaq

[Jane Vinet]

Thanks Russ for your comments, I will try to have these issues addressed
this week.

Jane

R P Herrold wrote:
> 
> On Sat, 20 Jan 2001, Phillip D. Beal wrote:
> 
> > I thought I'd post this to be added to the faq, as I was stumped on this
> > problem for a while, and I think some people might hit the same problem.
> 
> <snip good 'hint and kink type' contribution>
> 
> 1. The submission got me thinking.  I just examined
> http://parisc-linux.org/faq.html --- and there is no listing
> of a formal role-address for an 'editor' of FAQ content.  So
> it will probably be lost in the essectially unsearchable
> archive at:
> http://puffin.external.hp.com/mailing-lists/parisc-linux/
> 
> 2, I was going to address the question of who is responsible
> for making sure these gems to not get lost to the
> administratative contact on the mailing list, so I checked
> http://parisc-linux.org/lists.html -- no mention of the
> role-address for parisc-linux-owner@thepuffingroup.com or
> owner-parisc-linux@thepuffingroup.com.
> 
> Of course the first entry on that page, for the announce
> archive is a dead link ...
> http://parisc.thepuffingroup.com/mailing-lists/parisc-linux-announce
> 
> 3. So I checked the mailer headers -- nope- the list
> namagement headers are not there, of this sort from another
> list:
> 
> List-Help: <http://www.suncoastlug.org/lists.html>
> List-Unsubscribe:
>      <mailto:majordomo@owlriver.com?body=unsubscribe%20slug>
> List-Subscribe:
>     <mailto:majordomo@owlriver.com?body=subscribe%20slug%20YourName>
> List-Owner: <mailto:owner-slug@owlriver.com> (Human contact
>     for the list)
> List-Post: <mailto:slug@owlriver.com>
> Sender: owner-slug@owlriver.com
> 
> Nope, no help there.
> 
> 4.  In getting to the project webpages, I pasted
> parisc-linux-owner@thepuffingroup.com, and editted that down
> to www.thepuffingroup.com -- which went through two redirects
> to get to: http://parisc-linux.org/
> 
> A one line trailer might be useful:
> 
> See the website: http://parisc-linux.org/
> 
> -------------------------------
> 
> I don't see problems so much as too much work for too few
> hands, resulting in the technical side getting done first (as
> it must be a priority, lest the project be Yet Anither Dead
> Open Source Project [tm]).  Pollyanna would say they were
> 'opportunities'.
> 
> I can file a good bug report describing what I see -- I can
> follow documentation with the best of them -- I stand in awe
> of Alex, Grant and the rest of the coding team on the depth of
> their knowledge in getting the port up and running.
> 
> So my question is: How may one contribute at an editorial and
> project infrastructure level?  I wish to do so, and bet others
> on the list do too.
> 
> -- Russ Herrold
> 
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.

-- 
Jane Vinet, Director Professional Services/Canadian Operations
Linuxcare, Inc. 613.562.9260 (tel), 613.562.9700 fax
jvinet@linuxcare.com, http://www.linuxcare.com/
Linuxcare, Support for the Revolution

Re: Administrivia and a question

[Grant Grundler]

Russ,
We *need* editorial help in a serious way.
Give us some time to figure this out.  This project has had some rough
moments in the past two years and I don't think we want to rock the
boat on this issue(s) either.

Here are what I see as some of the issues:

To become a document maintainer:
o demonstrate they can be "trusted" or have existing folks vouch for them
o *user* of parisc-linux  (a vested interest in the information)
o Understand the *usage*  (not necessarily the underlying technology)

parisc-linux.org:
o clarify process for determining who should have CVS access
o find a maintainer for the document "ownership list" (Russ? :^)
o simple html interface so anyone can update web site
o timely, regular updates CVS repository -> Website

Of the above, I think parisc-linux team needs to decide on a process
first. It's been very informal up to now.  We will not give CVS access
to anyone who asks for it since it's clear that won't work and isn't
"the linux way" (to paraphrase the HP slogan).  We do need to
"scrub" the current CVS access of people who are no longer active
contributors.

I'm certain that over the course of this year, the binutils/gcc/glibc/linux
CVS repositories are going to be less active and the website will
see explosive activity. Primarily because most of the technical
developement will move out of our "sandbox" and into the "upstream"
sources. However, for user documents, I expect parisc-linux.org to
be the focal point.

Jane can help setup the details for you (and others) to contribute.
(thanks jane! You *are* doing a great job despite recent difficulties!)

R P Herrold wrote:
> 1. The submission got me thinking.  I just examined
> http://parisc-linux.org/faq.html --- and there is no listing
> of a formal role-address for an 'editor' of FAQ content.  So
> it will probably be lost in the essectially unsearchable
> archive at:

I don't agree the FAQ should become a repository for *all* "gems"
posted to parisc-linux mailing list. Our FAQ should be a starting point
for people with questions about parisc-linux. Not a database of trivia.
We have recipes and other documents the FAQ can point to provide details
about how to set things up, or workarounds for broken things.

> So my question is: How may one contribute at an editorial and
> project infrastructure level?  I wish to do so, and bet others
> on the list do too.

Agreed. Russ, is there a specific document you'd like to work on?
(eg FAQ or one of the recipes)

thanks all,
grant

Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253

Re: Administrivia and a question was: [parisc-linux] Question for the Faq

[Matt Taggart]

R P Herrold writes...

> On Sat, 20 Jan 2001, Phillip D. Beal wrote:
> 
> > I thought I'd post this to be added to the faq, as I was stumped on this
> > problem for a while, and I think some people might hit the same problem.
> 
> <snip good 'hint and kink type' contribution>
> 
> 1. The submission got me thinking.  I just examined
> http://parisc-linux.org/faq.html --- and there is no listing
> of a formal role-address for an 'editor' of FAQ content.  So
> it will probably be lost in the essectially unsearchable
> archive at:
> http://puffin.external.hp.com/mailing-lists/parisc-linux/

Dann Frazier is in the process of setting up a bug tracking system. Actually 
the BTS is setup but is dependent on the creation of mailing lists for each 
category in the BTS. We have already proposed a "website" category but perhaps 
a "FAQ" category would be useful too. Once this is done you'll have a place to 
direct feedback and contributions for all aspects of the port. Hopefully we'll 
have this setup this week.

> 2, I was going to address the question of who is responsible
> for making sure these gems to not get lost to the
> administratative contact on the mailing list,

It's informal right now but the BTS should help make it better.

> so I checked
> http://parisc-linux.org/lists.html -- no mention of the
> role-address for parisc-linux-owner@thepuffingroup.com or
> owner-parisc-linux@thepuffingroup.com.

We are going to be moving all the mailing lists to Mailman and each list will 
have an owner address once that happens.

> Of course the first entry on that page, for the announce
> archive is a dead link ...
> http://parisc.thepuffingroup.com/mailing-lists/parisc-linux-announce

That's only because no one has sent anything to the announce list in the Year 
2001 :) The move to mailman/pipermail will also fix that.

> 3. So I checked the mailer headers -- nope- the list
> namagement headers are not there, of this sort from another
> list:

Mailman wins here too.

> 4.  In getting to the project webpages, I pasted
> parisc-linux-owner@thepuffingroup.com, and editted that down
> to www.thepuffingroup.com -- which went through two redirects
> to get to: http://parisc-linux.org/
> 
> A one line trailer might be useful:
> 
> See the website: http://parisc-linux.org/

Hopefully this is something Jane can have done.

> I can file a good bug report describing what I see -- I can

Please do so when the BTS is announced.

> So my question is: How may one contribute at an editorial and
> project infrastructure level?  I wish to do so, and bet others
> on the list do too.

Grant answered this one.

HTH,

-- 
Matt Taggart        Linux Development Lab
taggart@fc.hp.com   HP Linux Systems Operation

Re: [parisc-linux] Question for the Faq

[Matt Taggart]

"Phillip D. Beal" writes...

> Hey,
> 
> I thought I'd post this to be added to the faq, as I was stumped on this
> problem for a while, and I think some people might hit the same problem.
> 
> Q: The system boots up on the sTI Console but no "login:" prompt appears,
> what do I do?
> 
> A: Uncomment the tty0 in /etc/inittab.
> 
> Just a thought....I spent a couple of days trying to figure out why the
> console didn't completely work and I found that the tty's were commented
> out under /etc/inittab.  

Yes this was mentioned on the list before but failed to make it into the FAQ.

Added.

Thanks,

-- 
Matt Taggart        Linux Development Lab
taggart@fc.hp.com   HP Linux Systems Operation