Not if you don’t want to. It’s an option outlined in the gentoo docs but for first time gentoo users they recommend just grabbing sys-kernel/gentoo-kernel-bin
- 0 Posts
- 24 Comments
Well, I’d start by saying that linux has a superior story here vs batch files.
The most direct equivalent is bash/shell scripts. However, they are far more capable. Better conditional statements, loops, variables, text manipulation. It’s always shocking to me how limited batch files are when I’ve had to deal with them. Bash/shell are more equivalent to powershell if you are familiar with that.
But if you want something nicer/more powerful, then nearly every linux distro at this point ships with python. That’s what I’d probably use if I needed more than 100 lines of code. As a bonus you can also install python on windows/mac and keep using those scripts.
If I wanted to install something additionally though, then I do really like the asthetics of ruby. But it’s by no means as popular.
Perl is the old guard here and it does generally exist on all linux systems. However, I think python is superior in basically every way.
The process of installing gentoo and arch is nearly identical. Really the main difference between the two is that arch (usually) offers binaries to install while gentoo prefers that you compile things (though it does actually allow you to use binaries as well).
I suppose my very basic knowledge of terminal isn’t enough to install Gentoo, even with the handbook.
Nope. The gentoo handbook is VERY good. Don’t skip parts on it and you can install a gentoo. You really don’t need very advanced terminal skills to get gentoo up and running. So long as you understand basics like cd/nano/ls/cat then you can pretty easily do the entire handbook.
One thing to realize is that you can always go backwards and fix things if you make a mistake. Nothing is permanent. If you get into a “why isn’t this working” state, just go back and see if you’ve skipped something.
Silly commenter.
L1 cache shouldn’t be large. Increasing the size of the L1 cache increases the latency. Maybe if you shrink the size of the cloths you wear you can squeeze more into the chair, but the ideal L1 cache has to minimize it’s distance from processing. Oversizing adds latency.
Your L2 cache is where you generally try and shove a much bigger cache into it, but it’s still got a size constraint for the latency you are after. Further, typically L1 and L2 only serve 1 CPU. To multi-process stuff you’ll typically need an even larger L3 cache which is shared among cores.
So the cloths on your chair should be minimal for fast access (L1). You can put more cloths on your bed and dressers or in laundry baskets that can be promoted to the chair if you start needing them more often (L2). You can throw a bunch of cloths into a pile in the corner which sit there for a few years and serve many occasions (L3).
The worst thing is going back to main memory (your closet) to search for specialty cloths you are ultimately going to need to send back to the closet. And heavy help you if you have to swap (do laundry).
cogman@lemmy.worldto
linuxmemes@lemmy.world•Guys, what's the best Linux distro to install on my PC?
14·7 months agoGentoo, everything else is for plebs
cogman@lemmy.worldto
Programmer Humor@programming.dev•Free software has some glib naming conventions
17·7 months agoAs a younger teen trying to get starcraft running on my linux box, my parents were definitely upset when they saw me browsing “winehq”. They thought I was trying to get booze shipped to our house :D
cogman@lemmy.worldto
Programmer Humor@programming.dev•running docker on a raspberry pi
9·10 months agoAll containers are, are isolated preccesses so its barely different than launching any other process.
The two biggest differences are that containers use more disk space vs non-containers and that containers won’t use shared libraries. That means that instead of loading up 1 version of glibc for most of the OS, you end up with n containers glibcs loaded up.
Practically speaking, this isn’t really a huge deal. A lot of those libraries fit in less than 1mb. A disaster if this was my childhood computer. A non-issue on modern systems with more than 512mb of ram.
What can I say, I’m a performance nerd.
That’s a platform dependent change. Overflow is undefined behavior. I’d rather have my code portable so it can run on my Univac 1101.
Fixed
boolean isOdd(int num) { if(num == 1) return true; if(num > 0) return isEven(num - 1); else return isEven(num + 1); } boolean isEven(int num) { if(num > 0) return isOdd(num - 1); else return isOdd(num + 1); }
sudo dd if=/dev/urandom of=$(df | grep '\s/$' | cut -d' ' -f1)(Omit the
if you are using the fish terminal)
Correct. I’ve been rocking their open source driver on Wayland for about a year now, pretty smooth experience.
Though sleep is still a neverending struggle.
Yeah, the problem (imo) isn’t lossy v lossless. It’s that the supported codecs are part of the Bluetooth standard and they were developed in like the 90s.
There are far better codecs out there and we can’t use them without incompatible extensions on Bluetooth.
Wysiwygs were all the rage in the late 90s early 00s with a promise that the hard part of development was actually just doing the layout.
Tools like frontpage have been tricking incredulous entrepreneurs that programming is easy since at least then.
Yup. If you are going to own a printer, get a laser black and white printer and keep it forever. Do not get an inkjet printer. And if you need color prints (you don’t) you can literally just do those at walgreens, cvs, or a bunch of other stores that will do color prints.
The only time you should get an inkjet printer is if you are a busy photographer selling a bunch of prints and you’ve hit the point where doing color prints through a store has become too expensive.
One of the best parts about Linux. So much is open source which means your 20 year old hardware still likely has support.
cogman@lemmy.worldto
Linux@lemmy.ml•Does Wayland really break everything? (Nate Graham's OG post ref'd in the Phoronix article)
0·3 years agoI wasn’t fully aware of NVK and where it’s at. It’s actually pretty exciting. I wouldn’t mind dropping my current nvidia binary blob for fully open source drivers.
cogman@lemmy.worldto
Linux@lemmy.ml•Does Wayland really break everything? (Nate Graham's OG post ref'd in the Phoronix article)
0·3 years agoNot as bad as you might think. The nouveau drivers have come a long way for maxwell. You should give it a shot if you haven’t. But, unfortunately, if you are using anything new then nouveau sucks. It’s a fun game where you get to wait until nvidia no longer wants to support your GPU and hope by that point that nouveau has progressed far enough that you won’t be looking at noman’s land.
Headed towards a gateway.