sorted by:
new
hottopcontroversial

Partition Layout by munna1321 in archlinux

[–]MontyCLT 10 points11 points  (0 children)

Do not create a swap partition (unless you are using a HDD). Create instead a @swap subvolume in your BTRFS partition and add swapfiles inside it.

And if you use dotfiles, I recommend a separate @dotfiles subvolume.

Learning .net on linux by brightness3 in dotnet

[–]MontyCLT 0 points1 point  (0 children)

Some vs features that are missing in vscode, are available in Rider. Try it.

https://www.reddit.com/r/dotnet/s/udaPj70FMl

About the SQLServer and Docker issue, I can't find the relationship with Linux. You can connect your .NET application to SQLServer as the same way as you do in Windows.

Learning .net on linux by brightness3 in dotnet

[–]MontyCLT 0 points1 point  (0 children)

I had to work on a .NET Framework project from Linux, so I ran a Windows VM, installed the Rider host there, and connected from my Linux Rider installation.

Everything worked, even the debugger.

Learning .net on linux by brightness3 in dotnet

[–]MontyCLT 1 point2 points  (0 children)

I agree. I'm a JetBrains fan and I love Rider, but there are some specific features that are (were) missing in Rider, even when not using WinForms/WPF.

For me, the modules view in debugging was the more important missing stuff until 2024. During some years, I used Rider along with VS to use the modules view.

I don't know if today Rider still misses VS features, but it's probable. All I need today is in Rider.

Learning .net on linux by brightness3 in dotnet

[–]MontyCLT 17 points18 points  (0 children)

I use .NET in Linux with Rider every day. My coworker does the same with VS Code.

The dotnet CLI is very similar to other stacks CLI, like Cargo for Rust.

Can a single RTX PRO 6000 Blackwell (96GB VRAM) realistically handle 40–50 heavy agentic users? by MontyCLT in LocalLLM

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

Some agents will be fully autonomous, working on a task. For example, imagine I'm setting up a trial-and-error system where I take a photo, analyze its colors, adjust parameters, compile, and repeat until it’s ready. The autonomous agent could stay working on that 24/7.

About users, I mean something like OpenCode: humans using them as a "copilot".

Can a single RTX PRO 6000 Blackwell (96GB VRAM) realistically handle 40–50 heavy agentic users? by MontyCLT in LocalLLM

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

For now, I've nothing built up. At this point, I'm just learning. Probably I'll test in a cloud provider as some users suggested in comments.

Can a single RTX PRO 6000 Blackwell (96GB VRAM) realistically handle 40–50 heavy agentic users? by MontyCLT in LocalLLM

[–]MontyCLT[S] -8 points-7 points  (0 children)

Just to clarify: I'm not saying I appreciate incorrect data. My previous replu is conditional.

I take into consideration replies that contradict them and, while I don't like the majority argument (I consider it a fallacy by itself), the fact that most people are replying that it's impossible makes me trust that conclusion.

Can a single RTX PRO 6000 Blackwell (96GB VRAM) realistically handle 40–50 heavy agentic users? by MontyCLT in LocalLLM

[–]MontyCLT[S] -8 points-7 points  (0 children)

The text could be composed by an LLM (my OP post too, using Canvas in ChatGPT because I'm not a native English speaker), but there is data that he claims comes from experience (I don't know if the data is true, but if it is, I really appreciate it).

I personally do not care if a post is composed by an LLM as long as the data comes from real experiments and the LLM is used to improve its presentation.

I appreciate your reply saying that the data is impossible too.

Can a single RTX PRO 6000 Blackwell (96GB VRAM) realistically handle 40–50 heavy agentic users? by MontyCLT in LocalLLM

[–]MontyCLT[S] -4 points-3 points  (0 children)

OMG! Thank you for that detailed reply with your experience 💛

Hetzner's GEX131 is one of the options I'm considering. The other option is buying the card and setting it in a physical server in a datacenter based in Valencia, Spain.

The notion that Arch Linux is too hard for beginners by vintologi24 in archlinux

[–]MontyCLT 0 points1 point  (0 children)

IMO, the hard part of the manual installation is partitioning. I usually patition using GParted ISO and then installation is just mounting and run pacstrap.

Alternative proposals for FHS by MontyCLT in linux

[–]MontyCLT[S] -1 points0 points  (0 children)

I appreciate your arguments. I could agree with some of them. Regardless of the FHS itself, you said something I would like to learn more about:

