Re: Custom /bsd.rd to send in dmesgs?
On 08/06/06, Nick Holland <[EMAIL PROTECTED]> wrote: vladas wrote: > Will devs ignore dmesgs from /bsd.rd that would resemble the -current > GENERIC > /bsd (if it is possible to do so)? > > I want to send in a few dmesgs from the machines where I cannot install > OpenBSD, so I thought /bsd.rd would help. There are a lot of reasons why developers want the dmesgs -- a major reason is to find out how the GENERIC kernel sees the hardware, another is to get reports of how it actually works with that hardware. A custom kernel does neither of those tasks. Simply booting bsd.rd (even an official one) doesn't answer either very well...what happens if a probe of something in GENERIC that isn't in bsd.rd causes the machine to lock? What happens if the disk interface is properly recognized..but doesn't work properly? You would never know if you didn't actually do the install. The lack of a "didn't work!" message might cause someone to think it did... Perhaps even more tantalizing, what if a problem IS seen in the dmesg...if you can't install, you can't test a fix. So..I suspect you won't get a lot of excited responses from developers, in general. Or I could be wrong... Nick, Thank you for the reply. I wiill send in only from the machines that I can do full install in. Nick.
Re: Custom /bsd.rd to send in dmesgs?
vladas wrote: Will devs ignore dmesgs from /bsd.rd that would resemble the -current GENERIC /bsd (if it is possible to do so)? I want to send in a few dmesgs from the machines where I cannot install OpenBSD, so I thought /bsd.rd would help. There are a lot of reasons why developers want the dmesgs -- a major reason is to find out how the GENERIC kernel sees the hardware, another is to get reports of how it actually works with that hardware. A custom kernel does neither of those tasks. Simply booting bsd.rd (even an official one) doesn't answer either very well...what happens if a probe of something in GENERIC that isn't in bsd.rd causes the machine to lock? What happens if the disk interface is properly recognized..but doesn't work properly? You would never know if you didn't actually do the install. The lack of a "didn't work!" message might cause someone to think it did... Perhaps even more tantalizing, what if a problem IS seen in the dmesg...if you can't install, you can't test a fix. So..I suspect you won't get a lot of excited responses from developers, in general. Or I could be wrong... Nick.
Custom /bsd.rd to send in dmesgs?
Will devs ignore dmesgs from /bsd.rd that would resemble the -current GENERIC /bsd (if it is possible to do so)? I want to send in a few dmesgs from the machines where I cannot install OpenBSD, so I thought /bsd.rd would help.
