Last year, I got myself a new Camera, a Lumix S5, and after uploading some photos to DeviantArt (I have had the same account for almost 20 years) and browsing my gallery I realized that I had had enough.

It was so slow and annoying to work with.

So I sat down and started work on a simple webpage that I could host on a normal webhost.

And I built a nice index page in HTML/CSS, and then used photo albums generated by digiKam for the photo albums.

It loads fast, it is easy to navigate, fairly easy to update, and the photo albums can be navigated with arrow keys or swipe gestures.

I am considering writing a blog UI for me to be able to make a simple blogging page, I’ll still write it in static HTML/CSS, so I’ll have to write every blog entry in HTML as it stands now, but I’ll keep looking for easier alternatives

Ah, I was involved in a hectic discussion in another thread, I also know that Linux users can be quite outspoken about their choice fs editor, so I didn’t catch the joke.

Sorry about that! (:

It is what I am used to, your approval did not factor into my choice.

Just make a template, once done you can easily do it while blasting Scooter, get pissed when it breaks due to a change of interface names, switch to Sabaton while you battle it out. After that you go to the local zoo and watch some Lynx just relaxing all day and ask yourself where it all webt wrong.

What education do you have in the area?

The IT/Sysadmin sector does have a risk with knowing enough to be dangerous.

Daily driving Linux is great to get used to the command line, but is different from running servers.

If you have no experience with running Linux servers, I would be focusing on that part, rather than daily driving at this point.

Running a server requires a bit of a different mindset to that of just using a desktop.

You need to be far more restrictive about installing software on the server, be more cautios of reboots, and in general focus on stabillity.

You also need to familiarize yourself with Debian/Ubuntu and Red Hat/Fedora based distributions, their package managers, apt and dnf, the general layout of the system, they are mostly similar, but they have their own flavours, especially when it commes to the config files.

Learn the basics of vim, it will allways be installed on a server, I prefer nano but can use vim if needed.

A big part of my job when I was a Helpdesk technician combined with a Linux sysadmin was storage, I had to set up VMs in vSphere and Nutanix and give them the correct ammount of storage, sometimes also expand the storage on a server, and work with mountpoints.

Play around with LVMs, learn the concepts of PVs, VGs and LVs, learn how to expand them, how to move an LV from one PV to another inside a VG, learn how to mount them.

Learn how to set a manual IP, this can change from version to version of a distribution.

Learn to get annoyed at YAML files.

Understand how to secure a system, I’ll admit that I never really had to do this as all servers I worked on was behind strong firewalls and not accessable from the internet, but I did my best with what I had.

I just saw it on the Swedish national broadcaster’s website:

https://www.svt.se/nyheter/snabbkollen/it-storningar-varlden-over-e1l936

Wait, you are building a system to allow people to book a USB drive?

…

Dude, just get a few more USB drives, they are cheaper than wasting your time on this.

I have thought about creating a video series that is distributed via torrent, that could be a decent idea…

Have you tried this:

https://support.mozilla.org/en-US/questions/1182594

Yeah, unfortunately it seems like it will not get a Wayland version though…

If you are still using X, get Fluxbox, very lightweight, requires some config, but that is fairly easy.

Yep, LVM is basically a software raid 0, I used it when setting up Linux server VMs for years at my last job, as far as I know they are still running fine.

The VM system backed up all VMs regularly, so I used LVMs as it made increasing the storage on a server easier for me.

Since it is just a raid 0 that can span several disks and one disk failiure can bring it down I don’t want any irriplacable data on it, so games from Steam seems like an excellwnt idea.

That also means that being able to just have a volume spanning several disks would be an easy and simple way to increase storage when space is running tight.

I am an avid hobby photographer and I would never trust an LVM without some kind of added protection, I am looking to get a Synology NAS with minimum of four drives raided in raid 5.

I have a very old Intel NAS with used drives that I used for many years, but I don’t trust it anymore, I keep it powered off as a cold backup.

That depends on your usecase.

I have setup servers where I mounted extra drives on /srv/nfs

When/If I switch to Linux I will probably mount my secondary drives to folders like

/home/stoy/videos

/home/stoy/music

/home/stoy/photos

/home/stoy/documents

/home/stoy/games

The ~/games will probably be an LVM since it contains little critical data and may absolutely need to be expanded to span several drives, though I would also be able to reduce the size of it and remove a drive from the LVM if needed.

I’d make a simple conky config to keep track of the drive space used

I’d just keep using the default automount spot for automounting drives.

What exactly did companies gain from making Linux distros switch over to systemd?

If anything, the switch ment a loss of productivity as their staff needed to relearn stuff, not to mention loss of technical knowledge as there would be others who simply would not accept the change and leave the company when the change happened.

This means increased costs, either due to retraining, or due to needing to hire new staff which is expensive.

Meanwhile, I can’t see anything that would mean that companies would earn or even save enough money to make it worth the effort of making distros implement systemd.

Ok so doing it for direct gain seems to be out, but you mention “corpo sabotage of opensource”, I can’t really see that either, a developer won’t move a successful Linux project to Windows, AIX, Solaris, Darwin or HP-UX just because of a move to systemd.

So even indirect gain seems to be out, so “corpo sabotage” doesn’t really seem plausible.

But, I may be wrong, please, tell us how exactly a move to systemd has benefited companies enough that it would make the effort and expense to make a distro move to sytemd, let alone a majority of distros, worth it.