Adwaita (font) Fan!

So, I can't do the next step the way I've been doing this so far. There's a lot more going on now than I expected - like ... at first we have to set this thing up. I mean, the next step is essentially the part where I "start over" after having gotten a base setup. Here I would normally also ponder like: Technically I could just write a thing here and ship it - like, a thing that you'd then write where I feel like, taking that away is where I thought: Nah, this sucks - so, let me just go on until ... .

So, for this next step to click it has to click and that's the difference then. So - on the one end then we're looking at what path__Root and path__Source can do for us; Which is a little different in linux than it is in windows.
And on the other hand I think it means something that I keep coming back to this setup. So, technically I could have released it years ago - but it also wouldn't have meant the same and ... I suppose the difference is in the nuance.


Like so, death of the author. I'm currently using linux in utter disregard of its inventors intentions and ambitions. I wouldn't even be able to tell. I can derive as much as that within his intentions was enough good to make it free for all - and his skill fine enough to make it take off. So, Linus ... what a chad!

Well, now however I also feel like what I do might take off, rather than drown in the confusing tensions of the world.


Anyway. So, I figured - since we're using Linux and we've done some efforts to allow you to do the same, I also feel obligated, somehow, to mentally prepare you for the transition somewhat.

1. Everything in Linux is case sensitive and every file and folder has ownership and permission tags. And that is immutable.

And it comes as a double edged sword. Within the space the user is given, that is their individual home folder, they are free to do as they please unless someone with administrative rights messes with that. So, every file comes with a user and a group id - and ... to my mind it is a bit confusing. The way this works is dependent on the system it's written. Because Windows filesystems don't work like that at all, linux would treat one such file as one with zero restrictions on it. And that's a weird thing ... within linux.

But with all those restrictions then also come issues once you ... have the freedom of being root and main user at the same time.

Also, in shared spaces ... well. I'm under the impression that there have to be solutions for this - while on the flipside it is | ... and that's it. I'm technically out of weed now ... . And yea, I've spent all my Christmas money on Gunpla, a PS5 Controller and Drugs - my smoking appliances are looking sad, a variety of stuff is broken and I'm broke ... | also just respectful to have files tagged by their owner and be static that way. If it needs to go an admin can do that. It's not inherently bad that such processes have to be like ... ordered and approved. And there may be situations outside of networking where that's the better way. But in normal day to day life, I'd argue, it's more often a point of unneccessary friction.

The trick would be done by some service that maintains some kind of default group and access mask for files, having the implied 'manual' option being somewhat sensitive to the environment.

That, I would assume, does however come with ... extra effort that is in some way also ... within the scope of what I'm working on. I mean, ultimately ... . The idea to work out an operating system was there before I learned more about Linux. So, there's no conflict of idea or interest there. But yes. Anyway ...


And the rest is mostly just an aspect of this one issue. Outside of that, I have no idea how Linux development works, how to get "into" it; And that may be a good thing.

I mean, first you need to be able to actually contribute something - so that when people actually get to use it, they can decide whether or not it means anything.

But as for getting into the know of the how of the various things ... well. That's like a door I haven't opened yet. I see that eventually I'll have to take a crack at it, but before I can do that I need something to actually work with. And that's also ... yea, where we take the turn towards the project as I'm somehow trying to sober up.
Yea, it's a matter of time.


Oh - yea, the way linux handles access rights may be ... insufficient. It sure makes sense, but not all the sense. Maybe. It's like ... it depends. So, there's read, write and execute. It may all be sufficient, but when it comes to 'write' - we technically have: alter, move and delete. Those would be three distinct processes with their own distinct purpose and quirks. Like read and execute are somewhat the same but also not. So, move and delete are the same thing, sort of - but delete is extra. So, for all you need 'write' access, but there is still an escalation in what can be written or what the system tries to protect.
Which may ... also be one of those software side solutions to make reasonable use of the given/implied permissions.


