00:56:17 <ShinyCyril> the wabt port appears to be missing a crucial library, but "pkg provides" insists that it should be there. How can I debug this mismatch? https://bsd.to/q0fs
00:56:18 <VimDiesel> Title: dpaste/q0fs (Plain Text)
06:20:28 <_xor> Why isn't /usr/local/var/{log,run,db} more common?
06:21:07 <_xor> I almost always see /var/... being used, which is fine, but I'm updating my skeleton (template) port and am contemplating using /usr/local/var/... instead.
06:22:35 <_xor> With zfs boot environments I see that usually only parts of the /var tree are included, which implies that upgrading base might not carry over some of those files.
06:24:34 * _xor feels like he's missing something that makes /usr/local/var/... not recommended
06:25:07 <_xor> Hmm, "A handful of ports create /usr/local/var and should probably be fixed."
07:48:06 <laidback_01> hey, I have two machines - one uses 10.123.109.57, the other uses 10.123.109.58 and my intent is to have a VIP of 10.123.109.60 using ucarp.  I have ucarp working, all it behave as expected.
07:49:12 <laidback_01> Now, my point for this is to use HAProxy.  so in the config, I'm setting the bind  to bind 10.123.109.60:1234  for every whatever port.  and that's for the listen.  that works.  Now, for the outbound, I am seeing attempts at connection on the native address.
07:50:23 <laidback_01> how do I get the machine to use the virtual ip for outbound connections rather than the native IP?  this seems like something I should be able to do and I'm positive this is some kind of routing or similar in FreeBSD ... so that's why I'm asking here not on #haproxy
07:51:18 <laidback_01> virtual IP is created as an Alias on the same nic as the native IP.  so the question could be boiled down to "How do I default outbound traffic to the Alias IP instead of the native IP?"
09:25:47 <meena> laidback_01: thru routing, usually
09:50:03 <meena> https://docs.freebsd.org/en/books/handbook/advanced-networking/#carp nothing here mentions needing to do anything special with routing
09:50:04 <VimDiesel> Title: Chapter 33. Advanced Networking | FreeBSD Documentation Portal
10:14:01 <nacelle> usually the software generating the packets needs to know to bind to the other IP, its not something done at the OS layer traditionally
11:44:16 <hjf_> can jails access serial ports or raw USB devices?
11:44:37 <hjf_> i'm guessing yes by just setting up the right permissions for the /dev file no?
11:45:47 <hjf_> i'm thinking of buying a USB zigbee dongle for Homeassistant which I have running inside a jail, idk if this dongle is a device in /dev/usb or if it acts like /dev/ttyS
11:57:22 <meka> hjf_: you can set up /etc/devfs.rules to unhide devices inside the jail and configure jail to use that ruleset
11:57:52 <meka> For example: https://github.com/cbsd/reggae/blob/master/templates/devfs.rules
11:57:53 <VimDiesel> Title: reggae/devfs.rules at master · cbsd/reggae · GitHub
11:59:38 <hjf_> meka: great thanks.. that's what i was guessing. awesome
12:00:48 <meka> hjf_: depending how you run your jails, maybe you'd like to use runtime for devfs: https://github.com/freebsd/poudriere/blob/master/src/share/poudriere/common.sh#L2006
12:00:51 <VimDiesel> Title: poudriere/common.sh at master · freebsd/poudriere · GitHub
13:54:35 <vkarlsen> Portlint fun: https://bsd.to/sXWm
13:54:36 <VimDiesel> Title: dpaste/sXWm (Bash)
14:16:23 <bsdbandit> good morning
14:17:18 <bsdbandit> im trying to switch my default version of java from openjdk 8 to openjdk 19 does anyone remember the tool to do that ?
14:17:30 <bsdbandit> im having a brain fart this morning
15:33:34 <V_PauAmma_V> bsdbandit, java/javavmwrapper maybe?
15:49:06 <CrtxReavr> Judicious symlink use?
17:08:11 <laidback_01> meena, nacelle thanks for the information.  I'll see what I can do with haproxy to convince it to use the alias address instead.
17:31:41 <meena> laidback_01: you just tell it, explicitly, which addresses to listen on.
17:32:11 <laidback_01> listen is great.  works fine.  it's the outbound connections that are the problem.
17:39:42 <meena> weird, why wouldn't it use the listen addresses to respond to a request coming in on them?
17:57:12 <sjk> Hi! When I run "iocage list" I get this message: "Please set a mountpoint on zroot/iocage/templates"
17:57:27 <sjk> zfs get mountpoint zroot/iocage/templates tells me its mountpoint is /zroot/iocage/templates, though
17:59:01 <sjk> templates/ is empty though, I might have accidentally removed its contents
17:59:45 <sjk> hrm, just remounting it fixed it
17:59:48 <sjk> *shrug*
18:00:55 <PredatorONormies> that moment when you fix some problem by restarting the device -_- (not FreeBSD dw)
18:01:06 <PredatorONormies> shitty device
18:01:19 <PredatorONormies> hmmm should've used #freebsd-social
18:07:00 <meena> sjk: iocage has fallen out of support and hasn't received any Bugfixes in at least a year
18:07:24 <sjk> meena: really? what's all the rage nowadays?
18:10:26 <lilufo> as a linux user, where would be a good place to get started with FreeBSD?
18:10:40 <lilufo> I'm interested in learning my way around it
18:11:18 <sjk> lilufo: i think the handbook on freebsd.org is pretty good
18:11:44 <lilufo> thanks, I'll give a read through
18:11:53 <meena> sjk: pot, or cbsd, or, if you don't have many jails, you could just manage them manually with jails.confs, or, if you're adventurous, you can go for podman
18:12:28 <PredatorONormies> lilufo, FreeBSD's guide, I guess.
18:12:39 <PredatorONormies> FreeBSD is pretty straight-forward, compared to OpenBSD, I think?
18:12:40 <lilufo> sjk before I dive into a physical install on my PC, is a virtual machine a good way to practice and check things out?
18:12:47 <PredatorONormies> Well.. if you're familiar with OpenZFS, that is
18:12:55 <PredatorONormies> You can install Arch on OpenZFS
18:13:05 <PredatorONormies> try with FDE and you'll probably cry from pain
18:13:11 <PredatorONormies> FreeBSD makes it ultra-easy
18:14:01 <lilufo> oh nice
18:14:08 <lilufo> it's a good starting point among the BSD's?
18:18:44 <PredatorONormies> I guess so.. it's friendly enough to me
18:18:59 <PredatorONormies> But compared to you - I might be too elite
18:19:03 <PredatorONormies> idk
18:19:14 <PredatorONormies> shit that is easy to me might not be to some
18:19:19 <PredatorONormies> for me*
18:19:48 <lilufo> ah
18:20:37 <PredatorONormies> I prefer OpenBSD for desktop if you can, but if you can't FreeBSD is good, too, and FreeBSD is, in my opinion, better for storage server stuff
18:21:04 <PredatorONormies> if for nothing else - at least for dynamic partition sizes and stuff trough OpenZFS
18:23:08 <meena> PredatorONormies: if you call yourself elite, I'm imagining you're at most 14.
18:23:52 <PredatorONormies> I'm 9, actually
18:24:12 <PredatorONormies> It would be extremely dope if I were only 14, and knew about FreeBSD, OpenBSD, some of their pros and cons, etc.
18:24:15 <PredatorONormies> Imagine that
18:24:20 <PredatorONormies> It would work in my favor
18:24:24 <PredatorONormies> somwhat
18:25:22 * meena is 38 and has about 22 years of Unix experience and knows nothing, really
18:26:20 <PredatorONormies> Is that sarcasm?
18:27:01 <PredatorONormies> I always say - age doesn't matter - one could learn a whole life-time of one's knowledge in just 1 year if they try hard enough.. it SERIOUSLY depends on how fast you learned your knowledge - and how much interested you were in it
18:27:08 <PredatorONormies> I remember almost nothing from school
18:27:26 <PredatorONormies> But shit that I learn - I often-times like it, and thus - it's much more easier to remember
18:27:50 <PredatorONormies> people who hate learning (probably a big part because of FORCED schooling) - won't know shit even if you gave them 200 years of time
18:28:07 <debdrup> There's probably many channels for that conversation, but #FreeBSD ain't it.
18:28:21 <sjk> Agreed
18:28:32 <PredatorONormies> neutral
18:28:34 <PredatorONormies> you win
18:29:31 <sjk> Sigh. All of a sudden ezjail went extinct and I had to switch to iocage. Now it's time to switch again. bah!
18:29:41 <sjk> Looking into pot now
18:29:45 <sjk> (The software)
18:30:14 * debdrup just uses the tools in FreeBSDs base systems, as he doesn't need to orchestrate thousands of jails.
18:30:32 <debdrup> And with jail.conf.d, orchestrating thousands of jails with base utilities is doable.
18:30:57 <sjk> hmm
18:31:17 <sjk> I have seven jails.
18:31:33 <debdrup> That's easily doable.
18:31:35 <sjk> I do enjoy pretending I am administering a huuuuge bunch of servers though
18:31:52 <sjk> But if you can do a whole bunch of jails with just the regular tools
18:32:01 <sjk> maybe I could do that too :)
18:33:29 <debdrup> https://www.youtube.com/watch?v=S3u8OtjfGFE is, until Someone™ get around to redoing the handbook, the best source of information on how to do jails with tools in base.
18:33:30 <VimDiesel> Title: 20 Years of FreeBSD Jails (2019) - YouTube
18:34:11 <sjk> debdrup: yeah, he wrote a book about jails too
18:34:25 <debdrup> Yea, but I can't remember if the book c overs _everything_
18:34:54 <sjk> is VNET recommended nowadays?
18:36:25 <sjk> ah, Lucas' got a section on vnet :)
18:38:30 <debdrup> There's no reason not to use vnet.
18:44:46 <spork_css> Highly recommend the book, especially paired with the two zfs books.
18:45:07 <sjk> spork_css: yeah, I read the zfs ones and just started reading the jail book
18:48:10 <debdrup> I think mwl stated that in order to write the jails book, he needed to write all the other freebsd mastery books.
19:00:12 <pertho> what's everyone's fave jail manager? doing it by hand? iocage? bastille? ezjail?
19:00:31 <pertho> I quite like the bastille thin jails
19:22:36 <laidback_01> yeah, I use bastille.  used ezjail, iocage, and bastille, and I swear something else, but I can't recall.  Only done it the by-hand way a couple times.  Been wanting to try out CBSD, but so far, the opportunity hasn't presented itself.  Bastille is the most useful to me at this point.
19:27:45 <pertho> yeah I used bastille for a juniper pulse connect vpn that takes over the default route.. got it set up for a VNET jail.. works a treat
19:28:02 <pertho> and doesn't muck with the routing table of the host system
19:35:25 <mason> Just occurred to me today, if I can't get Azerothcore or Trinitycore to compile on FreeBSD, maybe I can build out a Debian jail per a somewhat recent BSD Now.
19:37:09 <meena> i use jail.conf + PkgBase: https://alpha.pkgbase.live/howto/jails.html
19:37:10 <VimDiesel> Title: Howto: Setting up Jails
19:37:36 <mason> That sounds cool as well.
19:37:45 <pertho> mason: WoW :D
19:38:27 <mason> pertho: Yar. It ought to compile on FreeBSD but honestly the errors the code generates are a bit opaque to me. I'm not a C++ fan any more and I get easily confused. :P
19:38:43 <mason> https://www.youtube.com/watch?v=H4YRPdRXKFs
19:38:44 <VimDiesel> Title: Dennis Ritchie - Write in C - YouTube
19:41:13 <pertho> mason: I tried to fix the devel/adb port in OpenBSD but it's a C++ mess and I got lost trying to look at what to fix.. I think FreeBSD's port is newer but I couldn't translate it over.. so gave up
19:43:27 <pertho> I think adb changed all its namespaces.. noticed in FreeBSD it's devel/android-tools-adb
19:43:41 <rtprio> i need to move some bhyve things to jails
19:43:43 <mason> Surprised it's not Java.
19:43:53 <mason> Yeah, heavyweight -> lightweight is a win.
19:43:53 <pertho> Java... *shiver*
19:44:01 <mason> I'm trying to ditch all my VMs.
19:44:10 <cracauer> Can't find that port in head ports.
19:44:58 <cracauer> Oh it's inside androidd-tools.
19:44:59 <pertho> freebsd bhyve VMs... under.. freebsd?
19:45:57 <pertho> mason: so is azerothcore a way to host your own WoW server?
19:46:01 <meena> why use big resources when little resources do trick.
19:46:50 <mason> pertho: Yes. Specializes in WotLK.
19:47:09 <mason> So, client 3.3.5a
19:57:10 <rtprio> at the time i had more linux hosts
20:32:10 <polyex> i'm trying to set up a new external flash drive for fbsd so i start with 'dd if=/dev/zero of=/dev/da0 bs=1M' and it starts but then soon after says "dd: /dev/da0: Input/output error". what's that mean?
20:33:01 <vkarlsen> Maybe it's busted. But why do you zero it with dd?
20:34:31 <polyex> just to wipe anything that's currently on it
20:34:45 <polyex> it's a brand new drive but i guess it could be a DoA?
20:34:55 <polyex> anything else i could try?
20:35:47 <vkarlsen> Why not just create a filesystem on the thing?
20:36:26 <polyex> well i gotta run gpart create -s GPT da0 first no? it's currently MBR/ntfs
20:40:31 <V_PauAmma_V> You didn't specify a limit, so it keeps trying until you get to the end of the source. /dev/zero doesn't *have* an end.
20:40:44 <V_PauAmma_V> s/trying/copying/
20:40:55 <rtprio> but it shouldn't input output error
20:41:32 <rtprio> polyex: zpool create elements /dev/da0; zpool initialize elements;
20:41:33 <V_PauAmma_V> Why not? It tried writing past the end of the target.
20:42:33 <rtprio> V_PauAmma_V: ok, perhaps. if he was very patient
20:43:19 <polyex> wait so what did i do wrong?
20:43:41 <polyex> i used that dd line in the past and it worked
20:44:00 <V_PauAmma_V> Without count= ?
20:44:07 <polyex> ya i'm pretty sure
20:44:22 <rtprio> polyex: you didn't do anything wrong; it did the trick and blasted the front part of the disk. now make a filesystem
20:44:42 <polyex> so the input/output error can be ignored?
20:45:04 <V_PauAmma_V> Hold on. Let me try on one I know works and can be recovered.
20:45:25 <polyex> tyvm
20:46:42 <polyex> just tried to run gpart create -s GPT da0 and it said geom da0 file exists
20:47:00 <polyex> i think i need the dd to work first before i can run that
20:47:58 <rtprio> or you could use commands to remove the old paritions
20:51:34 <polyex> well i just tried gpart destroy -F /dev/da0 and it said input/output error but i guess it worked? gpart show shows a raw disk now
20:53:34 <V_PauAmma_V> Now *that* is worrying.
20:54:19 <V_PauAmma_V> (At 7 MB/S, 32GB is gonna take a while.)
20:54:21 <polyex> just did newfs /dev/da0p1 it said newfs: wtfs: 512 bytes at sector 454354353: input/output error
20:55:17 <V_PauAmma_V> Sounds like you got a dud. Or one that's lying about its size, as I'm told happens.
20:55:56 <polyex> hmmm i'll try another. i ordered 2
20:56:12 <rtprio> ... yeah; a fried of mine got a 1tb usb stick for $30; it was more like 32gb with some sector magic
20:57:09 <epony> might have had an mp3 player embedded in there too ;-)
20:57:33 <polyex> this is a samsung t7 shouldn't that be good? or does conterfeit junk get dumped onto amazon?
20:57:47 <debdrup> SSDs shouldn't get zeroed like that.
20:58:16 <polyex> they shouldn't?
20:58:31 <polyex> why not?
20:58:44 <debdrup> No. Short answer: They have a limited number of times they can be written to.
20:59:01 <debdrup> There are other reasons that can depend on the firmware, but that's the most important on.
20:59:03 <polyex> but it's just once to clear it, so that's only 1 write no?
21:00:09 <debdrup> What was on the disk before, and what are you going to be using it for?
21:00:32 <polyex> new drive
21:00:42 <polyex> gonna use it for freebsd-ufs fs
21:00:47 <polyex> just to put files on and stuff
21:00:49 <debdrup> Oh, so you're doing a burn-in?
21:01:20 <polyex> well whenever i get a new flash mem stick or drive i like to zero it then put gpt and fbsd-ufs on it
21:01:35 <polyex> this workflow worked on flash mem sticks before, this samsun t7 is my first external
21:02:43 <debdrup> Do you have any errors from CAM in the system log?
21:04:36 <polyex> would that be in dmesg or?
21:04:49 <debdrup> It'll be in /var/log/messages
21:05:08 <polyex> grep for CAM or?
21:05:32 <polyex> ya lots...
21:05:46 <polyex> cam status: ccb request completed with an error
21:05:47 <debdrup> tail -n 500 /var/log/messages | nc termbin.com 9999
21:05:51 <polyex> tons of those
21:05:57 <debdrup> Yeah, that's probably a DOA drive.
21:06:29 <debdrup> File an RMA with the seller or the manufacturer, depending on juristriction.
21:09:21 <polyex> is my command list termbin.com/xgmo7 right for future reference? it's to take a new flash stick or ssd, wipe it, and put generic gpt/freebsd-ufs on it
21:09:43 <debdrup> Termbin is just a pastebin that's accessible by sending the data to it via netcat.
21:10:04 <polyex> no i know that. go to that url
21:10:37 <debdrup> I don't see anything obviously wrong with that.
21:12:09 <polyex> ty!
21:12:11 <debdrup> I'd recommend using 2M for the blocksize because it's a factor of 4 but isn't evenly divisible with 4.
21:12:42 <polyex> 2MB up to 1TB capacity, then 4MB for >1TB capacity?
21:12:59 <debdrup> Nope, 2MB for basically anything that doesn't _require_ a certain number of bits.
21:13:43 <polyex> number of bits = block size in this context?
21:13:46 <debdrup> Some 520B sector disks will complain if you try to write anything but 520 bytes to them, but those are rare (and can usually be formatted to use 512B with sg_format).
21:15:25 <debdrup> No, blocksize means the kernel will send requests of that size to the disk, and it's up to the disk cache+firmware to decide how it gets written. 2MB happens to be a medium value between the native sector size of the drive and whatever the size of the cache is, as they usually top out at ~256MB.
21:16:20 <polyex> where does "number of bits" come from then?
21:16:23 <debdrup> Too small and it'll take forever to write, too big and can cause issues with the disks firmware and cache filling up too quickly.
21:16:30 <debdrup> What do you mean number of bits?
21:16:41 <polyex> "Nope, 2MB for basically anything that doesn't _require_ a certain number of bits."
21:17:06 <polyex> basically i wanna know how i can know when something requires a certain number of bits, to know when to use a different block size than 2MB
21:17:09 <debdrup> Oh, I explained that already, but you didn't catch it I suppose - see the thing about 520B.
21:17:33 <polyex> ah
21:17:51 <debdrup> Do you use enterprise SAS drives meant for enclosures made by the same manufacturer? (Ie. EMC drives for EMC enclosures in the past, nowadays Dell drives for Dell enclosures)?
21:17:58 <debdrup> If not, then you don't need to worry about it.
21:17:59 <polyex> ok so 2MB blocks on all external drives no matter the size or type (except the weird 520 byte stuff) got it ty
21:18:08 <polyex> ahh
21:18:11 <debdrup> 2MB blocksize for all drives.
21:18:22 <polyex> k i'll try that
21:18:28 <debdrup> ..unless they're special enterprise drives.
21:18:36 <polyex> btw the 2 new samsung t7s don't show up for gpart show now
21:18:43 <polyex> even when i change the usb port or whatever
21:18:45 <debdrup> Yeah, they're dead. :D
21:18:51 <polyex> wtf
21:19:13 <debdrup> That's why doing a burn-in test is good (though dd isn't the best tool, you ideally want something that can read and verify what it's written).
21:20:06 <V_PauAmma_V> By "not evenly divisible by 4", do you mean "not a power of 4"?
21:20:21 <debdrup> V_PauAmma_V: that's entirely possible. :3
21:20:38 <V_PauAmma_V> </math major>
21:21:11 * debdrup is not good at maths.
21:22:34 <debdrup> For a good burn-in test, creating a temporary pool directly on the drive then doing zpool-initialize is pretty much the best way I've found.
21:24:51 <cracauer> My cstream dd-like tool has reproducible random generated output. So you can first write it to disk and then `cstream -i- | diff /dev/da0 -`
21:25:13 <cracauer> Verifying that all bytes are the same.
21:25:30 <debdrup> Shouldn't that be procedurally generated instead of reproducibly random?
21:26:02 <cracauer> Err, yes. It just uses random with a constant init.
21:26:14 <cracauer> And it's ascii.
21:29:17 <V_PauAmma_V> I'm good at math that makes sense to me. When I was in 3rd-grade-equivalent, I had trouble with long division because I couldn't understand what that apparently pointless procedure had to do with figuring out how many of my 37 slices of pizza each of 17 people would get, with how many left over. It lasted until someone explained not how, but *why* it worked.
21:29:30 <V_PauAmma_V> </tangent>
21:29:36 <polyex> k i just plugged both drives into a mac and they both showed up just fine. reformatted them both just fine
21:30:01 <cracauer> What was the geom commandline to display the mapping between /dev/label entries and the original /dev/ entry?
21:30:32 <polyex> gonna try rebooting or smth i guess
21:31:23 <debdrup> cracauer: geom -t
21:32:06 <cracauer> thank you.
21:33:20 <debdrup> No worries.
21:33:37 <cracauer> I have to say that I find the Linux way of using symlinks to be very convenient for the labels.
21:36:22 <cracauer> I guess it costs some indirections through the filesystem on access, though.
21:38:39 <polyex> the drive shows up in gpart show after a reboot. running dd now with 2M bs. it's running however there were some CAM errors dumped into /var/log/messages
21:39:10 <debdrup> polyex: if you get _any_ CAM errors on a brand new drive, it's almost never a good idea to try and use it. Just RMA it.
21:39:19 <polyex> oh really?
21:39:20 <debdrup> Especially if you're using a filesystem without checksums.
21:40:21 <polyex> i wonder if samsung is putting their defective stuff on amazon
21:40:41 <debdrup> UFS on FreeBSD is at least better off than other Unix-likes, because FreeBSDs lack of block devices mean that the filesystem can correlate I/O errors to filesystem operations, but even with checksums like in ZFS you're still not gonna enjoy using a defective drive.
21:41:30 <debdrup> polyex: even if they were, it's pointless to speculate on it. All production lines, no matter how good, have a failure rate - otherwise, production lines can't be profitable.
21:41:50 <polyex> after dd finishes i'll run it again on same drive but from a motherboard usb port instead of pc case usb port. unlikely but maybe the pc case usb port is defective?
21:42:00 <polyex> oh
21:42:03 <debdrup> Even if Samsung is one of the more reputable manufacturers with certain of their product lines, they still have errors sometimes.
21:42:30 <polyex> well i got 3 of these drives so i'll try all of them. if they all generate CAM errors i'll be really suspicious
21:42:35 <polyex> might even become angry
21:43:58 <debdrup> I'm not familiar with that particular line of their product, but own several Samsunug SSDs in other products.
21:45:08 <debdrup> As for external disks, what I do is use one of these: https://www.akasa.co.uk/update.php?tpl=product/product.detail.tpl&model=AK-ENU3M2-05 combined with an M.2 drive.
21:45:12 <VimDiesel> Title: Portable M.2 SATA / NVMe SSD to USB 3.2 Gen 2 Aluminium Enclosure | Akasa Thermal Solution
21:46:52 <meena> we had logic in traffic server for figuring out the native block size of drives, when using it in raw mode
21:47:23 <meena> I wonder if that's still in
21:48:10 <cracauer> Nice enclosure.
21:48:21 <debdrup> They're fantastic.
21:49:59 <nomia> can u use regular nvme or only sata?
21:50:11 <debdrup> That's the advantage of it, you can do both.
21:50:24 <nomia> (: sweet
21:50:37 <debdrup> And switching between them is entirely toolless (though a little fiddly)
21:51:16 <cracauer> What kind of throughput are you getting with those?
21:55:20 <debdrup> I don't have any USB 3.N Gen2 ports, so haven't been able to test, but Anandtech tested a previous version: https://www.anandtech.com/show/16954/akasa-m2-ssd-enclosures-review-giving-spare-drives-a-new-lease-of-life - though I will say that to reach the highest speeds promised, you'll probably need to cool both the SSD and the controller chip on the drive.
21:55:22 <VimDiesel> Title: Akasa M.2 SSD Enclosures Reviewed: Giving Spare Drives a New Lease of Life
21:56:45 <debdrup> I'd say the main advantage of them, though, is to be able to get a reputable M.2 drive from a manufacturer you're comfortable with, instead of some NoName branded flash that's almost assuredly bought because it was discarded by someone else.
21:57:31 <debdrup> I do recall seeing over 1GBps though, so that's ~fast enough for me~
21:59:53 <debdrup> Wait, over 500MBps.
22:02:12 <V_PauAmma_V> Well, I was wrong about dd reporting end of of as an IO error. "dd: /dev/da0: end of device"
22:09:42 <polyex> k the dd finished, but it says the primary gpt table is corrupt or invalid
22:10:20 <polyex> debdrup btw if i use 2M for dd bs, should i also use 2M for gpart add -l DISK -t freebsd-ufs -a 1M da0?
22:10:31 <polyex> or are they 2 different unrelated things i think?
22:14:21 <cracauer> Might be critical.
22:16:45 <polyex> k rerunning the dd command on same drive but connected to motherboard usb port. tailing /var/log/messages for CAM errors
22:17:04 <polyex> in the meantime i'm checking out that akasa enclosure. looking niiiice debdrup
22:17:26 <cracauer> Costs a pretty penny, though.
22:19:47 <cracauer> Cheapest I can find in the US is $81 on Amazon.
22:29:10 <polyex> dd still running but NO CAM errors yet
22:29:31 <polyex> anyone ever see CAM errors when drive is connected to PC case usb port but not motherboard usb port?
22:46:27 <polyex> still no CAM errors
22:46:34 <polyex> gotta be almost done
23:02:02 <polyex> ok dd finished and not 1 CAM error when drive is plugged into mobo
23:02:11 <polyex> case usb port must have something wonky
23:02:28 <cracauer> USB cabling has always been a weak point.
23:02:41 <polyex> hmm but drive not showing up in gpart show wtf
23:03:08 <polyex> ah there it is
23:03:17 <polyex> after i gpart create -s GPT da0 it's there
23:36:10 <cracauer> This stupid Dell laptop refuses to turn on after I put in a better wifi card :-/
23:59:06 <phryk> I assume there's some device file I can read to get raw PCM audio from mic or other audio channels. Anyone happen to know which one i'm looking for?