LimHD:EXT2 - Revision history

Lundman at 07:44, 5 November 2007

2007-11-05T07:44:50Z

← Older revision		Revision as of 07:44, 5 November 2007
Line 93:		Line 93:
	/dev/ide/host0/bus0/target0/lun0/part1 39.1G 4.3G 34.8G 11% /mnt/HD1		/dev/ide/host0/bus0/target0/lun0/part1 39.1G 4.3G 34.8G 11% /mnt/HD1
	/dev/ide/host0/bus0/target0/lun0/part2 111.8G 18.0M 106.1G 0% /mnt/HD2		/dev/ide/host0/bus0/target0/lun0/part2 111.8G 18.0M 106.1G 0% /mnt/HD2


			In retrospect, mounting the HDD in read/write isn't a great idea. Since this device needs plenty of reboots, and you can not do that cleanly. I have '''fsck''' but it needs a huge amount of memory. If you kill everything, '''curacao''', smbmount etc, I could '''just''' run it. That's on a 100Gb partition, so not very nice. Seriously, you will need '''swap''' partition. So I will go back to read-only, and use '''FTP SITE MOUNT''' to make it read/write temporarily.

Lundman at 09:00, 1 November 2007

2007-11-01T09:00:18Z

← Older revision		Revision as of 09:00, 1 November 2007
Line 71:		Line 71:
	'''/mnt/smbfs/curacao-ext2 /mnt /dev/ir'''		'''/mnt/smbfs/curacao-ext2 /mnt /dev/ir'''

	I can not provide the patched binary of '''curacao''' sorry[~~http~~:~~//www.lundman.net/ftp/curacao-ext2 !~~]		I can not provide the patched binary of '''curacao''' sorry, but go here [[LimHD:Firmware\|Firmware]]

	Naturally, eventually I will roll my own firmware with my version of '''curacao''' but you really want to make sure it works before you do that, since without a working '''curacao''' you '''can not flash a new firmware!'''. This is why I did it this way for now.		Naturally, eventually I will roll my own firmware with my version of '''curacao''' but you really want to make sure it works before you do that, since without a working '''curacao''' you '''can not flash a new firmware!'''. This is why I did it this way for now.
Line 77:		Line 77:
	I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.		I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.

	I have compiled a version of busybox with '''fdisk''', '''e2fsck''' and '''mkfs.ext2''' so that simple ext2 setup can be performed. I have thus made my HDD have partition 1 as '''ntfs''' and partition 2 as '''ext2''' so that I can keep testing my code against both. '''curacao''' mounts both.		I have compiled a version of busybox with '''fdisk''', '''e2fsck''' and '''mkfs.ext2''' so that simple ext2 setup can be performed. I have thus made my HDD have partition 1 as '''ntfs''' and partition 2 as '''ext2''' so that I can keep testing my code against both. '''curacao''' mounts both.


	=== read-only ===		=== read-only ===

Lundman at 03:34, 19 October 2007

2007-10-19T03:34:26Z

← Older revision		Revision as of 03:34, 19 October 2007
Line 36:		Line 36:
	xseg000:00056904 CMP R0, #0 ; Set cond. codes on Op1 - Op2		xseg000:00056904 CMP R0, #0 ; Set cond. codes on Op1 - Op2
	xseg000:00056908 BNE loc_56934 ; Branch		xseg000:00056908 BNE loc_56934 ; Branch

			In binary
			00056910: 0610 a0e1 9020 9fe5 '''07'''30 a0e3 4e4d 09eb ..... ...0..NM..
			00056920: 0000 50e3 0800 000a 8030 9fe5 0030 8de5 ..P......0...0..
			00056930: 6000 4be2 8010 4be2 7420 9fe5 '''07'''30 a0e3 `.K...K.t ...0..


	Basically, it uses mount flags '''#7''' which is '''READONLY NOSUID NODEV''', tries to mount it with type '''vfat''' and mount options '''iocharset=utf8'''. If that fails, it tries '''#7''' with '''ntfs''' and '''nls=utf8'''. Changing '''ntfs''' to '''ext2''' will result in:		Basically, it uses mount flags '''#7''' which is '''READONLY NOSUID NODEV''', tries to mount it with type '''vfat''' and mount options '''iocharset=utf8'''. If that fails, it tries '''#7''' with '''ntfs''' and '''nls=utf8'''. Changing '''ntfs''' to '''ext2''' will result in:

Lundman at 02:33, 19 October 2007

2007-10-19T02:33:50Z

← Older revision		Revision as of 02:33, 19 October 2007
Line 84:		Line 84:

	So, most likely there is a '''3''' somewhere (actually, it is '''7''', as seen above) . Definitely in '''R3'''.		So, most likely there is a '''3''' somewhere (actually, it is '''7''', as seen above) . Definitely in '''R3'''.


			/dev/ide/host0/bus0/target0/lun0/part1 39.1G 4.3G 34.8G 11% /mnt/HD1
			/dev/ide/host0/bus0/target0/lun0/part2 111.8G 18.0M 106.1G 0% /mnt/HD2

Lundman at 02:32, 19 October 2007

2007-10-19T02:32:59Z

← Older revision		Revision as of 02:32, 19 October 2007
Line 83:		Line 83:
	#define MS_NOSUID 2 /* Ignore suid and sgid bits */		#define MS_NOSUID 2 /* Ignore suid and sgid bits */

	So, most likely there is a '''3''' somewhere ~~8actually~~, '''7''', ~~see~~ above) . Definitely in '''R3'''.		So, most likely there is a '''3''' somewhere (actually, it is '''7''', as seen above) . Definitely in '''R3'''.

