05:00:49 sommerfeld good stuff:) 16:21:25 Woodstock: thanks for swtpm 16:25:13 Just curious, has anyone tried illumos (or related) on a 45 drives system? 16:25:34 Didn't the old Thumper ship with that many? I'll have to check... 16:26:08 45drives is a company in Canada that ships thumper-like boxes but with their own version on the theme. 16:26:15 Yeah... 16:26:16 https://en.wikipedia.org/wiki/Sun_Fire_X4500 16:26:16 the thumper had 48 drives, IIRC. 16:26:29 I'm talking about the product from the company called 45drives. 16:26:43 they ship with Linux. 16:26:44 Oh... sorry, was finding the wikipedia link while you were clearing things up. Sorry. 16:26:49 np 16:27:44 Up until about ... maybe 8 months ago ... I was running FBSD on thumpers. They were good to the end. 16:28:02 They're selling turnkey boxes (they even have a wannabe-Oxide box, it looks like). Would be interesting to try that. 16:28:37 Yeah. It would be nice to give silicon mechanics some competition for our next fileserver. 16:29:04 but I don't want to run Linux on my fileservers, I want some heterogeneity in my environment. 16:29:46 They look like a Racktop competitor as well (Racktop uses their own illumos, and you see their folks on illumos community places). 16:30:26 * nomad goes for a look 16:32:33 Hmm. I must be finding the wrong company. I'm seeing lots of noise about a security system but nothing about file servers. 16:35:46 Their initial customer base was govt. so that makes sense (racktopsystems.com). Sorry for not catching that. 16:37:10 please stop apologizing :) 16:37:39 Just means I don't need to consider them for our fileserver needs. :) 17:01:44 [illumos-gate] 16838 libefi: efi_auto_sense should use sector size -- Toomas Soome 17:05:56 [illumos-gate] 16833 smbsrv: array subscript 12 is above array bounds -- Toomas Soome 19:27:33 [illumos-gate] 16844 pci_prd: array subscript 0 is outside array bounds -- Toomas Soome 21:06:45 hrm... i'm guessing truss is probably the best (though not authortative) source of ioctl values, isn't it? 21:09:32 i don't think it'd rise to needing an IPD, but all major I/O transports (SATA, SCSI, NVMe) support the notion of security protocol I/O 21:10:01 basically you can send and receive chunks of data for some security protocol (which I realize is very generic) 21:10:20 I can't tell what you're asking, about ioctl values 21:10:21 e.g. TCG has protocols for things like self encrypting drives 21:10:39 well mostly about trying to pick a set of values that aren't going to collide 21:11:44 truss does not have them all:) 21:11:56 so for whatever protocol you're trying to use (this -- at least in theory -- is more than disks) 21:12:27 truss is probably a convenient view of many things, but I don't think it's complete 21:12:29 TCG, IEEE1667 (I think that's the one), there's even a spec for doing IKEV2 to encrypt your I/O PDUs 21:12:42 yeah, but in terms of 'best guess' 21:12:43 I'm not sure we have a convenient symbol to search for either 21:13:39 mostly what people do is take a (set of) characters into the high bits, and use the low bits for their codes 21:13:59 could just create another couple of DKIOC values, but since it could also be used with say tape drives (for those using them), using a DKIOC value seems wrong.. 21:14:09 yeah, but still want to at least try to make sure they don't conflict 21:14:51 so mdd(4d) would maybe do `#define MDD_IOC ('m' << 24) | ('d' << 16) | ('d' << 8)` and `#define MDD_IOC_RINGBELL (MDD_IOC | 1)` 21:15:35 this is not advocacy, I just think the historical way things are, as opposed to _IOC() macros and such 21:16:01 e.g. if I picked 'S' << 24 | 'E' << 16 | 'C' << 8 and did say SECURE_IN (SEC_IOC | 0) and SECURE_OUT (SEC_IOC | 1)... my luck it'll end up stomping on something semi-obscure that no one notices for a while :) 21:16:45 I think the chances of collisions on a given device node are probably pretty tiny