Darren New schrieb:

> That pretty much went away when OSes started running in real mode. By 
> the time you got away from 16-bit code, nobody used the BIOS for basic 
> I/O any more.
> 
> But you knew that.

Indeed ;-)

Post a reply to this message

On Fri, 30 Oct 2009 10:16:20 -0700, Darren New wrote:

> Jim Henderson wrote:
>> openSUSE 11.1 and 11.2 RC (which is in final testing now) should
>> include ntfs-3g, so should be able to mount the NTFS partitions without
>> a problem.
> 
> I have no problem using ntfs-3g and mounting NTFS drives RW from my
> OpenSuse 11 that I downloaded many months ago. I don't know it's on the
> live CD, but it's definitely in the distro somewhere.

Yeah, on my 11.1 box, I've a small Vista partition (came with the system 
and I left it "just in case" I needed it for something, but shrunk it 
down really small) and I noticed that the system mounts them at boot time 
automatically.  I'm kinda assuming with the live media it's there - would 
make sense to me if it was, since one might want to use the software on 
the disc to open doc files to check compatibility.

>> With the live media, everything runs of the media - no need to perform
>> an installation.  The media is primarily to permit a user wanting to
>> "test drive" Linux to see some of the features/functionality and to
>> ensure system compatibility prior to installation.
> 
> Yeah, I learned that one the hard way. :-)

:-)

Jim

Post a reply to this message

On Fri, 30 Oct 2009 13:43:48 +0000, Invisible wrote:

> TC wrote:
> 
>> I did try the Ubuntu Live CD and it did reset my computer's clock to
>> either daylight saving time or universal time - both -1:00, so I cannot
>> be sure which.
>> 
>> This is no real problem, though, merely a very minor annoyance. Still,
>> this should not be.
> 
> The Linux Way(tm) seems to be to set the system clock to UTC and compute
> local time from that depending on your timezone configuration. (Which,
> on a live CD, is probably not set right anyway.) The Windows Way(tm) is
> to set the system clock to local time...

This is true - the *nix way (in general) is that the HW clock is set to 
GMT and the OS calculates the offset.  That may be what TC is seeing.

Jim

Post a reply to this message

Am Fri, 30 Oct 2009 06:59:05 -0400 schrieb Warp:

>   I don't understand why linux would modify the frequency/timings of cpu
>   and
> memory, and even if it did, why it would have to modify BIOS to do that.

I don't know why it would change the BIOS either, but AFAIK for some 
CPU's one could reduce the power consumption by using a lower CPU 
frequency (power savings on mobile computers).

Post a reply to this message

Jim Henderson wrote:
> This is true - the *nix way (in general) is that the HW clock is set to 
> GMT and the OS calculates the offset.  That may be what TC is seeing.

Speaking of which... how do you change the timezone on Linux these days? The 
TZ variable isn't set. I think it's a Debian install. (It's a VM at work, so 
I barely know anything about it, but if screws up the timestamps because the 
head office is in a different timezone.)

-- 
   Darren New, San Diego CA, USA (PST)
   I ordered stamps from Zazzle that read "Place Stamp Here".

Post a reply to this message

On Fri, 30 Oct 2009 23:42:19 +0100, Darren New <dne### [at] sanrrcom> wrote:
>
> Speaking of which... how do you change the timezone on Linux these days?  
> The TZ variable isn't set. I think it's a Debian install.

http://lmgtfy.com/?q=debian+change+timezone



-- 
FE

Post a reply to this message

On Fri, 30 Oct 2009 15:42:19 -0700, Darren New wrote:

> Jim Henderson wrote:
>> This is true - the *nix way (in general) is that the HW clock is set to
>> GMT and the OS calculates the offset.  That may be what TC is seeing.
> 
> Speaking of which... how do you change the timezone on Linux these days?
> The TZ variable isn't set. I think it's a Debian install. (It's a VM at
> work, so I barely know anything about it, but if screws up the
> timestamps because the head office is in a different timezone.)

I would change it on my SUSE systems using YaST, most likely, in the time/
date configuration.

Jim

Post a reply to this message

Jim Henderson wrote:
> I would change it on my SUSE systems using YaST, most likely, in the time/
> date configuration.

That's why I asked. The VM I'm using is all command-line driven, let alone 
something as nice as YaST.

Fortunately, Fredrik googled it for me. ;-)

-- 
   Darren New, San Diego CA, USA (PST)
   I ordered stamps from Zazzle that read "Place Stamp Here".

Post a reply to this message

On Sun, 01 Nov 2009 10:06:51 -0800, Darren New wrote:

> Jim Henderson wrote:
>> I would change it on my SUSE systems using YaST, most likely, in the
>> time/ date configuration.
> 
> That's why I asked. The VM I'm using is all command-line driven, let
> alone something as nice as YaST.
> 
> Fortunately, Fredrik googled it for me. ;-)

I was tempted to, but since he already did.... ;-)

Jim

Post a reply to this message

Darren New wrote:
> Warp wrote:
>>   I don't understand why linux would modify the frequency/timings of cpu
>>   and
>> memory, and even if it did, why it would have to modify BIOS to do that.
> 
> Actually, during boot-up, something along the lines of "installing new
> microcode" or "installing new firmware" or something like that scrolls by.
> That always worried me, but I figured it either got reversed at the next
> reboot or it was too late to do anything about it, and it never caused any
> trouble.

CPUs have volatile memory to store microcode updates. If an OS, during 
bootup, loads microcode into your CPU and screws things up, reboot and it's 
gone.

Many pieces of hardware have a similar thing for firmware, except that it's 
not for "updating". If the device driver doesn't load the firmware into the 
device, then it won't work at all, or it will lack features.

In any case, it's volatile memory (that's why it's being done on boot).

Post a reply to this message