Date: Mon, 07 Jul 2003 19:57:59 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Karel J. Bosschaart" <K.J.Bosschaart@tue.nl> Cc: current@freebsd.org Subject: Re: how to create device nodes when devfs doesn't do it? Message-ID: <3425.1057600679@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 07 Jul 2003 17:43:14 %2B0200." <20030707154314.GA30526@phys9911.phys.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030707154314.GA30526@phys9911.phys.tue.nl>, "Karel J. Bosschaart" writes: >Hi, > >After googling and searching in the mailing list archive I still can't >figure out how to make device nodes in -current when devfs doesn't do this >automatically. You can't. If the device driver doesn't tell DEVFS to, it's because the device does not exist. >1.6 GB HD) from which I want to mount /dev/da0s4h. It works fine in -stable, >after MAKEDEV'ing the node, but on -current I only get da0s4. My USB flash >drive (Apacer Handysteno) works fine; /dev/da0s1d is created after insertion >of the flash drive (I reformatted it to UFS, but it also worked with msdosfs, >though slower). >Using disklabel on the external USB drive shows some warnings: >phys9911# disklabel da0s4 ># /dev/da0s4: >8 partitions: ># size offset fstype [fsize bsize bps/cpg] >a: 72513 63 4.2BSD 1024 8192 16 >b: 269892 72576 swap >c: 3324825 63 unused 0 0 # "raw" part, don't edit >d: 131544 342468 4.2BSD 1024 8192 16 >e: 49896 474012 4.2BSD 1024 8192 16 >g: 716688 523908 4.2BSD 1024 8192 16 >h: 2084292 1240596 4.2BSD 1024 8192 16 >disklabel: partition c doesn't start at 0! >disklabel: partition c doesn't cover the whole unit! >disklabel: An incorrect partition c may cause problems for standard system utilities > >FWIW, this drive contains an OpenBSD 2.7 installation. All partitioning >was done by the OpenBSD installer. Can you mail me the output of: diskinfo -v da0 diskinfo -v da0s4 dd if=/dev/da0 count=63 | uuencode - openbsd.sect0 dd if=/dev/da0s4 count=16 | uuencode - openbsd.slice4 Then I'll try to see what goes on. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3425.1057600679>