Re: Hercules Bus Error

2014-02-23 Thread Philipp Kern
On Wed, Feb 19, 2014 at 03:15:06PM -0500, Stephen Powell wrote:
 Now back to my main subject.
 For network devices in Debian for s390x, hardware configuration is
 designed to be done by sysconfig-hardware, and software configuration
 is designed to be done by ifupdown.  These two packages front-end
 the lower level commands.  [...]

I think that your post should end up somewhere accessible and google'able in
documentation, as it is probably something a bunch of people will struggle
with when getting started with Debian on the mainframe. Except that I don't
know where. Some of it might belong into the installation manual, but most
of it is just how Debian network configuration works on the mainframe
and I'm not sure if we have good enduser docs where this would fit…

(Thanks for writing it up!)

Kind regards
Philipp Kern


-- 
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140224022210.ga22...@simplex.0x539.de



Re: Debian-390 / Hercules Problems

2014-02-23 Thread Philipp Kern
On Tue, Feb 18, 2014 at 11:23:19PM -0500, Stephen Powell wrote:
 I downloaded the Debian source package for s390-tools 1.17.1.
 The source code (it's a shell script) for znetconf is present in the source
 package, but for some reason it does not get built into the binary version
 of the package.  I was able to get it to run from the source package
 (using ./znetconf -c) when my current directory was debian/build/build/zconf
 (starting from the top directory of the source package).  But in order to
 get it to run, I had to make some changes.  Both znetconf and lsznet.raw have
 hard-coded references to a directory called /lib/s390-tools, which does not
 exist on a stock Debian system.  This may be causing a build failure.
 But if so, it is a silent build failure.  dpkg-buildpackage produces no 
 errors.
 I got it to run by changing the directory to ., for testing purposes.
 This is no good for the general case, of course, but I did it just to see if
 I could get it to run, and I was able to get it to run that way.
 ./znetconf -c finds and lists my CTCA.
 
 I think this is a question for the package maintainer.  Philipp, are you
 listening?

Is znetconf solely doing runtime configuration or does it also try to persist
it?

Kind regards
Philipp Kern


signature.asc
Description: Digital signature