> WA women inmates allege sex assaults
> Seattle, WA, USA
> The Washington state prison system is
> investigating allegations that four male
> guards at the main women's penitentiary
> sexually assaulted two inmates. ...http://seattlepi.nwsource.com/local/64=

> See all stories on this topic:http://news.google.com/news?hl=3Den&ncl=3Dh=

>
> Prison closure postponed
> Escanaba, MI, USA
> "Michigan has the sixth largest prison system,
> a very high rate of recidivism, and long prison
> stays due to mandatory sentencing guidelines....http://www.dailypress.net=

> See all stories on this topic:http://news.google.com/news?hl=3Den&ncl=3Dh=

> ...

> Maxim Sobolev wrote:
>

>> Scott Long wrote:
>>

>>> David O'Brien wrote:
>>>

>>>> On Sat, Jul 08, 2006 at 12:17:19PM -0400, Craig Rodrigues wrote:
>>>>

>>>>> I was thinking of doing something like that. You can basically
>>>>> get the same info by doing something like:
>>>>> file - < /dev/ad0s1e
>>>>> /dev/stdin: Unix Fast File system (little-endian)
>>>>> file - < /dev/ad0s4
>>>>> /dev/stdin: SGI XFS filesystem
>>>>>
>>>>> I leaned away from this approach in mount(8) because:
>>>>> - I didn't want to tie mount(8) to file(1)

>>>>
>>>>
>>>> ...

> Scott Long wrote:
>

>> David O'Brien wrote:
>>

>>> On Sat, Jul 08, 2006 at 12:17:19PM -0400, Craig Rodrigues wrote:
>>>

>>>> I was thinking of doing something like that. You can basically
>>>> get...

> David O'Brien wrote:

>> On Sat, Jul 08, 2006 at 12:17:19PM -0400, Craig Rodrigues wrote:
>>

>>> I was thinking of doing something like that. You can basically
>>> get the same info by doing something like:
>>> file - < /dev/ad0s1e
>>> /dev/stdin: Unix Fast File system (little-endian)
>>> file - < /dev/ad0s4
>>> /dev/stdin: SGI XFS filesystem
>>>
>>> I leaned away from this approach in mount(8) because:
>>> - I didn't want to tie mount(8) to file(1)

>>
>>
>> Why not? We have libmagic for purposes like this.
>>

>
> This is an interesting idea. However, it has the potential to
> add a dependency on /usr to the early boot environment. Maybe it ...

> On Sat, Jul 08, 2006 at 12:17:19PM -0400, Craig Rodrigues wrote:
>

>>I was thinking of doing something like that. You can basically
>>get the same info by doing something like:
>>file - < /dev/ad0s1e
>>/dev/stdin: Unix Fast File system (little-endian)
>>file - < /dev/ad0s4
>>/dev/stdin: SGI XFS filesystem
>>
>>I leaned away from this approach in mount(8) because:
>>- I didn't want to tie mount(8) to file(1)

>
>
> Why not? We have libmagic for purposes like this.
>

> I was thinking of doing something like that. You can basically
> get the same info by doing something like:
> file - < /dev/ad0s1e
> /dev/stdin: Unix Fast File system (little-endian)
> file - < /dev/ad0s4
> /dev/stdin: SGI XFS filesystem
>
> I leaned away from this approach in mount(8) because:
> - I didn't want to tie mount(8) to file(1)

>>lead to all kinds of funnies. Linux does this (iterating all filesystem
>>types in kernel) for the special case of the root filesystem where mount(8)
>>is not available, and it showeds various interesting bugs at least in the
>>fat driver.
>>

>
> How does it resolve situations like with UDF vs iso9660, where both
> structures can co-exist?

> On Mon, Jul 10, 2006 at 01:06:02PM -0600, Scott Long wrote:
>

>>So in your opinion and experience, what are the pros and cons of
>>maintaining a table of magic numbers?

>
>
> The feature is imensely useful. The implementation won't win any
> points for a clean design but works very well in practice. I think
> it's definitly better than probing in the kernel because letting a filesystem
> driver try to make sense of something that's not it's own format can
> lead to all kinds of funnies. Linux does this (iterating all filesystem
> types in kernel) for the special case of the root filesystem where mount(8)
> is not available, and it showeds various interesting bugs at least in the
> fat driver.
>

> On Mon, Jul 10, 2006 at 10:52:33AM +0200, Andre Oppermann wrote:

>> Sam Leffler wrote:

>>>I committed the revised netif cloning api so you can now specify
>>>parameters when cloning. I also modified the vlan code to use this
>>>mechanism so doing something like:
>>>
>>>ifconfig vlan create vlan 1 vlandev em0
>>>

>>
>> /me wants to do:
>>
>> "ifconfig em0.1 inet 192.168.2.2/24"
>>
>> Even simpler. And yes, this works already but only if if_vlan.ko
>> was loaded before or compiled into the kernel. It doesn't do auto-
>> load.

>
> Unless cause ifconfig to autoload all if_ modules when cloning fails,
> it's impossiable to support this without having if_vlan loaded. That ...