Re: [Leaf-devel] TS-req-HowTo / How Do I Request Help?

2002-02-10 Thread David Douthitt

On 2/10/02 at 2:22 PM, Ray Olszewski <[EMAIL PROTECTED]> wrote:

> OK. My suggestion is that we need something short and
> sweet, something that is not comprehensive (by a long
> shot) but that contains a short list of items that covers
> the most common things we need to know.
> 
> It's part of a general ambition I have to put the F back
> in FAQ (by which I mean that FAQs grow over time, but old
> Q&As that no longer fit the "frequently" part of the FAQ
> term never get culled out).
> 
> Here's my first-draft suggestion for a new item:
> 
> ---begin sample---
> 
> Q. If I want help troubleshooting a connectivity failure
> with my LEAF router, what information you you need from me?

Maybe I'm out on a limb - but I keep thinking of this (which does the
same thing as your answer

---begin code---
#!/bin/sh

banner () {
echo
echo "== $1 =="
}

banner Release
cat /etc/*release

banner "Linux Kernel"
uname -a

banner "System Logs"
tail -n 30 /var/log/messages

banner "Networking"
if which ip ; then
   ip addr show
   ip route show
else
   route
   ifconfig -a
fi

banner "Kernel Modules"
lsmod

banner "Firewall"
ipchains -Lvn
---end code---

I noticed that FreeSCO (which seems to have a STRONG following) uses
this method - they have a program called "report" ...only problem is
there is no "sanitizing" of information here...
--
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] TS-req-HowTo / How Do I Request Help?

2002-02-10 Thread Mike Noyes

At 2002-02-10 14:22 -0800, Ray Olszewski wrote:
>OK. My suggestion is that we need something short and sweet, something
>that is not comprehensive (by a long shot) but that contains a short list
>of items that covers the most common things we need to know.
>
>It's part of a general ambition I have to put the F back in FAQ (by which
>I mean that FAQs grow over time, but old Q&As that no longer fit the
>"frequently" part of the FAQ term never get culled out).

Ray,
In keeping with your suggestion of short and sweet FAQs. I propose the net 
etiquette information move into "Mailing List Questions Answered" (docid 
1465). Replacement of Appendix A with a link to:
http://www.expita.com/nomime.html

Create a new FAQ "Diagnostic Commands Explained" that contains most of the 
information in Sec 4.1. This should complement Lynn's "LEAF Command FAQ".

--
Mike Noyes <[EMAIL PROTECTED]>
http://sourceforge.net/users/mhnoyes/
http://leaf.sourceforge.net/content.php?menu=1000&page_id=4


___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] TS-req-HowTo / How Do I Request Help?

2002-02-10 Thread Ray Olszewski

OK. My suggestion is that we need something short and sweet, something that
is not comprehensive (by a long shot) but that contains a short list of
items that covers the most common things we need to know. 

It's part of a general ambition I have to put the F back in FAQ (by which I
mean that FAQs grow over time, but old Q&As that no longer fit the
"frequently" part of the FAQ term never get culled out).

Here's my first-draft suggestion for a new item:

---begin sample---

Q. If I want help troubleshooting a connectivity failure with my LEAF
router, what information you you need from me?

A. The exact information needed will vary by what trouble needs shooting. As
a general matter, exact quoting of error messages, log entries, command
output, and such, is better than your trying to paraphrase or summarize them.

When asking for general help with routing or firewalling questions, you
should ALWAYS include this information:

the exact name of the LEAF distribution and version
you are running
the exact kernel version you are running
the complete, exact output of "ip addr show"
the complete, exact output of "netstat -nr"
the exact wording of any ping failure responses

Depending on the specific problem, you may want to include some or all of
the following:

the exact output of "lsmod"  [typically for NIC-related problems]
the exact output of "ipchains -nvL" [typically for firewall-
related problems]
[add here whatever the corresponding one is to check port-
forwarding rules in place]
any messages from dhclient in your logs [typically for setup
of DHCP-dynamic external connections]
any messages from ppp or pppoe in your logs [typically for
setup of PPPoE-dynamic external connections]

This is not an exhaustive list; we've tried here to cover only the most
common sorts of troubleshooting problems that arise. If you have a less
common problem, or if you use an ISP that does something unusual, you may
need to provide other specifics to get good help. 

---end sample---
 

At 02:10 PM 2/10/02 -0800, Mike Noyes wrote:
>Ray & Lynn,
>Let's open this up to the rest of the developers for suggestions. Please 
>restate your suggestions, so we can get an idea of what everyone would like 
>to see in the revised document.
>
>The document under consideration for revision is:
>
>How do I request help?
>http://sourceforge.net/docman/display_doc.php?docid=1891&group_id=13751
>
>CVS doc/docmanager/docid_1891.html
>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/doc/docmanager/


--
"Never tell me the odds!"---
Ray Olszewski-- Han Solo
Palo Alto, CA[EMAIL PROTECTED]



___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] TS-req-HowTo / How Do I Request Help?

2002-02-10 Thread Mike Noyes

Ray & Lynn,
Let's open this up to the rest of the developers for suggestions. Please 
restate your suggestions, so we can get an idea of what everyone would like 
to see in the revised document.

The document under consideration for revision is:

How do I request help?
http://sourceforge.net/docman/display_doc.php?docid=1891&group_id=13751

CVS doc/docmanager/docid_1891.html
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/doc/docmanager/

--
Mike Noyes <[EMAIL PROTECTED]>
http://sourceforge.net/users/mhnoyes/
http://leaf.sourceforge.net/content.php?menu=1000&page_id=4


___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Booting Flash on PCMCIA vs. IDE

2002-02-10 Thread Mike Noyes

At 2002-02-10 10:21 -0500, Johan Ugander wrote:
>>I was unable to locate anything in the 3115b manual that mentions 
>>CompactFlash (CF) or true IDE mode. I don't think CF devices are 
>>supported as a boot medium.
>>
>>CF 1.4 specifications.
>>http://www.compactflash.org/cfspc1_4.pdf
>
>Section 6-1 - 6-8 discuss PCMCIA-ATA. Like I said above, I'm pretty much 
>past this step. It's booting. No problems. I am now encountering a linux 
>and lrp specific problem -- the one with pcinitrd and integrating the 
>pcmcia boot initrd image.

Johan,
I stand corrected. I didn't read chapter 6. I apologize for wasting your time.

--
Mike Noyes <[EMAIL PROTECTED]>
http://sourceforge.net/users/mhnoyes/
http://leaf.sourceforge.net/content.php?menu=1000&page_id=4


___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Booting Flash on PCMCIA vs. IDE

2002-02-10 Thread Johan Ugander


>Johan Ugander, 2002-02-09 15:15 -0500
>>Oh, and by the way, my pc/104 pcmcia bridge is the tri-m aaeon pcm3115b
>>http://www.tri-m.com/products/aaeon/pcm3115b.html
>>http://www.tri-m.com/products/aaeon/manual/pcm3115b.pdf
>
>
>After reading the 3115b manual pages 4-7 through 4-10, I believe 
>you're going to need the TrueFFS kernel patch from M-System [1] to 
>enable booting from the flash drive. The other option is the MTD 
>driver from the site [2] I mentioned before.
>
>[1] http://google.com/search?hl=en&q=trueffs+linux
>[2] http://www.linux-mtd.infradead.org/


Hmm, the way I see things, those are all steps to get it booting. . . 
I already have it 'booting', that is to say I already have it reading 
from the pcmcia slot and getting as far as the package installation, 
at which point it fails. I can boot windows 98 off of a flash disk 
withou any problems what so ever. This isn't my hang-up...at least 
I'm pretty sure my problems lie elsewhere.

Right now I believe my best allocation of efforts would be to try and 
figure out the 'pcinitrd' I mentioned, but I am unsure of how to 
integrate it into the leaf/lrp booting sequence.

>I was unable to locate anything in the 3115b manual that mentions 
>CompactFlash (CF) or true IDE mode. I don't think CF devices are 
>supported as a boot medium.
>
>CF 1.4 specifications.
>http://www.compactflash.org/cfspc1_4.pdf

Section 6-1 - 6-8 discuss PCMCIA-ATA. Like I said above, I'm pretty 
much past this step. It's booting. No problems. I am now encountering 
a linux and lrp specific problem -- the one with pcinitrd and 
integrating the pcmcia boot initrd image.

I read the documentation in the lrp dev. guide, which was quite 
useful in understand some of the working of the boot process (page 
25). (bravo dave!). Now I'm wondering, since lrp seems to use initrd 
image technology already, is there any way to use the pcmcia image to 
do a double-pass? On another note, can I perform pcmcia-module 
inserts and start the pcmcia cardmgr from linuxrc?

I read through the Loopbak-fs mini-howto (ibiblio is down right now, find it:)
http://www.linuxpowered.com/archive/mini/Loopback-Root-FS.html

But what it couldn't tell me is how this all applies to lrp/leaf. any takers?

I really don't know enough about the boot process. If somebody could 
tell me or point me in the direction of a howto that discusses how to 
insert an initrd image on lrp (which I'm guessing can't be an 
all-to-uncommon way to add functionality), I would greatly appreciate 
it.

thanks for the help Mike. Charles, you rock as well. Does anyone have 
a clue on this next step?

/johan

---
.  . . .. ...S I G.
   name:   Johan Ugander
   school: AEDT2002
   email:  [EMAIL PROTECTED]
   icq:4330752
.  . . .. ..._.

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



Re: [Leaf-devel] Booting Flash on PCMCIA vs. IDE

2002-02-10 Thread Mike Noyes

Johan,
I decided to post this to the list after all. Note: the message from 
Charles is still probably more accurate than my analysis below,

At 2002-02-09 15:15 -0500, Johan Ugander wrote:
>Oh, and by the way, my pc/104 pcmcia bridge is the tri-m aaeon pcm3115b
>http://www.tri-m.com/products/aaeon/pcm3115b.html
>http://www.tri-m.com/products/aaeon/manual/pcm3115b.pdf

After reading the 3115b manual pages 4-7 through 4-10, I believe you're 
going to need the TrueFFS kernel patch from M-System [1] to boot from a 
flash drive in the pcmcia slot. The other option is the MTD driver from the 
site [2] I mentioned before.

[1] http://google.com/search?hl=en&q=trueffs+linux
[2] http://www.linux-mtd.infradead.org/

I was unable to locate anything in the 3115b manual that mentions 
CompactFlash (CF) or true IDE mode. I don't think CF devices are supported 
as a pcmcia boot medium on the 3115b.

CF 1.4 specifications.
http://www.compactflash.org/cfspc1_4.pdf

--
Mike Noyes <[EMAIL PROTECTED]>
http://sourceforge.net/users/mhnoyes/
http://leaf.sourceforge.net/content.php?menu=1000&page_id=4


___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel



[Leaf-devel] New dachstein 1.0.2 CD with glibc 2.1.3

2002-02-10 Thread KP Kirchdörfer

Today I've put up a new build of dachstein 1.0.2 CD with glibc 2.1.3 
onto sourceforge:

leaf.sourceforge.net/devel/kapeka/lrp-packages

I fixed one or two minor bugs, repackaged ipmail.lrp, updated to 
latest openssh version from Jacques Nilo, updated ez-ipupdate and 
replaced login, adduser etc. with tinylogin 1.0.

Michael D. Schleif sent me a copy of his new net-snmp package, which 
he runs successfully on five routers. The previous net-snmp.lrp's has 
been replaced. 

AFAIK original dachstein 1.0.2 configurations should work without 
changes.

regards kp

___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel