Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CO
Posts
1
Comments
43
Joined
2 yr. ago

  • Immutable distros aren't immutable in the home folder though, they would be unusable otherwise, so that doesn't solve OPs problem of dotfiles/personal files (I know nixOS tries to get rid of dotfiles, but in my experience that almost never works, it's only helpful for replacing config files in /etc)

  • Your example exactly shows that Fahrenheit is not "more precise", you're literally dropping the precision. In Celsius you just don't drop the precision, you'd say "around 12", which gives just as much info

  • Not quite correct. For html, that is to signal standard compliance, you can leave it away and the browser will still handle it. For the bash one, all (most) shell scripts use .sh, so you need to give a shebang to tell the loader which executable (sh, bash, zsh, csh, ...) to use

    Also on Linux xdg does take file extensions into account, just executables do not

  • You can start steam just fine without the packages. In fact, if you install without them, it'll ask you to install them every time, but you can skip that and it'll work, just 32bit games won't launch

    Edit: Looks like I'm partially wrong, as pointed out by a commenter below, steam currently only launches the 32-bit version of the client, despite support for a 5l64-bit client

  • It'sintended to be used when the cookies are actually required for the app to work. For example, to preserve your login, you need a cookie, no way around. Unfortunately, as mentioned by others, it's often abused

  • Secure boot means only signed code can run in the kernel/ring 0. Grub, as the loader, needs to be signed as well. Basically anything with system privileges needs to be signed. If I remember right you need to enroll the signing key on installation, and the rest is handled automatically, but you can't use any custom kernel or kernel drivers.

  • Not a problem if you stick to Ubuntu packages. All packages in the default apt repositories contain signed stuff, so you can install drivers (graphics, virtualbox, ...) like normal. I had it accidentally enabled when I initially installed and only noticed when I tried to build custom drivers myself.

  • 555 is still in beta, so I wouldn't be surprised if something doesn't work. That said, I haven't experienced what you have (on GTX 1070 TI), though using 555 causes lots of kernel errors for me. Checking dmeg might reveal something in your case as well.

  • Usually we don't distinguish between many2one and one2many, since it's the same just viewed from the other entity.

    There is one more class though, which is one2one. That is, the entities have a direct relationship. Sometimes this also includes the case where you have zero or one, i.e. the relation is optional on one side. This can be accomplished with an FK plus unique constraint or by merging the tables.

  • streaming small commits straight into the trunk

    The image even calls it like that

    Some things don't have good CI/tests, so it doesn't make sense to include the build step, especially on a small team where we trust each other. But yes, it's not good practice, and we don't do this on every project, but sometimes it's necessary to adjust the flow to the specific project

  • We do, for two 2-3 person projects, where no code reviews are done. This is mostly because (a) it's "just" a rewrite and (b) most new functionality is small and well-defined. For bigger features a local branch is checked out and then merged back later. Commits are always up-to-date, which makes it much easier to test integration of new featues.

  • You can set the initial value directly in /etc/environment, did you check that? It could also be set only for your user, so it might be in ~/.profile, ~/.bashrc or ~/.bash_profile` (or the rc file for your shell if you're not using the default bash).

    Edit: I suppose you could also have added a startup script in /etc/init/ or /etc/init.d/, or in /etc/rc.local