Mark,
Thank you very much for this info. Will wait for the SP3.
Best regards,
Florian
On Thu, Jul 2, 2009 at 7:32 PM, Mark Post wrote:
> >>> On 7/1/2009 at 3:43 PM, Florian Bilek
> wrote:
> > Dear colleagues,
> >
> > With regard to the mail published by Gerhard Hiller from 06/30/2009
> > men
Note the USMC logo. The anchor chain is wrapped around the anchor. So,
all marines are always fouled up. ;-)
The use of the fouled up anchor as a symbol of the marines goes back to
at least the late 1700's. The term SNFU or SNAFU (I have seen it both
ways although the later is now the more common)
one more view -
3 of my great uncles were marines - 1 in 1918, WW1 in France. The other 2
in the Pacific in WW2.
All 3 agreed that the terms SNAFU and FUBAR were in general use by the
enlisted Marines even before their time(s).
Was the subject of several memorable conversations at family reunions w
Thanks to all for the answers and suggestions.
Cordiali saluti / Best regards
Marco Bosisio
IBM Italia S.p.A.
Sede Legale: Circonvallazione Idroscalo - 20090 Segrate (MI)
Cap. Soc. euro 400.001.359
C. F. e Reg. Imprese MI 01442240030 - Partita IVA 10914660153
Società soggetta all?a
Isn't that snafu -- situation normal all fouled up?
Scott
On Thu, Jul 2, 2009 at 10:46 AM, Stephen Frazier wrote:
> A related term also from WW2 is SNFU. Widely used in the Navy for
> "Situation Normal Fouled Up." In Navy terminology "fouled up" means that
> your anchor chain is tangled so you c
A related term also from WW2 is SNFU. Widely used in the Navy for
"Situation Normal Fouled Up." In Navy terminology "fouled up" means that
your anchor chain is tangled so you can't raise the anchor and get
aweigh. Aweigh of course means that the ships anchor has been pulled in
enough that it is no
> I see no real reason why someone at ITSO would get his proboscis out of
> joint concerning the meaning of words such as these
Personally I liked the way some vaxen and pdp's reported failed unibus
transactions. One thing reported was the failed address. Naturally enough
it was reported in the
Yup, beyond all doubt.
But "foo" was still the license plate on Smokey Stover's car and has nothing
to do with "fubar" or "foobar".
It may have been Pascal, but I had a textbook whose favorite variable names
were foo, bar and foobar.
--
Robert P. Nix Mayo Foundation.~.
RO-OE-5-
>>> On 7/1/2009 at 3:43 PM, Florian Bilek wrote:
> Dear colleagues,
>
> With regard to the mail published by Gerhard Hiller from 06/30/2009
> mentioning an installation of a terminal server under z/VM, I would like to
> know if there will an update forseen for SLES 10 supporting that kernel and
> > 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
Hello!
I can confirm your posting (or musings) regarding the word "foo". It was
indeed the license plate indicator for that illustrious gentleman. I
remember seeing the comic strip someplace and the plate struck me as
amusing.
I believe the words "Fubar" and "foobar" surfaced during the Un*x epoch
FOOBAR dates from WW2 where it was more commonly spelled FUBAR.
The polite definition is fouled up beyond all recognition.
Guess what the real definition is!
Edward Long
--- On Thu, 7/2/09, RPN01 wrote:
> From: RPN01
> Subject: Re: OT (was Re: RHEL 5.4 Beta is out in the wild)
> To: LINUX-390
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
Actually, "foo" is unrelated to "fubar". Foo was the licence plate on Smokey
Stover's two wheeled car in the comic strips, dating back to the 1920's or
1930's. "Fubar" and "foobar" came into use later, as far as I can tell, but
it's hard to trace things like that.
--
Robert P. Nix Mayo Fo
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
Thanks for your answers, I can just add that to avoid std problems, we have
only one clone-base(golden)
per SLES version. We use the 'clone-any-server' possibility just if really
needed or for example
when we have one new server that had been setup with customer apps, we can
clone that one
to sa
Rob,
> Maybe you could get a position at the ITSO as an editor and flag
> the phrase "kill a daemon"
I recently got a variable named "foo" edited out by an ITSO editor.
Because everyone knows that foo is a variant of fubar which is an acronym
with a *bad word* in it - "foo" might offend a reader.
On Thu, Jul 2, 2009 at 4:22 AM, Scott Rohling wrote:
> Hmmm.. Disabled cpu topology, added processor degradation capability...
>
> Those sound, well.. bad. I'm sure they're not, but something gets lost
> in the 8 words or less synoposis ;-) I passed your post on to a customer
> and they com
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
Shawn could you provide a url/link for downloading this?
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Shawn Wells
Sent: Wednesday, July 01, 2009 7:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: RHEL 5.4 Beta is out in the wild
RHEL 5.4 public beta i
Hi, thank's for this update.
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.
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 o
22 matches
Mail list logo
