Divine call reply for more information.
新しいメ．襯ドレスをお知らせします新しいメ．襯ドレス： toyoreply2...@yahoo.co.jp Greetings in name of our Lord.I am Mrs Ukadi,69years old widow a Christian, suffering from long time cancer of the blood.I have the sum($5.1m)USD in COTE D'IVOIRE i want to donate it for you to use it to help the poor.Contact me for more information on how you will get my charity donation. - Mrs Ukadi
Re: How to partition magneto-optical disks with sectors of 2048 bytes?
On 03/06/11 02:25, Matthew Dempsky wrote: On Sat, Mar 5, 2011 at 7:20 AM, Jens A. Griepentrog griep...@wias-berlin.de wrote: What went wrong? The procedure works for usual hard disks and memory sticks with sectors of 512 bytes. I would be grateful for any hint. (As a final aim I would like to have some bootable magneto-optical disk with root partition a: and two more partitions d: and e: ...) When you say The procedure works for usual hard disks and memory sticks [...], do you mean it works on this same system when attached to the same ahc(4) controller? E.g., if you replace this sd0 with a standard SCSI disk, will the same set of fdisk/disklabel/newfs commands work correctly? Thanks, Matthew, I just checked this again with some 16-year old SCSI disk to give a rigorous proof of my above statement: ... ahc0 at pci6 dev 2 function 0 vendor Adaptec, unknown product 0x0082 rev 0x02: apic 7 int 21 (irq 3) scsibus0 at ahc0: 8 targets, initiator 7 sd0 at scsibus0 targ 4 lun 0: QUANTUM, FIREBALL1080S, 1Q09 SCSI2 0/direct fixed sd0: 1042MB, 512 bytes/sec, 2134305 sec total ... Here, the same set of commands works successfully: # fdisk sd0 Disk: sd0 geometry: 132/255/63 [2134305 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused # fdisk -i sd0 Do you wish to write new MBR and partition table? [n] y Writing MBR at offset 0. # fdisk sd0 Disk: sd0 geometry: 132/255/63 [2134305 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 2 -131 254 63 [ 64: 2120516 ] OpenBSD # disklabel -E sd0 Label editor (enter '?' for help at any prompt) p OpenBSD area: 64-2120580; size: 2120516; free: 2120516 #size offset fstype [fsize bsize cpg] c: 21343050 unused a e offset: [64] size: [2120516] FS type: [4.2BSD] w q No label changes. # disklabel sd0 # /dev/rsd0c: type: SCSI disk: SCSI disk label: FIREBALL1080S uid: 6e33f59301aa59ca flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 132 total sectors: 2134305 boundstart: 64 boundend: 2120580 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c: 21343050 unused e: 2120512 64 4.2BSD 2048 163841 # newfs /dev/rsd0e /dev/rsd0e: 1035.4MB in 2120512 sectors of 512 bytes 6 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each super-block backups (for fsck -b #) at: 32, 414688, 829344, 1244000, 1658656, 2073312, # mount /dev/sd0e /mnt # mount /dev/sd1a on / type ffs (local) /dev/sd1d on /home type ffs (local, nodev, nosuid, softdep) mfs:12008 on /tmp type mfs (asynchronous, local, nodev, nosuid, size=2097152 512-blocks) /dev/sd2d on /usr type ffs (local, nodev, softdep) /dev/sd2e on /var type ffs (local, nodev, nosuid, softdep) /dev/sd0e on /mnt type ffs (local) # umount /mnt By the way, I also tried to add the sector-size option -S 2048 to the newfs command on the MO disk but without any success. Jens
Re: MacBook pro compatibility
Hey Luis, I just booted 4.8 up on my MBP ( first release of the unibody ). The broadcom interface is not recognized. Ethernet works tho. Cheers, Aaron On Fri, Mar 4, 2011 at 8:35 AM, Luis Useche use...@gmail.com wrote: Hi Guys, I was wondering if anybody is using the last macbook pro with OpenBSD. They come with an intel or ati video device now which I guess make it more compatible. My main concern was about the wireless net device. I think it comes with a broadcom by default that, as far as I know, is not supported in OBSD. Is anybody using this laptop with OBSD? Luis.
Re: How to partition magneto-optical disks with sectors of 2048 bytes?
On Sun, Mar 06, 2011 at 04:14:33PM +0100, Jens A. Griepentrog wrote: On 03/06/11 02:25, Matthew Dempsky wrote: [...] Jens A. Griepentrog griep...@wias-berlin.de wrote: What went wrong? The procedure works for usual hard disks and memory sticks with sectors of 512 bytes. I would be grateful for any hint. (As a final aim I would like to have some bootable magneto-optical disk with root partition a: and two more partitions d: and e: ...) When you say The procedure works for usual hard disks and memory sticks [...], do you mean it works on this same system when attached to the same ahc(4) controller? E.g., if you replace this sd0 with a standard SCSI disk, will the same set of fdisk/disklabel/newfs commands work correctly? Thanks, Matthew, I just checked this again with some 16-year old SCSI disk to give a rigorous proof of my above statement: ... ahc0 at pci6 dev 2 function 0 vendor Adaptec, unknown product 0x0082 rev 0x02: apic 7 int 21 (irq 3) scsibus0 at ahc0: 8 targets, initiator 7 sd0 at scsibus0 targ 4 lun 0: QUANTUM, FIREBALL1080S, 1Q09 SCSI2 0/direct fixed sd0: 1042MB, 512 bytes/sec, 2134305 sec total ... a e offset: [64] ^^ That was 32 in your earlier example. Did you try some appropriately-large offsets? (AFAIK, that shouldn't help, but maybe the first sectors are magical or maybe the disk barfs on unaligned access?) Joachim
BSDCan 2011 - schedule released
The list of talks and speakers for BSDcan 2011 has been released. For 2011, we once again have a strong collection of talks that will appeal to a wide range of attendees. Registration will open later this week. Be sure to start making your travel plans. http://www.bsdcan.org/2011/schedule/ We also have a Facebook and Twitter pages. Please help us to spread the word. http://www.facebook.com/group.php?gid=272755641371 http://www.twitter.com/bsdcan -- Dan Langille - http://langille.org/
Mounting NTFS, Invalid argument
Hi, When I attempt to mount a NTFS-formatted external drive, it fails: # mount -t ntfs /dev/sd2i /media/usb/ mount_ntfs: /dev/sd2i on /media/usb: Invalid argument There is a note about this under BUGS in mount_ntfs(8): If the attempt to mount NTFS gives you an error like this: # mount -t ntfs /dev/wd0k /mnt mount_ntfs: /dev/wd0k on /mnt: Invalid argument make sure that the appropriate partition has the correct entry in the disk label, particularly that the partition offset is correct. If the NTFS partition is the first partition on the disk, the offset should be '63' (see disklabel(8)). However, disklabel already says 63 for the argument, so this seems not to apply. Also, the size entry matches fdisk output and the type is (obviously) NTFS. Any ideas of what to debug? Is this a PEBKAC? fdisk: Disk: sd2 geometry: 14593/255/63 [234441648 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 07 0 1 1 - 14592 254 63 [ 63: 234436482 ] NTFS 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused disklabel: # /dev/rsd2c: type: SCSI disk: SCSI disk label: HM121HC duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14593 total sectors: 234441648 boundstart: 0 boundend: 234441648 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:2344416480 unused i:234436482 63NTFS
Re: Mounting NTFS, Invalid argument
NTFS support is not enabled in the GENERIC kernel. -Otto On Sun, Mar 06, 2011 at 10:18:45PM -0700, Anthony J. Bentley wrote: Hi, When I attempt to mount a NTFS-formatted external drive, it fails: # mount -t ntfs /dev/sd2i /media/usb/ mount_ntfs: /dev/sd2i on /media/usb: Invalid argument There is a note about this under BUGS in mount_ntfs(8): If the attempt to mount NTFS gives you an error like this: # mount -t ntfs /dev/wd0k /mnt mount_ntfs: /dev/wd0k on /mnt: Invalid argument make sure that the appropriate partition has the correct entry in the disk label, particularly that the partition offset is correct. If the NTFS partition is the first partition on the disk, the offset should be '63' (see disklabel(8)). However, disklabel already says 63 for the argument, so this seems not to apply. Also, the size entry matches fdisk output and the type is (obviously) NTFS. Any ideas of what to debug? Is this a PEBKAC? fdisk: Disk: sd2 geometry: 14593/255/63 [234441648 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 07 0 1 1 - 14592 254 63 [ 63: 234436482 ] NTFS 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused disklabel: # /dev/rsd2c: type: SCSI disk: SCSI disk label: HM121HC duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14593 total sectors: 234441648 boundstart: 0 boundend: 234441648 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:2344416480 unused i:234436482 63NTFS
Re: Mounting NTFS, Invalid argument
On Mon, Mar 07, 2011 at 07:57:56AM +0100, Otto Moerbeek wrote: NTFS support is not enabled in the GENERIC kernel. Oops, I may be wrong. It is enabled on recent i386 and amd64 kernels. But since you neglect to give us a dmesg, we cannot tell if it is actually enable on your machine. -Otto On Sun, Mar 06, 2011 at 10:18:45PM -0700, Anthony J. Bentley wrote: Hi, When I attempt to mount a NTFS-formatted external drive, it fails: # mount -t ntfs /dev/sd2i /media/usb/ mount_ntfs: /dev/sd2i on /media/usb: Invalid argument There is a note about this under BUGS in mount_ntfs(8): If the attempt to mount NTFS gives you an error like this: # mount -t ntfs /dev/wd0k /mnt mount_ntfs: /dev/wd0k on /mnt: Invalid argument make sure that the appropriate partition has the correct entry in the disk label, particularly that the partition offset is correct. If the NTFS partition is the first partition on the disk, the offset should be '63' (see disklabel(8)). However, disklabel already says 63 for the argument, so this seems not to apply. Also, the size entry matches fdisk output and the type is (obviously) NTFS. Any ideas of what to debug? Is this a PEBKAC? fdisk: Disk: sd2 geometry: 14593/255/63 [234441648 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: 07 0 1 1 - 14592 254 63 [ 63: 234436482 ] NTFS 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused disklabel: # /dev/rsd2c: type: SCSI disk: SCSI disk label: HM121HC duid: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 14593 total sectors: 234441648 boundstart: 0 boundend: 234441648 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:2344416480 unused i:234436482 63NTFS
Re: Mounting NTFS, Invalid argument
Am 07.03.2011 07:57, schrieb Otto Moerbeek: NTFS support is not enabled in the GENERIC kernel. CVS says that it is enabled. Kind regards, Markus
