--- In email@example.com
, "Mike \(mwester\)" <mwester@...>
> "pizzulicchio1981" <pizzulicchio@...> writes:
> > I'm interesting to know if it's possible to view the boot strap
> > NSLU using the serial port.
> Yes, that is it's primary purpose. It is also possible to interact
> bootloader on the NSLU2.
> > Simply....
> > The serial port gives a continuos output ( as a classic
> > example a cisco router - modem - switch ) or it startups during
> At initial power-up, the serial port is used by the bootloader
> As soon as the kernel begins to boot, the serial port is used to
> boot log. What happens after that depends on the firmware -- With
> (and the native Linksys firmware), once boot-up reaches a certain
> interactive shell is started on that port; with standard Linux
> (SlugOS) a login prompt appears and one must login to gain access
> > What are the beneficts of a serial port?
> Diagnostics, particularly early-boot-time failures and debugging.
> kernel attempts to do its best to log all events and messages to
> files, as specified by the user. However, messages and events that
> before such logging can be set up are lost without a serial
> in the event of the failure of the storage device to which the logs
> routed, again the serial port is the only place one can see the
> [I should note that Unslung 6.10 includes an implementation
> which attempts to address some (but not all) of these issues. Of
> netconsole has been available for SlugOS for some time now. In a
> what netconsole does is take console messages and transmit them on
> ethernet port. Even so, netconsole requires that your NSLU2 boot
up to the
> point where it can function on the network, so it is still very
> to have a serial port for diagnosing early-boot issues. In other
> netconsole is better than nothing, but a serial console on the
> still ideal.]
> Mike (mwester)
I'm Using Debian! What appens during boot strap ? ( this NSLU is
fantastic !!! )