Python Installation using sudo make install + obligatory Linux rant
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
you're supposed to do things differently on Linux because Linux distros have embraced the idea of the central repository long before anybody else
Which, BTW, typing the application version to the OS version is about the dumbest idea ever done in computers ever.
Note that when companies like Steam, Apple and Microsoft took the "app store" concept they actually let apps in the store update themselves whenever they want instead of having to wait for an entire OS release.
With modern Linux distributions, you can have it both ways: on one hand, you have "tried and true" stuff from the distro's repositories where at least 99.9% of the time it's checked against possibilities of screwing up the rest of the stuff in the distro's repositories, and you have author repositories (PPAs/COPRs) for the use case you are describing. Oh, and you get flatpaks and snaps and appimages, of course.
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Which doesn't really work that well anyway. At least in my experience, old software on new Windows releases is not guaranteed to work.
Until AMD's 64-bit CPU designed forced them to abandon 16-bit apps, Windows still ran Visicalc. (I bet if you install the 32-bit version of Windows it does to this day.)
In Windows-land, if a program is incompatible with future OS versions, it's the program's fault because they violated the API contract. That's not true of any other OS. (Macintosh: Apple threw out 68k compat, then PPC compat, then Classic API compat. On Linux: the API has no real contract, GUI applications have no stable APIs, there's no way to have backwards compat without application source.)
You do realise that in the Linux world everything is tailored to the needs and expectations of the OSS community? Remember the giant "fuck you" to Nvidia by Linus Torvalds. You want to play our game? Our rules.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Untrue anyway. If a distro is so inclined, it can maintain old libraries and stuff back to the start of time.
Right; and they COULD also give each of their users 26 bars of 24-carat gold. But since none do, why bother discussing it?
The point is that in the OSS world this is unnecessary.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
With OSS, it's not an issue because you just recompile stuff as needed (and the software which builds upon certain libraries can improve too without changing a single line of code sometimes).
And if it uses GUI code that no longer exists or is no longer maintained? Fuck you! What if you don't know how to recompile stuff? Fuck you! What if the source code isn't available to you? Fuck you!
- if the code no longer exists and you want to rely on it, maybe you shouldn't have chosen closed source stuff to begin with. Complain with the original vendor.
- there might be somebody who can, and it's usually not that hard anyway. (Recompiling stuff per se, I mean).
- see point 1.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
With commercial software, they can provide their own libraries. With snaps or flatpaks, even more so.
But if there's a security flaw in their own libraries, you're stuck with it (the flaw) forever. You have no way of fixing it, and if you tried the fix would change the incredibly unstable API and break the application.
Not if the software provides updates to the stuff they rely on. That's how it works wherever libraries are statically linked or provided by the vendor.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
With snaps or flatpaks, even more so.
If these were available in 1999 or so this would be a different discussion. But it's like just a couple years since the horrible people who run Linux thought to themselves, "hey, maybe our OS should be less ass?"
It's just that there is more proprietary software on Linux these days. Back then, there was no big need.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Break ABI/API. You can run binaries back from 1996 on a current kernel (with few, motivated exceptions).
As long as the application doesn't want to draw windows or interact with a printer or...
The kernel doesn't do shit. The kernel ABI doesn't matter. All the other stuff does.
And you can still run all the userland from back then if you really want. You could backport fixes if you wanted to. You can also modify the code yourself if it's a very specific need. (And you aren't even forced to give it away either).
... also why 1996? Isn't Linux from 1991? Does this mean they... GASP!... broke compatibility!?!?!?
They changed binary format. No biggie, it was a hobbyist project before.
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
At least in my experience, old software on new Windows releases is not guaranteed to work.
In my experience, the only time I remember old software not working is on major system updates. Like when 16bit support was dropped. Or when software is just fucking stupid and uses GetVersion to see if it can run. And parses the version number wrong. Finally making MS say "Fuck you, we'll deprecate GetVersion. Fix your shit." (except, of course, the API will never go away...)
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
You do realise that in the Linux world everything is tailored to the needs and expectations of the OSS community?
So they NEED to have shitty software, and they EXPECT software to be shitty? Well that explains a lot.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Remember the giant "fuck you" to Nvidia by Linus Torvalds. You want to play our game? Our rules.
Maybe you should consider a spokesman who's not an asshole. He also wrote Git, so not only is he an asshole, but he's not even good at writing software.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
The point is that in the OSS world this is unnecessary.
Well now that I know you need software to be shitty, I guess that ruins all my arguments.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
They changed binary format. No biggie, it was a hobbyist project before.
I thought you just said like 4 posts up that that never happens! You liar.
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
You do realise that in the Linux world everything is tailored to the needs and expectations of the OSS community?
So they NEED to have shitty software, and they EXPECT software to be shitty? Well that explains a lot.
Snarky snark snark heehee.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Remember the giant "fuck you" to Nvidia by Linus Torvalds. You want to play our game? Our rules.
Maybe you should consider a spokesman who's not an asshole. He also wrote Git, so not only is he an asshole, but he's not even good at writing software.
Snarky snark snark heehee.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
The point is that in the OSS world this is unnecessary.
Well now that I know you need software to be shitty, I guess that ruins all my arguments.
Snarky snark snark heehee.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
They changed binary format. No biggie, it was a hobbyist project before.
I thought you just said like 4 posts up that that never happens! You liar.
:(
-
@admiral_p Snarky snark snark heehee.
-
@blakeyrat you're getting even better at it. A bit more effort and you'll reach
nirvanaSnarknado.
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
maybe Linux should improve so that it's BETTER than Windows at some things
Windows Update
-
@TimeBandit Things. Plural.
-
@loopback0 text processing...
-
@loopback0 said in Python Installation using sudo make install + obligatory Linux rant:
Things. Plural.
I figured that Windows Update is such a giant piece of smelling cow shit, it counted more than once
-
@TimeBandit said in Python Installation using sudo make install + obligatory Linux rant:
@loopback0 said in Python Installation using sudo make install + obligatory Linux rant:
Things. Plural.
I figured that Windows Update is such a giant piece of smelling cow shit, it counted more than once
No because Windows does a better job of restarting when it wants which puts a point back in its favour.
-
@Gribnit said in Python Installation using sudo make install + obligatory Linux rant:
@loopback0 text processing...
The stuff Word does?
-
@loopback0 no, I mean
find . -name '*.foo' -exec grep foo {} \; | anonymize.sh | sort | uniq -c | sort -k1n
Edit:
| tee foos.${ stamp.sh } | less
# and fix xargs/exec f'up
-
@Gribnit
plop gloop . --$''trin seh;; - | unq || -k2bvca sh{}dsah
-
@Gribnit i know but
fact | barrier | joke
-
@blakeyrat Is that Powershell? I'd believe it. But I heard Powershell uses big words for all things.
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
@Gribnit
plop gloop . --$''trin seh;; - | unq || -k2bvca sh{}dsah
@Gribnit said in Python Installation using sudo make install + obligatory Linux rant:
@blakeyrat Is that Powershell? I'd believe it. But I heard Powershell uses big words for all things.
Googling for plop gloop took me to a book called "glimpses of horror" (google books link). I think it fits it well.
-
@Gribnit said in Python Installation using sudo make install + obligatory Linux rant:
But I heard Powershell uses big words for all things.
Your words are too short for Powershell! Here, try this version:
“However, oneself personally received intimations inclining assertional belief that Powershell prefers extended lexicographical terminology whenever discussing control matters, related utterances, etcetera, etcetera…”
-
@loopback0
fact && barrier || joke
is absolutely as far as I am willing to go on that.
-
@Gribnit
cat /post/1392407 >> /dev/what?
-
@loopback0 yeah that just dumps the output on a block device. if you got a 0, it worked. weird setup you got there. try
apropos
or maybeman
if you have a really good guess.Edit: inb4 uuoc
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Subjective. In the OSS (especially GPL) world, you're expected to engage with the community.
Eww, no. Especially not GPL toe-jam eaters.
More seriously, if I install software to frobnicate widgets, I want to frobnicate widgets, not interact with people (unless in a particular case "frobnicate widgets" == "interact with people"). I might perhaps have occasion to to interact with other widget frobnicators to learn or teach how to frobnicate better, but in general I have no interest in interacting with people who write widget-frobnicating software beyond the (hopefully rare) "fix yo' shit!"
-
@HardwareGeek then use a widget frobnicator whose mission statement is to provide a stable, backwards compatible way to frobnicate widgets which is guaranteed to work in perpetuity. OSS doesn't necessarily mean "move fast, break stuff". What OSS does is make it viable to do so.
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
@HardwareGeek then use a widget frobnicator whose mission statement is to provide a stable, backwards compatible way to frobnicate widgets which is guaranteed to work in perpetuity. OSS doesn't necessarily mean "move fast, break stuff". What OSS does is make it viable to do so.
So again we see the basic theme stated here that open source software is expected to be shitty and broken all the time.
I'm not sure how many other open source fans would agree with you, but I have to admit that it does shut down most of my arguments which rely on the assumption that the people using the software don't want it to me broken and shitty.
-
@blakeyrat "move fast, break stuff" only breaks stuff when the user of what is a collaborative effort steered in such a way does not collaborate. It's weighing pros and cons, do we want to ensure stability and live with the mistakes of the past, or do we want to improve at the expense of requiring our users to keep track of our efforts? You can choose. Some OSS is like the former, some is like the latter. You can also (gasp!) fork the code and maintain it as you see fit. You can't do this when you don't have the code.
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
@blakeyrat "move fast, break stuff" only breaks stuff when the user of what is a collaborative effort steered in such a way does not collaborate.
Wha... what?
Hang on, let me try to unfold this...
So you're saying, if I'm reading this word-fart salad correctly:
- Despite being called "move fast, break stuff" it doesn't actually break stuff
- Well it does but only when the user of it doesn't collaborate
So... you've introduced some weird universe where my intention when I use the software determines how buggy it is? Is this like a spec script for a Black Mirror episode or something?
Moreover, people who intend to collaborate by reporting bugs would never actually do anything because (according to your dumbshit theorem) they'd never encounter a bug! Only the people using the program who had no intention of reporting bugs would see bugs.
Interesting. It's like "mind over matter", doused with a little bit of "holy shit admiral_p has to be the dumbest motherfucker on this forum".
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
It's weighing pros and cons, do we want to ensure stability and live with the mistakes of the past, or do we want to improve at the expense of requiring our users to keep track of our efforts?
But you haven't replied to my previous response to that, which is that Git is developed this way and it still sucks just as much now as it did when it was released a decade ago. Maybe even more.
I mean you could point to thousands of mistakes and bad design decisions in Bash that'll never be fixed because they'll break scripts. If anything, I'd say the open source community is MORE change-averse than closed source software vendors, right? I mean, Linux was still using it's awful 1986 way of launching and tracking services until just a couple years ago, when Microsoft had improved this functionality way back in 1999. Linux is still using Bash and friends as its default CLI when Microsoft has since introduced both WSH and PowerShell.
I mean I get your general point, and it's something I say all the time too: if you never change anything, you can't improve anything. But the problem is, while the open source-y developers can change things, they don't actually do it! And their stuff never improves.
And yet somehow Microsoft innovated the new Ribbon GUI concept without the backwards compatibility in Windows being any kind of burden to it. Somehow Microsoft created PowerShell without the backwards compatibility in Windows being any kind of obstacle. Somehow Microsoft created RDP, switched window rendering to GPU, adding in DPI scaling, etc etc etc without Windows backwards compatibility being in the way.
So where's your fucking argument?
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
You can choose.
Can I.
Ok; I choose to use the source control that's compatible with Git servers but doesn't have a complete ass UI. I choose it! Make it so! I am using my amazing mind-over-matter powers! Give the software to me now!
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Some OSS is like the former, some is like the latter. You can also (gasp!) fork the code and maintain it as you see fit. You can't do this when you don't have the code.
Yeah well open source-y people have all the code, and yet somehow their products are still shittier.
-
@blakeyrat you very well know what I mean. If you've chosen to associate to a fast-moving target, you have to move fast too. (The user, here, is not necessarily the end user). Otherwise you choose something nice and conservative.
There are countless shells on Linux. People use Bash just because it's available everywhere. Many these days favour zsh (which I'm not familiar with). You can also use Powershell on Linux these days, right?, if you're so inclined. Up to a few months ago, you couldn't use Bash and a Linux userland on Windows. (That's why many developers apparently creamed their pants when WSL was announced - you'll say, of course, they won't have to put up with shitty Linux anymore).
GNOME has radically changed their UI, many people hate it (I think it's decent), they had the choice to actually take the old stuff and keep it maintained (MATE), or take the new stuff and change it to something more traditional (Cinnamon). Everything works everywhere in the meantime. Git is bad? Again, subjective. If it's so bad, why do people use it so much? It's not as if there aren't any alternatives. Maybe it's just really bad for you and the others don't care that much about its issues. If it's so bad and you know better, you have (gasp!) the opportunity to fork the code and make modifications with other like-minded people as you deem fit (and if you're right, you'll even get paid, maybe handsomely, for this eventually).
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
you very well know what I mean.
I don't even think you know what you mean.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
If you've chosen to associate to a fast-moving target, you have to move fast too.
Ok; so where do I associate with the Bash that moves fast? The Git that moves fast?
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Up to a few months ago, you couldn't use Bash and a Linux userland on Windows.
Believe it or not that code has been in Windows NT forever, and was originally intended to let NT emulate OS/2 and Xenix back in the day. Microsoft just kind of brought it back from the dead and spruced it up a little.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
GNOME has radically changed their UI, many people hate it
They should choose to use the GNOME that moves slowly then. Since in insane admiral_p logic there's a fast version and a slow version of everything.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Git is bad? Again, subjective.
No; Git is objectively bad. It objectively does not have many very useful features that most of its competitors have. It objectively does have many features that are terribly-designed (like pre-commit/post-commit hooks.)
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
If it's so bad, why do people use it so much?
The majority of people use it only as a condition of employment. The people who use it voluntarily, I can only assume they're just rock-stupid.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Maybe it's just really bad for you and the others don't care that much about its issues.
... that's still bad. Saying "this program has tons of issues but some people don't care about them!" doesn't somehow magically fix the issues.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
If it's so bad and you know better, you have (gasp!) the opportunity to fork the code and make modifications with other like-minded people as you deem fit
Except you can't because Git is specifically designed to make that virtually impossible.
(Specifically: Git doesn't separate its programmatic interface from its user interface, so it's impossible to evolve its user interface without also breaking other applications that expect to use its programmatic interface.
Why is Git built this way?
Well it turns out, Linus Torvalds is a fucking hack who has no fucking clue how to write software. I guess he should stick to being a jerk on email lists.)
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
(and if you're right, you'll even get paid, maybe handsomely, for this eventually).
Riiight. The goldmine that is the open source ecosystem, where every user pays through the nose for their apps.
Look, working on a C app written by a dumbshit without even a working UI is not my idea of a fun project I'd do on my spare time. I'm glad you're such a fan of tedium and annoyance and shitty tools, but I'd require some $$$ up front.
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
The majority of people use it only as a condition of employment. The people who use it voluntarily, I can only assume they're just rock-stupid.
You switched the subject to Windows?
-
@blakeyrat bash doesn't move fast, nor does git. Other things move faster. What's your point? And anyway, if you don't like git, don't use it. If you're forced to use it (and why are people forced to use it?), it's a job and get on with it, or propose something better.
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
@blakeyrat bash doesn't move fast, nor does git.
Yeah that's why I want to choose the one that does. The one you said I could choose. Tell me what button to press for that.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
What's your point?
I'm just kind of poking and prodding to tell what idiotic statement you'll make next.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
And anyway, if you don't like git, don't use it. If you're forced to use it (and why are people forced to use it?),
Because it's a condition of employment.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
it's a job and get on with it,
I could do the same job with TFS and have a far better time.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
or propose something better.
I think I did that about 20 times in this thread: why don't the dumbshit assholes who make Git get off their lazy asses and MAKE IT BETTER?! Isn't that why open source is so great and wonderful and beautiful and all that bullshit?
-
This post is deleted!
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
@blakeyrat bash doesn't move fast, nor does git.
Yeah that's why I want to choose the one that does. The one you said I could choose. Tell me what button to press for that.
Just use WTF you want to use. You want to use Powershell? It's even open source now! VCSs, but you like TFS, use it.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
What's your point?
I'm just kind of poking and prodding to tell what idiotic statement you'll make next.
Snark snark heehee.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
And anyway, if you don't like git, don't use it. If you're forced to use it (and why are people forced to use it?),
Because it's a condition of employment.
And why is it? I don't think companies at large decide to use stuff just because it's hip. (Some companies do).
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
it's a job and get on with it,
I could do the same job with TFS and have a far better time.
Then sell your idea to management.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
or propose something better.
I think I did that about 20 times in this thread: why don't the dumbshit assholes who make Git get off their lazy asses and MAKE IT BETTER?! Isn't that why open source is so great and wonderful and beautiful and all that bullshit?
But maybe they think it's fine as it is?
-
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
Just use WTF you want to use. You want to use Powershell? It's even open source now! VCSs, but you like TFS, use it.
What if all these things suck and I want to use something GOOD.
What if I want to use development tools that have gone through some form of UX or usability testing.
What if I want software that gets better year-over-year instead of getting worse.
The problem is I can't because none of those things exist anymore. None of them.
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
And why is it? I don't think companies at large decide to use stuff just because it's hip. (Some companies do).
Are you 12?
@admiral_p said in Python Installation using sudo make install + obligatory Linux rant:
But maybe they think it's fine as it is?
If they do, they're assholes. If they have done a usability study, there's no way the report recommended making no changes. If they haven't, well, then they're assholes. And I know they haven't. Because the entire open source philosophy is to be an asshole to your users.
-
@admiral_p
git moved very fast to get into existence when Hg yanked rug.
-
@Gribnit said in Python Installation using sudo make install + obligatory Linux rant:
@admiral_p git moved very fast to get into existence when Hg yanked rug.
?
Linux used BitKeeper before they moved to Git. And they had to move to Git because BitKeeper was providing it to them for free, but they decided to stop because some Linux devs were being dickholes and reverse-engineering it which violated the agreement.
AFAIK Mercurial had nothing to do with Linux development or the move to Git.
-
@blakeyrat Bad memory. Somebody yanked rug. Guess it was BitKeeper. How they holding up?
Edit: Hg was discussed as a possibility, is I think how it got mis-wadded.
-
@Gribnit I dunno. Apparently their product was pretty solid. Before Git there were like 2 source control products in existence that could be used for projects that large (and, arguably, even Git can't, because it has a lot of design flaws that prevent it from being effective at it). BitKeeper and TFS were basically it.
So when BitKeeper said "fuck it", the choice was either move to TFS or write their own, so they wrote their own. And they came up with Git. Which is fucking terrible.
-
@dkf said in Python Installation using sudo make install + obligatory Linux rant:
that Powershell prefers
“regarding Powershell’s preference respecting”
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
arguably, even Git can't, because it has a lot of design flaws that prevent it from being effective at it
The proof is that Git is not used to develop the Linux kernel.
Oh, wait...
-
@TimeBandit said in Python Installation using sudo make install + obligatory Linux rant:
The proof is that Git is not used to develop the Linux kernel.
The problem is Git has to pull the entire codebase even if you only want to edit one small part of it. (At least, until recent patches from Microsoft have made that work correctly.)
So I'm not saying it couldn't do the job, but I am saying it couldn't do the job as well as TFS or BitKeeper of the time could. (Both of which had the ability to check out just certain folders or files.)
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
Linux used BitKeeper before they moved to Git. And they had to move to Git because BitKeeper was providing it to them for free, but they decided to stop because some Linux devs were being dickholes and reverse-engineering it which violated the agreement.
I can assure you that we're talking dickholes all round. The guy in charge of BitKeeper is a jerkwad of the first order. I've met him, and that description I've just used is 100% accurate and he knows it so it is totally a fair description. I also know people who work for him (and they're OK; it's their boss I don't care for). I don't know the upper parts of the Linux community as well, but some of them definitely come across as jerkwads from what they've written and said in online videos. (Linus isn't even close to the worst. Which is sad, really.)
I'm glad I'm not locked into BitKeeper. I'm glad I don't use git for everything. I'm glad I don't have to interact with the maintainers of git on a regular basis,. I'm very glad I've found a GUI for it that suits me so that when I have to use it, I can usually avoid the command line completely. (I've done things with git in the past that shouldn't be part of any sane GUI, but they're very unusual stuff like deliberately breaking a repository in an undetectable way in order to make a platform for assessing students' ability to software engineer. That involved bizarre stuff indeed and much application of things that don't belong in any sane API.) And where I have a choice and no overriding reason to pick one thing or another? I choose non-git.
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
The problem is Git has to pull the entire codebase even if you only want to edit one small part of it. (At least, until recent patches from Microsoft have made that work correctly.)
See, the advantage of Open Source right there
-
@stillwater said in Python Installation using sudo make install + obligatory Linux rant:
@admiral_p Kubuntu looks clean enough for my purposes. I already have win10. Is there a way to install a Linux distro but not have the Linux bootloader load first to choose which os to boot into, instead have the windows bootloader let me choose. Is that even possible?
Not with Windows 10
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
And they had to move to Git because BitKeeper was providing it to them for free, but they decided to stop because some Linux devs were being dickholes and reverse-engineering it which violated the agreement.
TIL Telnet is reverse-engineering.
-
@JazzyJosh said in Python Installation using sudo make install + obligatory Linux rant:
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
And they had to move to Git because BitKeeper was providing it to them for free, but they decided to stop because some Linux devs were being dickholes and reverse-engineering it which violated the agreement.
TIL Telnet is reverse-engineering.
Just like how guessing URLs in your browser is hacking.
-
@JazzyJosh said in Python Installation using sudo make install + obligatory Linux rant:
TIL Telnet is reverse-engineering.
It doesn't matter how they did it, it matters that they did it.
-
@blakeyrat said in Python Installation using sudo make install + obligatory Linux rant:
It doesn't matter how they did it, it matters that they did it.
He used telnet to connect to the server port.
Once connected, he tried a command, "help" and got a list of commands.
He typed "clone" and got the output of a bunch of files.
Reverse engineering made easy !!!!!1
-
@TimeBandit Ok?