Re: SAS scsibus target numbering

2012-07-27 Thread Brett Lymn
On Fri, Jul 27, 2012 at 09:49:38AM +1000, Simon Burge wrote: > > > > ISTR SPARC machines used an initiator address 6 for hysterical reasons. I > > forget why. > > Likewise for some early models of DECstation (2100 and 3100?). I never > understood why. > Priorities. When negotiating for the

Re: Core statement on directory naming for kernel modules

2012-07-27 Thread John Nemeth
On Dec 17, 1:58pm, Matthew Mondor wrote: } On Fri, 27 Jul 2012 13:57:52 + (UTC) } Geoff Wing wrote: } > John Nemeth typed: } > : .. Being able to properly unload a built-in module would be a nice } > : feature. } > } > This sounds a bit like a possible security problem, though presumab

Re: Core statement on directory naming for kernel modules

2012-07-27 Thread Matthew Mondor
On Fri, 27 Jul 2012 13:57:52 + (UTC) Geoff Wing wrote: > John Nemeth typed: > : .. Being able to properly unload a built-in module would be a nice > : feature. > > This sounds a bit like a possible security problem, though > presumably/hopefully > limited by the current security level

Re: fss: Inappropriate ioctl for device (on dk*)

2012-07-27 Thread Edgar Fuß
This code in fssconfig.c looks suspicious to me: if ((xflag || istmp) && isreg) fss.fss_flags |= FSS_UNLINK_ON_CREATE; else fss.fss_flags = 0; Shouldn't that "|=" be a "="?

fss: Inappropriate ioctl for device (on dk*)

2012-07-27 Thread Edgar Fuß
Now, additionally to fssconfig -c not working at all for me (it does work without "-c"), it now looks that it doesn't work on wedges: fssconfig CALL open(0x7f7fdbb0,2,0) fssconfig NAMI "/dev/rfss0" fssconfig RET open 3 fssconfig CALL ioctl(3,FSSIOCSET,0x7f7fdbf0) fssconfig GIO fd 3

Re: Core statement on directory naming for kernel modules

2012-07-27 Thread Geoff Wing
John Nemeth typed: : .. Being able to properly unload a built-in module would be a nice : feature. This sounds a bit like a possible security problem, though presumably/hopefully limited by the current security level and AAA. Regards, Geoff

Re: raid1: unable to open device, error = 16

2012-07-27 Thread Edgar Fuß
> I think that opendisk should do something like this: Yes.

Re: raid1: unable to open device, error = 16

2012-07-27 Thread Alan Barrett
On Thu, 26 Jul 2012, matthew green wrote: library functions like opendisk() will look for a file-path of the given name before trying other names. that tends to make them use the block dev when you want the char dev. eg, compare the ktrace for "newfs raid1d" when you are in/not in /dev. I thi

Re: total sector size in disklabel != the size of raid

2012-07-27 Thread Edgar Fuß
> Or does the warning disappear as soon as I have a GPT on the RAID > (atm, I have neither an MBR nor a disklabel nor a GPT on it)? No, it doesn't. I dont't know whether I have made myself sufficiently clear: What annoys me is that I get a warning I can't do anything about and despite having don