Mounting RW image on VICE - Revision history

Jayctheriot at 00:25, 9 July 2018

2018-07-09T00:25:29Z

← Older revision		Revision as of 19:25, 8 July 2018
Line 31:		Line 31:
	Capturing the card again, but individual partitions.<br>		Capturing the card again, but individual partitions.<br>
	I think this is going to work. I plugged the SD card in and all the partitions automounted. I just have to make the machine do it now.		I think this is going to work. I plugged the SD card in and all the partitions automounted. I just have to make the machine do it now.

			<hr />
			The following, in part, is taken from https://unix.stackexchange.com/questions/9099/how-to-read-one-filesystem-from-a-whole-disk-image-file
			<pre>
			kpartx

			sudo apt-get install kpartx
			losetup -fs my.raw
			sudo kpartx -a my.img
			ls /dev/mapper

			Output:

			/dev/mapper/loop0
			/dev/mapper/loop0p1

			where loop0p1 is the first partition, so we can do:

			mkdir -p d
			sudo mount /dev/mapper/loop0p1 d
			</pre>

Jayctheriot at 21:25, 22 June 2018

2018-06-22T21:25:18Z

← Older revision		Revision as of 16:25, 22 June 2018
Line 26:		Line 26:

	Using kpartx and a script I'm able to easily mount the partitions in read mode. I may have to put the partitions in fstab to grant permissions correctly as all my other efforts are failing.		Using kpartx and a script I'm able to easily mount the partitions in read mode. I may have to put the partitions in fstab to grant permissions correctly as all my other efforts are failing.
			<br>
			What I'm reading leads me to believe it would be easier to split the image up into individual partitions, instead of the whole disk.

			Capturing the card again, but individual partitions.<br>
			I think this is going to work. I plugged the SD card in and all the partitions automounted. I just have to make the machine do it now.

Jayctheriot at 20:54, 22 June 2018

2018-06-22T20:54:05Z

@@ Line 19: / Line 19: @@
 dd if=/dev/sd<Letter> of=<raw image filename.img>
 </pre>
-To successfully mount the partitions, you need to know the offset.  This is done by multiplying the valuse in the "Start" column by the I/O size, in this case, it is 512.
+Prerequisite:  kpartx
 <pre>
-Disk BayouBBS_SD8.img: 14.9 GiB, 15931539456 bytes, 31116288 sectors
+sudo apt install kpartx
 </pre>
-mount_parts.sh contains the script to mount them all. (I should just have the parts.dat have the start and then have the script do the math!!)<br>
+Using kpartx and a script I'm able to easily mount the partitions in read mode.  I may have to put the partitions in fstab to grant permissions correctly as all my other efforts are failing.

Jayctheriot at 19:33, 22 June 2018

2018-06-22T19:33:34Z

← Older revision		Revision as of 14:33, 22 June 2018
Line 39:		Line 39:

	</pre>		</pre>
			<br>
			for the sake of automation:
			parts.dat is a tab-delimited text file containing partition name and offset, one per line.

			Such as:
			<pre>
			system 1048576
			plus_files 35651584
			etc_user 72351744
			ud-1 108003328
			ud-2 143654912
			mail 179306496
			ux-dirs 214958080
			</pre>

			mount_parts.sh contains the script to mount them all. (I should just have the parts.dat have the start and then have the script do the math!!)<br>

Jayctheriot at 15:50, 22 June 2018

2018-06-22T15:50:00Z

← Older revision		Revision as of 10:50, 22 June 2018
Line 19:		Line 19:
	dd if=/dev/sd<Letter> of=<raw image filename.img>		dd if=/dev/sd<Letter> of=<raw image filename.img>
	</pre>		</pre>
			To successfully mount the partitions, you need to know the offset. This is done by multiplying the valuse in the "Start" column by the I/O size, in this case, it is 512.
	<pre>		<pre>
	Disk BayouBBS_SD8.img: 14.9 GiB, 15931539456 bytes, 31116288 sectors		Disk BayouBBS_SD8.img: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Line 28:		Line 28:
	Disk identifier: 0x10f541c2		Disk identifier: 0x10f541c2

	Device ~~Boot~~ Start End Sectors Size Id Type		Device Start End Sectors Size Id Type offset =512*Start
	BayouBBS_SD8.img1 2048 69631 67584 33M b ~~W95~~ FAT32		BayouBBS_SD8.img1 2048 69631 67584 33M b FAT32 1048576
	BayouBBS_SD8.img2 69632 31115263 31045632 14.8G 5 Extended		BayouBBS_SD8.img2 69632 31115263 31045632 14.8G 5 Extended
	BayouBBS_SD8.img5 71680 139263 67584 33M b ~~W95~~ FAT32		BayouBBS_SD8.img5 71680 139263 67584 33M b FAT32 36700160
	BayouBBS_SD8.img6 141312 208895 67584 33M b ~~W95~~ FAT32		BayouBBS_SD8.img6 141312 208895 67584 33M b FAT32 72351744
	BayouBBS_SD8.img7 210944 278527 67584 33M b ~~W95~~ FAT32		BayouBBS_SD8.img7 210944 278527 67584 33M b FAT32 108003328
	BayouBBS_SD8.img8 280576 348159 67584 33M b ~~W95~~ FAT32		BayouBBS_SD8.img8 280576 348159 67584 33M b FAT32 143654912
	BayouBBS_SD8.img9 350208 417791 67584 33M b ~~W95~~ FAT32		BayouBBS_SD8.img9 350208 417791 67584 33M b FAT32 179306496
	BayouBBS_SD8.img10 419840 31115263 30695424 14.7G b ~~W95~~ FAT32		BayouBBS_SD8.img10 419840 31115263 30695424 14.7G b FAT32 214958080

	</pre>		</pre>

