It’s more: I have routed a few pipes in our test system and it’s now spitting out water known to be contaminated but now should have some extra sprinkles in so it’s fine.

What I’m saying is it’s even worse than didn’t do any checks. It’s willfully ignoring existing checks intentionally.

That’s rpm, suse Linux 1.0 was never built off the same source or installer that Redhat Linux was.

Do you have a historical example where any suse distribution used redhat based source? As opensuse as I said only used the rpm package manager, it never used any other components of a redhat derived install.

Source: I work there and can find zero redhat strings in any old source code from that era, the old greybeards took offense to the implication that suse was ever based on redhat other than using rpm which at the time was about it for packaging.

All they did was start to use rpm instead of tar for packaging.

Opensuse and fedora have no common history though? Just because it uses rpm doesn’t make it a red hat derivative.

https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Distribution_Timeline.svg

I’m an annoying millennial I call em acetates cause I figure what they were called in the 40s or thereabouts is good enough for me see. Now I’m off to my ether frolicking and ice cream social daddy o or watever.

I use arch, err nixos/nix on macOS btw. Do I win or have I made the Linux nerds angy?

Yeah this only really applies to Algol style imperative languages. Dependent types and say stack languages like idris and apl are dramatically different in their underlying axioms.

Sorry, but your reply suggests otherwise.

I’m at work, I’m not going to go into a thesis on ip allocation.

The RIRs (currently) never allocate a /64 nor a /58. /48 is their (currently) smallest allocation. For example, of the ~800,000 /32’s ARIN has, only ~47k are “fragmented” (smaller than /32) and <4,000 are /48s. If /32s were the average, we’d be fine, but in our infinite wisdom, we assign larger subnets (like Comcast’s 2601::/20 and 2603:2000::/20).

Correct all noted here https://www.iana.org/numbers/allocations/arin/asn/

Taking into account the RIPE allocations, noted above, the closer equivalent to /8 is the 1.048M /20s available. Yes, it’s more than the 8-bit class-A blocks, but does 1 million really sound like the scale you were talking about? “enough addresses in ipv6 to address every known atom on earth”

If you’re going to go through and conflate 2^128 as being larger than the amount of atoms on earth to a prefixing assignment scheme I’m just going to assume this is a bad faith argument.

Have a good one I’m not wasting more time on this. The best projections for “exhausting” our ipv6 allocations is around 10 million years from now. I think by then we can change the default cidr allocations.

https://samsclass.info/ipv6/exhaustion-2016.htm

Its old sure but not worth arguing further.

Cows will also chomp down on meat and little birds if given the opportunity. I grew up on a ranch herbivore doesn’t mean vegan like peeps seem to think it does. If they feel like they’re low on a nutrient and have opportunity they’ll nom on anything. No this isn’t pica either.

I’m fully aware how rirs allocate ipv6. The smallest allocation is a /64, that’s 65535 /64’s. There are 2^32 /32’s available, and a /20 is the minimum allocatable now. These aren’t /8’s from IPv4, let’s look at it from a /56, there are 10^16 /56 networks, roughly 17 million times more network ranges than IPv4 addresses.

/48s are basically pop level allocations, few end users will be getting them. In fact comcast which used to give me /48s is down to /60 now.

I’ll repeat, we aren’t running out any time soon, even with default allocations in the /3 currently existing for ipv6.

This is the worst math that ever mathed. IPv4 is 32 bits of address space. IPv6 is 128. That is 2^32 vs 2^128. Not 2^52, which isn’t even wrong it’s just weird, hopefully this is just some weird performance joke. There are enough addresses in ipv6 to address every known atom on earth. We aren’t running out anytime soon. 96 doublings of IPv4s address space is a number you can’t fathom.

I mean I’ve been using native dual stack for over a decade and I’m most definitely American. A fun anecdote was I was having issues with clicking on links from Google once and turned out ipv4 was busted but 6 worked fine for half a day. And there really isn’t any turning on ipv6 I get it by default and it’s with the most hated isp Comcast. They’re actually really good about v6 support I’ve not moved off them because of it. It’s literally 10ms faster than 4 lilely due to cgnat.

The USA is ahead of most nations at about 50% so not sure how you’re coming to that conclusion based off of evidence. Outside of maybe Brazil in the americas on both continents our ipv6 adoption is better than the rest, Canada included.

No don’t take shitposts literally. I’ve been using ipv6 for a decade at home now in the USA and I don’t pay extra for it ever. Also why are you assuming this post refers to the us?

I grew up on a farm, any programmer that thinks farming or ranching is better is gonna have a rude awakening as to why there are very few farmers anymore.

So no not every computer guy dreams of the farm, repairing 10miles of fence every April for the entire month all day every day isn’t what I would consider an improvement over programming. And that’s the easy part wait till you gotta help an animal struggling to give birth.

I get programmers have this idea that farming or ranching is more pure somehow but it is murder on your body and soul in ways you wont understand. programming and computer stuff is a cakewalk in comparison. more politics but learn to play the game of thrones and its not too bad.

https://store.steampowered.com/app/2690330/Vampire_Survivors_Emergency_Meeting/ If it helps

Make me should just refuse to do anything.

Its deprecated kinda like `` should be $() https://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xcu_chap02.html seach for arithmetic expansion or $[].

On ye olde hpux this would work, especially when you did rm-fr /$var and $var was unset and nobody unit tested their shell back then. That db server ran for 2 days though with open file handles before it finally died.

Is fash like that fish shell only more fetch? zsh is obviously the best, its the omega end to shell names with the z (in latin alphabets so there).

Key here is the outer [] and interaction of $[], test doesn’t have == by default in standard posix, so no this isn’t posix shell or bourne compatible. Tis but another bashism. I could probably force zsh into a more bourne mode to try it but its definitely not portable bourne shell its bash.

$ [ $[ $RANDOM % 6 ] == 0 ] && echo rm || echo ok
zsh: = not found
$ zsh --version
zsh 5.9 (x86_64-pc-linux-gnu)

== should be -eq for this to be posix/bourne portable, you could use = but -eq is for numeric comparisons so not quite right.