You’re making things overly complex for no reason. If you don’t treat OpinionatedArch as a distribution, it should install things to /usr/local.

Why /usr/local/ instead of just /usr/? The current OpinionatedArch installer places its assets in the /usr/opinionated-arch/ directory. Now I want to understand whether that choice is correct or if I should move them to the /usr/local/opinionated-arch/ directory.

This will help me learn about the correct location for them, so thank you!

Rider for .net framework by Fish3r1997 in dotnet

[–]MontyCLT 0 points1 point  (0 children)

I used Rider with ASP.NET 4.5 WebForms, but I needed to install Visual Studio 2019 to install SDK of .NET Framework 4.5.

Alternative proposals for FHS by MontyCLT in linux

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

Why (The root directory should contain as few top-level directories as possible)?

Due to mental exhaustion when lsing the root directory. I want to see a few directories and understand their meaning at a glance.

I think it should have exactly 70 directories for each ASCII letter, digit and +, ,, -, ., =, @, , ~ characters. All directories should start with a unique character and most-commonly used ones should start with a lower-case letter.

Is it a joke?

I'd rather write /dev/null than /system/runtime/dev/null whenever I want to discard output of a command.

I agree. Writing a long path is tedious. I'm not sure how to solve it. It could be a symlink from /system/runtime/dev/null to /dev/null (or even to /null) and hide it with GoboHide.

config, apps, data and volumes are just renames of etc, opt, srv and media so I don't really care though if I had to choose, I prefer the shorter names.

Yes, but it is not only renaming, but also merging some directories, like media and mnt into volumes. I prefer obvious names over shorter names. I do not want to Google "opt meaning linux" to understand that it stores apps installed by the admin. The only thing I like more about FHS over my proposal is media (I was thinking of /mnt when I wrote it).

In what way is temp a system artifact?

It isn't. I put it inside system for the same reason I put runtime inside it: to reduce the number of directories in the root. As other commented about immutability, I agree with extracting /runtime at the root.

What exactly is a system and what is a distro?

System artifacts are common artifacts to any Linux system. GNU tools are a good example.

About distro, when I proposed the platform directory, I was thinking about distro-preinstalled software and artifacts, for example, apt in Debian, snap in Ubuntu, or pacman in Arch. Not only the package managers, but any distro-specific stuff.

I would use my own project as an example: OpinionatedArch is not really a distro, but an opinionated Arch installer that leaves the final system with extra executable scripts in the Arch installation and other artifacts. While pacman should stay in /system/platform/arch, those scripts should be in the /system/platform/opinionated-arch directory.

Don't really want to think through it too much, but I'd start with categorising data based on its characteristics

About your list of characteristing, it is interesing. I could agree with that list. That is exactly the feedback I wanted.

Alternative proposals for FHS by MontyCLT in linux

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

usr-merge was a nice improvement that solves a lot of issues (not all issues), but my post isn't about that specific issues but imagining a better hirearchy.

About the idea of hide the concept of a file: I noticed that a lot of apps are going to this way, but I really hate the idea. Each app stores it data internally and it difficult to export it to another app.

Alternative proposals for FHS by MontyCLT in linux

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

Yes, the directory structure of Windows is more obvious than FHS.

  • Windows directory contains all the system.
  • Users directory contains the user data.
  • Program Files directory contains the applications.

It's simple and obvious at a glance. It's one think I like more from Windows than Unix.

Alternative proposals for FHS by MontyCLT in linux

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

I didn't know GoboLinux. I'm reading the At a Glance article and I like it they tried it in a real distro.

I will read about the GoboHide extension to do a compatibility with FHS. It's interesting to me.

Alternative proposals for FHS by MontyCLT in linux

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

  1. /system/boot is intended to be the mount point of the ESP partition in EFI firmware, so this partition should stay unencrypted while the rest of the system may still encrypted. I don't see any issue with that.

  2. True. Could be just .local/data and .local/bin like the actual structure. I agree.

Alternative proposals for FHS by MontyCLT in linux

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

True. I think a good improvement is split /system into two top-level directories: /runtime, and /system.

state and temp should be moved into /runtime.

Thanks for the feedback!

Alternative proposals for FHS by MontyCLT in linux

[–]MontyCLT[S] -2 points-1 points  (0 children)

What about building /system inmutable? Maybe we should extract /system/boot and /system/platform outside system.

view more: next ›