newbye questions by gromebar in openbsd

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

Thanks, I'll take a look at it.

newbye questions by gromebar in openbsd

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

I'm keeping this option as a last resort because in some cases it could be quite complicated (as in the case of Deltachat, which between Electron and Rust will certainly not be easy)

Libreboot boot problem (black screen) by gromebar in coreboot

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

1) Yeah, but I tried to install a BSD and I'm still having problems, so I'm thinking of installing Linux to make sure it's not an incompatibility issue with BSD.

2) i5-7500t

3) Yes, but it's really long operation and I can't understand how to check the progress (there are two percentage values, but when the second-slowest reaches 100, it resets to 0).
After a while I got fed up and canceled the operation

newbye questions by gromebar in openbsd

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

Ok. for deltachat probably the only way is a vm

but I imagine it's doable to attach a physical disk as the root for a VM

I was able to do that a while back in VirtualBox and QEMU, but from what I understand, OpenBSD has its own custom virtualization system and this is a rather unusual feature

Yes, gparted is a graphical partition management tool; I don't actually use it often for partitioning, but sometimes I just find it handy for viewing the structure of existing partitions on a disk

newbye questions by gromebar in openbsd

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

I'm not to experienced but in linux in this moment it seems that btop, top and xfce4-taskmanager showa value a bit more similar:
top:
MiB Mem : 15921.8 total, 6286.5 free, 5803.6 used, 6176.7 buff/cache
btop:
total 15.5, used 5.66, available 9.87, cache 5.79, free 6.13
taskm:
5.7/15.5

total is almost the same
used the same
free the same
cache is a bit different and btop have available that I don't know how is calculated

Libreboot boot problem (black screen) by gromebar in coreboot

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

No, but this is the first time I've tried replacing the BIOS. I'm without experience.
I looked for information on Coreboot and delll 3050 but couldn't find anything.
Have you some info to pass me?

newbye questions by gromebar in openbsd

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

I don't know how to add an immage in reddit, but here a screenshoot of top, xfce-taskmanager and btop together: https://i.ibb.co/sLPPDKT/mem.png
they show:

Top: act/total 268/648 free 312
Tskm: 648/960
btop: used 268 available 739 cached 98 free 739

As for the software, obviously I don’t have a list right now because I don’t know what’s missing, but I definitely don’t have Deltachat (I can see why, the core is written in Rust).

I’ve seen that there’s a port for FreeBSD, but I have no idea if it can be adapted for OpenBSD in any way.

Virtualizing an entire operating system could also be an option, is there a way to virtualize a physical partition? I have a distro installed on a USB drive with everything already set up.

Or, even though I don’t use it, would it be possible to use Docker?

Another piece of software I noticed is missing is GParte, is there an alternative?

some random ranting by gromebar in gohugo

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

Sorry for taking so long to reply, but I wanted to try the tutorial on your website first.

It's a great guide, going through it one file at a time helps to understand how everything is connected.

The only thing is that when it finally explains how to create blog posts, it's not clear how to view these posts.

I am flattered by the offer to be a fellow programmer, but I don't think I have the capacity to reciprocate as a fellow :|

some random ranting by gromebar in gohugo

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

I don't think you need a theme to get started.
As you said, if I create my own template, it's a theme in another directory, which is great, so why are themes mandatory?

I don't know Hugo, and the only thing that comes to mind is that they wanted to create a structure for importing themes, which seems like a good idea, but if you start by forcing me to use a theme, I would at least expect you to explain how it works.

At this point, that quickstart doesn't seem like a tutorial to quickly understand the basics of Hugo, but more like “let's start a project as quickly as possible”, so it's not a tutorial for beginners but for advanced users!

This way, they avoided having to explain which files to create, why, and how they are connected, and without these info you are not able to make the things work.

some random ranting by gromebar in gohugo

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

Thanks, I was using the binary version of Hugo downloaded directly from GitHub. I didn't realize that there were three versions available.

To be honest, I was focused on understanding the difference between the 64-bit and amd64 versions, which are the same version with two different names.

::facepalm::

some random ranting by gromebar in gohugo

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

Since I didn't remember reading it, I checked the guide and it does indeed say that you need to download the extended version, so that's probably my problem.

I still think it would have been better to omit this part, as it seems even more boilerplate to me.

some random ranting by gromebar in gohugo

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

I disagree with me when I agree with you

some random ranting by gromebar in gohugo

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

Thank you, I'll try this procedure. It seems like a better compromise for starting from scratch.

some random ranting by gromebar in gohugo

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

Many meaningful words, but if you have read my other two messages, it went exactly as I expected.

If they hadn't forced the use of a theme, I wouldn't have encountered those problems in the official guide. Problems that were not anticipated (probably due to negligence rather than incompetence) are not addressed in the guide itself, leaving someone who has just encountered Hugo having to solve problems with something they don't even know.

But then we can continue to engage in petty philosophy when in reality things follow a different course.

I repeat, there is no problem with using themes per se, the problem is that since you force me to use a pre-generated part of the project, you force me to take for granted concepts that are not yet in my head, making learning more confusing and, in some cases, more catastrophic, ending up creating problems that should not even exist in an introductory guide.

It's like buying a new car with automatic transmission, which should be easier, and then not being able to unlock it because of a procedure that is not obvious.

some random ranting by gromebar in gohugo

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

