Re: how to create device nodes when devfs doesn't do it?

2003-07-08 Thread Karel J. Bosschaart
On Mon, Jul 07, 2003 at 07:57:59PM +0200, Poul-Henning Kamp wrote:
 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.

Sure, see below. Because I messed around with the drive, the partitions
changed (new disklabel output also included), but the problem remains exactly
the same. I noticed that on a -stable system the c partition does start
at 0, according to disklabel.

Karel.

phys9911# disklabel da0s4
# /dev/da0s4:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
a:   165249   634.2BSD 1024  819216
b:   612864   165312  swap
c:  3326337   63unused0 0 # raw part, don't edit
d:   165312   7781764.2BSD 1024  819216
e:   165312   9434884.2BSD 1024  819216
g:   717696  11088004.2BSD 1024  819216
h:  1499904  18264964.2BSD 1024  819216
partition c: partition extends past end of unit
disklabel: partition c doesn't start at 0!
disklabel: An incorrect partition c may cause problems for standard system utilities
partition h: partition extends past end of unit
phys9911#

phys9911# diskinfo -v da0
da0
512 # sectorsize
1704665088  # mediasize in bytes
3329424 # mediasize in sectors
207 # Cylinders according to firmware.
255 # Heads according to firmware.
63  # Sectors according to firmware.

phys9911# diskinfo -v da0s4
da0s4
512 # sectorsize
1703084544  # mediasize in bytes
3326337 # mediasize in sectors
207 # Cylinders according to firmware.
255 # Heads according to firmware.
63  # Sectors according to firmware.

phys9911# dd if=/dev/da0 count=63 | uuencode -o openbsd.sect0 -
63+0 records in
63+0 records out
32256 bytes transferred in 0.320866 secs (100528 bytes/sec)
phys9911# dd if=/dev/da0s4 count=16 | uuencode -o openbsd.slice4 -
16+0 records in
16+0 records out
8192 bytes transferred in 0.097826 secs (83741 bytes/sec)
phys9911#

