Kendrick Myatt wrote:
>
> I have one box that is still Debian 1.2, can I upgrade to hamm
> directly, or should I go to bo first? Unfortunately this is not a
> test machine, so I can't afford to have it crashed. What's the best
> route for something like this?
My personal opinion is not
On Thu, 11 Jun 1998, Kendrick Myatt wrote:
> I have one box that is still Debian 1.2, can I upgrade to hamm
> directly, or should I go to bo first? Unfortunately this is not a
> test machine, so I can't afford to have it crashed. What's the best
> route for something like this?
I have simulate
On Wed, Apr 15, 1998 at 09:16:57PM +0300, Jaakko Niemi wrote:
> >> I have 2.0.33 running on an ABIT IT5H 2.0, K6-233 w/ 64 megs of RAM.
>
> I think that motherboard is based on the TX chipset, which does not cache
> any memory over 64mb. So adding more than that is most propably worse.
It's b
>> On Wed, Apr 15, 1998 at 12:29:39AM -0700, George Bonser wrote:
>> > There are some rather severe problems with memory corruption. Generally,
>> > you will only see them on busy systems. Other problems include memory
>> > leaks, filesystem problems and system hangs. There are also networking
>>
>>
>> And some 2.0.33 systems (mine at least) are quite stable with hamm.
>>
>> Bob
>>
>
>Quite possible if it only runs a few hours/day or is lightly loaded. I
>would consider it a ticking timebomb, though. One particular system of
>
we have quite a few systems running 2.0.33 up 24/7 with ple
Wow thanx
It turns out that MY CPU has a metal heat sink with a fan attached
but no heat sink grease (I will add some)
as fo r the memory
About a month back my memory went bad (2 days after a pwer
failure...I runa UPS now -- 1.5 KVA..its nice) and I grabbed 32
MB out of an old Pentium
Jeff Noxon wrote:
> to 2.0.32 or 34pre? My K6 is one of the ">32M bug free" ones.
>
You have me a bit worried
I posted last night (througha friend) and a littlwe while ago about a
major hardware problem
When I replaced my motherboard I also got some more RAM...
my new motherboard has 1
On Wed, Apr 15, 1998 at 10:39:40AM -0700, George Bonser wrote:
> On Wed, 15 Apr 1998, Jeff Noxon wrote:
>
> > I have 2.0.33 running on an ABIT IT5H 2.0, K6-233 w/ 64 megs of RAM.
> > It's rock solid, but when I add another 64 megs, things start to segfault
> > all over the place. Is that a sympto
On Wed, 15 Apr 1998, George Bonser wrote:
>
>
> On Wed, 15 Apr 1998, Chris wrote:
>
> > I am, however, conserned about stablility...
> >
> > Does anyone know of any major problems with a hamm system?
> >
> > Chris
>
> Only on systems that have run 2.0.33. All systems running 2.0.32 are
> fi
On Wed, Apr 15, 1998 at 12:29:39AM -0700, George Bonser wrote:
> There are some rather severe problems with memory corruption. Generally,
> you will only see them on busy systems. Other problems include memory
> leaks, filesystem problems and system hangs. There are also networking
> issues. 2.0.3
I was in the same position as you as of yesterday. I upgraded,
although, i had to use the upgrade script three times (well just to make sure, I
only needed to do it twice) for dependencies. However, I could not figure out
how to reexecute the script installation after the first time, so I
On Wed, 15 Apr 1998, Angel Vicente Perez wrote:
> > Only on systems that have run 2.0.33. All systems running 2.0.32 are
> > fine. There are none of the problems that Red Hat has been having with
> > its 5.0 release.
>
> I'd like more info about kernel 2.0.33. We have a linux box running 2.0.
> Only on systems that have run 2.0.33. All systems running 2.0.32 are
> fine. There are none of the problems that Red Hat has been having with
> its 5.0 release.
I'd like more info about kernel 2.0.33. We have a linux box running 2.0.33 and
nearly all packets from hamm, and I afraid...
--
To
Bill Leach <[EMAIL PROTECTED]> writes:
> Also, if you installed the specially compiled for bo bash 2.01 package
> be CERTAIN that you look back through the recent archives (this month)
> for note about the upgrade process -- the upgrade WILL fail.
Specifically, check
http://www.debian.org/Lists-A
Currently the best way to do what you want to do _IS_ to upgrade as
opposed to do a reinstall.
You want to use the 'autoup.sh' script file to start the process. Note
that the 'mountable' access method might still have some problems
intitially when you use dselect (after the autoup.sh has complete
the short answer is "maybe yes, maybe no". read on if you want the long
answer :-)
On Fri, 30 Jan 1998, Kirstin S. Reese wrote:
> Is it worthwhile to upgrade to hamm now, or should I wait till it is
> released?
that depends entirely on how well you deal with dselect/dpkg problems.
on the whol
16 matches
Mail list logo