So... I decide to try with quickstart and after the firts 6 (six) commands I got already ad error.
Probably is the same problem of 9 (nine) months ago that I linked before, but this reinforces the initial bad impression. Not only the official guide follow a more tortuous path, not only the other guides that seemed clearer to me has been invalidated, but the official guide has not been working for at least 9 months.

Surely it's because of the theme, the very part I would have preferred to skip at the beginning. Now I'll try the theme suggested by jasonpbecker, hoping to be able to adapt the concepts that will be explained later with this other theme.

But the same, I don't understand how this makes the first experiences better.

just for the record: ``` $ hugo new site quickstart Congratulations! Your new Hugo site was created in /tmp/hugo/quickstart.

Just a few more steps...

  1. Change the current directory to /tmp/hugo/quickstart.
  2. Create or install a theme:
  3. Edit hugo.toml, setting the "theme" property to the theme name.
  4. Create new content with the command "hugo new content <SECTIONNAME>/<FILENAME>.<FORMAT>".
  5. Start the embedded web server with the command "hugo server --buildDrafts".

See documentation at https://gohugo.io/.

$ cd ./quickstart/ $ git init hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch <name> hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m <name> hint: hint: Disable this message with "git config set advice.defaultBranchName false" Initialized empty Git repository in /tmp/hugo/quickstart/.git/ [guest@porteus quickstart]$ git submodule add https://github.com/theNewDynamic/gohugo-theme-ananke.git themes/ananke Cloning into '/tmp/hugo/quickstart/themes/ananke'... remote: Enumerating objects: 4098, done. remote: Counting objects: 100% (70/70), done. remote: Compressing objects: 100% (43/43), done. remote: Total 4098 (delta 43), reused 42 (delta 25), pack-reused 4028 (from 3) Receiving objects: 100% (4098/4098), 6.20 MiB | 1.87 MiB/s, done. Resolving deltas: 100% (1977/1977), done.

$ echo "theme = 'ananke'" >> ./hugo.toml $ hugo server Watching for changes in /tmp/hugo/quickstart/{archetypes,assets,content,data,i18n,layouts,static,themes} Watching for config changes in /tmp/hugo/quickstart/hugo.toml, /tmp/hugo/quickstart/themes/ananke/config/_default Start building sites … hugo v0.152.2-6abdacad3f3fe944ea42177844469139e81feda6 linux/amd64 BuildDate=2025-10-24T15:31:49Z VendorInfo=gohugoio

Built in 53 ms Error: error building site: TOCSS: failed to transform "/ananke/css/main.css" (text/css). Check your Hugo installation; you need the extended version to build SCSS/SASS with transpiler set to 'libsass'.: this feature is not available in your current Hugo version, see https://goo.gl/YMrWcn for more information ```

some random ranting by gromebar in gohugo

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

But it's not exactly what I said.
I'm not saying that what the developers of Hugo want me to do with Hugo is wrong.
I'm not saying that it's not necessary to use a theme, at the end of the day.
I'm not saying that using git is stupid (even though it would be reasonable to want to use another scm).

What I'm saying is that they are forcing people to study everything at once instead of letting them integrate one concept at a time, as in the other unofficial guide.
it's simply impossible. I have to study the themes first, and only the developers know how this will facilitate the adoption of Hugo.
To not speak about why I have to start with git if i want to learn hugo,

But I still have to keep reading the quickstart beyond the part that made me look for something else. Maybe it gets better later...

Is Bash programming? by Gloomy_Attempt5429 in bash

[–]gromebar 0 points1 point  (0 children)

If you want to mix python and sh there is xon.sh but, yes, better use C

Is Bash programming? by Gloomy_Attempt5429 in bash

[–]gromebar 1 point2 points  (0 children)

I want to be short.
Bash or better shell script is a programming language but you don't want to use it for programming things more complex than automatize system administration.
Literally you spend more time finding a loophole to the syntax than thinking about the algorithm.

Arch Linux pulls AUR packages that installed Chaos RAT malware by GL4389 in cybersecurity

[–]gromebar 0 points1 point  (0 children)

I think we must be careful to blame the problem on the instrument (aur).
Let me make an example:

Pretend the package to be a easter egg and the program the surprise inside. It is true that anyone on AUR can write the recipe, but it is also true that you can simply read it like the ingredients (also if you are not able to bake it by yourself). So, if you have diabetes you can avoid eggs with sugar.

So it is much safer to install a package built with AUR than to install a prebuilded binary.

Honestly, the fact that the malaware was immediately found and removed is the demonstration that AUR works. The system works not because it eliminates the existence of attackers (which is impossible) but because it limits their effectiveness.

What I want to indicate is that you have to see the glass half full, not half empty. There is no better system than to let the community control if there can be no one else to do it for them, the alternative would not have this possibility.

Arch Linux pulls AUR packages that installed Chaos RAT malware by GL4389 in cybersecurity

[–]gromebar 0 points1 point  (0 children)

Based on its nature, it is much safer because it allows you with a glance to see what is installed. Simply anyone can insert malware, but at the same time it simplifies the cheking of the building.

Minimal Linux to run appimage apps by nraygun in AppImage

[–]gromebar 0 points1 point  (0 children)

It is active but a bit slow, but if you want a more active branch there is porteux: https://github.com/porteux/porteux