[kismac] Re: Darwin Update in 10.2.6

  • From: Galen <blueandwhiteg3@xxxxxxxxxxxx>
  • To: kismac@xxxxxxxxxxxxx
  • Date: Wed, 21 May 2003 16:38:42 -0700

Yes, I am able to build and exchange my own and read the note about 
10.2.5 and all, but I'm considering other people. I know quite a few 
people that have, despite the scary messages about the kernel swap 
being "suicidal" among other things, do it anyway, mess up their 
system, re-install OS X and repeat 2-3x. I'm a computer consultant 
doing lots of Mac stuff (as well as web design) and see all these 
users. I know they're being stupid and it's at their own risk and all, 
but it wouldn't be hard to refuse to exchange the kernel unless the 
kernel versions match and require the option key or something else to 
be pressed in order to force it to exchange regardless of the kernel 
version. Just anything so the user can't possibly not read a message 
that explains (in brief) how dangerous switching kernel versions is. 
This message could either be in the form of a readme or a dialog box. I 
am assuming that you are trying to develop a mature program that is 
relatively usable for the masses and I think this would be very 
helpful. And it really wouldn't take much code or effort, either.

Galen

On Wednesday, May 21, 2003, at 02:15 PM, N. Karras wrote:

>
> Who suggested going back a version?
>
> You are not understanding.  The KisMAC program tells what version the =
> modified kernel is designed for.  If you do not know without checking =
> every time, what version of Mac OS you are running, maybe you 
> shouldn't =
> be using a utility such as this.  And if you knowingly exchange the =
> kernel for a previous version, that's your problem.  Maybe you should =
> consider exchanging your own.
>
>
> NPK
>
>
>
> ----- Original Message -----=20
> From: "Galen" <blueandwhiteg3@xxxxxxxxxxxx>
> To: <kismac@xxxxxxxxxxxxx>
> Sent: Wednesday, May 21, 2003 1:16 AM
> Subject: [kismac] Re: Darwin Update in 10.2.6
>
>
>> =20
>> Well, if I'm not mistaken, Apple updates Darwin for a reason. A lot 
>> of =
>
>> people started having kernel panic issues with Darwin 6.5 (USB=20
>> related), many of which were supposed to have been solved with the=20
>> latest system update (and Darwin 6.6), and going back a version on 
>> the =
>
>> kernel might not always be a good idea, even if it generally works.
>> =20
>> Would you consider a checking mechanism for KisMAC to prevent=20
>> installing the wrong kernel (causing problems - I know multiple 
>> people =
>
>> who've whacked out their OS X install by doing this)? And it 
>> wouldn't=20
>> hurt if you kept the kernel build up to date with the latest 
>> Darwin... =
>
>> custom building my kernel isn't nearly as easy as clicking 
>> "exchange=20
>> kernel" in KisMAC.
>> =20
>> Galen
>> =20
>> =20
>> On Tuesday, May 20, 2003, at 04:44 AM, Michael Rossberg wrote:
>> =20
>>> hey,
>>>
>>>> Last time I upgraded from 10.2.4 to 10.2.5 and tried the swap =
> kernel
>>>> function of KisMAC, I got bitten hard by a bug - they updated =
> Darwin
>>>> and KisMAC didn't know about it. I had to re-install OS X. Darwin =
> went
>>>> from 6.3 to 6.5. Now, with the release of 10.2.6, Darwin has been
>>>> updated to 6.6. I'd rather not test this on my system, but does=20
>>>> anybody
>>>> know if KisMAC has been updated with the latest kernel? Also, have =
> you
>>>> ever thought about having KisMAC check the kernel version *before*
>>>> swapping it to avoid installing an older or newer version and =
> creating
>>>> all kinds of issues?
>>>
>>> i did not think about it, because usually this is working. the jump
>>> from .5 to .6 causes no problems. the same with .3 and .4, but they
>>> must have changed some critical in .5, which caused the problems. i
>>> added a warning, but i do not want to tell the people what they =
> shall
>>> do.... because sometimes it makes sense to exchange a newer kernel
>>>
>>> mick
>>>
>>>
>>> -- Binary/unsupported file stripped by Ecartis --
>>> -- Type: application/octet-stream
>>> -- File: PGP.sig
>>>
>>>
>>>
>>
>


Other related posts: