PiJiNWiNg

joined 10 months ago
[โ€“] [email protected] 1 points 5 days ago

Thank yoy so much! I actually lay out the method step-by-step in one of the comments. ๐Ÿ™‚

[โ€“] [email protected] 3 points 6 days ago (1 children)

If you're willing to pay for premium, Proton supports custom domains and catch-all addresses, so you can cut out all the extra mail relay stuff. Just give out [email protected], and it all comes back to the same mailbox. If it gets compromised, just set up a rule to trash anything to that address.

[โ€“] [email protected] 2 points 6 days ago

PORK CHOP SANDWICHES

[โ€“] [email protected] 2 points 1 week ago

Awesome! I resin printed some batarangs myself! I did four different styles from different movies, then picked up a shadowbox frame and some red velvet and mounted them vertically with some wire. I ended up giving that to my younger brother as well, lol.

[โ€“] [email protected] 16 points 1 week ago

So now this satellite can be an "anomaly" for another satellite, and the circle of life continues...

[โ€“] [email protected] 3 points 1 week ago (2 children)

Gave it to him today and he was stoked! Also figured id post a detail shot of the base:

[โ€“] [email protected] 2 points 1 week ago (1 children)

Of course! But it's all filament, specifically PETG. ๐Ÿ™‚

[โ€“] [email protected] 2 points 1 week ago (3 children)

Not sure id say "prefer" as i don't have experience with many others, but i used rustoleum sand and fill primer from amazon

[โ€“] [email protected] 4 points 1 week ago

Just realized i should probably share the STL link in case anyone wants to make their own: https://www.thingiverse.com/thing:4245103

[โ€“] [email protected] 7 points 1 week ago (1 children)

Its translucent green filament with green EL wire run through it, with the battery pack stored in the base.

[โ€“] [email protected] 0 points 1 week ago

I was about to put in my two weeks notice I when i had to run out to one of our sites to update the firewall. Fortunately, i happened to have a 3d printed "dick-o-saur" in my backpack, and placed him atop the rack before taking new photos for documentation.

 

Really happy with how it turned out! Decided to show it off to strangers for now as I haven't given it to him yet and i know he isn't on here. ๐Ÿ˜†. And it lights up!

 

Hey Folks, I have a bit of a conundrum that I'm hoping the hive mind can assist with.

I am in the process of learning docker to prep for my migration to Linux, but I have some questions about my filesystem structure. Currently my media files of all types live on a single file-based iSCSI LUN hosted on a QNAP which I connect to from a Windows machine. In my research to see if this would be consistent with best practice, I came to the conclusion that I should create independent NFS shares that the docker containers would connect to individually, rather than serving the files to the containers through the host and it's iSCSI connection.

This leads to my problem.

I can't seem to find any way to directly copy data from the LUN to one of my newly created NFS shares. With the volume of data I'll need to copy I'm trying to avoid as much overhead as possible, and using my Windows machine to connect to the new NFS share, then transferring the files from the iSCSI share, would be ludicrously inefficient.

As I'm able to SSH into my NAS, my first thought was to try and mount the iSCSI file locally and rsync the contents directly to the NFS share. After finding the home of the iSCSI file in the NAS filesystem, I discovered that it is not stored as a single, mountable file, but broken up into 1TB chunks. This leaves me unable to mount it, even in part, as each of the files lack an identifiable filesystem. Further, this is my largest partition, and so I don't (currently) have the space to attempt to concatenate the files into a single file (assuming that would even work, no idea).

After giving up on this approach, I decided to try and log into it's own external iSCSI target (from the NAS), then mount the LUN as I would from an external client. I thought I might be in the clear, as the login was successful, and both iscsiadm and the NAS GUI showed the active session to itself. But no matter where I looked I could see no evidence of a newly available partition, only those that were there from before I connected to the iSCSI target.

At this point the next step seems to be shrinking the partition and trying to concatenate the iSCSI files as I mentioned earlier. I have the space to play with, but I'll need to convert the volume to thin-provisioned, then shrink the volume, which would likely take foreverrrrrrr. But really, even this option sucks, because I'd prefer to avoid jeopardizing my primary storage volume in changing the provisioning style.

So anyway, after banging my head on it for the last few hours, I decided to step away and do some "rubber ducky debugging" with you guys.

So here are my questions: Is migrating to NFS worth the effort? Would the file concatenation method even work? COULD the loopback iSCSI method work if I do something differently? Any other tricks, or maybe something in the QNAP App Marketplace?

Any assistance welcome, thanks for reading!

 

Didn't see any posts about it in here yet so thought I'd share!

 

I've been considering a switch to Linux for my main rig, which also runs my Plex and associated services. Does anyone have any advice for me regarding distro, tool compatibility, similar tools to consider while switching, gotcha moments, losses in key functionality, etc. Any advice appreciated!

view more: next โ€บ