Skip Navigation

DefederateLemmyMl
DefederateLemmyMl @ SpaceCadet @feddit.nl
Posts
1
Comments
585
Joined
2 yr. ago

  • I think it's a good tool to have on your toolbelt, so it can't hurt to look into it.

    Whether you will like it or not, and whether you should move your existing stuff to it is another matter. I know us old Unix folk can be a fussy bunch about new fads (I started as a Unix admin in the late 90s myself).

    Personally, I find docker a useful tool for a lot of things, but I also know when to leave the tool in the box.

  • Huh? Your docker container shouldn't be calling pip for updates at runtime, you should consider a container immutable and ephemeral. Stop thinking about it as a mini VM. Build your container (presumably pip-ing in all the libraries you require) on the machine with full network access, then export or publish the container image and run it on the machine with limited access. If you want updates, you regularly rebuild the container image and repeat.

    Alternatively, even at build time it's fairly easy to use a proxy with docker, unless you have some weird proxy configuration. I use it here so that updates get pulled from a local caching proxy, reducing my internet traffic and making rebuilds quicker.

  • postgres

    I never use it for databases. I find I don't gain much from containerizing it, because the interesting and difficult bits of customizing and tayloring a database to your needs are on the data file system or in kernel parameters, not in the database binaries themselves. On most distributions it's trivial to install the binaries for postgres/mariadb or whatnot.

    Databases are usually fairly resource intensive too, so you'd want a separate VM for it anyway.

  • what would I gain from docker or other containers?

    Reproducability.

    Once you've built the Dockerfile or compose file for your container, it's trivial to spin it up on another machine later. It's no longer bound to the specific VM and OS configuration you've built your service on top of and you can easily migrate containers or move them around.

  • Because you're bored. It says so right in the title.

    Personally I don't see the point of changing the shell either. Bash is more than good enough for my use and any other shell is going to have the disadvantage of not being the ubiquitous standard so it is always going to have an uphill battle to dislodge bash.

    That said, if people want to play around with a new shell just for the sake of it, why not? I like to play around with exotic window managers myself, not because my regular plasma desktop doesn't suffice, but because I like to try something different every now and then.

  • That's just retconning/backronyming it.

    /usr does historically stand for user. It's where the user home directories were on old Unix versions.

  • Binaries in the former are installed by the OS/package manager, binaries in the latter are installed manually by the user, for example by compiling from source and running make install

  • 100% possible with a Windows 10 guest in kvm/libvirt.

    You can connect the disk to your Linux system, and then pass through the disk's entire block device to the VM. Windows will see the device as an actual disk, and you can perform your repairs that way. I have something like this in my domain definition to pass through my game drive to my Windows 10 VM: https://pastebin.com/GzuvMTWP

    I can even use the manufacturer's SSD maintenance tool from my VM.

    Edit: lemmy doesn't seem to like XML in code blocks, so used pastebin instead.

  • The trouble is that my workload doesn't decrease with an amount equivalent to the outage time. I still have the same tasks to accomplish, so if the network is down for half a day, it just means I have half a day less to get my work done and meet my deadlines.

  • So little is done by others that, if Red Hat stops, Xorg is effectively done.

    Source?

    As far as I know the X.org foundation is an independent non-profit organization, and while Red Hat is a sponsor and they have 1 member in the board of directors (out of 8), they don't appear to be the main contributor.

  • Who made Red Hat the arbiter of when xorg should end?

    I mean, sure they're a major Linux vendor but their market is servers with hardly any foothold in the desktop market. It would be more interesting to see how long Debian, Ubuntu or Arch will keep xorg alive.

  • I think there may also be a cultural angle here. Anglo-Saxon culture really places a much higher emphasis on "not causing offense", whereas other cultures place a higher emphasis on speaking truthfully, even if harshly.

    So Linus, who grew up in Finland, may have thought of his message as harsh but fair, whereas to native English speakers it comes across as incredibly rude.

  • What a toxic ass message

    dickriders

    Oh the irony...

  • Just use rsync -va

    NO STOP!

    The default quick check algorithm of rsync is not safe for this. It only checks filesize and modification time to determine if files are equal. After a b0rked copy, these are not to be trusted.

    You should add the -c flag so that files are properly checksummed, unfortunately if you have slow storage on either end, this often negates the speed advantage of rsync.

    For example, consider this example:

     `
        
    mkdir source
    mkdir destination
    echo "hello" > source/file.txt
    echo "world" > destination/file.txt
    touch -r source/file.txt destination/file.txt
    rsync -avh source/ destination/
    cat source/file.txt
    cat destination/file.txt
    `
      

    Contrary to what you might expect, the rsync command copies nothing and the output at the end will show:

     `
        
    hello
    world
    `
      

    If you change the rsync command in the example above to rsync -c -avh source/ destination/, it will work as expected.

  • Reminds me of the time I brought down a whole AIX server with the killall command back in the 1990s.

    On AIX killall really means kill every single process.

  • These days, a part time income may not even be enough to cover books, let alone room and board… forget about tuition

    This is again a more American perspective I think, which doesn't make it invalid of course. The situation over there where students typically get loans and suffer crippling debt for years after they've graduated is frankly outrageous. Over here though, higher education is government regulated and highly subsidized, and while it's not free and can still be pretty expensive, it's possible to fit it within the budget of most families without loans, and people from families with a really low income are eligible for a grant.

    So I'm going to stand by my point that in Belgium at least, education has become more accessible compared to how it was for the boomer generation. It's visible in the statistics too: the number of people with a higher education level is still increasing every year, and younger people are much more likely to be highly educated than older people.

    Sources:

  • And affordable education

    Depends on where you where born I guess? Living in Belgium, my boomer parents never got a higher education because it was not affordable for working class families with 6 or more children. My dad had to go to work in a factory at 14, which was very common at the time. Props to him though, he got a degree through evening classes when he was already married with two children and working full time.

    Higher education only became common and affordable with my generation.

    On the other hand, while I make more money than my parents ever did, they were able to buy a 4 bedroom house in the 1980s on a working class income, whereas I could only afford a 2 bedroom appartment in the mid 2000s, the tail-end of affordability for housing.

  • Eh, WTF? It has normal Unix-like userland tools.

    You don't understand what I mean.

    I mean that you can't really do much with those userland tools to effectively manage and configure your system. All configuration is abstracted away in a forest of xml files (i.e. /Library/Preferences) that's as opaque and undocumented as the Windows registry and which you're not supposed to touch other than with the approved GUI tools.

    MacOS applications never follow Unix principles either regarding file placement.

    So yeah while MacOS technically still is "Unix", it really is a giant monolithic blob of shite built on top of the skeleton of what once was a decent Unix.

  • Yeah, but none of the system tools and applications follow Unix-like paradigms, so it's really only Unix-like in name. Sure you can launch a bash or zsh shell, but there aren't a lot of useful things you can do with that without installing a bunch of third party tools like brew, so the experience isn't all that different from having to install Cygwin or WSL in Windows.

  • Third person in the present time is ALWAYS conjugated as stem+t for regular verbs

    It gets more complicated in the second person though, with the inversion exception.