In crystals/libra/whatever ... or "Libra MetaSystem" ... I've already kind of low-key homed in on leaving file markers in folders to assign parameters to them. But it's all a little bit ... more complicated than that. ...

The issue, I almost lost track, is that right now I'm still free to say what I want to be working on. Or ... towards. In a sense. But then again ... oh, so, it wasn't important. So, my mind sent me rambling towards this issue - it happens - so, good to know. It's not a bad thing or wrong - it's just that technically there's no target or goal here. It's just that whatever goal I would pick, there's a certain few steps I shouldn't skip. Not at this point.

But so, I'm trying to get my bearings - and see ... how we're going to do this. So, the first time I got set up I already linked up some of my ntfs folders to ... points "in the system". I'm set up in a way that just by browsing the root, there's no access to the ntfs partitions. Dolphin however uses other methods to read out what's accessible - and so it's easy with Dolphin to circumvent that boundary. And so should Dolphin also be a good indicator to what is ultimately accessible and what not. Like, when using the (hidden) side-bar folder-tree thingy, it cannot show me those filesystems as it tries to resolve the actual path to the actual file. So, when it cannot list a directory it stops.
While we're at it: When not unmounting ntfs partitions properly, the system can fail to access them. You need to run 'ntfsfix -d /dev/sdXY' to clear the 'dirty' flag.
"There should be a way to do this automatically" - I guess. Maybe it's a root thing.

And so, technically, to be really doing this right - the base systems of crystals are property of meta. So, it would only make sense to have the critical system includes here in the meta folder. So ... hehe ... using dolphin I can do the following:

First I open up my 'volume' or whatever, here I have all my code archived in a folder named _MIRROR_. Mirror means, this is supposed to be in sync with my backups. I load my backups that I want mirrored into my local Mirror - and copy files I want to backup from my local system into the Mirror also. This way I can easily check with my backup "mirror". There can similarly move backups from the mirror into storage.
Maybe there ought to be a better term as mirror would also refer to an ... hmm.
Sure, but it works a little differently? Anyway ...
So, using the split view, I can then copy a source from my mirror archive into my other ntfs partition (16 GB for good measure - I mean, if like ... icon themes in linux can have a casual 64 to 128 MB ... well ... . Not that it matters. I tried qt6ct - I tried theming in cinammon, it's like ... nothing changes. The only effect that qt6ct seems to have is on itself. I mean, filezilla looks different in cinnamon and I'm sure there's a way to fix that ... I also haven't tried everything I know of yet, so ...) - now I can right click on home, select open in new tab - open another split view into my crystals partition - where ... well, let's think.


One advantage in linux is that in i3 for instance I have to hit win+return and now I can compile code. It doesn't matter "where" I am in the filesystem. So ... just starting with a simple nano hellothere.cpp ... 'gcc hellothere.cpp -o hellothere.bin' and then './hellothere.a' ... works. So, the goal should be to set this up as it's in windows. To that point we'll then need a shell script - ... and I just realize that this is going to take a while.


Problems: Well, everything in linux is case sensitive. So, some includes had to be adjusted.
Some libraries are named different, updating.
See ... when changing gcc to g++ in the 'echo' but not in the call, it doesn't do anything. g++ links well with iostream, gcc doesn't. I'm not old enough to know what's up there.
And now for some reason the whole thing segfaults. I believe it is to do with the ... log somehow. Hmm ... no. Well - it worked on my computer!

So, back to square one ... troubleshooting.
Well - so, before I gimp around in kate with no proper session setup and without sublime ... trying to fix this ... I'm calling it quits here for now.

Cheers!


(A nice way to install icon themes (the effect of which I am also yet to make sense of) downloaded from say ... opendesktop.org ... is to have the packages stored somewhere and use midnight commander (mc) as root to extract them directly into /usr/share/icons or wherever they need to go (navigate to the package, hit enter (to enter it) and then F5 to copy the folder inside to the target). (With F9 > Options you can alter the [A]ppearance. Cool shit!))