Jayctheriot at 13:27, 22 June 2018

2018-06-22T13:27:19Z

← Older revision		Revision as of 08:27, 22 June 2018
Line 1:		Line 1:
			***WARNING! This is a living document and information will change frequently. Please, subscribe for updates***
	Problem: Running ImageBBS v1.2a+ in VICE using tcpser incurs two problems: REL file corruption and datastream corruption using tcpser.<br>		Problem: Running ImageBBS v1.2a+ in VICE using tcpser incurs two problems: REL file corruption and datastream corruption using tcpser.<br>

Jayctheriot at 13:25, 22 June 2018

2018-06-22T13:25:40Z

← Older revision		Revision as of 08:25, 22 June 2018
Line 4:		Line 4:
	#Mount an msdos formatted image file or files to one or more of the available four drives to VICE. Method to be described below.		#Mount an msdos formatted image file or files to one or more of the available four drives to VICE. Method to be described below.
	#Route emulated Swiftlink traffic to com port then have com port connected via TelBBS wire to a 2nd PC running BBS Server.		#Route emulated Swiftlink traffic to com port then have com port connected via TelBBS wire to a 2nd PC running BBS Server.

			Thoughts:
			*Filesystem:
			**Mounting a directory in VICE allows the underlying operating system hosting VICE access to that directory. I feel this is what is causing the REL file difficulty. By mounting an "img" of the storage device, then access to the file system from the hosting system is denied. All access is through VICE.
			*Internet Connection:
			**I have witnessed datastream corruption in tcpser. The timing between VICE and the outside world doesn't work well consistently with tcpser. BBS Server is a known good. By routing the i/o through the host computers serial port then through the TelBBS wire, to a 2nd PC, you should be able to avoid this timing issue and provide a sustainable data stream.

	Method:		Method:

Jayctheriot at 13:17, 22 June 2018

2018-06-22T13:17:40Z

← Older revision		Revision as of 08:17, 22 June 2018
Line 9:		Line 9:
	Create SD Card with partitions using gparted. Partitions formatted as FAT32, 33MB. Block size of 512		Create SD Card with partitions using gparted. Partitions formatted as FAT32, 33MB. Block size of 512
	Using DD, capture the image of the SD Card:		Using DD, capture the image of the SD Card:
	<~~code~~>		<pre>
	dd if=/dev/sd<Letter> of=<raw image filename.img>		dd if=/dev/sd<Letter> of=<raw image filename.img>
	</~~code~~>		</pre>

	<pre>		<pre>

Jayctheriot at 13:17, 22 June 2018

2018-06-22T13:17:07Z

← Older revision		Revision as of 08:17, 22 June 2018
Line 1:		Line 1:
	Problem: Running ImageBBS v1.2a+ in VICE using tcpser incurs two problems: REL file corruption and datastream corruption using tcpser.		Problem: Running ImageBBS v1.2a+ in VICE using tcpser incurs two problems: REL file corruption and datastream corruption using tcpser.<br>
	Hypothesis: 1) Mount an msdos formatted image file or files to one or more of the available four drives to VICE. Method to be described below.
	2) Route emulated Swiftlink traffic to com port then have com port connected via TelBBS wire to a 2nd PC running BBS Server.		Hypothesis: <br>
			#Mount an msdos formatted image file or files to one or more of the available four drives to VICE. Method to be described below.
			#Route emulated Swiftlink traffic to com port then have com port connected via TelBBS wire to a 2nd PC running BBS Server.

	Method:		Method:

Jayctheriot: Created page with "Problem: Running ImageBBS v1.2a+ in VICE using tcpser incurs two problems: REL file corruption and datastream corruption using tcpser. Hypothesis: 1) Mount an msdos formatt..."

2018-06-22T13:16:32Z

Created page with "Problem: Running ImageBBS v1.2a+ in VICE using tcpser incurs two problems: REL file corruption and datastream corruption using tcpser. Hypothesis: 1) Mount an msdos formatt..."

New page

Problem: Running ImageBBS v1.2a+ in VICE using tcpser incurs two problems: REL file corruption and datastream corruption using tcpser.
Hypothesis: 1) Mount an msdos formatted image file or files to one or more of the available four drives to VICE. Method to be described below.
2) Route emulated Swiftlink traffic to com port then have com port connected via TelBBS wire to a 2nd PC running BBS Server.

Method:
Run VICE v.3.2 on Ubuntu.
Create SD Card with partitions using gparted. Partitions formatted as FAT32, 33MB. Block size of 512
Using DD, capture the image of the SD Card:
<code>
dd if=/dev/sd<Letter> of=<raw image filename.img>
</code>

<pre>
Disk BayouBBS_SD8.img: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x10f541c2

Device Boot Start End Sectors Size Id Type
BayouBBS_SD8.img1 2048 69631 67584 33M b W95 FAT32
BayouBBS_SD8.img2 69632 31115263 31045632 14.8G 5 Extended
BayouBBS_SD8.img5 71680 139263 67584 33M b W95 FAT32
BayouBBS_SD8.img6 141312 208895 67584 33M b W95 FAT32
BayouBBS_SD8.img7 210944 278527 67584 33M b W95 FAT32
BayouBBS_SD8.img8 280576 348159 67584 33M b W95 FAT32
BayouBBS_SD8.img9 350208 417791 67584 33M b W95 FAT32
BayouBBS_SD8.img10 419840 31115263 30695424 14.7G b W95 FAT32

</pre>