Archived threads in /g/ - Technology - 1264. page

>>61571773
fuck off rapist

>>61571799
>the first think is to commit a crime
lmao no, retard.

>>61571799
He's not a rapist if he cannot even find women yet.

>>61571766
They won't check just replace it

Buy an external HDD and just use Time Machine to backup your machine. That way when you boot the new machine, when it asks "How would you like to set up this Mac" you can click "Restore from a Time Machine Backup"

>>61571766
>advices ?
>tweaked as FUCK, mySIMBL and everything
install gentoo

sj ded

now there are 4 you fucking retard

>>61571739
Fpbp

>>61571717
Someone at LINUS MEDIA GROUP™ is shilling hard.

>>61571700
master race

>>61571700
bye

Hi pajeet

The second big problem: Attack Surface

On a hardened system without systemd, you have at most one root-privileged process with any exposed surface: sshd. Everything else is either running as unprivileged users or does not have any channel for providing it input except local input from root. Using systemd then more than doubles the attack surface.

This increased and unreasonable risk is not inherent to systemd's goal of fixing legacy init. However it is inherent to the systemd design philosophy of putting everything into the init process.

RED HAT PAYING DEBIAN TO FORCE SYSTEMD

Systemd is not an init system!!
If someone characterizes systemd as an “init system,” you may safely assume that s/he is either utterly clueless or deliberately obfuscating the discussion. Calling systemd an init system is like calling an automobile a cup holder. Not even Lennart Poettering pretends that systemd is anything but the “Core OS” (sic).

What systemd is is an effort to re-create large portions of existing userspace (including login, job scheduling, and networking, just to name a few) inside a single process traditionally reserved for the sole purpose of starting *nix userspace. (Just in case it isn't clear, there is a huge difference between starting userspace (init) and being userspace (systemd).)

At the end of the day, how one perceives this re-creation of existing userspace strongly influences one's reaction to systemd. There are plenty of perfectly legitimate reasons to be troubled by this re-invention of the wheel; they range from the philosophical and aesthetic, to the technical and mechanical, even the purely political and brutally practical.

And that's part of the problem when folks start to “debate” systemd. Very few folks have the chops to think about, much less talk about all of these areas simultaneously. As a result, the discussion becomes fractured and disjointed, in what is literally the textbook definition of bikeshedding. Suddenly, a talking head who's never written a line of code in his/her life offers up an authoritative-sounding-but-utterly-bogus opinion on systemd's maintainability. Add in the fact that folks on both sides (including Poettering himself) act as if name-calling is a perfectly good substitute for empirical evidence, and the “debate” becomes indistinguishable from white noise.

Full story:
http://forums.debian.net/viewtopic.php?f=20&t=120652&p=570371

Linus Torvalds bashing systemd developers for making kernel developers work around their problems

mailing message:

>Key, I'm f*cking tired of the fact that you don't fix problems in the code *you* write, so that the kernel then has to work around the problems you cause.

>Greg - just for your information, I will *not* be merging any code from Kay into the kernel until this constant pattern is fixed.

>This has been going on for *years*, and doesn't seem to be getting any better. This is relevant to you because I have seen you talk about the kdbus patches, and this is a heads-up that you need to keep them separate from other work. Let distributions merge it as they need to and maybe we can merge it once it has been proven to be stable by whatever distro that was willing to play games with the developers.

>But I'm not willing to merge something where the maintainer is known to not care about bugs and regressions and then forces people in other projects to fix their project. Because I am *not* willing to take patches from people who don't clean up after their problems, and don't admit that it's their problem to fix.

>Kay - one more time: you caused the problem, you need to fix it. None of this "I can do whatever I want, others have to clean up after me" crap.

http://www.phoronix.com/scan.php?page=news_item&px=MTY1MzA

please help

>>61572006
I'd say X230T but it's 16/9

>>61571395
Non-gpu surface book is under 1k on eBay and still less clunky than most modern laptops.

>>61571317
Who cares about dipshits having too many apps on their candy crush.

>>61571317
>not rooting and blocking ads with hosts file

>>61571317
things always start out good then the moneymen suck it dry.

>>61571258
Is this that pedo?

>>61571258
Oh god. I had seen this on other threads but I just now clicked it.

It's fucking Alucard. Of course. Also of Rizon fame for being a prolific IRC autist, and known for being the (ex) host of a variety of lewdly named pomf clones.

Of course it's Alucard.

I have absolutely no qualms with the loli for sale domain. I found it comical.

>but muh offensive child trafficking joke!

It's a joke. It's funny. It's relating to a comical alternate anime universe. Calm down.

File: intel ceo JUST.jpg (165KB, 1002x1480px) Image search: [Google]

165KB, 1002x1480px

>>61571143
Took them long enough to realize.

Intel seems to be in deep shit right now and Krzanich piss-poor management certainly is to blame.

File: brian gets blacked.png (3MB, 1172x1416px) Image search: [Google]

3MB, 1172x1416px

>>61571143
>author is some pajeet street shitter

DELET. PLS

Home servers are for plebs.
Colocating your own box is the highest of high tiers.

>Not even using an entire data center in your house.

>>61571116
When I get a home

File: 1500853499228.jpg (92KB, 500x688px) Image search: [Google]

92KB, 500x688px

>>61571013
>attempting to gain statistics through anonymous anecdotes

File: lmao.jpg (50KB, 634x512px) Image search: [Google]

50KB, 634x512px

>>61571013
>degree

>>61571013
I majored in CS but ultimately ended up as a recruiter. Now I go to my old University and make all the students feel retarded for not knowing how to program stupid algorithmic questions that they'll never EVER have to tackle in IRL life.

>>61570952

Tried calling the service hotline, the number in China is not even available from European net. LMAO

Just revert the payment and report their website for fraud/scam on Google, Paypal, and as an anonymous tip to the authorities since you didn't receive a receipt.

>>61570976

Not really worried about getting my money back, but not having the phone sucks

I thought you guys knew about GeekBuying? Its pretty big in China IIRC. Im sure if it was a scam people on here would be aware, no? But I see it being posted in CSG a lot.

HTTP tunnel

They blocked all ports besides 80 and 443.

>>61570911
Use a vpn that runs over 80 or 443. Then ssh through that

Windows 7 kek

>>61570899
LTSB, on TPB

>>61570670
Ugly af

>>61570687
>t. Mr. Poor

That's the ugliest phone I've ever had the displeasure of laying eyes on.