Five network tricks for Linux on S/390 systems
Feb 16, 2009, 14:03 (0 Talkback[s])
(Other stories by Anjali Gupta)
WEBINAR: On-demand Event
Replace Oracle with the NoSQL Engagement Database: Why and how leading companies are making the switch REGISTER >
[ Thanks to An Anonymous Reader for
this link. ]
"Linux is a very useful operating system for the IBM
S/390 platform (also referred to as System z) because it
consolidates connectivity among legacy, Linux, and middleware
applications such as Web, mail, application servers, firewalls,
etc. By working as a "native" operating system, Linux leverages all
the hardware capability of the S/390 platform.
"This article shares five troubleshooting tips to counter the
various problems that can arise when you bring up a Linux system on
a System z series machine:
- Surviving a Martian invasion: Martians messages are the packets
with sources that don't have any known route.
- Disciplining network services on restart: Sometimes when
bringing up the Linux image on an LPAR, the service just doesn't
- Intercepting corruption to your file system on shutdown: There
are three ways shutdown can lead your file system astray.
- Making the most of cio_ignore: Or, how to shorten your list of
"must sense and analyze" boot path devices.
- Keeping Virtual LAN from being a pain in the flash: By looking
for the physical installation files.
"This article refers to various versions of SUSE Linux, so as a
bonus tip, I'll shed some light on a few bugs in different versions
of SUSE and give you a workaround for those bugs."