riginal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jacques Nilo
Sent: 15 April 2002 21:47
To: Eric B Kiser
Cc: [EMAIL PROTECTED]
Subject: Re: [Leaf-user] serial console access
Eric B Kiser wrote:
> [Jacques-Snip]
> Bering v1.0-rc1 does not have serial compiled in t
, 2002 4:47 PM
To: Eric B Kiser
Cc: [EMAIL PROTECTED]
Subject: Re: [Leaf-user] serial console access
Eric B Kiser wrote:
> [Jacques-Snip]
> Bering v1.0-rc1 does not have serial compiled in the kernel. This seems
> necessary to have serial console access. I am considering to have serial
&
Eric B Kiser wrote:
> [Jacques-Snip]
> Bering v1.0-rc1 does not have serial compiled in the kernel. This seems
> necessary to have serial console access. I am considering to have serial
> compiled in v1.0-rc2 for that reason. Any comment from the list on that
> issue?
> [/snip]
>
> Based on the
got called out of town so this response is a bit delayed...
[Joey-snip]
Not to sound impolite... but there is currently I HOW-TO already available,
linked below... I know the excitement though of getting this particular
project working
[/snip]
Not impolite at all. The only reason that I suggest
On Fri, 12 Apr 2002 08:40:01 -0500
"Charles Steinkuehler" <[EMAIL PROTECTED]> wrote:
> > > Bering doesn't have serial support compiled into the kernel.
> >
> > Yes. True. I have used the posts at the beginning of this thread to
> > configure my serial-as-a-module kernel to boot, and I get (fina
> > Bering doesn't have serial support compiled into the kernel.
>
> Yes. True. I have used the posts at the beginning of this thread to
> configure my serial-as-a-module kernel to boot, and I get (finally) a
> login message, but no boot messages.
>
> I just get the initial message which lets me
ion to
the serial console (check the syntax, it might be wrong).
Joey
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Chad Carr
Sent: Thursday, April 11, 2002 10:34 PM
To: Mike Noyes
Cc: [EMAIL PROTECTED]
Subject: Re: [Leaf-user] serial console access
On 11 Apr 2002 09:09:42 -0700
"Mike Noyes" <[EMAIL PROTECTED]> wrote:
> On Thu, 2002-04-11 at 08:45, guitarlynn wrote:
> > Boot messages are set in Syslinux, not the LEAF OS until the kernel
> > gives up control to INIT. The console keyword in /syslinux.cfg should
> > point to the serial port ins
On Thu, 2002-04-11 at 08:45, guitarlynn wrote:
> Boot messages are set in Syslinux, not the LEAF OS until the kernel
> gives up control to INIT. The console keyword in /syslinux.cfg should
> point to the serial port instead of tty if your planning to run
> headless. Charles serial HowTo and the Se
On Thursday 11 April 2002 10:07, Chad Carr wrote:
> The contents of this thread make a delightful howto, but I am
> wondering when you say success what you really mean. I can copy the
> same results as you from my minicom window (i.e the boot happens and
> I can log in) but there is one large th
B Kiser
Cc: [EMAIL PROTECTED]
Subject: Re: [Leaf-user] serial console access
On Thu, 4 Apr 2002 15:18:59 -0500
"Eric B Kiser" <[EMAIL PROTECTED]> wrote:
> _SUCCESS_
>
> The results as copied from my hyperterm window..
>
> LEAF configuration men
On Thu, 4 Apr 2002 15:18:59 -0500
"Eric B Kiser" <[EMAIL PROTECTED]> wrote:
> _SUCCESS_
>
> The results as copied from my hyperterm window..
>
> LEAF configuration menu
>
>
> 1 ) Network configuration
>
> 2 ) System configuration
>
> 3 ) Pac
_SUCCESS_
The results as copied from my hyperterm window..
LEAF configuration menu
1 ) Network configuration
2 ) System configuration
3 ) Packages configuration
b) Back-up a package
EMAIL PROTECTED]
Subject: Re: [Leaf-user] serial console access
> Charles,
> As you suggested I typed in the line below at a command prompt:
>
> T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
>
> ...and got this response:
>
> T0:23:respawn:/sbin/getty: not found
>
> I assu
At 4/4/02 02:18 PM -0500, Eric B Kiser wrote:
>Thanks for the heads up Sjaak,
>
>I have been unable to locate the serial.o and made the assumption that
>it was compiled into the kernel. I have just found out that this is not
>the case. I just looked again and I am still not finding it. If someone
: [Leaf-user] serial console access
Hello Eric,
For me the serial console works on Bering, without compiling a
kernel.
I am using the 2.4.18 kernel and the matching serial.o from Jaques
site.
My syslinux.cfg starts with the folowing lines:
serial 0 19200 0
display syslinux.dpy#(displays nicely on
> Charles,
> As you suggested I typed in the line below at a command prompt:
>
> T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
>
> ...and got this response:
>
> T0:23:respawn:/sbin/getty: not found
>
> I assume, that as we have discovered, this is being caused by the absence
of
> serial support in
[snip]
Bering v1.0-rc1 does not have serial compiled in the kernel. This seems
necessary to have serial console access. I am considering to have serial
compiled in v1.0-rc2 for that reason. Any comment from the list on that
issue ?
Jacques
[/snip]
Yes Jacques. Please compile serial into the nex
Hello Eric,
For me the serial console works on Bering, without compiling a
kernel.
I am using the 2.4.18 kernel and the matching serial.o from Jaques
site.
My syslinux.cfg starts with the folowing lines:
serial 0 19200 0
display syslinux.dpy#(displays nicely on my serial console)
serial.
Hello Eric,
For me the serial console works on Bering, without compiling a
kernel.
I am using the 2.4.18 kernel and the matching serial.o from Jaques
site.
My syslinux.cfg starts with the folowing lines:
serial 0 19200 0
display syslinux.dpy#(displays nicely on my serial console)
serial.
> This sounds just like what I had happening a few weeks ago when I
> switched
> to the released version of Dachstein from the release candidate. I
> solved it by swapping in a kernel that had serial support compiled in
> but never was able to figure out why serial.o wouldn't work. Is it
> possibl
Charles,
This sounds just like what I had happening a few weeks ago when I
switched
to the released version of Dachstein from the release candidate. I
solved it by swapping in a kernel that had serial support compiled in
but never was able to figure out why serial.o wouldn't work. Is it
possible t
> Thanks for the response. Here is where I am so far...
>
> [1] modified /etc/inittab so that my serial terminal line looks like this:
> T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
> also, I did verify that the serial port is set for com1
>
> [2] added ttyS0 as the first entry on the list in /et
It would be very usefull to have serial support compiled in the kernel.
I still haven't upgraded to Bering because of that.
My firewall does not have a video card and keyboard.
I control it using the serial console...
-Original Message-
[big snip]
Bering v1.0-rc1 does not have seria
>From a recent post by Chad Carr (March 17) :
Installing Bering LEAF on compact flash for the Soekris net4501 router platform
1) download floppy image and mount using
mount -t msdos bering-1680-b4.bin /mnt/image -o loop
2) make msdos filesystem on compact flash
mkdosfs /dev/hde1
3) mount compac
t this may mean would be appreciated.
Thanks,
Eric
-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 03, 2002 9:13 PM
To: Eric B Kiser; [EMAIL PROTECTED]
Subject: Re: [Leaf-user] serial console access
> _system_
> Bering v1.0-rc1
&
> _system_
> Bering v1.0-rc1
>
> _task_
> I want to implement serial console access to my firewall.
>
> _resources_
> LRP-Serial-HOWTO written by Charles.
>
> _questions_
> Do I need to load the serial.o module?
Depends on your kernel. Try adding the following to your kernel command
line (typica
After some discussion with Larry I am resubmitting this question to the list
with more information and a more fitting title.
_system_
Bering v1.0-rc1
_task_
I want to implement serial console access to my firewall.
_resources_
LRP-Serial-HOWTO written by Charles.
_questions_
Do I need to load
sage-
From: david goodrich [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 1:39 AM
To: 'Luis.F.Correia'
Subject: RE: [Leaf-user] serial console...
Umm... forgive my cluelessness, but how, exactly, do I "just copy it to the
floppy"? alternately, /what/, exact
david goodrich [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 29, 2002 6:02 AM
To: [EMAIL PROTECTED]
Subject: [Leaf-user] serial console...
I followed the Serial-HOWTO on lrp.steinkuehler.net and I'm still not
getting console messages on my dachstein 1.0.2 floppy setup... however
I followed the Serial-HOWTO on lrp.steinkuehler.net and I'm still not
getting console messages on my dachstein 1.0.2 floppy setup... however,
from the boot logs...
Jan 29 00:39:40 firewall kernel: Warning: unable to open an
initial console.
Jan 29 00:39:40 firewall kernel: Serial
On Friday 21 December 2001 13:32, you wrote:
> hyperterminal should do what you want. assuming you have an
> appropriately wired serial cable connected between your laptop and
> your dachstein box, open hyperterminal
> (start->programs->accessories->communications->hyperterminal) or
> something s
Title: RE: [Leaf-user] serial console
Ray's absolutely right. The basic windows terminal emulator, HyperTerminal, has been included in all versions windows at least since Win95. When setting up the connection, set the "Connect using:" to "Direct to Com 1" and then
Like someone else already posted you need a serial terminal program. The
one that leaps to my mind that most everyone has is HyperTerminal.
Instead of putting a phone number into it, change the Connect Using from
whatever it is listed to 'Direct to ComX' where X is your serial port
number (ie
guitarlynn wrote:
> Any advice or suggestions would be appreciated,
Kermit (now capable of using ssh),
and, in general, man getty.
Matt
___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
A serial console connects to a serial terminal, not to a TCP stack. You are
running programs that expect to make telnet (or ssh, since you mention
PuTTY) connections over TCP/IP, not ones that expect to make serial
connections (or you are running them in telnet mode, not serial mode).
The termina
This is likely a no-brainer for those that have done this, but after
a couple of days of hunting and trying, I can't seem to get it.
I've enabled a serial console following Charles' Serial HowTo
on ttyS0 on Dachstein CD v1.0.2, everything there appears to
be fine. I have Win95 on a laptop (haven'
What does your /etc/hosts.allow file look like?
Mine, with working SSH, looks like:
# /etc/hosts.allow: list of hosts that are allowed to access the
# system. See
# hosts_access(5) and /usr/doc/net/portmapper.txt
# Example: ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
Kevin wrote:
>
> added both ttyp1 and ttyp2 to the /etc/securetty file, saved and rebooted
>
> putty still will not connect - get Remote Session Closed by Host
>
> any other suggestions to get this sshd going??
I agree with Victor, you don't have to add ttyp1 or ttyp2 and you must
have the fil
On Mon, 25 Jun 2001, Kevin wrote:
> Sorry so late, tried everything I could to get this working.
>
> I have now dropped and tried the ssh option.
>
> I have successfully installed from two floppy set-up, can backup and have
> keys made ans saved.
>
> When I try to log-in via the putty program,
followed the directions and have the same set-up as advised in the HOWTO.
Any idea on what is needed to help troubleshoot this issue or where to try
first?
thanks
Message: 2
Date: Sun, 24 Jun 2001 12:49:29 -0700
To: <[EMAIL PROTECTED]>
From: Ray Olszewski <[EMAIL PROTECTED]>
Subject: Re
At 03:15 PM 6/24/01 -0400, Kevin wrote:
>Can anyone help share some experience in getting this to work?
>
>http://lrp.steinkuehler.net/Documentation/LRP-Serial-HOWTO.txt
>
>is where I retrieved the docs
>
>
>I can not get step one of echo'ing from the # LRP prompt to the pc with
>hyper term o
Can anyone help share some experience in getting this to work?
http://lrp.steinkuehler.net/Documentation/LRP-Serial-HOWTO.txt
is where I retrieved the docs
I can not get step one of echo'ing from the # LRP prompt to the pc with
hyper term open and connected.
I was trying to get a dual fl
43 matches
Mail list logo
