> Thank's David :)
> It is as you say, don't configure inside the Linux servers if you don't
> have to.
You're welcome. It sounds like a pretty cool system.
> We did some tries with DHCP as well at first, but it did not work due
> to we only had IP-packets sent
> via vswitches, and not ethernet
On Thu, Jul 2, 2009 at 5:31 PM, Scott Rohling wrote:
> Agreed - that is clever .. I've played around with tags and PUN files to
> get info to Linux, but this is much more direct. Sweet - thanks, Tore!
Actually, if you make them like this
SET PFx fconfig eth0 192.168.0.10 netmask 255.255.255.
[selected responses interleaved]
Agblad Tore wrote:
> Here comes some feedback.
Awesome. Thanks! This is exciting stuff.
By the way, you people at Volvo make good cars.
> The bind mount is a source of failure, or not ?
> What happens if it does not work for some reason ?
> I guess the origina
ux-...@vm.marist.edu] On Behalf Of David Boyes
[dbo...@sinenomine.net]
Sent: Thursday, July 02, 2009 15:39
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Updated paper available - "Sharing and maintaining SLES 10 SP2
Linux under z/VM"
> > About creating clones, we have made another approach.
> > Would be nice if CP really did have user environment variables :)
Use the CP tag field for a virtual 3800 printer. 8K worth of space to store
various useful stuff that will survive IPL of the virtual machine, settable
outside the OS, etc, etc.
Very easy to write a little thing that loads
Agreed - that is clever ..I've played around with tags and PUN files to
get info to Linux, but this is much more direct. Sweet - thanks, Tore!
Scott
On Thu, Jul 2, 2009 at 8:40 AM, Marcy Cortes
wrote:
> Tore Agblad wrote:
>
>
> >To have this working in SLES10 :
> >We set a number of FKeys
Tore Agblad wrote:
>To have this working in SLES10 :
>We set a number of FKeys in the VM profile to for example: IPNR=1.2.3.4
>and MASK=255.255.255.0 and GATEWAY=1.2.3.0 and so on.
>Then we get these values via vmcp in /etc/init.d/boot.local, and sets the
>ipconfig values.
>And whatever you need
> > About creating clones, we have made another approach.
> > Every server configures the network/ip itself at every boot,
> Configures the network at *every* boot? Why not just at first boot? Do
> you
> never put the real IP address, host name and other values in /etc?
Pretty much DHCP, without t
@VM.MARIST.EDU
Subject: Re: Updated paper available - "Sharing and maintaining SLES 10 SP2
Linux under z/VM"
Agblad,
> Here comes some feedback.
> It is a very good source for info in this matter, and explains a lot of
stuff you need to know.
Thanks!
> I have read the previous one
Agblad,
> Here comes some feedback.
> It is a very good source for info in this matter, and explains a lot of
stuff you need to know.
Thanks!
> I have read the previous ones and tried to implement it.
> It was however tricky, most due to that reality changes (like: oops, we
need more space on /op
: Linux on 390 Port [linux-...@vm.marist.edu] On Behalf Of Michael MacIsaac
[mike...@us.ibm.com]
Sent: Wednesday, July 01, 2009 17:58
To: LINUX-390@VM.MARIST.EDU
Subject: Updated paper available - "Sharing and maintaining SLES 10 SP2 Linux
under z/VM"
Hello everyone,
I am please to annou
Hello everyone,
I am please to announce an updated paper "Sharing and maintaining SLES 10
SP2 Linux under z/VM", and an associated tar file with scripts and
configuration files.
The paper is available on the Web at:
http://linuxvm.org/present/misc/ro-root-S10.pdf
The tar file is available at:
12 matches
Mail list logo