begin 644 -
M9NH(P`,R/J.T:\_/\``/N.V:XH```([`9C'V9C'[EMAIL PROTECTED]/.D
M9NHUH`[EMAIL PROTECTED][EMAIL PROTECTED]';@;[EMAIL PROTECTED]
MP!FOKX!``!FN00```*1``\@'039H/$.+S9KXR`0``Z%$`^O3K_%)T(/@
M#X/(,*+X`(G(2(/P`X/@#X/(,*(%`5B*=`+3`**1`1FN`$```QV\T3PMF
MOB4!``#H$P#KP:^ZP```.@(`;J`'P`4/RLA,!T$F;[EMAIL PROTECTED]
M#C';0\T06UAFPU5S:6YG($1R:79E.B!8(%!AG1I=EO;[EMAIL PROTECTED]4B!O
M;B!F;]P'D@;W(@;VQD($))3U,-@!296%D(5R[EMAIL PROTECTED]:79E
M('!AG1I=EO;@T*`$EN=F%L:[EMAIL PROTECTED];F%T=7)E#0H`D```
M
M``$`
M```!`0`
M`0$`IC__.#\```!P3(`5:I715:!0```%D,G,Q
M``(``#\DO`4``-P(``0S3(0
[EMAIL PROTECTED]
M``!715:J=L([EMAIL PROTECTED](```
M``0S3(`
M`)#-,@X`
M
M
M
M
M
M`.L.0E18`0[EMAIL PROTECTED]@
M!P`0``#Z,.T+P`([`CMAF:@)FG;\`'[EMAIL PROTECTED]:LF)'C':R2K9.M
[EMAIL PROTECTED],+B06(=0*(504%!`-?0CB[.OQD4%,9%!#10TQD5F:[EMAIL PROTECTED]
M``\!'G:6#P$6)8/(,[EMAIL PROTECTED]@!#R+`ZG^0``QR;$0CMQ.`\`V;[EMAIL PROTECTED]
M!1,$``#!X`HM`!```G0L3-14@[EMAIL PROTECTED]:BO_-0R0``!145%14K$':@#B_$'
M'P^A#ZG/^KP#R#`,EFZM:0`Q(([1CMF.P8[ACNE(#R+`ZNN0```Q
MP([0CMB['#HP`/`1Y\EOOV!@0`73^9\%@[EMAIL PROTECTED](5#DH5P
M$[EMAIL PROTECTED](V.8AB/CFH;`$YBP`N:AL`'F(:A6.:A6.8AP_1J`.M`:@'K/H#
MZSAJ!.LT:@7K,HZRQJ!^LH:@CK+H*ZRAJ^LD:@SK(H-ZPAJ#NL8:A#K
M#/9$)!([EMAIL PROTECTED]/\T),9$)`0`_!X8+`]D0D.@)U`^H#Z`!K`9H-\
M)$0([EMAIL PROTECTED]/]T)%#^R'7X:A`?'@)[EMAIL PROTECTED]`#``!
MZ/@#``-90880[EMAIL PROTECTED]'^__^-90(S_P!XU5/(LUI!\``*V)\X7`
M=6_`*```(M'(D$'XU\!PCV1_H$=`+13!FB488C5X0A]:Q!/.EB=:-?2BQ
M!/.EB=ZQ!?.EB36D'P``88UD)`@''P^A#ZG/_H0'V)[EMAIL PROTECTED]
M_C')L0(QP*P\9G4$L03K]SST=0V!_CR1``!U3NET/`]UX`^('4@'X!
MP'1%//IT2SS[=$T/MUTXP,$4P-=-(M5,#R=$$\G718/,T/A,H\SW0]
M6V'IT_[__XE5,%HITXE=-G^B74H88UD)`C/#R#`B441D;KZX!E,?WKY8!-
M,0+KWRG+@/D$=`%FB1/KS0^W,P^WP*-6P2)?2PQ_X#Y!'0#B=!FBP,!RR7_
MCB``@(`=__+KH%!35EQP#';BW4$BUT\9HGPP,$`.*0Q2*8Q?!X!!F
MBT,2B:*0QR*8Q_!X!!FBT,:B!U$QR6:+31C!X0'SI%E?7EM8QD4=`(#B
[EMAIL PROTECTED]'DE1_?__K#P9=.\\%74B4(M%'(#\AW4#6.N,9CU33W4/
[EMAIL 

how to create device nodes when devfs doesn't do it?

2003-07-07 Thread Karel J. Bosschaart
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. I have an external USB-drive (external 3.5 case with leftover 
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   offsetfstype   [fsize bsize bps/cpg]
a:72513   634.2BSD 1024  819216
b:   26989272576  swap
c:  3324825   63unused0 0 # raw part, don't edit
d:   131544   3424684.2BSD 1024  819216
e:49896   4740124.2BSD 1024  819216
g:   716688   5239084.2BSD 1024  819216
h:  2084292  12405964.2BSD 1024  819216
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.

Any suggestion? (Apart from newfs...)

Karel.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: how to create device nodes when devfs doesn't do it?

2003-07-07 Thread walt
Karel J. Bosschaart wrote:
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.  I have an external USB-drive (external 3.5 case with leftover
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. 


Have you tried mounting da0s4h?  It may show up in /dev after mounting it.


Using disklabel on the external USB drive shows some warnings:

phys9911# disklabel da0s4
# /dev/da0s4:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
a:72513   634.2BSD 1024  819216
b:   26989272576  swap
c:  3324825   63unused0 0 # raw part, don't edit
d:   131544   3424684.2BSD 1024  819216
e:49896   4740124.2BSD 1024  819216
g:   716688   5239084.2BSD 1024  819216
h:  2084292  12405964.2BSD 1024  819216
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


My experience is that these warnings can be ignored as long as the drive
will mount.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]