Lundman at 02:32, 19 October 2007

2007-10-19T02:32:19Z

← Older revision		Revision as of 02:32, 19 October 2007
Line 37:		Line 37:
	xseg000:00056908 BNE loc_56934 ; Branch		xseg000:00056908 BNE loc_56934 ; Branch

	Basically, it uses mount flags '''#7''' which is '''READONLY\|NOSUID''', tries to mount it with type '''vfat''' and mount options '''iocharset=utf8'''. If that fails, it tries '''#7''' with '''ntfs''' and '''nls=utf8'''. Changing '''ntfs''' to '''ext2''' will result in:		Basically, it uses mount flags '''#7''' which is '''READONLY NOSUID NODEV''', tries to mount it with type '''vfat''' and mount options '''iocharset=utf8'''. If that fails, it tries '''#7''' with '''ntfs''' and '''nls=utf8'''. Changing '''ntfs''' to '''ext2''' will result in:

	EXT2-fs: Unrecognized mount option nls=utf8		EXT2-fs: Unrecognized mount option nls=utf8

Lundman at 02:31, 19 October 2007

2007-10-19T02:31:51Z

← Older revision		Revision as of 02:31, 19 October 2007
Line 37:		Line 37:
	xseg000:00056908 BNE loc_56934 ; Branch		xseg000:00056908 BNE loc_56934 ; Branch

	Basically, it ~~looks for partition type~~ '''#7''' which is '''~~HPFS/NTFS~~''', tries to mount it with ~~strings~~ '''vfat''' and '''iocharset=utf8'''. If that fails, it tries '''#7''' with '''ntfs''' and '''nls=utf8'''. ~~The partition type for Linux should be '''#83''', and changing~~ '''ntfs''' to '''ext2''' will result in:		Basically, it uses mount flags '''#7''' which is '''READONLY\|NOSUID''', tries to mount it with type '''vfat''' and mount options '''iocharset=utf8'''. If that fails, it tries '''#7''' with '''ntfs''' and '''nls=utf8'''. Changing '''ntfs''' to '''ext2''' will result in:

	EXT2-fs: Unrecognized mount option nls=utf8		EXT2-fs: Unrecognized mount option nls=utf8
Line 46:		Line 46:

	I went with '''nocheck''' for now. There are a few in there that would be relatively harmless.		I went with '''nocheck''' for now. There are a few in there that would be relatively harmless.

			So basically, I have decided to change '''vfat''' to '''ext2''' so that you can still mount '''ntfs''' as well as '''ext2'''. I have changed the first '''#7''' to '''#6''' to make '''ext2''' mount in '''read-write''' mode.


			=== Restarting curacao ===


	The next problem is restarting '''curacao'''. It needs to be shut down in such a way that we can open '''/dev/ir''' again, which is only allowed to be opened once.		The next problem is restarting '''curacao'''. It needs to be shut down in such a way that we can open '''/dev/ir''' again, which is only allowed to be opened once.
Line 64:		Line 70:

	I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.		I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.

			I have compiled a version of busybox with '''fdisk''', '''e2fsck''' and '''mkfs.ext2''' so that simple ext2 setup can be performed. I have thus made my HDD have partition 1 as '''ntfs''' and partition 2 as '''ext2''' so that I can keep testing my code against both. '''curacao''' mounts both.


Line 75:		Line 83:
	#define MS_NOSUID 2 /* Ignore suid and sgid bits */		#define MS_NOSUID 2 /* Ignore suid and sgid bits */

	So, most likely there is a '''3''' somewhere~~. Probably in~~ '''R4'''.		So, most likely there is a '''3''' somewhere 8actually, '''7''', see above) . Definitely in '''R3'''.

	~~Unfortunately~~, ~~the mount commands does a:~~

	~~LDR R4, [R11, #arg_4]~~

	~~Just before it calls sys_mount~~. ~~So, I have to chase down where this is set. That isn~~'~~t as easy~~.

Lundman at 02:49, 17 October 2007

2007-10-17T02:49:24Z

@@ Line 64: / Line 64: @@
 I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.
   /dev/ide/host0/bus0/target0/lun0/part1 on /mnt/HD1 type ext2 (ro,nosuid)
 Alas, it is mounted '''read-only'''. I need to find this option next.

Lundman at 01:46, 17 October 2007

2007-10-17T01:46:43Z

← Older revision		Revision as of 01:46, 17 October 2007
Line 64:		Line 64:

	I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.		I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.

			/dev/ide/host0/bus0/target0/lun0/part1 on /mnt/HD1 type ext2 (ro,nosuid)

			Alas, it is mounted '''read-only'''. I need to find this option next.

Lundman at 00:56, 17 October 2007

2007-10-17T00:56:33Z

← Older revision		Revision as of 00:56, 17 October 2007
Line 60:		Line 60:

	I can not provide the patched binary of '''curacao''' sorry[http://www.lundman.net/ftp/curacao-ext2 !]		I can not provide the patched binary of '''curacao''' sorry[http://www.lundman.net/ftp/curacao-ext2 !]

			Naturally, eventually I will roll my own firmware with my version of '''curacao''' but you really want to make sure it works before you do that, since without a working '''curacao''' you '''can not flash a new firmware!'''. This is why I did it this way for now.

			I also need to compile '''e2fsck''' and run it at boot. Maybe even '''mke2fs''' because I am nice.