Re: Partition confusion
On Sat, Jun 06, 2009 at 09:10:28AM -0400, Donald Allen wrote: I've got OpenBSD 4.5 installed on a Thinkpad X61, dual-booted with Windows XP. XP is at the beginning of the disk, starting at sector 63. The XP slice, to use BSD terminology, is about 10 Gb (the disk is 100 Gb). The OpenBSD slice occupies the rest of the disk. During the OpenBSD install, I created partitions a, b, d, e, f, and g for the mountpoints /, swap, /tmp, /var, /usr, and /home. I don't believe there was any interaction regarding the XP slice during the install. Now I want to mount the XP (ntfs) partition. So, having created /mnt/windows as root, I tried r...@sophie:/mnt$ mount -t ntfs /dev/sd0i windows mount_ntfs: /dev/sd0i on /mnt/windows: Operation not supported So I did r...@sophie:/mnt$ disklabel sd0 # Inside MBR partition 1: type A6 start 20487600 size 174877920 # /dev/rsd0c: type: ESDI disk: ad4s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 12161 total sectors: 195371568 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0# microseconds drivedata: 0 8 partitions: #size offset fstype [fsize bsize cpg] a: 316575 20487600 4.2BSD 2048 163841 b: 2104515 20804175swap c:1953715680 unused d: 321300 22908690 4.2BSD 2048 163841 e: 176715 23229990 4.2BSD 2048 163841 f: 12594960 23406705 4.2BSD 2048 163841 g:159364800 36001665 4.2BSD 2048 163841 disklabel: warning, unused partition i: size 7148239195883 offset 17551383986520 disklabel: warning, unused partition j: size 238106791916026 offset 211716520590544 disklabel: warning, unused partition k: size 163974838534045 offset 206347192303801 disklabel: warning, unused partition l: size 271451018559616 offset 5237774174023 disklabel: warning, unused partition m: size 190849433245138 offset 190845464470417 disklabel: warning, unused partition n: size 211668966116211 offset 5864912221576 disklabel: warning, unused partition o: size 17630285786338 offset 76717108839878 disklabel: warning, unused partition p: size 17136519487675 offset 217832169078968 So partition i in the actual label does not describe the XP partition. But the default label does r...@sophie:/mnt$ disklabel -d sd0 # Inside MBR partition 1: type A6 start 20487600 size 174877920 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST9100821AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 240 sectors/cylinder: 15120 cylinders: 12921 total sectors: 195371568 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0# microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:1953715680 unused i: 20487537 63NTFS So I tried disklabel -cd sd0 thinking that this would set the in-memory copy of the label to the default and then I'd be able to mount /dev/sd0i. No luck -- same error: Operation not supported. Would someone please unconfuse me and explain how to get the XP slice mounted? GENERIC does not contain ntfs support. -0- -- Q: How many IBM cpu's does it take to do a logical right shift? A: 33. 1 to hold the bits and 32 to push the register.
Re: Partition confusion
Thank you all for the clearing this up for me. The presence of mount_ntfs suggested to me that ntfs was supported, but apparently not. I'll either work around this with two machines and pscp on the Windows side, or build a kernel with ntfs support enabled. Thanks again -- /Don Allen On Sat, Jun 6, 2009 at 9:58 AM, Owain Ainsworthzer...@googlemail.com wrote: On Sat, Jun 06, 2009 at 09:10:28AM -0400, Donald Allen wrote: I've got OpenBSD 4.5 installed on a Thinkpad X61, dual-booted with Windows XP. XP is at the beginning of the disk, starting at sector 63. The XP slice, to use BSD terminology, is about 10 Gb (the disk is 100 Gb). The OpenBSD slice occupies the rest of the disk. During the OpenBSD install, I created partitions a, b, d, e, f, and g for the mountpoints /, swap, /tmp, /var, /usr, and /home. I don't believe there was any interaction regarding the XP slice during the install. Now I want to mount the XP (ntfs) partition. So, having created /mnt/windows as root, I tried r...@sophie:/mnt$ mount -t ntfs /dev/sd0i windows mount_ntfs: /dev/sd0i on /mnt/windows: Operation not supported So I did r...@sophie:/mnt$ disklabel sd0 # Inside MBR partition 1: type A6 start 20487600 size 174877920 # /dev/rsd0c: type: ESDI disk: ad4s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 12161 total sectors: 195371568 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0# microseconds drivedata: 0 8 partitions: #size offset fstype [fsize bsize cpg] a: 316575 20487600 4.2BSD 2048 163841 b: 2104515 20804175swap c:1953715680 unused d: 321300 22908690 4.2BSD 2048 163841 e: 176715 23229990 4.2BSD 2048 163841 f: 12594960 23406705 4.2BSD 2048 163841 g:159364800 36001665 4.2BSD 2048 163841 disklabel: warning, unused partition i: size 7148239195883 offset 17551383986520 disklabel: warning, unused partition j: size 238106791916026 offset 211716520590544 disklabel: warning, unused partition k: size 163974838534045 offset 206347192303801 disklabel: warning, unused partition l: size 271451018559616 offset 5237774174023 disklabel: warning, unused partition m: size 190849433245138 offset 190845464470417 disklabel: warning, unused partition n: size 211668966116211 offset 5864912221576 disklabel: warning, unused partition o: size 17630285786338 offset 76717108839878 disklabel: warning, unused partition p: size 17136519487675 offset 217832169078968 So partition i in the actual label does not describe the XP partition. But the default label does r...@sophie:/mnt$ disklabel -d sd0 # Inside MBR partition 1: type A6 start 20487600 size 174877920 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST9100821AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 240 sectors/cylinder: 15120 cylinders: 12921 total sectors: 195371568 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0# microseconds drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] c:1953715680 unused i: 20487537 63NTFS So I tried disklabel -cd sd0 thinking that this would set the in-memory copy of the label to the default and then I'd be able to mount /dev/sd0i. No luck -- same error: Operation not supported. Would someone please unconfuse me and explain how to get the XP slice mounted? GENERIC does not contain ntfs support. -0- -- Q: How many IBM cpu's does it take to do a logical right shift? A: 33. 1 to hold the bits and 32 to push the register.
Re: Partition confusion
Can't the legacy system be modified to work with FFS or EXT2? -Lars
Re: Partition confusion
On 6 Jun 2009 at 12:11, Donald Allen wrote: On Sat, Jun 6, 2009 at 11:49 AM, Lars Noodenlars.cura...@gmail.com wrote: Can't the legacy system be modified to work with FFS or EXT2? Hi -- Are you addressing that question to me? If so, I'm really not sure I understand your question. What do you mean by the legacy system? If so, are you suggesting that perhaps XP can be modified to work with FFS or ext2? The answer to that, I believe, is no. While proudly not a Windows expert, I believe XP supports only Microsoft filesystems -- ntfs, fat and fat32. It is common to use the term legacy system to refer to proprietary OS including/especially Micro$oft Windows. And since I learned more than I ever cared about Windows XP, it _can_ be made to support much more than what is provided by Microsoft. In particular, there are a few stable and open source drivers to allow XP to access Linux ext2/3 filesystems. There is also a FOSS driver for FFS but it has not been updated in a long time and in my experience did not work too well with OpenBSD. As I said in my previous post, pscp and another machine present a simple workaround for this issue. I've got multiple machines, I rsync my home directory from one to the other when I have occasion to use something other than my primary machine, and so it's a simple matter to pscp file from the Windows filesystem to another machine running OpenBSD or Linux (which I run on my old TP 600x, on which OpenBSD doesn't fare too well, discussed in an earlier thread). This is needed very rarely (typically only when I travel and get on the network via wifi, which I do with Windows, just because it's easier) and so it's probably not worth bothering to build a kernel to add ntfs support. /Don -Lars
Re: Partition confusion
On Sat, Jun 6, 2009 at 1:27 PM, Jacob L. Leifmanjac...@bitwise.net wrote: On 6 Jun 2009 at 12:11, Donald Allen wrote: On Sat, Jun 6, 2009 at 11:49 AM, Lars Noodenlars.cura...@gmail.com wrote: Can't the legacy system be modified to work with FFS or EXT2? Hi -- Are you addressing that question to me? If so, I'm really not sure I understand your question. What do you mean by the legacy system? If so, are you suggesting that perhaps XP can be modified to work with FFS or ext2? The answer to that, I believe, is no. While proudly not a Windows expert, I believe XP supports only Microsoft filesystems -- ntfs, fat and fat32. It is common to use the term legacy system to refer to proprietary OS including/especially Micro$oft Windows. And since I learned more than I ever cared about Windows XP, it _can_ be made to support much more than what is provided by Microsoft. In particular, there are a few stable and open source drivers to allow XP to access Linux ext2/3 filesystems. There is also a FOSS driver for FFS but it has not been updated in a long time and in my experience did not work too well with OpenBSD. Thanks. I was unaware of those filesystem drivers and that usage of the term legacy (which I usually think of as referring to something from the past and, unfortunately, Windows exists in the present -- Webster: 1. A gift by will esp. of money or other personal property; 2. Something received from an ancestor, a predecessor, or from the past), though I knew that it was possible (I have a vague recollection that Cutler built Windows NT on some Unix-ey, perhaps micro-kernel thing -- Mach?). But knowing that wouldn't change my approach to this issue -- I wouldn't trust some random third-party driver for Windows to be writing in my FFS filesystem. If I were going to do this with one machine, which at this point I'm not, I'd build an OpenBSD kernel, mount the ntfs partition read-only (which I guess is my only choice) and copy the files from Windows with OpenBSD. I'd certainly trust OpenBSD a heck of a lot more to a. not scribble junk in the ntfs partition that was mounted ro, and b. to write the stuff correctly in the FFS filesystem. /Don As I said in my previous post, pscp and another machine present a simple workaround for this issue. I've got multiple machines, I rsync my home directory from one to the other when I have occasion to use something other than my primary machine, and so it's a simple matter to pscp file from the Windows filesystem to another machine running OpenBSD or Linux (which I run on my old TP 600x, on which OpenBSD doesn't fare too well, discussed in an earlier thread). This is needed very rarely (typically only when I travel and get on the network via wifi, which I do with Windows, just because it's easier) and so it's probably not worth bothering to build a kernel to add ntfs support. /Don -Lars
