 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
I was looking for a 64-bit Linux live cd (or dvd) - a dvd bootable linux
that can access my windows ntfs volumes but does not make any changes to hdd
(like, e.g, repartition the disk).
Something like knoppix but for 64-bit intel pc. I'd like to try some 64-bit
Linux programs vs. 32 bit Windows XP.
Now, is the opensuse 11 live cd what I am looking for? Or does one have to
boot from live-cd and then install linux?
Then, with opensuse there seems to be a problem with changes to BIOS. If it
is just the bios date-time that is changed - no problem. But if the cd
should manipulate the frequency/timings of cpu and memory - ouch! I cannot
imagine it does, but safe is safe, so I'll ask here before I have to go
hunting for the reset-bios jumper ;-)
Has anybody here experience with the live-cd?
http://www.marco.isrelated.com/?p=67
Since I am not much into linux I'd appreciate any help / suggestions.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
You could use the Ubuntu 64 live CD.
It will automatically mount all your partitions, in case of NTFS I think read
only.
If it's a live CD you won't need to install anything.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
TC wrote:
> Has anybody here experience with the live-cd?
I have used the livecd of both opensuse10, opensuse11x86 and opensuse11x64.
Never had a problem, didn't change disks or bios (at least not
irreversably). No problems going back to Windows after.
Ubuntu also comes with a version that will install into a file on your C:
drive, so it's a full-blown installed Linux without repartitioning your
drive in any way. Uninstall consists of deleting c:\ubuntu and taking the
option out of boot.ini, or something equally trivial.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
> Ubuntu also comes with a version that will install into a file on your C:
> drive, so it's a full-blown installed Linux without repartitioning your
> drive in any way. Uninstall consists of deleting c:\ubuntu and taking the
> option out of boot.ini, or something equally trivial.
Thank you, Darren. I will try this. Sounds exactly like the thing I am
looking for.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
TC wrote:
> Thank you, Darren. I will try this. Sounds exactly like the thing I am
> looking for.
You and lots of others. Hence the option. :-)
It used to be called "Lindows" a couple years ago until MS sued them (or
threatened to) for trademark violation. Now Ubuntu took over the idea and
made it an official part of their distributions.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
On Thu, 29 Oct 2009 13:04:11 +0100, TC wrote:
> I was looking for a 64-bit Linux live cd (or dvd) - a dvd bootable linux
> that can access my windows ntfs volumes but does not make any changes to
> hdd (like, e.g, repartition the disk).
>
> Something like knoppix but for 64-bit intel pc. I'd like to try some
> 64-bit Linux programs vs. 32 bit Windows XP.
>
> Now, is the opensuse 11 live cd what I am looking for? Or does one have
> to boot from live-cd and then install linux?
>
> Then, with opensuse there seems to be a problem with changes to BIOS. If
> it is just the bios date-time that is changed - no problem. But if the
> cd should manipulate the frequency/timings of cpu and memory - ouch! I
> cannot imagine it does, but safe is safe, so I'll ask here before I have
> to go hunting for the reset-bios jumper ;-)
>
> Has anybody here experience with the live-cd?
>
> http://www.marco.isrelated.com/?p=67
>
> Since I am not much into linux I'd appreciate any help / suggestions.
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'm not aware of the Live media doing anything to fiddle with BIOSes -
would be too many permutations and versions of bioses to get it right
enough of the time to make it worthwhile.
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.
Jim (openSUSE Forums Moderator & Novell employee)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
TC <do-not-reply@i-do get-enough-spam-already-2498.com> wrote:
> Then, with opensuse there seems to be a problem with changes to BIOS. If it
> is just the bios date-time that is changed - no problem. But if the cd
> should manipulate the frequency/timings of cpu and memory - ouch! I cannot
> imagine it does, but safe is safe, so I'll ask here before I have to go
> hunting for the reset-bios jumper ;-)
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.
(What good would it do to modify BIOS anyways? It would have to re-boot in
order for the changes to become effective. BIOS is not something which is
constantly running in the background. It just sets up the hardware and starts
the OS and that's it.)
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
> 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.
> (What good would it do to modify BIOS anyways? It would have to re-boot in
> order for the changes to become effective. BIOS is not something which is
> constantly running in the background. It just sets up the hardware and
> starts
> the OS and that's it.)
I thought this to be so, too. I was astonished to see that people seem to
have had some problems with this.
And I was not sure if this is true or not, so I asked.
BTW:
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.
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
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...
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp schrieb:
> 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.
> (What good would it do to modify BIOS anyways? It would have to re-boot in
> order for the changes to become effective. BIOS is not something which is
> constantly running in the background. It just sets up the hardware and starts
> the OS and that's it.)
Well, /nowadays/ that's how it is. Used to be different in DOS times.
Then again, that's quite a long time ago...
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
clipka <ano### [at] anonymous org> wrote:
> Warp schrieb:
> > 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.
> > (What good would it do to modify BIOS anyways? It would have to re-boot in
> > order for the changes to become effective. BIOS is not something which is
> > constantly running in the background. It just sets up the hardware and starts
> > the OS and that's it.)
> Well, /nowadays/ that's how it is. Used to be different in DOS times.
DOS could change the CPU/memory frequency by modifying BIOS and without
having to reboot?
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp schrieb:
>>> 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.
>>> (What good would it do to modify BIOS anyways? It would have to re-boot in
>>> order for the changes to become effective. BIOS is not something which is
>>> constantly running in the background. It just sets up the hardware and starts
>>> the OS and that's it.)
>
>> Well, /nowadays/ that's how it is. Used to be different in DOS times.
>
> DOS could change the CPU/memory frequency by modifying BIOS and without
> having to reboot?
No, but BIOS did more back then than just start the OS. For instance,
hard disk access or keyboard input would be handled by the BIOS.
Back then, the role of the BIOS was still closer to its name ("Basic
Input/Output System) than it is nowadays: It really did basic input and
output handling even while the OS was running, and was far from evolving
into a hardware configuration interface. (Remember how CPU and memory
frequency would be configured via hardware jumpers or DIP switches, port
I/O addresses would be jumpered on the /expansion card/ the ports were
on, etc?)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
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.
> 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. :-)
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
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.
I am curious what that's all about, tho.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
clipka wrote:
> Back then, the role of the BIOS was still closer to its name ("Basic
> Input/Output System) than it is nowadays: It really did basic input and
> output handling even while the OS was running,
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.
--
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 18:17:49 +0100, Darren New <dne### [at] san rr com> wrote:
>
> 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.
>
> I am curious what that's all about, tho.
http://kerneltrap.org/node/2678
Typically, microcode updates are loaded by the BIOS, but not everyone
updates their BIOS when new microcode is released for their CPU.
--
FE
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Fredrik Eriksson wrote:
> Typically, microcode updates are loaded by the BIOS, but not everyone
> updates their BIOS when new microcode is released for their CPU.
Thank you!
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
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] san rr com> 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
|
 |
|  |
|  |
|
 |
|
 |
|  |