Re: 8.x grudges

2010-07-11 Thread M. Warner Losh
In message: Garrett Cooper writes: : On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. wrote: : > 07.07.2010 14:59, Jeremy Chadwick ???(??): : >>> : >>>      FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and : >>>      thus not an "option") -- the kernel-config files, tha

Re: 8.x grudges

2010-07-08 Thread jhell
On 07/08/2010 10:08, Marian Hettwer wrote: > Hi jhell, > > ehm... > > Am 08.07.10 14:46, wrote jhell: > On 07/08/2010 06:54, for whatever Marian Hettwer wrote: > >> I certainly not wrote the text below. That's what, I guess, you wrote. >> Your MUA is defect. >> And honestly, I don't know why th

Re: 8.x grudges

2010-07-08 Thread Marian Hettwer
Hi jhell, ehm... Am 08.07.10 14:46, wrote jhell: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/08/2010 06:54, for whatever Marian Hettwer wrote: I certainly not wrote the text below. That's what, I guess, you wrote. Your MUA is defect. And honestly, I don't know why that's a reply to

Re: 8.x grudges

2010-07-08 Thread jhell
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/08/2010 06:54, for whatever Marian Hettwer wrote: With any major upgrade or release process comes a commitment from the developers and end-users alike that involves a review, testing & release. The release part on the end-users

Re: 8.x grudges

2010-07-08 Thread Mikhail T.
07.07.2010 16:50, Marcel Moolenaar написав(ла): Not to mention that if you change uart(4) to create dev entries like sio(4) after uart(4) has been in the tree for more than 6 years creating ttyu* entries, you actually introduce a gratuitous change. If sio and uart could co-exist, then you'd b

Re: 8.x grudges

2010-07-08 Thread Marian Hettwer
Am 07.07.10 22:52, schrieb Mikhail T.: 07.07.2010 16:34, Randi Harper ???(??): Attached is the kernel config-file (i386), that worked fine under 7.x. The kernel-compile will break (some *freebsd7* structs undefined), without the COMPAT_FREEBSD7 option. Try it for yourself... Don't use

Re: 8.x grudges

2010-07-07 Thread Ken Smith
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/7/10 4:17 PM, Mikhail T. wrote: > 07.07.2010 14:59, Jeremy Chadwick написав(ла): >>> FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and >>> thus not an "option") -- the kernel-config files, that worked with >>> 7.x, br

Re: 8.x grudges

2010-07-07 Thread Garrett Cooper
On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. wrote: > 07.07.2010 14:59, Jeremy Chadwick ???(??): >>> >>>      FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and >>>      thus not an "option") -- the kernel-config files, that worked with >>>      7.x, break without this option in th

Re: 8.x grudges

2010-07-07 Thread Sean Bruno
> > > 5. > > One of the upgraded systems would repeatedly hang at boot, until I > > disabled the on-board firewire-device through the BIOS... It was > > not a problem under 7.x, although I don't know, whether the device > > actually worked. > > This is a commonly-reported p

Re: 8.x grudges

2010-07-07 Thread Sean Bruno
> > > 5. > > One of the upgraded systems would repeatedly hang at boot, until I > > disabled the on-board firewire-device through the BIOS... It was > > not a problem under 7.x, although I don't know, whether the device > > actually worked. > > This is a commonly-reported pr

Re: 8.x grudges

2010-07-07 Thread Garrett Cooper
On Wed, Jul 7, 2010 at 1:52 PM, Mikhail T. wrote: > 07.07.2010 16:34, Randi Harper ???(??): >> >>> Attached is the kernel config-file (i386), that worked fine under 7.x. >>> The >>> kernel-compile will break (some *freebsd7* structs undefined), without >>> the >>> COMPAT_FREEBSD7 option. Try i

Re: 8.x grudges

2010-07-07 Thread Randi Harper
On Wed, Jul 7, 2010 at 1:52 PM, Mikhail T. wrote: > Your "telling" me this is just as valid as warning me against using > computer-cases of a particular color. It is a silly requirement. My > expecting things, that worked for 7, to work in 8 is reasonable. There may > be (documented!) exceptions,

Re: 8.x grudges

2010-07-07 Thread Randi Harper
On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. wrote: > 07.07.2010 14:59, Jeremy Chadwick ???(??): >>> >>>      FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and >>>      thus not an "option") -- the kernel-config files, that worked with >>>      7.x, break without this option in th

Re: 8.x grudges

2010-07-07 Thread Mikhail T.
07.07.2010 16:34, Randi Harper ???(??): Attached is the kernel config-file (i386), that worked fine under 7.x. The kernel-compile will break (some *freebsd7* structs undefined), without the COMPAT_FREEBSD7 option. Try it for yourself... Don't use a kernel config from 7. We've already

Re: 8.x grudges

2010-07-07 Thread Marcel Moolenaar
On Jul 7, 2010, at 1:34 PM, Randi Harper wrote: >> Well, pardon the political pun, but I don't believe in change for the sake >> of change. These particular changes are gratuitous. If sio is no longer >> available -- and replaced by uart, why change the /dev-entries?.. > > These changes aren't gr

Re: 8.x grudges

2010-07-07 Thread Mikhail T.
07.07.2010 14:59, Jeremy Chadwick ???(??): FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and thus not an "option") -- the kernel-config files, that worked with 7.x, break without this option in them (in addition to all the nuisance, that's documented in

Re: 8.x grudges

2010-07-07 Thread Kevin Oberman
> Date: Wed, 07 Jul 2010 14:22:22 -0400 > From: "Mikhail T." > Sender: owner-freebsd-sta...@freebsd.org > > I'm upgrading several systems these days to the 8.1 (pre-release) and > have hit the following troubles... I could file a formal PR for each, I > suppose, but, maybe, this way will get th

8.x grudges

2010-07-07 Thread Mikhail T.
I'm upgrading several systems these days to the 8.1 (pre-release) and have hit the following troubles... I could file a formal PR for each, I suppose, but, maybe, this way will get the right people's attention sooner. In no particular order: 1. A picture, that one of the systems was dis

Re: 8.x grudges

2010-07-07 Thread Jeremy Chadwick
On Wed, Jul 07, 2010 at 02:22:22PM -0400, Mikhail T. wrote: > I'm upgrading several systems these days to the 8.1 (pre-release) > and have hit the following troubles... I could file a formal PR for > each, I suppose, but, maybe, this way will get the right people's > attention sooner. > > 2. >