Re: /dev/null doesn't get created

From: Derek Tattersall (dlt_at_mebtel.net)
Date: 08/01/04

  • Next message: Mark Murray: "Re: /dev/null doesn't get created" 
    Date: Sun, 1 Aug 2004 17:09:37 -0400
To: Mark Murray <mark@grondar.org>

    * Mark Murray (mark@grondar.org) [040801 17:03]:
    > From: Mark Murray <mark@grondar.org>
    > Message-Id: <200408011825.i71IPZgG018406@grimreaper.grondar.org>
    > To: dlt@mebtel.net
    > Cc: current@FreeBSD.ORG
    > Subject: Re: /dev/null doesn't get created
    > Date: Sun, 01 Aug 2004 19:25:34 +0100
    >
    > Derek Tattersall writes:
    > > CURRENT as of this morning dint'create /dev/null. My previous
    > > CURRENT, from July 25 created it fine so all was well.Can anybody
    > > offer me a clue as to what this is all about? I tried to figure out
    > > what causes /dev/null to get created, but was unsuccessful.
    >
    > BOOBOO of mine. Please always check src/UPDATING for clues :-)
    >
    > M
    > --
    > Mark Murray
    > iumop ap!sdn w,I idlaH

    Well I appear to have cvsup'ed just before you added the text to
    UPDATING. Oh well. That brings up an interesting question: Under
    what circumstances would it be advantageous to not compile the drivers
    into the kernel, but leave them as modules and load from
    /boot/loader.conf? I haven't had any luck imagining why you would
    want to leave them as modules. 

    -- 
Derek Tattersall   | "Don't say yes until I finish talking."   --
                   | Darryl F. Zanuck 
dlt@mebtel.net     | 
                   | 
dlt666@yahoo.com   | 
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Mark Murray: "Re: /dev/null doesn't get created"