(upbeat music)
- Well, it is my pleasure
to have somebody that I have admired for decades,
Linus Torvalds, joining me on...
At the Innovation Conference for a conversation
about history of Linux, technology, open source.
So, if you don't mind, Linus,
maybe just start out telling us the early days, right?
When Linux was getting underway and what was that like?
And, take us back, right?
You're now 30 years old, right?
A little bit over a 30 years old for Linux.
So, this has been an incredible journey.
So, take us back to the beginning.
- Right, so 32 years ago, I got a new computer,
and I was used to home computers,
and I came from, for the geeks among you,
I was used to 6502 CPUs originally,
and then upgraded to the 68K series.
And, the C80 camp and the 8086 camp
was kind of strange to me.
The ugly instructions--
- What, you didn't like that segmentation style?
- I really did not like that at all, right?
And, the odd addressing too, with no rules at all.
And, but, at the same time,
the writing was on the wall
and the 386 had come out, right?
- Yes, yes, my baby.
- And, 386 really changed, took away...
Well, I mean it, you could ignore, let's put it this way.
You could ignore all the bad parts.
And, I really wanted to learn how it worked
and that's where your book comes in,
because that was one of the basically two tomes I used
to learn my new machine
and start writing low level code
to really understand it wasn't just the CPU,
it was all the PC peripheral components around it too,
which I was completely unfamiliar with.
And, so I wrote a VGA character driver,
I've wrote the serial driver,
I've learned how to get into protected mode,
because that was kind of what I was interested in.
And, when you do that,
and you work on it for a few months,
suddenly, what you have
is kind of the beginning of an operating system.
And, I realized that if I took this the next step,
I could actually use this,
not just as a like teaching myself
how the system worked,
but also use it as a daily driver.
And, that's when I actually started actively developing
as an operating system.
- So, when you...
When it went from being, hey,
this is just me learning the...
This new machine to it becoming an operating system,
did you have any idea what you were unleashing?
- No, and I didn't really...
I had a very low expectations,
because I was always expecting that, okay,
this is one of these projects that I will do for myself,
and then, at some point, I will get bored,
and then I will get a real operating system eventually,
which I couldn't afford at the time,
because I came from a not blue color,
but like not a--
- Pretty humble beginning.
- Exactly, right.
And, so what happened was
that I was still pretty proud of what I started.
So, I put it out,
and it wasn't really initially about open source for me.
Initially, it was more like, hey, look at what I've done,
right?
Kind of, this is, this is kind of cool,
this is interesting.
Maybe, somebody else is interesting.
And, that completely changed everything.
And, that's, I went from being, kind of,
knowing about open source
to being completely convinced
this is the only way I ever want to do it.
- That was your light bulb moment.
- That was my light bulb moment,
because it...
It wasn't initially so much that it brought in
all these other people,
because that took a while.
It really takes a while for the process
to get to the point where it's self-sustaining.
But, it meant that this project that...
Was my small thing that I expected to go away,
suddenly the open source part
made it so much more motivational for myself,
because I got questions,
I got people involved that said, this doesn't work for me.
Can you do something about this?
I ended up having to buy a math co-processor,
because I didn't care originally.
And, I wrote a small software emulation layer,
but there was this, I think, guy in Germany,
who said,
I have a math core processor and I can't use it.
It only uses your emulation and it's really slow.
So, I actually got myself hardware
just to be able to support people
who suddenly were interested in this project
that I hadn't taken so seriously before.
- So, all of a sudden,
so this project is gaining momentum.
You have people starting to contribute to it
around the world
and you've taking a life on,
and so on.
And, all of a sudden, you've unleashed
the operating system wars,
you have all these other unixes going on, and free BSD,
and Microsoft, and so on.
And, all of a sudden, it's not a little project anymore.
So, what's the dynamics here?
- Well, to me,
I mean you mention all these other operating systems,
but, to me, they didn't matter, right?
I didn't care.
To me, like...
- They cared about you.
- It, not initially, but eventually they started noticing.
But, even when, like,
we made jokes about Windows being the enemy,
and we made jokes about world domination,
and they turned out to not be so much fun after all,
because the world domination kind of started happening.
And, the Windows jokes became pretty old too.
And, for the people who actually were involved,
it was never about the competition.
It was really all about the technology
and making Linux itself better.
And, it turns out a lot of people asked, for example,
about so BSD had all of a lot of infrastructure already,
and it's really hard to take other people's code
and try to make that fit in your world.
- Yeah, yeah.
- Right?
So, we never even went down that path.
And, there was also the BSDI lawsuit
and everything ugly going on on that side,
which would have made it a horribly bad idea.
But, it was not that we...
Well, it was that we really ignored
all the other operating systems
and there were people who were in both camps,
but they, they're actually fairly.
- Now, so, one of the things, so we're in the middle,
obviously your friend, Dirk Hondel,
worked for me at VMware,
and we're in the middle of Covid, right?
And, all of a sudden everybody has to work from home, right?
And, all of a sudden,
we have distributed development going on.
- It wasn't actually all of a sudden,
because I'd been working from home.
- Precisely, precisely.
And, this idea of fully distributed development
and, I think, how often has the core Linux team
actually even been together in person, right?
I mean, you've always worked this way, so, somewhat,
once again, you were like decades ahead of your time.
- We literally did not notice, in fact,
somebody did the statistics
in some of the early months
and people staying more at home
meant that they were more productive
when it came to Kernal work.
It did, we do actually have a yearly meeting
where maintainers get together and discuss--
- Oh, is that beer or pizza
or do you actually do work there?
- We do some work there.
- Okay, not much though.
- But, it is, it is social
and it's a way to catch about what's going on,
and what's going wrong, and what's going right.
And, we missed that for a couple of years,
but it actually happened two weeks ago.
So, we're back on track.
We have met each other again, face to face,
but it's, the real work,
gets all done over email.
And, when we meet, it's about the...
It tends to really be about the social issues,
not about code issues.
Because, code you can discuss over email
and you can actually quote the actual piece of code
much more easily in email than you can in person.
- Yeah, and I, as we were in that period,
we're now all of a sudden
everybody had to do distributed work.
It was like, man,
you've been doing this for two and a half decades
at that point.
- And, it's wonderful. It is wonderful.
I mean, you can tell you a lot of tech companies
have trouble getting people to come back to the office,
I think.
- Yeah, it really has been very much more productive.
You didn't realize how far ahead of your time you were,
right there.
Now, talk about open source in the context of cloud, right?
And, cloud is taking advantage
of open source industry ways,
and just give us your perspective on that.
- You know, there's no...
There's no cloud is taking advantage of.
There's more like some companies
are not necessarily as good
at really participating in the process
and it's--
- Say more, what do you mean participating in the process?
- So, to be a really productive user,
you don't have to just use the product,
you have to interact with the whole process
in doing bug reports,
in helping support the project,
and ultimately being part of
the actual development community.
And, some companies are more open to that than others.
And, it's maybe...
And, it's not so much cloud or not cloud.
Intel has been very good.
I mean, I was...
- Thank you.
- Which--
- [Pat] And, we're gonna be better.
- Actually surprised, it surprised me,
because when I moved to the US,
we had a lot of problems with Intel engineers
that could not participate, because legal said, no,
you cannot do that.
- Those nasty lawyers, they're always getting in our way.
- That was a problem.
And, then something happened,
and it was almost like a switch was turned,
and it must have been something inside,
where the lawyers were told make it work.
And, Intel became one of the more active participants.
But, we have cloud providers who are active participants,
and do a lot of development, and do very well.
And, we have cloud providers who,
I call them black holes,
I will not name names, where--
- Maybe some of our listeners can guess--
- People, yes,
some places you can probably guess people go
and become developers inside that company
and we never hear from them again.
- Yeah, so open source is really about not just benefiting,
but it's participating and contributing to the ecosystem.
- And, the participation doesn't necessarily
have to be about actual development,
because development is something, I mean,
development is a part of it,
but it's not necessarily even the major part always.
We have like, I concentrate obviously on development,
but a lot of problems get found
only once you have users,
and having companies and individuals
who just test and who participate
in literally doing test cases,
doing documentation,
just sometimes teaching other companies how to participate
has been a huge deal.
So, it's multifaceted,
let's put it that way.
That it's not necessarily...
people think about open source as just the tech geeks
who do the programming,
but it actually is a lot more than that.
- Now, talk a little bit more, I mean,
part of open source is also also the licensing model,
right?
And, how that has progressed as well.
Just talk a little bit more,
and how you participated in that,
and your views on where that is today.
- Well, I mean we have multiple different licensing models
and I happen to like some of them,
and I'm not a fan of others,
but, in the end...
People choose the license
that they are most comfortable with.
And, the open source initiative has a few rules
for what a license has to do
in order to be called open source.
And, they basically boil down
to everybody has to be able to participate
and then you can have, the details may change,
but you can't limit people's participation or people's use.
And, for me, personally,
it has always been
the legal side hasn't been as important
as the conceptual side to...
For me, open source is tit for tat.
We all give each other something
and the tat is you give,
you give your improvements back.
And, it turns out, in game theory,
tit for tat is considered
to be a fairly good strategy in general,
not just in like when it comes to source code,
but just as a general approach to many problems.
And, I think one of the most important parts
to opensource, for me,
has been that everybody needs to feel
like they are at an equal footing.
We've had a lot of companies who do dual licensing
and it's perfectly legally fine,
but it tends to result in a...
In politics and internal strife about the project
when one company or one entity
has more rights than the other entities.
So, I've tried to...
I've personally tried to always keep all my projects that,
very clearly, I'm not special,
I'm the top level maintainer when it comes to the Kernel,
but if somebody else does a better job
and, one day, that will happen,
they will take over,
because I don't have any special rights
except for the fact that people trust me,
because I've been doing it for 30 plus years.
- Yeah, so it does seem like open source trust,
I mean this idea of contributing to the community, right?
And, having the, right?
The exposure of the community
and then finally the trust of the community, right?
- Yes, but, I mean,
so you say I don't actually like the notion
of contributing to the community,
because that implies a certain amount of altruism
that I'm not a huge believer in.
So...
- Okay, tit for tat, yes.
- I really think it's more like
you're not contributing to the community.
What you're doing is you are trying to make a project
better for yourself
and the rules of the project
end up then meaning that,
as you're making it better for yourself
and trying to improve your own situation,
you kind of...
- Make it better for everybody,
- Indirectly contribute to the community.
But, your...
You should always be motivated by your needs.
And, that's actually how a lot of these
open source projects,
including very much the Kernel,
have improved so much is because,
I'm looking at all that we've done
in the last 25 years,
and none of it was stuff that I needed or I wanted,
because, as far as I was concerned, 25 years ago,
the system pretty much did what I needed, right?
It...
- Yeah, and I've been very fascinated,
when Linux was first starting,
I was a young engineer, right?
And, watching this and, right?
And, it was always curious to me
how it would play in the enterprise space, right?
'Cause, enterprise, they need somebody to support it,
somebody to maintain it, they're not, right?
And, some of the legal and security aspects
associated with that.
And, that was somewhat surprising to me
how the whole enterprise licensed supportive version, right?
Of open source emerged.
- A lot of it took...
I mean, all the initial enterprise use
tended to be grassroots use,
where somebody in the IT--
- [Pat] Yeah, some fringy guy.
- Yeah, exactly.
- Or, often, they were not in IT.
- Just decided I need to do a print server for my office
or something like that,
and started using it internally,
and it took years for,
especially legal does tend to be a bit nervous when...
And, it's licensing, obviously,
but it's, in general, when you don't have anybody to blame,
that makes some people very, very cautious.
And, having all the infrastructure,
including having companies to blame
when things go wrong
so that you have somebody you can call and say, hey,
come and fix this,
that took a long time.
I mean, it's...
It...
None of this has been exactly overnight.
Actually, so Linux has been going on for a long time.
Just to contrast that with the other project I started, Git,
and that was almost overnight in comparison.
It was like, that was a project
that I kind of knew what I was getting into.
And, I've done this...
I've started a project before,
and now I'm starting a new project,
and I was like, this is gonna take years.
And, nobody's interested in source code control anyway.
And, CBS has been around for decades
and nobody has ever been able to really replace CBS.
And, initially, that seemed to be very true.
And, then that was overnight, the...
Like the Ruby people, strange people,
started using Git,
and, suddenly, it just exploded.
And, that was very different from Linux,
which was interesting to see.
- Yeah.
Now, let's move forward a little bit.
AI and machine learning, right?
Obviously, lots of open source projects going on
in that space,
but, in machine learning,
the data is maybe more critical,
the training sets, the data sets associated with that,
right?
And, say a little bit more about
your views on how that could and should evolve
and do we need more open data initiatives
to compliment what I'd say is more open source?
Here, right?
The code can be small, the data is big, right?
It was just...
- Right, I mean we've seen that in other projects too.
It's not just AI.
I think AI is the one that people are now very aware of
just because it's such a big, like...
Big issue, both,
technically and from an economic standpoint.
But, if you look at a lot of other software
and hardware issues,
you do see some of the same things
where game engines, for example,
is something where, on the one hand, you have the code,
and, on the other hand, you have the data
and the game environment,
and the two are fairly clearly separated,
and you can have one game engine that runs
many different games,
and a lot of the intellectual property ends up being
on the pure data side.
- Yeah, well, and even here, I mean,
when we think about things like ethical AI,
a lot of it has nothing to do with the algorithms.
It has everything to do with the training sets
for that algorithm.
And, if they're closed,
do I know that this was a good model
that was produced associated with it?
- Well, and we're seeing all the same issues
that you see with people,
when you have data sets that are biased
in ways you don't even realize.
Yeah, no.
I have to say I'm not...
I only get involved with AI in the sense
that we see it on the Kernel side in the...
On the hardware space,
where we provide drivers for the accelerators.
And, I've been so hyper focused on the Kernel
that anything I say about AI is likely to be wrong anyway.
- And, I love what you said to me in our stage interview.
I was trying to get you to predict the future and, right?
20 years down the road.
And, how did you describe yourself?
- That I'm a plotting engineer, right?
And, I'm...
I take pride in that,
but I realize it also means
that there are these people with,
visionaries that want to talk about the big picture
and I don't tend to be one of them.
- Yeah, well, and I think there is something
in that constancy of purpose,
in a consistent direction, right?
Right?
You just keep progressing.
- And, you need, you need all kinds, right?
You need...
You need the kind of person who sticks to one project
for 30 years,
which, I mean, not everybody will do, right?
- Yeah, that's a different personality as well, so.
So, here we are, right?
We're at the Intel Innovation Event, right?
We say, and as I like to say,
we used to have the Intel Developer Forum,
and I am bringing back that spirit,
engaging with developers,
rebuilding of our cred in the open community,
open standards,
interfaces, WiFis, USB, PCIEs,
and now we're doing triplet standards, et cetera.
And, as you would look at us, how's Intel doing?
- Well, I think everybody knows that issue.
The problems on the execution side have been pretty painful
for everybody.
And, it's...
I don't, I mean, I don't see any of the hardware
and fab issues.
What I see, have seen,
are kind of the fallout
from the Intel software development standpoint where
the last few years have not been quite as a ebullient
as they were before.
And, people have not been as happy
with being inside of Intel,
because I don't think Intel has necessarily
been a very happy place for a few years.
And, I'm hoping that's changing.
- Well, that's certainly my job, right?
To change it, as well.
And, we're...
We're getting on it, right?
As we rebuild.
And, obviously, having events like this one
are about rebuilding our commitment,
our engagement with the community,
participating, driving standards as well.
Other advice for me?
- So, what I've really liked about Intel
is when you do standards based around hardware,
I loved how NVME turned out.
PCIE is obviously another great thing.
The Xavier6 architecture in general.
I just think, put good hardware out there
and document it enough that it will be the standard.
That's all I ask for,
because that makes my job so much easier.
We...
There are clearly other companies
that don't do the documentation part, for example,
and don't help make--
- Well, that's why you liked me in the first place.
I documented the 3D sets--
- Absolutely, right?
No, documentation is important,
even if I'm probably the wrong person to say that
since I never write any myself, so.
- How dare you?
- Yeah, no, it's...
It's being a bit...
Yeah, asking others to do something I can't do,
but it's also participation, yes?
Being, especially for a hardware company,
when it takes years to get a process or a processor
or other new hardware out into the market,
and then it takes like a week when you announce it,
and it's, well,
it hopefully takes a week when you announce it,
and it's on shelves.
For us to support it,
it usually takes months or years.
So, being proactive
and actually interacting with the community
before the product is out,
and Intel has been good in that sense.
- Yeah, well, and, tomorrow,
we'll be announcing early hardware
on the intel dev cloud, right?
Which, starting to put up our products months,
if not a year or more,
that developers start to have access to them sooner.
And, starting to really...
And, to me,
I'm just passionate about this, this re-engagement,
that people can start saying, oh,
that's a cool idea,
and we're ready to be tested on our ideas
early in the process.
Get that feedback early,
get the hardware out there in their hands.
- And, since I have your ear, and this may be cut out,
I...
The thing I sometimes despise about different companies
and Intel has had that problem
is when you do market segmentation
where certain features only exist in certain...
Certain markets that aren't necessarily
as available as others.
And, I'm thinking of things like the transactional memory.
I mean, it's gone now, maybe it's never coming back,
but that was very painful for us
when only certain server CPUs had it.
And, the people who actually needed to develop for it
couldn't access it easily on their own desktops.
And, that's...
That's, I think, an area where Intel can maybe improve
and not let the market segmentation drive
these kind of technical issues
that make it hard for developers.
- Well, I look forward to always getting your feedback
in the future, right?
And, maybe, you're just one fun little way
to finish our time together.
What is this about penguins?
- There is no deeper truth behind the penguin.
It was, literally,
I was in Australia many, many years ago
and there was a fairy penguin there.
They're literally, they're about a foot tall
and they weigh a pound or something like that.
And, I was in an enclosure with a low thing,
and I tried to get it to come closer
by making like a fish,
and it bit my finger.
And, I thought that was very cute.
So, when we were looking for a--
- [Pat] A mascot?
- Mascot, it was like, penguins are kind of cool.
And, they're like well known enough
that people know what a penguin is,
but they're not like a dog or a cat
or something like so common
that they're not really noticeable, so.
It turned...
I, it was funny,
a lot of people thought that the penguin,
especially the Linux kind of cartoony fat penguin,
was a really bad logo,
because this was late 90s.
Like Linux was not that corporate at the time, right?
So, a lot of people felt like having a cartoonish logo
was a bad thing for a project
that wants to appear--
- Enterprise that's great, yeah.
- Yeah, exactly, yes.
And...
And, then the whole .com thing happened
and it turns out that, on the web, in particular,
having a friendly and like graphically interesting logo
is actually a good thing.
- It looked pretty good, yeah.
- And, I'm told that the Linux logo
has actually been used as a...
As an example of great logos in like, in marketing.
- Your great technology,
an entire open source movement,
and the pinnacle of branding as well.
- Yeah, no, it was completely unintentional.
And, I did...
I did not design the logo.
I just...
I just gave a high level explanation of what I wanted
and I made it a kind of competition
for who can come up with the best one.
And, then others did the graphical part.
- My wife and I did a cruise to Antarctica
and we saw tens of thousands of penguins.
So, anyway, it's a pretty...
We like 'em too.
- Yeah, no, it's a nice, it's a nice animal.
Although, the Linux penguin is kind of an unholy mix
of penguins and ducks,
'cause penguins don't actually have like the orange feet
that the Linux penguin has.
- Very good.
Well, I am, again,
so honored to have you join us at Intel Innovation.
Thank you for taking time for a more in-depth interview,
joining us on stage,
being here,
and, of course, becoming the recipient
of the Intel first ever Intel Innovation Award.
I couldn't think of somebody more impactful
for the evolution of technology,
the development of entirely new software model,
and deploying in something that, literally,
has become the operating system of choice
for so many industries.
Thank you so much, Linus.
- Thank you.