what_to_buy;337990 Wrote:
I'm new to all of this, but after much reading of this forum and the
dBpoweramp forums, here is my strategy:
Wow what_to_buy. I slack off for a couple days, and you do all the leg
work for me. Thanks a bunch!
--
johnvb
Rob van der Heij wrote:
On Sun, Sep 14, 2008 at 2:26 AM, John Summerfield
[EMAIL PROTECTED] wrote:
I may have missed something. Is there no way that a virtual machine
cannot have use of a clock, corrected for drift, that reflects the
correct time of day, either now or in the future? A TOD
Alan Altmark wrote:
On Saturday, 09/13/2008 at 08:34 EDT, John Summerfield
[EMAIL PROTECTED] wrote:
I may have missed something. Is there no way that a virtual machine
cannot have use of a clock, corrected for drift, that reflects the
correct time of day, either now or in the future? A TOD
Alan Altmark wrote:
On Sunday, 09/14/2008 at 05:36 EDT, Patrick Spinler
[EMAIL PROTECTED] wrote:
Uhm, I'm coming to this discussion late, but aren't all 127.0.0.0/8
addresses defined to be loopback?
Yes, I mentioned that in an early post on the subject. That's one of the
reasons it makes no
Do you want it to work when the interface is up? What I was trying to say is
that with most hardware it will work when the interface is up or down, or it
will not work when the interface is up or down. You can't do what I think you
want.
-Original Message-
From: Linux on 390 Port
I am not sure I understand what you are saying. The change that was made was
to the name for the host in /etc/hosts. The name loopback should always have
been to a 127.* address, and all the 127.* addresses should be routed to the
loopback interface.
-Original Message-
From: Linux on
Hi,
I'm pleased to announce that JBoss is now officially certified on System z:
http://www.press.redhat.com/2008/08/27/jboss-enterprise-application-platform-expands-certified-configurations-adds-more-mainframe-java-se-6-support/
For specific version info, see:
I don't know if there is any actual standard for /etc/hosts entries. There is
also no guarantee that /etc/hosts will have an entry for localhost, or the
hostname of the system.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Alan Altmark
Sent: Friday,
On Monday 15 September 2008 12:38, Ron Foster at Baldor-IS wrote:
Has anyone come to a conclusion?
Run NTP or not?
Adjust the time once a day using cron?
Given that the current ntpd implementation wakes up every second, I'd say
*never* run ntpd on more than a few guests.
I think the jury is
On 09/12/2008 07:18 PM, Fargusson.Alan wrote:
The problem I eluded to is that some network cards and hubs don't
send and receive at the same time, so if you send a packet to your
own IP address you don't see it come back. That means that you won't
be able to access machine x from machine x
Has anyone come to a conclusion?
Run NTP or not?
Adjust the time once a day using cron?
Ron Foster
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO
Kim Goldenberg wrote:
Alan Altmark wrote:
On Sunday, 09/14/2008 at 05:36 EDT, Patrick Spinler
[EMAIL PROTECTED] wrote:
Uhm, I'm coming to this discussion late, but aren't all 127.0.0.0/8
addresses defined to be loopback?
Yes, I mentioned that in an early post on the subject. That's one of
Steffen Maier wrote:
On actually sending something to that address, the following entries are
added to the routing cache, revealing that the ICMP echo request was
sent on the loopback interface and the echo reply was received from the
loopback:
[EMAIL PROTECTED] sbin]# ip route list table
Fargusson.Alan wrote:
I don't know if there is any actual standard for /etc/hosts entries. There is
also no guarantee that /etc/hosts will have an entry for localhost, or the
hostname of the system.
man hosts
RFC 952 (maybe).
I think you may have some problems if localhost doesn't resolve,
Fargusson.Alan wrote:
Alan, I have a threaded view of my incoming email: its displayed in a
tree hierarchy reflecting who replied to whom. For some reason, your
email isn't being threaded properly. Could you pls check your settings
and see whether there's something you can tweak?
Do you want
Fargusson.Alan wrote:
I am not sure I understand what you are saying. The change that was made was to the name
for the host in /etc/hosts. The name loopback should always have been to a
127.* address, and all the 127.* addresses should be routed to the loopback interface.
This entry:
Posted for the participants of IBMVM, IBMMAIN, and Linux-390
who are interested in System z Education.
Enrollment is open for the next IBM conference for the mainframe
IBM System z Expo
featuring z/OS, z/VM, z/VSE, and Linux on System z.
Oct. 13-17, 2008
RIO All Suites Hotel
Las Vegas
17 matches
Mail list logo
