PiJiNWiNg

joined 8 months ago
[–] PiJiNWiNg@sh.itjust.works 1 points 1 day ago

Lets not forget Pol Pot

[–] PiJiNWiNg@sh.itjust.works 6 points 2 days ago (1 children)

I call when i hear gunshots.

[–] PiJiNWiNg@sh.itjust.works 22 points 2 days ago (2 children)

I think he's maybe just too obvious a choice and people are trying to be more creative in their answer.

Also, could the harm Hitler caused truly be inflicted back on his physical form? It seems to me like there is no way he could truly pay for what he'd done (if he were to live again).

[–] PiJiNWiNg@sh.itjust.works 2 points 5 days ago (1 children)

10 years ago i might have agreed with that, but these days even when you pay for it you're probably still getting harvested.

[–] PiJiNWiNg@sh.itjust.works 6 points 1 week ago (3 children)

Am i the only one who just presses the windows button and types the setting thry want? I havent looked at control panel forever...

[–] PiJiNWiNg@sh.itjust.works 2 points 1 week ago

Ha! Thats amazing

[–] PiJiNWiNg@sh.itjust.works 2 points 1 week ago (1 children)

How does this article show it was a valid defence? They withdrew, as they knew it clearly wasnt going to work for them, so im not sure what your point is...

[–] PiJiNWiNg@sh.itjust.works 3 points 1 week ago (4 children)
  1. I'll eat my hat if that turns out to be a working defence for Disney, so as a reason to pirate, it's pretty feeble.

  2. Duh?

  3. Hardly. Hollywood is breaking box office records every other month, and the pirating community is very, very small compared to the larger population. Have you looked at video game prices lately? Movie ticket prices? Theyre out of control, seemingly not bothered by piracy in the slightest. Studio lawyers are going after piracy because they have nothing else better to do then pursue every point of revenue increase they possibly can, including going after the small fish.

But you forgot the biggest reason....It's free.

The large majority of people who pirate couldn't give a shit about "digital media preservation". Sure, people all have their own reasons, but to the other commentors point, most people are gonna delete shit right after they listen/play/watch it. Storage space is expensive.

[–] PiJiNWiNg@sh.itjust.works 42 points 1 week ago (4 children)

Man, BBC really scraping the bottom of the barrel for content here 😄

[–] PiJiNWiNg@sh.itjust.works 5 points 1 week ago (1 children)

Did something change in advertising law in the US in the last few years? I feel like ive been seeing this specific phrase in advertising more and more lately.

[–] PiJiNWiNg@sh.itjust.works 4 points 1 week ago (6 children)

Totally agree. The self aggrandizing, "hero of digital media preservation" thing is getting a bit ridiculous.

[–] PiJiNWiNg@sh.itjust.works 6 points 1 week ago

They always say the best gifts are the ones your kids makes you, Chinese parents must get some great stuff.

 

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 ›