is there a $1 VPS with FreeBSD ?

Comments

• whynotlearn Member

  January 20

  @dedicados said:
  Hello, i am looking a simple vps with freebsd just to learn and test. nothing fancy.

  I don't want charity or a free VPS (To get it, you must jump three times and land with your hands on a chair.)

  $.01 - $2.0 per month max.

  checked on my actual providers but none has Freebsd to install on the vps.

  dedirock delux and racknerd, tna, solid, veluxscam (fuck you), no need to tag them.

  thanks

  If you are willing to jump through some hoops, Scaleway kind of allows a 1 gb server for around 3$ per year (technically says 1.10 euros per year but I am assuming some extra thigns I am not sure) if you can follow a guide similar to this but for bsd instead (please try this, there is no guarantee about this, do it at your own precaution but I feel like there is a strong likelihood that a qcow image can be built/used with bsd)

  If you are still not sure & want to confirm, scaleway has a slack server you can join and ask. I would recommend you to do so

  https://www.scaleway.com/en/docs/tutorials/create-openwrt-image-for-scaleway/

  https://www.scaleway.com/en/pricing/virtual-instances/

  (look at the stardust 0.10 euros per month)

  Some additional costs are also here in the legal notice page let me paste it here for you

  Unified Snapshot will be billed at €0.000044/GB/hour.

  Flexible IP is billed at €0.004/h.

  Prices before tax.

  The price is different for DC PARIS 3: please check it in the console.

  Hope this helps
• TimboJones Member

  January 21 edited January 21

  @rcy026 said:

  @TimboJones said:

  @rcy026 said:
  but calling FreeBSD a distribution is not correct and most people hate it.

  BSD is an acronym. If they hate it so much, change the D to something else. Arguing it's not what is in the name should have resulted in a name change decades ago.

  Well, an operating system is software and they do distribute software, so the acronym is not incorrect. The difference is that in the case of linux distribution is used as a noun, which means a thing, a software distribution, while it in the BSD acronym is used as a verb, something you do, you distribute software.

  What? It's definitely a thing, a noun. I'm no English expert, but that's a noun. I've never heard of anyone misunderstanding the acronym like you before.

  I've never heard of anyone misunderstanding the acronym like you before so I do not think they will change an acronym that predates the existence of linux with a decade or so just because of that.

  https://forums.freebsd.org/threads/freebsd-distributions.76628/post-474504

  I seem to align with Mjölnir (post 9 in the link). From what I can tell, it was referred to as a distribution from the start, it's only when Linux came along that the term changed in usage.

  "Epic" used to mean fucking long, not fucking awesome, but some dumb kids kept saying it and now it's also known as awesome.

  But really, I don't give a shit. I don't use BSD and it's been years since the last time I discussed it. I'm also never going to say Linux/gnu even if that's correct.

  Edit: funny enough, Google had this response, which says noun but I would have guessed verb based on the example. Hehe, English was my worst course in school.

  Dictionary
  Definitions from Oxford Languages · Learn more
  dis·tri·bu·tion
  /ˌdistrəˈbyo͞oSHən/
  noun
  the action of sharing something out among a number of recipients.
  "she had it printed for distribution among her friends"
• ralf Member

  January 26

  @TimboJones said:
  Has WSL2 made that less of a hassle or switching to WSL2 is more hassle after years of tweaking what works?

  So, I did a more more playing with WSL over the weekend as it turns out.

  I wanted to test a new LLM thing that was released last week that sounded interesting, and figured this would be a good time to try out running it on WSL as the LLM needs CUDA (and so a decent nVidia GPU) and I don't have Linux on any such machines.

  There's a small gotcha with CUDA which I read about and dealt with before encountering it - there's special version of libcuda that knows how to talk across the hypervisor, and if you just let Linux update the nvidia driver it won't work any more as it gets overwritten. So you just install / update one package rather than everything. This is documented here: https://learn.microsoft.com/en-us/windows/ai/directml/gpu-cuda-in-wsl including the link to the nvidia page that tells you what debs to add. For my purposes, I had to install 12.9 rather than 13.1 as per nVidia's instructions.

  And then, I just created a new user inside WSL, set up a python venv and installed everything. It just worked, not a single issue, and seems to nicely share GPU between desktop apps as well.

  If I can get WSL starting on boot and fix the shutdown issue (I've seen a post that addresses both my having a user Windows startup task that runs wsl nohup sleep 99999999 but that feels a bit hacky!) and my wireguard issue, I think I like this setup.

  One thing that's a bit weird is WSL2 has an IP4 address of 192.168.45.32/20 and the host machine is 192.168.32.1/20. There doesn't seem to be any way to change this, so it might conflict on some network setups, but also it makes it hard to connection to the WSL from elsewhere. Between Windows and WSL2 you can just just localhost and some magic happens that sends things to the right underlying IP. It seems there is a way of using windows firewall to open up ports from outside to WSL2, but I've not figured it out yet.

  If I do get this firewall working, it'd be quite nice so that I can switch from using visual studio to debug my app backend to running it under linux. On Windows, I can just listen to 0.0.0.0:8080, but other machines can't access that doing the same in WSL.

  But anyway, the summary is that WSL2 is actually better than I discovered last time I tried it.

  Thanked by 1TimboJones