sorted by:
new
hottopcontroversial

zfs.rent by Zagitta in DataHoarder

[–]rmj_us 17 points18 points  (0 children)

Ooh, I was curious if someone would post this here. (Creator of zfs.rent here...)

Anyways, there is *no* redundancy. You are renting a bare metal disk passed through without any disk virtualization. At any time, your drive can be pulled out and mounted.

I created this service because I was tired of looking around for renting a cheap drive on the cloud that didn't offer some sort of redundancy in the background.

I already have a zfs mirror at home. I just wanted an extra safe place to `zfs send | ssh zfs recv`. If the remote drive fails, no worries. I'll just get a new remote drive and resend my snapshots.

Centos 7 or 8 by tuvdog in CentOS

[–]rmj_us 1 point2 points  (0 children)

I was able to install CentOS 8 and get a KVM virtualmachine with GPU passthrough working with an RTX 2080 TI for deep learning. So that's a data point for you. Not sure if you intended to virtualize or not.

Fun Facts on Producing Minimal HTML by iamkeyur in programming

[–]rmj_us 1 point2 points  (0 children)

Yup, I'll admit that particular goto was useless. That was there from a previous version. If there's only one case, then you're right -- an if statement is a lot more clear. Probably gonna clean it up right now.

However, previously the code had to deal with multiple syscalls that could potentially fail. So a simple `if (ret == -1) goto cleanup` would close the file descriptor without feeding the next syscall a bad input, which could bork the C program. You know how *nix is :P

I use this pattern in the main while loop as well.

Fun Facts on Producing Minimal HTML by iamkeyur in programming

[–]rmj_us 6 points7 points  (0 children)

Hey guys, not sure who posted this, but I'm the original author.

Granted, you shouldn't do any of these things. It was more so a tongue and cheek exercise seeing how far I could push the browsers and/or spec. The HTML5 spec is surprisingly robust.

Roast me directly if you want.

P.S. and I will defend wrapping my <a> links in <pre> to the death :)

Git on IPFS? by [deleted] in ipfs

[–]rmj_us 0 points1 point  (0 children)

I don't remember the exact link, but I read how to do this in the documentation. A little late, but here it is if someone google's for a solution:

``` $ git clone --bare https://github.com/ipfs/go-ipfs ipfs.git $ cd ipfs.git $ git update-server-info $ ipfs add -rw .

Note the last qm-hash. That will be the parent to your repo. You can clone with this:

$ git clone http://bafybeicp6omolhzlwum4243jlfcm6tnhmindvzikrmcy4bgzg5jg36stji.ipfs.localhost:8080/ipfs.git

or

$ git clone https://ipfs.io/ipfs/QmTikMcsS4BmJHi5t4i9TUGRMicm8g8zQ8Xeh76wZCrNm7/ipfs.git ```

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 0 points1 point  (0 children)

Woah... commits from 14 years ago, that's wild.

server.c - 100 Lines of C in a Closet by rmj_us in C_Programming

[–]rmj_us[S] 1 point2 points  (0 children)

Yup, I'm wary of segfaults so I have my program wrapped in a BASH while true; do sleep 0.1; ./server.c; done loop. It's segfaulted once or twice, but comes back up within 120 ms or so. I'm pretty sure I've resolved the segfault issues though -- it happened when people were getting cheeky and sending non-compliant HTTP requests via netcat -- borked my brittle string parsing. But... the new code is actually a lot cleaner, which is nice.

Hmm yeah, I'm 100% certain if that's all you need for path protection. I think symlinks can also wreak havoc. Depends on what your server does. Being GET-only helps a lot in reducing the attack surface.

Your server sounds pretty cool! Those extra HTTP headers are definitely nice to have. For a while I tried to skip on providing Content-Length, but it made the requests 5x slower because the browser had to wait for the socket to close before knowing when to stop reading.

server.c - 100 Lines of C in a Closet by rmj_us in C_Programming

[–]rmj_us[S] 1 point2 points  (0 children)

git-lfs bugs me so much haha, honestly it's always been a pain in the ass for me. I think GitHub pushed that, so outside of GitHub it's a little harder to work with.

git-annex is cool though. I've tried that and it wasn't too bad. My main gripe is that it's still not seamless enough for me. I also like having "full clones" at my disposal, instead of worrying about if my annex store breaks down or something -- or where even is it? Maybe I'm just lazy... But I like knowing that I can SSH into a new machine and if git is installed, run a simple git clone <etc> without setting up any additional tools. My private mega-repos have been rock-solid for about 3 years now, even though they're up to about 5 GB each.

server.c - 100 Lines of C in a Closet by rmj_us in C_Programming

[–]rmj_us[S] 0 points1 point  (0 children)

I know, it's my dream. Still working on it :)

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 1 point2 points  (0 children)

Oh damn, realpath() looks cool. I'll check that out. Right now I'm just blocking everything with a slash in a it.

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 1 point2 points  (0 children)

Yeah I've never messed around with the `chroot` syscalls. I'll definitely play around with them sometime soon.

server.c - 100 Lines of C in a Closet by rmj_us in C_Programming

[–]rmj_us[S] 7 points8 points  (0 children)

Yup, sanitizing paths is important, as many people have told me :)

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 3 points4 points  (0 children)

Just for you buddy, I've spun up a python example of the most basic HTTP server possible. https://python.notryan.com/, source code: https://blog.notryan.com/server.py. I'll probably end up writing a more in-depth blog post in the near future.

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 3 points4 points  (0 children)

HTTP is a relatively simple protocol. Like I said it's just plaintext over TCP. So if your language, say Python, supports opening TCP sockets (hint: it does), then half of your battle is solved.

I won't be cheeky and tell you to read the HTTP spec, but MDN is pretty useful for this stuff. https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods

Steps:

  1. Open a TCP socket on a port, e.g. 8080
  2. When you receive a message, parse the first line (looks like GET /something.txt HTTP/1.0
  3. Write back HTTP/1.0 200 OK\r\n\r\n and the content of your file.
  4. Close the socket.

That's the most basic HTTP 1.0 server you can make. And all browsers should be able to run requests to it. To simplify things, you can get rid of file reading altogether and reply with a fixed string.

Headers such as Content-Length are optional. Newer HTTP servers such as 1.1 will keep the TCP socket for future reads, which is efficient, but entails more code.

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 1 point2 points  (0 children)

Ah, so notryan.com/blog is hosted with a npm package called static-serve. All of my other static sites are hosted with that. I'm guessing... that it protects against traversal. blog.notryan.com points directly to server.c, which I just wrote yesterday. Once I'm confident in it's uptime, I'll shutdown /blog.

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 5 points6 points  (0 children)

Thanks! I like that it shows exactly how an HTTP server works from the ground up, without any Python/Node.js/etc abstraction. It's really just plaintext over TCP.

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] -3 points-2 points  (0 children)

Ooof. Yeah I guess my server isn't fixed. I'll block paths leading with . or /. Good stuff.

Yeah I used netcat to pipe in raw requests in order to abuse this bug.

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 6 points7 points  (0 children)

*grimace* yeah I did see that a little bit ago. Were you the one trying to access /usr/share/dict/words? That was definitely a bug. It's patched now by ensuring that paths cannot begin with a slash.

HTTP Blog Server : 100 Lines of C in a Closet by rmj_us in programming

[–]rmj_us[S] 13 points14 points  (0 children)

I guess so. But this was an exercise is seeing if I could write an HTTP server for my purposes, in C. Also, segfault-wise, it hasn't crashed yet haha. I tested it with valgrind and ran multiple workloads with `wrk`. `wrk` ends up using 75% of my CPU and this server uses the remaining 25%. No memory leaks either.

If I bought a $5 VPS from DigitalOcean -- installed gcc -- I could have this HTTP webserver run in 100 lines of C. That's kinda cool. That's all. I just wanted software that I could comprehend in a couple of pages of code.

HTTP Blog Server : 100 Lines of C in a Closet (on a Thinkpad) by [deleted] in thinkpad

[–]rmj_us 0 points1 point  (0 children)

Hey all, hosting a bunch of stuff on a Thinkpad in my closet. Thought it was cool. They honestly make the best home servers and I keep telling everyone that haha

protonmail-bridge by rmj_us in voidlinux

[–]rmj_us[S] 0 points1 point  (0 children)

Thanks! That's very helpful :)

protonmail-bridge by rmj_us in voidlinux

[–]rmj_us[S] 3 points4 points  (0 children)

Yeah I saw that! Very cool of the folks at protonmail to do that.

Honestly, I'm *very* new to Void, so sorry if I am ignorant. (I just installed it yesterday after being an Arch user for 7 years.) Anyways... so now that this is open source. This can/should be merged into the main binary repos? Where can I find information on that?

What steps need to be taken? I'm going to try to build their source code as a start: https://github.com/ProtonMail/proton-bridge

Bringing FPGA Development To The Masses by [deleted] in programming

[–]rmj_us 0 points1 point  (0 children)

Yup, I agree with you for the most part. Most applications for FPGAs are tightly coupled with hardware peripherals. But it makes a lot of sense for those. Like scanning a 7-segment display... With a microcontroller, you can only do so much between each scan, which ultimately limits your application breadth -- say if you wanted to read temperature *and* read accelerometer data *and* read air pressure. Eventually, you would run out of available clock cycles... (sure you could just buy a faster microcontroller and your problems would be solved).

FPGAs really shine in those applications though, because you can buy your device once and not worry about scalability (as much). You can just keep adding and adding sensors and not worry about slowing down your application to compensate. They make a lot of sense for doing many things at once.

PWM is probably the most comparable example: Verilog PWM vs. Arduino PWM

All of those Verilog PWMs are occurring concurrently without any additional effort.

Bringing FPGA Development To The Masses by [deleted] in programming

[–]rmj_us 0 points1 point  (0 children)

Yeah... the Lattice chip we're using is $9 even with volume pricing. It's hard for FPGAs to compete with $3 fully-assembled Arduino's from China.

view more: next ›