World: r3wp

Hi Phil,


*nix doesn't use drive-letters, so _all_ drives show up somewhere 
under the root as directories. _Where_ they show up is up to you 
;-)

Drives are "named" /dev/hda1 (first paritiion on first disk), /dev/hdb3 
(third partitiion on second drive), etc ...

There's a file, which describes the mapping, where your drives are 
put, in Rebol

print read %/etc/fstab


the first two columns show where ich drive is put in the directory 
tree (and then some more info)

or you can do 

call "mount"

which displays the currently mounted drives.

ah! - AltME did it once again. When sending message, it got grey, 
and message sent is lost (did not make it to the Linux group)

I get following error message with my old Fedora Core install. I 
can't run SDK (dated 2.8.2006) rebols, it throws following error 
to the console:


/usr/local/rebol-sdk-cmd/bin/rebcmd: error while loading shared libraries: 
libstdc++-libc6.2-2.so.3: cannot open shared object file: No such 
file or directory

I've lost several messages that way today, despite being on a broadband 
line.

Seems either the new server is not stable, or the latest Altme is 
buggy.

Either way, this remains one of the most annoying Altme usability/reliability 
issues.

Pekr; On my Debian system, I had to do an
  apt-get install libstdc++5
to get an older sdk version running.
I don't know Fedora's package manager but under Debian you would
  apt-get install libstdc++6
to get the shared libraries required.

Under GNU/Linux, having various shared libraries around isn't great, 
but it rarely hurts things.
the ldd command will show what shared libraries are required.

I've got this odd problem.  I am running fedora core 6 as a vmware 
image.  the time keeps dropping back 12 hours.  I have the right 
time zone, and ntpd is running, and I'm pointing to a local time 
server.

How does hwclock react?

hwclock is correct.

and I've ticked that the system clock is not set to utc

I don't think a vmware image can alter the host clock ...

happening at boot?
does hwclock --hctosys fix the time?
I'm fishing here...could it be a cron job "helping"

oh .. is hwclock a program?

I'll try that when it goes bad again.  Seems to happen when I'm asleep.

I'll reboot the image and see what happens.

the main reason I am running this image is so that I have an imap 
server to use with rebelBB !

damm... gone back 12 hours after rebooting.

how about tzconfig

and now it has been set correctly using hwclock --hctosys

don't have a tzconfig program

Oh, it just makes sure  /etc/localtime is copied from proper /usr/share/zoneinfo 
and puts the tz in /etc/timezone...my directories are for Debian

Ok.  Well, Gnome shows me the correct timezone.

Does that help?

do a cat /etc/timezone

nothing

Then make sure that /etc/localtime is identical to the /usr/share/zoneinfo/Canada/Eastern 
where the Canada/Eastern part is for me...

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144894

Other images keep the correct time?  I had to add --directisa  to 
get the system time to hardware in the hwclock executed at shutdown. 
 That was just to get the PC to hold UTC.

one is out by an hour only ( day light saving I guess ).

What does hwclock --show say

Ubuntu says 6:46 EDT April 6, but i have not round to setting this 
up yet.

Gee, all my images have different times!

How about ntpdate.  Does it correct itself?

Fun stuff isn't it.  :)

hwclock --show says 10:23 NZST

it's lost 20 mins since I set the time!

ntpdate says socket is being used

Debian comes with ntpdate-debian that uses ntpdate 0.debian.pool.ntp.org 
 (for the (first) server arg)

How does one set the time from bash ?

date

I used tzselect to reset the timezone, but the time is still wrong.

After the tzselect was there an ntpdate or hwclock --hctosys executed?

no

hwclock --hctosys is not setting the time correctly now

Off by how many hours?

hwclock --utc  (if hardware is utc) or hwclock --localtime  can effect 
things.

20 mins

I used date to set the time correctly .. now going to wait 20 mins 
and see what happens

Write a little script like   forever [print now/exact wait 00:05:00] 
 and log it or just monitor

/exact = /precise sorry.

already lost 2 mins :(