Question for people with Batch 2 units:
{{Edit: Turns out this is not a question so much as a series of questions, statements, and then a vague request for your input near the end. Just fyi.}}Earlier in the thread it seems like a lot of Batch 1 owners were reporting issues with the unit losing all (or some) config data upon reboot. (I think the gist was that some people just had EVERYTHING overwritten/reset, and others were just losing specific parts of their customizations, like IPs and changes to initscripts or passwords, etc.) Are Batch 2 units showing this same problem? If not, then do we know if that's because the new firmware fixed the problem...or if it's just magic...or if it's just that not enough Batch 2 units are out there yet to know for sure?
The reason I ask, is I was looking at the Beagle Bone Black
(the embedded device that's always exactly 1 slip of the tongue away from like, 3-4 different probable titles for porn films, but I digress) wiki and I found something that *might* be germane to the discussion:
Known Issues / Software1) The microSD card cannot be used as a storage device when booting from microSD in the 3.8 kernel.
...
I don't have one of these in front of me to toy with, but going by what others were saying I got the impression that the -- how should I phrase this -- "the cost-reduced, simplified BBB version" being used by Bitmain in the S2 units lacks any eMMC/internal memory...so it doesn't have any choice but to boot off the SD card each time...so if it's running the 3.8 kernel, could this be the reason why people are having trouble getting certain changes to "stick?"
Just an educated guess, here, but following the same logic -- could this also explain perhaps why a number of people have reported success fixing various problems, by replacing the (Bitmain) S2 BBB with their own spare/OEM/Official version -- ie, one that has all the parts one would expect a BBB to have, including internal memory...?
Apologies if this is just way off course and not useful to anyone troubleshooting the matter; I was just trying to "think aloud" on what might or might not be causing that issue... Perhaps replacing the cheaper/stock BBB with a standard/OEM BBB might be a potential "upgrade" worth considering for people with special needs, like those who *know* they are going to run stuff on a different subnet and use SSH keys and ...I don't know, need the system to play Ms Pac Man on the display or something. :)
And I think I just realized -- there are either 8 questions in there, or none... Not quite the "one question for Batch 2 owners" that I advertised above. Sorry about that... Need more caffeine, talking a bit too much in "stream of consciousness" format, I'm afraid!
So I'll cheat and use the generic question:
"So, Batch 2 owners: Any thoughts regarding any of this?" haha, there, I've condensed everything to one question vague enough that anyone can "interpret it for themselves" and answer it in some form or fashion. :)
PS, just so this post adds some actual 'value' to the discussion instead of just vague questions about things I may or may not actually know anything about, for the people discussing the SD card image and its filesystem/partition structure (around 5-8 posts ago), here's the breakdown/sizes of the 3 partitions (with thanks to the kind individual who provided the image):
/tmp$ file bitmain.img
bitmain.img: x86 boot sector; partition 1: ID=0xc, active, starthead 1, startsector 63, 144522 sectors; partition 2: ID=0xc, starthead 0, startsector 160650, 144585 sectors; partition 3: ID=0x83, starthead 0, startsector 305235, 3534300 sectors, code offset 0x0
/tmp$ fdisk bitmain.img
Command (m for help): p
Disk bitmain.img: 1965 MB, 1965841920 bytes
255 heads, 63 sectors/track, 239 cylinders, total 3839535 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
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
bitmain.img1 * 63 144584 72261 c W95 FAT32 (LBA)
bitmain.img2 160650 305234 72292+ c W95 FAT32 (LBA)
bitmain.img3 305235 3839534 1767150 83 Linux
/tmp$ cfdisk bitmain.img
cfdisk (util-linux 2.20.1)
Disk Drive: bitmain.img
Size: 1965841920 bytes, 1965 MB
Heads: 255 Sectors per Track: 63 Cylinders: 239
Name Flags Part Type FS Type [Label] Size (MB)
------------------------------------------------------------------------------------------------------------------------------------
bitmain.img1 Boot Primary vfat [BtmBoot] 74.03
Pri/Log Free Space 8.23
bitmain.img2 Primary vfat [BtmBootBak] 74.03
bitmain.img3 Primary ext4 [Config] 1809.57
Partition Table for bitmain.img
---Starting---- ----Ending----- Start Number of
# Flags Head Sect Cyl ID Head Sect Cyl Sector Sectors
-- ----- ---- ---- ----- ---- ---- ---- ----- ----------- -----------
1 0x80 1 1 0 0x0C 254 63 8 63 144522
2 0x00 0 1 10 0x0C 254 63 18 160650 144585
3 0x00 0 1 19 0x83 254 63 238 305235 3534300
4 0x00 0 0 0 0x00 0 0 0 0 0
Anyway, ... for those who were asking what sizes and how many partitions to look for on their SD cards, ... um...there you go!
Note, for your convenience, all readers and posters to this thread have automatically been invoiced for the 407 hours it took me to generate the data, above. You're welcome. And no worries: I bill out WELL BELOW any competitor's price (at a mere $49.9999998051 an hour) so I'm basically just giving it all way for free, you lucky freeloading helpful-as-hell community of bastards! :) 
asic_num=64 asic_status=oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo
