Locating source code of the PureOS installer
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have been playing with PureOS installation options (the ultimate goal is to install it dual boot with MacOS on a MacBook Air, but this is out of the scope of this question).
What I would like to see is how this "Boot loader location: Boot Partition (/boot)" option actually works behind the scenes (in particular, how it makes the Mac's bootloader know where the /boot
partition is, by "blessing"?):
I thought that digging through the source code of that installer should shed some light on what it does. I therefore went to see what is under the "Source Code" link on their website, but it looks like a packages repo rather than source code:
So, the question is: where is the source code of the PureOS bootloader installer? Am I just missing something obvious, or is it not actually available?
debian-installer source source-code pureos
add a comment |
up vote
0
down vote
favorite
I have been playing with PureOS installation options (the ultimate goal is to install it dual boot with MacOS on a MacBook Air, but this is out of the scope of this question).
What I would like to see is how this "Boot loader location: Boot Partition (/boot)" option actually works behind the scenes (in particular, how it makes the Mac's bootloader know where the /boot
partition is, by "blessing"?):
I thought that digging through the source code of that installer should shed some light on what it does. I therefore went to see what is under the "Source Code" link on their website, but it looks like a packages repo rather than source code:
So, the question is: where is the source code of the PureOS bootloader installer? Am I just missing something obvious, or is it not actually available?
debian-installer source source-code pureos
1
It seems there's more code there : tracker.pureos.net/diffusion Otherwise I would say as the Mac probably uses UEFI, so the installer is probably updating the EFI boot loader as you would on a regular PC, by adding an entry using efibootmgr maybe.
– Pierre-Alain TORET
Dec 6 at 10:19
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have been playing with PureOS installation options (the ultimate goal is to install it dual boot with MacOS on a MacBook Air, but this is out of the scope of this question).
What I would like to see is how this "Boot loader location: Boot Partition (/boot)" option actually works behind the scenes (in particular, how it makes the Mac's bootloader know where the /boot
partition is, by "blessing"?):
I thought that digging through the source code of that installer should shed some light on what it does. I therefore went to see what is under the "Source Code" link on their website, but it looks like a packages repo rather than source code:
So, the question is: where is the source code of the PureOS bootloader installer? Am I just missing something obvious, or is it not actually available?
debian-installer source source-code pureos
I have been playing with PureOS installation options (the ultimate goal is to install it dual boot with MacOS on a MacBook Air, but this is out of the scope of this question).
What I would like to see is how this "Boot loader location: Boot Partition (/boot)" option actually works behind the scenes (in particular, how it makes the Mac's bootloader know where the /boot
partition is, by "blessing"?):
I thought that digging through the source code of that installer should shed some light on what it does. I therefore went to see what is under the "Source Code" link on their website, but it looks like a packages repo rather than source code:
So, the question is: where is the source code of the PureOS bootloader installer? Am I just missing something obvious, or is it not actually available?
debian-installer source source-code pureos
debian-installer source source-code pureos
asked Dec 6 at 10:10
Greendrake
1286
1286
1
It seems there's more code there : tracker.pureos.net/diffusion Otherwise I would say as the Mac probably uses UEFI, so the installer is probably updating the EFI boot loader as you would on a regular PC, by adding an entry using efibootmgr maybe.
– Pierre-Alain TORET
Dec 6 at 10:19
add a comment |
1
It seems there's more code there : tracker.pureos.net/diffusion Otherwise I would say as the Mac probably uses UEFI, so the installer is probably updating the EFI boot loader as you would on a regular PC, by adding an entry using efibootmgr maybe.
– Pierre-Alain TORET
Dec 6 at 10:19
1
1
It seems there's more code there : tracker.pureos.net/diffusion Otherwise I would say as the Mac probably uses UEFI, so the installer is probably updating the EFI boot loader as you would on a regular PC, by adding an entry using efibootmgr maybe.
– Pierre-Alain TORET
Dec 6 at 10:19
It seems there's more code there : tracker.pureos.net/diffusion Otherwise I would say as the Mac probably uses UEFI, so the installer is probably updating the EFI boot loader as you would on a regular PC, by adding an entry using efibootmgr maybe.
– Pierre-Alain TORET
Dec 6 at 10:19
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
The link provided does indeed point to a package repository, but that package repository also includes all the source code for the packages. All the tarballs contain source code: in the example you show, the various .orig.tar.xz
files contain the upstream source, and the .debian.tar.xz
files contain the distribution-specific patches applied to them.
PureOS seems to use the Calamares installer framework; this is where the “Boot loader location” selection lives. You’ll find the source code for the PureOS version in the relevant repository, and all the PureOS core source code just above.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486332%2flocating-source-code-of-the-pureos-installer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The link provided does indeed point to a package repository, but that package repository also includes all the source code for the packages. All the tarballs contain source code: in the example you show, the various .orig.tar.xz
files contain the upstream source, and the .debian.tar.xz
files contain the distribution-specific patches applied to them.
PureOS seems to use the Calamares installer framework; this is where the “Boot loader location” selection lives. You’ll find the source code for the PureOS version in the relevant repository, and all the PureOS core source code just above.
add a comment |
up vote
1
down vote
The link provided does indeed point to a package repository, but that package repository also includes all the source code for the packages. All the tarballs contain source code: in the example you show, the various .orig.tar.xz
files contain the upstream source, and the .debian.tar.xz
files contain the distribution-specific patches applied to them.
PureOS seems to use the Calamares installer framework; this is where the “Boot loader location” selection lives. You’ll find the source code for the PureOS version in the relevant repository, and all the PureOS core source code just above.
add a comment |
up vote
1
down vote
up vote
1
down vote
The link provided does indeed point to a package repository, but that package repository also includes all the source code for the packages. All the tarballs contain source code: in the example you show, the various .orig.tar.xz
files contain the upstream source, and the .debian.tar.xz
files contain the distribution-specific patches applied to them.
PureOS seems to use the Calamares installer framework; this is where the “Boot loader location” selection lives. You’ll find the source code for the PureOS version in the relevant repository, and all the PureOS core source code just above.
The link provided does indeed point to a package repository, but that package repository also includes all the source code for the packages. All the tarballs contain source code: in the example you show, the various .orig.tar.xz
files contain the upstream source, and the .debian.tar.xz
files contain the distribution-specific patches applied to them.
PureOS seems to use the Calamares installer framework; this is where the “Boot loader location” selection lives. You’ll find the source code for the PureOS version in the relevant repository, and all the PureOS core source code just above.
edited Dec 6 at 12:51
answered Dec 6 at 10:29
Stephen Kitt
162k24358436
162k24358436
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486332%2flocating-source-code-of-the-pureos-installer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
It seems there's more code there : tracker.pureos.net/diffusion Otherwise I would say as the Mac probably uses UEFI, so the installer is probably updating the EFI boot loader as you would on a regular PC, by adding an entry using efibootmgr maybe.
– Pierre-Alain TORET
Dec 6 at 10:19