On Tue, Apr 30, 2002 at 06:01:57AM -0700, Matt Kraai wrote: > On Mon, Apr 29, 2002 at 09:09:41PM -0400, Matt Zimmerman wrote: > > On Mon, Apr 29, 2002 at 07:56:09AM -0700, Matt Kraai wrote: > > > > > I've fixed this. Does this also need to be done for > > > parmfile.example1: > > > > > > dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 > > > peer=192.168.0.1 dns=192.168.0.2 netinterface=iucv1 > > > netmodule=netiucv iucv=tcpip:gateway > > > > > > and parmfile.example2: > > > > > > dasd=192-191 ro hostname=debian.domain.com ip=192.168.0.42 > > > netmask=255.255.255.0 gateway=192.168.0.1 dns=192.168.0.2 > > > netmodule=lcs chandev=noauto;lcs0,0x1000,0x1001,0,1,0 > > > > > > ? > > > > Yes, it can't hurt. These numbers are usually changed by the administrator > > to match the system being installed, but a more correct example is helpful. > > OK, fixed. I don't suppose you know how to handle the TDF file?
TDFs are used for supplying data to an emulated tape device; the file that Jochen Hein supplied looks OK, but I haven't tested it. The pathnames typically have to be edited by the admin anyway, so it should be considered an example. It would probably do fine under the tape/ directory, by analog to vmrdr/debian.exec (which is the same kind of metadata). -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
