Re: /dev/null doesn't get created

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 08/03/04

  • Next message: Mike Hunter: "Re: panic from July 21 kernel (acpi related?)"
    To: freebsd-current@FreeBSD.org, dlt@mebtel.net
    Date: Mon, 2 Aug 2004 18:38:44 -0400
    
    

    On Sunday 01 August 2004 05:09 pm, Derek Tattersall wrote:
    > * 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.

    It's a preference thing. I pretty much never use modules myself (things
    compiled into the kernel are more optimized, mutex and atomic ops are inlined
    rather than function calls for example) unless doing development on a device
    driver in which case I leave the device driver as a single module.

    -- 
    John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
    "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
    _______________________________________________
    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: Mike Hunter: "Re: panic from July 21 kernel (acpi related?)"

    Relevant Pages

    • Compiling the drivers for a ADSL Modem (IceData500)
      ... My modem model is IceData500 and the vendor says it is compatible with RH ... The unicorn driver is a standard Linux ... PPPoE, PPPoA or RFC2684 protocols, the kernel may need to be patched. ... To compile the drivers, ...
      (Fedora)
    • Re: modules load
      ... The Handbook is not so clear about what you must compile ... > kernel, ... modules (the nVidia graphics driver is a good example of the latter). ... system sources, you can just look at the source code for each driver ...
      (freebsd-questions)
    • Re: Problems with kernel: no sound, printer, cdwriter
      ... Compile them, install them and then load the module. ... kernel, not as module. ... > Journalled Block Device driver loaded ...
      (Debian-User)
    • Re: Back to ubuntu
      ... but not in regular ubuntu 6.06 or any other version of ubuntu? ... so i attempted to compile the drivers on ubuntu 7.04, ... that under kubuntu 6.06 you were using a compatible kernel, ... unless you figure out how to get the driver to compile. ...
      (Ubuntu)
    • Re: kernel? 2.4.x vs 2.6.x
      ... Sorry about the contractions. ... > compile a new kernel and then compile the driverfrom ... this fails w.o custom kernel and I couldn't get syskonnects ... > driver to compile at all which googling suggested) This was all a good ...
      (Debian-User)