Hi Mark,
Have you actually configured the device online to the Linux LPAR?
Adding the device by means of this echo command *is* the first step to
install
this device, to switch it online (with another echo command in sysfs) is
a next one.
The problem was: the echo command did just nothing,
Did you ever try the --excludepath OLDPATH option, which means Don't
install any files whose name begins with OLDPATH? I wonder if you
could use that option when you installed the software on the other
guests who have /usr r/o, e.g. RPM --excludepath /usr rpm file. Maybe
that would tell RPM to
Mono.posix is supposed to be part of mono-core so I'm not sure why you're
seeing what you are seeing. Try using the --nodeps option on the rpm -Uhv
and see if xsp will come up okay. (I prefer to use mod_mono with Apache
rather than using the xsp standalone.)
If it works then that may just
Installing with --nodeps appeared to work. I issued 'xsp' as a command and
got:
xsp
Listening on port: 8080 (non-secure)
Listening on address: 0.0.0.0
Root directory: /root/RPMs
Hit Return to stop the server.
On to configuring Apache and mod_mono, also the DB2 interface to allow us
to actually
When doing things like this, you won't see any error messages on the console.
You'll need to do a dmesg command, and look at the last few lines to see if
anything shows up there. A lot of times, it won't, but you never know.
All Linux and UNIX systems are case-sensitive, so indeed A is _not_
Hi Mark,
All Linux and UNIX systems are case-sensitive, so indeed A is _not_ the
same as a.
This is exactly what I thought when writing 0.0.0A08.
And this is what I don't understand: why echo did not accept this.
I will aks dmesg.
Anna
-Original Message-
From: Linux on 390 Port
If you look at the Device Drivers and Installation Commands manual, you'll
note that all their examples have the letters in the device numbers in lower
case. So, the kernel is expecting all the device numbers you send it to be in
lower case as well. All-caps is an AOL and legacy mainframe
OK, I went back to the device drivers book only. (Same steps as the
SHARE presentation).. I do have a layer3 QDIO guest LAN..
For a router or the Hipersocket Network Concentrator thhe book says to
issue the following to the hipersocket device:
echo primary_connector
We've been seeing some disturbing differences between the packet size being
(aparrently) sent on SLES9 vs SLES8 over the hipersocket interface.
The tool we have been using to tell us the packet length going over the
hipersocket is tracepath.
On SLES8:
nokomis:~ # uname -r
2.4.21-83-default
Keep in mind: a hipersocket and a OSA are NOT the same beast -- they
both use QDIO to deliver frames to the media, but the similarity stops
there. Some things just don't work on hipersockets -- for example,
hipersockets don't have that silly PRI/SECROUTER thing, so they *should*
return an error
On Friday, 04/14/2006 at 12:11 CST, Lee Stewart
[EMAIL PROTECTED] wrote:
OK, I went back to the device drivers book only. (Same steps as the
SHARE presentation).. I do have a layer3 QDIO guest LAN..
For a router or the Hipersocket Network Concentrator thhe book says to
issue the following
Did you ever try the --excludepath OLDPATH option, which means Don't
install any files whose name begins with OLDPATH? I wonder if you
could use that option when you installed the software on the other
guests who have /usr r/o, e.g. RPM --excludepath /usr rpm file. Maybe
that would tell
According to page 102 of the book, you use primary_connector to tell the OSA
interface you're routing between it an a HiperSocket network. You use
multicast_router to tell the HiperSockets the same thing. In the section
you're working from, they're doing the opposite. They seem to have a
13 matches
Mail list logo
