As long as there is a way to force it. I hate it when "precautionary = measures" are taken so far as to be absolute (at least as far as that = specific program is concerned)... ----- Original Message -----=20 From: "Galen" <blueandwhiteg3@xxxxxxxxxxxx> To: <kismac@xxxxxxxxxxxxx> Sent: Wednesday, May 21, 2003 7:38 PM Subject: [kismac] Re: Darwin Update in 10.2.6 >=20 > Yes, I am able to build and exchange my own and read the note about=20 > 10.2.5 and all, but I'm considering other people. I know quite a few=20 > people that have, despite the scary messages about the kernel swap=20 > being "suicidal" among other things, do it anyway, mess up their=20 > system, re-install OS X and repeat 2-3x. I'm a computer consultant=20 > doing lots of Mac stuff (as well as web design) and see all these=20 > 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=20 > kernel versions match and require the option key or something else to=20 > be pressed in order to force it to exchange regardless of the kernel=20 > version. Just anything so the user can't possibly not read a message=20 > that explains (in brief) how dangerous switching kernel versions is.=20 > This message could either be in the form of a readme or a dialog box. = I=20 > am assuming that you are trying to develop a mature program that is=20 > relatively usable for the masses and I think this would be very=20 > helpful. And it really wouldn't take much code or effort, either. >=20 > Galen >=20 > On Wednesday, May 21, 2003, at 02:15 PM, N. Karras wrote: >=20 > > > > Who suggested going back a version? > > > > You are not understanding. The KisMAC program tells what version = the =3D > > modified kernel is designed for. If you do not know without = checking =3D > > every time, what version of Mac OS you are running, maybe you=20 > > shouldn't =3D > > be using a utility such as this. And if you knowingly exchange the = =3D > > kernel for a previous version, that's your problem. Maybe you = should =3D > > consider exchanging your own. > > > > > > NPK > > > > > > > > ----- Original Message -----=3D20 > > From: "Galen" <blueandwhiteg3@xxxxxxxxxxxx> > > To: <kismac@xxxxxxxxxxxxx> > > Sent: Wednesday, May 21, 2003 1:16 AM > > Subject: [kismac] Re: Darwin Update in 10.2.6 > > > > > >> =3D20 > >> Well, if I'm not mistaken, Apple updates Darwin for a reason. A lot = > >> of =3D > > > >> people started having kernel panic issues with Darwin 6.5 (USB=3D20 > >> related), many of which were supposed to have been solved with = the=3D20 > >> latest system update (and Darwin 6.6), and going back a version on=20 > >> the =3D > > > >> kernel might not always be a good idea, even if it generally works. > >> =3D20 > >> Would you consider a checking mechanism for KisMAC to prevent=3D20 > >> installing the wrong kernel (causing problems - I know multiple=20 > >> people =3D > > > >> who've whacked out their OS X install by doing this)? And it=20 > >> wouldn't=3D20 > >> hurt if you kept the kernel build up to date with the latest=20 > >> Darwin... =3D > > > >> custom building my kernel isn't nearly as easy as clicking=20 > >> "exchange=3D20 > >> kernel" in KisMAC. > >> =3D20 > >> Galen > >> =3D20 > >> =3D20 > >> On Tuesday, May 20, 2003, at 04:44 AM, Michael Rossberg wrote: > >> =3D20 > >>> hey, > >>> > >>>> Last time I upgraded from 10.2.4 to 10.2.5 and tried the swap =3D > > kernel > >>>> function of KisMAC, I got bitten hard by a bug - they updated =3D > > Darwin > >>>> and KisMAC didn't know about it. I had to re-install OS X. Darwin = =3D > > 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=3D20 > >>>> anybody > >>>> know if KisMAC has been updated with the latest kernel? Also, = have =3D > > you > >>>> ever thought about having KisMAC check the kernel version = *before* > >>>> swapping it to avoid installing an older or newer version and =3D > > 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 = =3D > > 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 > >>> > >>> > >>> > >> > > >