Asahi Linux: Installer research

okay should be up let me get the chat up and irc cool should be good all right welcome back so uh yeah last time i was missing with dcp which is the um uh display controller and i cleaned some stuff up by the way i have these structures mostly figured out now um but i'm going to change uh to instruction and do something else today because uh one thing that has been on my mind for most of the past few months has been the installer story um how to make an installer for us at unix that doesn't require you to first install mac os and then put linux on top which is dumb and the pain in the ass for um uh and you know needs like 70 gigabytes of wasted disk space which is what you have to do for the current install guide so basically reminder for i've talked about this before on the stream but basically what's going on is m1 max apple so you can max natively support dual booting and so um for regular users what i expect people to do is to have a mac os installed on the linux install and each os that is installed comes with its own iboot bootloader and a set of firmware files and this is stuff that we cannot touch so it has to be um you know they're signed by apple but we can't install them ourselves right and the idea is that uh ideally we will have an installer that can set all of this up for you there is one um sort of critical thing which is that um to be able to reuse so this is a this is a bit of a catch-22 if we were to completely wipe mac os and do a install of only assad linux we'd have a problem because the uh to authenticate to basically to install a custom kernel to be able to run unsigned code on the machine on boot you need to authenticate yourself as a machine owner and to do that you need to have a username and a password on the machine and to set that up you need mac os which is why um at least initially we can't support uh sort of you know having a completely blank mac that you don't even boot mac os on once and then like deleting it and installing us at linux that's not gonna be supported initially uh but all you have to do is log into mac os once uh like like go through the you know first time setup and create a username and password and then you're fine um i do expect people to keep mac os around mostly for updates and things like that because we're not going to support updating um system firmware like not the firmware that comes with uh with the os but like you know the stuff that is actually the first level uh bootloader we're not going to support updating that for linux for probably a long time because it's you know obviously dangerous and you know a pretty complicated set of code um that's part of the macos updates um and also you know there's other firmwares on the board and flash memories and things so you know all of that is a very a key thing we're not going to support um initially so what i expect people to do is to keep a mac os installed around so they can do you know uh updates on that that will update global system firmware but um as the owners of the partition that linux is installed on we are responsible for the firmware that is there that is paired to run when that os runs and so that's what i'm going to talk about today basically the state of my mac mini here right now um is that i have to well you know i'm just gonna i'm gonna show you this detail here um but basically i have two main partitions one is a mac os partition that is like 11.3 points something it's it's kind of old um and then the other one is linux which i actually recently updated to 12.0 beta 3. uh you can see there that it says mac os 0.0 and this one says um mac os 031 so um this is what i'm basically going to do today is this is a full mac oscillator using for the hypervisor i'm going to get rid of this and i'm going to say that from now on if i mess with hypervisor i'm going to do it in my primary mac os partition here because i don't really care because i never really use this mac os install because as a regular mac os machine for like development they have like the macbook air and stuff so i'm going to say that from now on this machine is only going to have you know it's really there's actually except the same way that end users are going to set up their machines that is there's going to be a mac os install here and it's going to be a linux install that is not going to be this uh 70 gigabyte uh nonsense that it that uh i'm using right now because it's not going to contain a phone mac os install so what we're going to end up with is uh a primary mac os partition a stub apfs partition that is going to contain all the things needed for the system to recognize this as a bootable os but then is uh you know it's only going to boot mini and then of course they will have the linux boot and linux root partitions which i haven't used yet but now that uh nvme support actually works uh now is a good time to once the installer works especially now it's a good time to finally have a linux install on this machine that is you know bootable and stuff so i'll probably throw our linux on it and um so i don't spend too much time on the installer right now because i do have to work on the gpu but i don't think it's gonna be too much work to do at least a basic um you know minimal proof of concept script and that's already gonna make people's lives much easier uh so i'm going to be mostly working from ssh because i have a separate keyboard here it's kind of been a yes uh but this is just to give you an idea of what's going on here so basically i'm going to wipe this and this is a bit of a special case because normally you can't install an os version that is newer than the system firmware so we expect people to update their mac os to the latest version first and then install linux with a compatible os version and we will have specific mac os sort of base versions that we use to pair linux 2 because we can't support all the versions because uh apple doesn't have a stable api for their firmwares so if we had to support every single release that that apple does where they change something that would be a pain in the ass so we're basically going to say that you know you can update your mac os to the latest version of whatever you want but when you install linux the firmware and bootloader it will download for you for a second linux will be one of a set of options that you can pick and at least for testing purposes i'm gonna be working with 12.3 beta 3 which is the one that's actually installed here so i know that this machine's global firmware is already at least as new as 2.3 beta3 so that's definitely going to work so um and i'm also going to be mostly working on the installer from this mac os install because uh it's a lot easier to sensation than using the recovery environment but this is going to eventually run from the recovery environment it should basically work um the only thing we're going to do manually from the recovery environment is bputil and kmutil but that's okay um that's really not a big deal so i can even for the prototype this will be enough right basically tell people hey run this script from mac os um it will install things and then go into the recovery environment and uh run like you know actually script so that's kind of going to be the prototype approach here so um first thing i just installed the xcode utilities because i'm going to need some mac things installed on the mac side uh so what we have here i hope you can see that is um what i just showed you on the graphical one this is this cute little stuff right so before deleting linux i want to do a proof of concept where i put back only the files i've already done this once before in the past um quite a while ago with an ancient version um where i can just recreate everything and put the files in the right place and it should work so what i'm going to do is copy everything off first i need to disk until mount the preboot and recovery partitions shouldn't need a vm partition because this is not mac os [Music] and yes so what i'm going to do is copy these things here and even before using the sort of official mac os um images i'm going to download from apple's cdn to install this i'm just going to see if i can delete everything and manually copy the files over and have it still work it really should um the main thing that's going to happen is this id is going to change and also why is this dot recovery hold on what's going on here oh yeah so this is a copy yeah um recovery the uh boot yeah and active just contains the file name of that i think this is just a random hash but i don't remember if there was a meaning to this or not um this should be uh b7 so the second one ah not this sorry that's the m uh f5v yeah that's the next state okay that's the next stage image for hash is what that was and i seem to recall that this was like the sha something something of one of the bootloader files so this is important stuff that we need to figure out i know that this is just going to be the image id the uh yeah the volume group uid which is going to be basically if i look at this apfs store yeah this uh dcbc thing sorry b785 uh hold on i'm confused now uh disc three is linux did i get that wrong i can't hold on this is volumes reboot is disk 3s4 which is linux yes um and that is using [Music] b7854a hold on oh no i'm confused by dc something else yes uh b7 854 so that should be the uh uid of this partition linux 3s3 yes b7854a blah blah blah this thing here whether you possibly have microsoft external drives you can plug in and use only for the information and stuff uh if apple fixed their bugs with booting mac os from an external drive yes uh it's been glitchy ever since the m1 release and i don't know how much has been fixed uh but i mean that's apple's fault so it's going to be possible as long as booting mac os from external drive is possible and works properly which depends on apple fixing their bugs so yeah anyway so yeah there's a volume group you idiot here um i think actually that we might not need that uh let me look at 3s5 okay there's no volume group here but i don't know if we actually need a volume group because i suspect that the volume uid because that's the same as the volume group i believe if we look at the data partition which should be 3s1 it's v78 that's the same as the volume uid so i think if we just create a volume um that's fine we don't need a separate system volume i'm pretty sure i did that in the past and it worked fine uh so yes so i'm wondering if i really wanna wipe this first or do a little test on a smaller partition yeah you know what instead of making a whole new one just so that i can more easily diff things if it's if it breaks i'm going to create another one and then once i know that it works i might just wipe this one so i'm going to um do a third you always install effectively which is actually more interesting because it's going to be a completely new uh partition and hopefully i don't break everything uh so let's do this qtl um and let's go ahead and we have a linux boot here that is not big enough and it looks route that uh yes delete those so it's uh disk until um what was the right thing here uh this cute little so confusing one good thing about this utility has a p-list output mode so i'm going to wrap this q in python eventually to deal with this and uh thankfully it will work but i need erase volume yes and so free free is what i need and let's get rid of these linux partitions which are uh useless and so then we're going to create um apfs not erase volume uh create container yes create but i need a size and this don't not let me yeah i need i need to first partition that um add partition so actually let me uh we already have most of this documented in the manual install guide um but in this case since i'm creating the main os partition i'm going to be making notes of this so that uh it makes sense so it goes after the nth partition so in this case this free space is after 0s3 so and in this case it will have to be apple apfs why is this percents and well we do want to format and then the size yeah so we're going to need by the way you can see recovery here as almost a gigabyte um i'm going to go ahead and say just to be on the safe side that we're going to leave 2.5 gigs for the boot partition so let's do that um why is it like apple apfes that seems weird yeah i don't know what the story here is let's see apfs and let's call it uh linux 2. oh i don't want it zero damn it uh i think i just created uh a big one yes no that's not what i want um volume erase volume we'll just delete that free free disk 0 disk 5 which is disk 0s 4. uh yeah there you go um why did it say delete container if the oh no because the others were linked yeah okay so we remind myself that this is a thing we need to do uh here is free free yeah or that um can you show that this guitar gui at the end yeah sure uh yeah so let's do 0.5 gigs for this one cool and that should be enough for the boot stuff i won't even worry with the free space um for the linux stuff until later so now we have an apfs partition that is called linux2 and it has a single volume which is going to be our main volume so we've got the add partition thing and now this qtil info 65 disc 5s 5s1 should be enough and so now we have a uid so let's do this utility info and we know that this is the volume uid which should be the what is considered the volume grouper uid and now we need to create the extra apfs partitions and i seem to recall that there was a let me close all this junk first um i remember there was a someone has already figured this all out this q-tip um ap fs uh pre-boots recovery something something someone there was um yeah this stuff because there's interesting commands we need to use to create this stuff uh not asr but basically we don't need to use the snapshot stuff we don't need asr what we need to do is i i've done this before uh and actually it was part of the backup thing because you need to set like specific um [Music] things to restore backup oh there we go this one this is the page i was looking for how much minimum space does mac os need for an updatable mac os install you need 70 gigabytes uh it's unfortunate it's because apple's updater is terrible and extremely inefficient so yeah this part here um add volume yes so draw b that's the important part so we need this stuff um this and this is on disk 5 apfs preboot row b and we're going to need a recovery 2 which would be uh uh uh uh i'm also kind of hoping that the permissions don't really matter for uh iboot i think they won't um and we don't need the blessed stuff i'm pretty sure either because that's not how this works on uh on apple's silicon um but this is for um intel uh recovery oh there's no recovery here but i think it's the same thing anyway so basically just run this and then recovery roll r probably i think that's all we need yeah you don't need vm because this is not mac os and in theory this is basically the data partition in this case so most of the stuff is going to go in preview and recovery links 2 only has to contain basically a it so the bootloader recognizes this as an os um so let's uh go around copying everything basically what we do is um yeah these two pre-one recovery one are the ones that we care about and i'm going to i'm going to make some sim leaks because it's going to be really annoying i should have named them differently honestly but yeah this is really annoying too to mount this stuff actually yeah you can just unmount i already copied them so uh whatever uh yes it's like this actually what what oh uh i have some stupid i have some stupid ads that don't work on my quest because this night uh so let's get this util amount let's amount everything here and 3s4 and 3s5 and then i can mount the new ones and it'll be in the right place yes so let's create some scene links uh that'll be a bit easier to manage this now yeah volumes are like uh sub partitions i guess you can call them they just share all the space um but apple needs multiple of them to make this work so um yeah first let's do the preboot stuff so i need to create um 5s1 i need to create the uuid here which is the uuid for the mac os partition and then basically if i boot files preboot this i don't think staging is useful for anything uh so this stuff here uh let's see what we actually need here and actually uh most of this we don't need restore is useful possibly for the recovery but i'm not even sure if we need that we pretty definitely sure we don't need any of this crap because that's for x86 um i don't know about these playlists probably not or even the var db stuff um what we definitely need is this the boot folder with um this with the uh custom kernel in this case uh well this is mini but we're going to have to use um kmu tool to set this up anyway we need the ap tickets uh and i don't know if those are personalized per partition or not that might be an interesting question and then we need all these image for files which you actually have to create from the um which you have to create from the uh like from the uh image 4p files that apple um have in their uh the recovery image um but i think this should work so i'm pretty sure i've done this before by making a new partition with an eu id and it didn't matter so basically if i copy the whole boot folder i'm pretty sure that should be all that's needed for a basic boot and the big question is will the recovery mode work because i know that has changed too in with a 2.0 beta 3. i'm pretty sure they don't need any of this pre-logging data junk so let's copy just this boot partition and then you can use rsync here just copy and see what happens and yeah this should be pretty much all the bootloader stuff that we need on the preview partition and now on the recovery partition uh that's the same thing with the uid so we create this thing again and then we copy again this is actually just this uh it's really the two these two directories which also can prove that this is all that matters because um obviously this is also a bootable os installed so so we've got a user on boot here and that's going to be the big recovery image this is a bit what's the long has after boot stuff that is uh the hash of the actually i'm going to show you in a second because i need to get a image for tool on this it should be this iboot image it should be the um the image for p hash of this so actually we're gonna need image for two of the eventually so let's install that now um i just installed the xcode tools thankfully because that's always a pain in the ass um so let's clone this and i uh that's another thing is i'm gonna eventually have to set up um some kind of build system for building this stuff on mac but uh uh i don't have auto tool do i oh that's so annoying oh there's releases uh is this actually compiled oh it is mac os and one too cool uh then i don't have to build this excellent oh no that would be good um what was it i keep forgetting that dash o yeah and what's in there oh great um dash l yes um yeah hopefully this works uh of course it's a freaking zip file okay yeah it works so yeah so let's uh let me show you what i mean by that uh if i do extract um uh the boot files uh pre-boot this thing and then uh boot the long thing uh user firmware fud not fought ayaboot.image4. so if i do this extract it with am to hp if i remember correctly it should be the hash of the metadata or of the no it should have the of the p file i think uh so it's just um let's just do multiple things uh that's a 384 i think is what that uses or something like that um this should be f5e something something is it 512 or or of the metadata yeah thorough if i use it's uh this thing here 5v49b whatever is the sha-384 hash of the image for metadata that is associated with iboot on the target partition um and this is actually uh important because that's something we're making these files ourselves from the image 4p and the tickets that apple provides uh also the local things annoying uh so yeah so that's where that comes from uh and uh and there was a reason for that i think too something about regenerating the uh the boot policies when something changes so so let's do that let's make a note of that boot fast pre-boot so that's the path we need and then in there we have this user standalone firmware thing uh all of these files we get from the recovery image so from the um restore image and uh the kernel cache of course we also get from that i don't even know if we need the original mac os kernel cache we might not um that's a good question actually it might be fine if we just uh and this is the same thing i think by the way uh i think this is also the hash of the image for m um but i don't actually care about this because um k muted is going to set that up for us it'd be nice if vp util had an option to just set them hash for this so that we didn't have to uh do it um manually but uh yeah the uh the image short two thing don't worry about it because i that's gonna be different this was an extraction we're actually gonna have to do is a creation later so uh but i know that already the important part is that i know this is the image forum um hash so we created this and recovery so we got that and then we'll you know the files i don't care about because um once it works i'll just say it's those are the files i need to create um but uh yeah so actually this and then we just need the os um the target uh os thing here and so if i'm recording this would be like syst i forget what this was there was a thing with a version number uh somewhere in system library now let's see if i can kind of guess by just looking at the files for services probably uh i remember there was a version thing here like i just kind of found it um so how big is prebot recovery now let's see uh recovery is 2.4 gigs which is actually surprising hold on let's do df uh recovery capacity 100 available used really is it that big it's 1.7 gigs but how i i bet there's some compression thing involved because it's not that big in this one though and the one that i copied it from 700 right so i bet there's a compression thing going on ah there's a thing yeah a psc tool apparently so we did it actually failed actually there was no space yeah it did but why it's only 1.7 gigs on a 2.5 gig partition um uh let me just try this again three actually boot fast um and boot files recovery there boots not boots uh user i might need to expand this actually 75 uh hold up there's your standard firmware that got copied at least is there that much stuff in boot oh yeah okay because we do have uh a bunch of firmwares and crap oh the kernels too in boot uh system library caches yeah hold on it's in the end all those firmwares do matter it's mostly yeah just the firmware's even is uh it's pretty big right for the recovery yeah uh i'm gonna need more space then that's kind of annoying see this is the thing with apple is like why do they always okay let's go fc and delete all of this yeah there we go it's empty now actually where's all that stuff in the in here come from 600 megabytes in fud that should be the yeah and boots that's like too much for fud so the kernel cache is 23 megabytes which sounds reasonable uh and the user from fudd no that's not that big wait why is that there too that doesn't make any sense why are there two copies of the of the base system why are there two copies of the hold on is there a hard link no let's compress that wheel because this anyway this says recovery 700 megabytes so this is some other weird uh some other weird apfs thing i know i know it's different it's definitely a hard link should be the same in these two also the same contents yeah okay that's weird uh let's just see how much it compresses by default that is kind of weird though why are there two of these i think it wasn't like this in the past is there an abfs thing that is like a sibling but not a sim link i bet it's this i bet it's this cp.c oh that's interesting i find out if they're clones or something no it uh got 600 yeah that makes sense so 600 suppose the other stuff is about the 700 we saw here first compression so there's compression involved and cloning um okay so in that case let's just copy uh boot files recovery the boot directory on here we have 1.7 gigs and then in [Music] user and let's just do a clone user arm 64 ebay system let's see yeah also i should have called that boot i did not but that's okay uh let's see uh hello yes there we go okay now we have what we want we got the base system in both places now actually just do it like this find dot and so what's changed uh i know it is uh sorry i'm dumb the no it was correct sorry boot files recovery is b oh it's b7 boot whatever okay sorry sorry i'm outside the uh that it was sorry i'm confusing myself there we go it's exactly the same cool uh so that should be the recovery thing taken care of and uh let's not care about the compression for now and see the cp have anything for compression probably not uh anyway whatever i don't particularly care about that right now um but the previous one is more important uh so let's go fc find here and then that one's gonna have a bunch of junk in the um and the real one but i think it doesn't matter yeah if i do boot though see it's basically the same which is what matters and uh that should be that so again back to back to the os i think so system library see if i can find uh score services and see if i can find what that thing was system version p-list i'm pretty sure that's what it was yes so let's do that sp boot fast target os system library card services and copy this thing over there um actually let's copy that one from the real os um this linux system library core services system version.p list uh what is it what's in the bundle i wanted actually uh yeah let's copy that to good files system library courses services system version bundle what's in there anyway oh it's just strings uh yeah so one thing that about this system version plus is that you can change the things but if you change the product name it still shows up as uh as mac os which is really sad um but i do wonder if there's a way of changing the icon though um like uh this thing um go back to mac os so actually let's see what happened here uh and yeah by the way the description ui will not show the other partitions which is dumb uh you need to i think no even if you do show all devices it still doesn't uh doesn't show everything it's just other volumes which is stupid uh but yeah i mean this is what it looks like so in principle i think this should find it um if i go to here and i go to start a disk oh it doesn't it does is it just because of the lock nah uh i'm not sure if it needs this uh scan it again or not or it might be uh related to like a blessed thing where i need to bless something just to get it to show up on the ui uh smc patches i don't know what you mean uh so there might be something else i needed on the boot partition i don't think i need the uh i don't think i need the uh uh like um what was it the actual um volume group though ah sorry wrong uh there you go uh where am i here actually this might just be a cache let me just uh close system preferences open it up again i get the feeling this is using a cache or something and it didn't actually look anything up so um let's let me look at info for unix linux data and we definitely don't need the read-only stuff uh we might need the like some kind of bootable thing yeah there's a butter disk and a recovery disk story going on here which is uh probably possibly important uh if i go to info disc 5s1 no no it's uh it found them because this has the right apfs types this can be installed yes this can be installed now cs1 yes yeah e7 b7 yeah i think it's fine okay let's just reboot into a recovery mode and see what happens um because i think it might just work anyway uh let's go in here ah that was a very fast shutdown so the two questions are does it show up here and doesn't show up in the um in the actual boot choice selector inside uh recovery os nope uh so there's something else that i need but that's my that might be okay because we don't have even a boot policy for this yet this shows up here i used to i know i did this once i forgot what files i needed it might be something besides the pds file nah there's nothing there is there oh wait is there a third one there no no it's just two okay so um let's just go back go back to shutdown yeah i might need a fake kernel file or something you might need to be blessed actually even though it's not used let me go back to the bootable clone thing oh there was an update preboot thing i forgot about that i don't know if i actually need that i don't think we need a shared cache uh let's ssh into that and we need date preboot then uh disc 5s1 okay oh sorry uh it's this too ah it renumbered them i hate it when this happens uh five is two mount it's this guy three or this two as one now i don't think this actually matters though but because i think this is all the efi stuff yeah it creates no doesn't even do that what did it do crypto user info i think that matters uh yeah i created this stuff which whatever i don't think that matters but the kernel thing might matter system library core services uh yeah it might need bless uh services uh yeah it does want the uh booty if i i don't think this matters or apple silicon though but i might need it um i think we have that yeah we do have the efi even if it's nothing there i'm sorry not a p but i think if i just make an empty file and bless it it might work and it needs uh core services and preboot all right also wants the core efi there okay so let's make that in tb uh so let's place that uh what let's create that what oh uh huh oh sorry let's see that's p pb slash that system record services and then we bless so let's see if that works i think that might work uh system preferences starter disk nope still not there but it might show up in the other thing uh what else do we have i i know i did this once and i totally forgot how it worked um it could be that it really doesn't like me not having a pair of data volume but that doesn't really sound right i'm pretty sure it didn't matter at some point at least for booting uh so someone probably has figured this out already [Music] okay let's do another reboot just in case it's uh again some kind of cache thing actually you might be able to get recovery logs to tell us what the problem is or even just the os logs once i get into the startup stuff one of the other version files you go into options see if the other menu has it nope uh utilities recovery log it's up here yeah so there's stuff here that tells this no users on volume is that the problem no it's key recovery assistant but that's not the issue with the starter disc let's see there are two that does not have a lot of uh okay let's go back to mac os and actually uh let's set the start of disk through this so i don't have to keep doing this because right now it's linux i think last time i may have done this by like just copying mac os and then deleting stuff and uh might want to do this this time there is going to be making the partition bigger though so i remember that that pdf was needed but uh remember if there was anything else needed let me see if i can get some logs in here log uh show this might tell us some things next to nope system settings that's most of it yeah all right oh wait what oh this is from mike like forever ago uh log show start um this is work dashes yeah that's a lot of locks now there's some stuff there not a system or data volume okay why not i think it needs a rose system or something hold on um or yeah i think hold on i think uh one of these oh yeah data system right this has data system and then in this case linux two is probably the wrong role yeah no role that's that's why it needs to be a system uh how was that thing uh the set role thing change volume roll probably uppercase um no specific role no i think there was like something done with change volume role in the past uh impeachment disco different yeah look for excuses like yes why is it not letting me do s why is it not letting me do a system i can make it recovery apparently or no okay yeah ownership of the effectiveness this is required sure but like that's that's just the that's part of the help message i can make it vm or something right yeah see u for users no is it because it's mounted oh uh yeah i think it might need to be created as a system volume from the very beginning uh which is fine yeah i think i remember having this issue before so i think i remember this being an issue oh that's spotlight i hate this so much okay yeah so we all need these things hopefully um but uh yeah let me disk what that's 2s1 and then it would be create volume with the right flags add volume this two in this case what yes i did come on really it's like it just doesn't want me to do is this a thing like some kind of safety or something someone knows about this s is definitely an option uppercase drive ownership and not the user created uninstalled yes and no but like that's a different story i'm pretty sure with the um you know the credentials and all that but that you know here i just need the down volume to exist oh is it because um it needs to be grouped for a system volume that might be it but in that case uh in that case it would just be maybe it does want it to be grouped okay let's do it properly um let's do a linux to let's call it a oh another uid is going to change and yeah that's annoying um so let's call it uh was it you for the data yeah see things i remember how this looks for non-um i don't remember how this was done before the split you might need to do the split in this case um oh maybe this data works actually that might be enough let's see uh without the u ids are different for the boot stuff yeah um that's okay we can create the paired system volume afterwards just do info disk 2 s1 and now this has changed this is data yeah just possibly what we want so anyway um i definitely need to at least move that hold on what just happened here why is this empty why are these uh uh did this just die no it's definitely got stuff no wait yeah wait why are these empty now what happened to the contents of preboot and recovery they just like disappeared well okay i uh when did that happen it was uh hide it there i deleted anything when i destroyed linux 2 really that is annoying but okay oh remove oh thank you so much um bastard at least i have copies for that now the volume not really voluntary it's just that it helpfully wiped all the recovery and previous stuff for me because it's fun like that uh lovely okay well that's fine because i need to recopy it anyway info disk to s1 create the volume uid uh pre-boot here um this will copy everything from now anyway hopefully it's not too big uh might might not fit i probably don't need most of restore i definitely don't need this and i definitely need pre-logging data it's a bit better um and then in recovery files recovery this uh scopy boot and then user had that thing same thing ah yeah that's fine uh okay that should fit in there yep and let's copy all of that uh i already copied that apparently let's see if this shows it now it's thinking more than last time but i didn't like it um oh there's this too is that from before yes from just now hold on it's not in a volume group okay yes that's fine should be a bit more recent than that the next one you might want the paired system thing yeah okay start up this press panel move 5s parent disks yeah let's see what happened here uh oh yeah see there's a demon thing involved so it might be cached anyway that's this one before this is the one i called now but uh that's just random crap yeah the storage kit thing here right let's do a reboot anyways to see what happens otherwise i'll create a system thing the period system volume and see if it matters nope it might be that i need some other files that i forgot about uh but uh for now let's make sure that and let's do it from here because i'm lazy so i need um how was the pair thing created i didn't do the bless though i think this time so that might be the issue yeah i need that uh add volume disc one disc two pair with group with uh [Music] and the um is uh and then just move everything see if it shows anything now nope let's try the blessed thing again oh that's just oh oh i haven't complete system yet wait yes i have oh dumb uh the slash that's why did they copy the other one wrong too 90 copies are fine what ah i might have just killed something there i don't know because it's uh i guess that's just really new snapshot anyway um let's try that again nope okay so we got users done though yeah let's do the uh bless that's that booty is fine nope ah so let's see i know look at this at some point it might even be one of my old streams but i was like messing with this and i have to look for it uh this might be in core services something let's see i'll put efi when i was there let's do another reboot just to check otherwise i'm going to just start uh i'm just going to re like like make the partition much larger and start copying more of mac os in here and see how much it needs it because it might need more than that file there might be something else but i think it was just that boot efi though and the version b list let's see what happens this time nope still not there ah let's go to macintosh hd and check the uh logs again and otherwise i'm just gonna start copying more things actually no i can do i can mess with linux2 and i can break it and then fix it by just moving file oh no but that one's sealed that's annoying yeah i'm gonna have to copy everything then okay that's fine i'll just expand this volume and start copying things let's just do that and uh let's see about getting into startup disk i'm doing something there okay let's see what we've got there yeah there you go and so more cash that's just the cash stuff though that's there actually that's much going on there now it definitely doesn't require sealed volume because i've done this before without a sealed volume unless that has changed only the kernel should care about that might just be some other file that i don't know about um so let's do a resize uh should be linux two this one disc two and then i need to pass it new size let's give it 10 gigs actually let's just do it 20 gigs and um and we don't need any of this that's the data volume much stuff is in system actually let's do it from here hmm pretty sure we don't need anything but system library okay just right let's copy everything unless the compression is going to screw me over here we'll see alternatively i do it a different way and start deleting things from the links partition and see within breaks i'll have to unseal the volume though which will break that macos install from booting but it shouldn't actually make it stop working though maybe it was the kernel collections that i wanted i don't know that shouldn't be the one that matters though pretty sure private framework is in it other copies i'm gonna go do a thing i guess that's finished now uh oh and yeah also it is uh probably compressed i'm gonna give it 30 gigs at least i used rsync and now it's going to take a while to do the stupid checks because i just copied crap in there okay let's sync everything again sorry for the delay uh let's see uh will that make it show up oh now it's definitely cached so what about blessing that again oh what oh it is pretty full i guess the compression really matters huh i probably should update this mac os version anyway because uh this is an older version than the one i'm trying to copy which is a bit silly recovery definitely shouldn't matter for bootability anyway so let's just look at pre-boots wait is this actually paired shouldn't that be a holding group did that create thing not work uh linux two oh no i just it just shows up like this maybe that uh what i think i was supposed to show it differently [Music] um yeah okay anyway this disc two s4 yeah looking group c6 a4 or whatever yeah that's this volume groups does show this as theta [Music] um yeah they copy everything here tonight and delete some of the efi stuff but that shouldn't be it uh yeah i might need the user and stuff next actually that could be this one or yeah volume snakes all the three letter things oh hold on that's not where i want to put them just here and there's anything in private that's important might be that too and otherwise i think uh something in library no let's just copy that okay there was something there probably user and now we know i don't need to reboot to make this work uh so what was that ah let's do the right thing okay okay i thought so that's none of those are it i'm pretty sure user is part of it yep okay uh pretty sure it's not going to be x or bin or libec sec or local or s bin i'm pretty sure i can get rid of those probably one of the lib things uh standalone is gonna have a bunch of stuff that matters but i don't think this rumor stuff unless it's that boot cache standalone uh let's see if it's standalone and i wonder if i can actually get rid of the system volume and just have it work with the data volume worth checking later maybe okay standalone matters uh i should just use the freaking hotkeys shouldn't i um what's in here said boot caches uh oh this stuff might matter yeah well if i might matter yeah update probably doesn't update firmware we had we fight before though didn't we yeah no that's fine um what about this thing hopefully not i think it's just boot efi in this case oh or not okay so firmware matters uh was it because there was uh huh really just the boot catches aha so that file matters and i'm pretty sure boot efi matters here but not nothing else yeah okay so it was that boot cactus thing probably i'm pretty sure share doesn't matter yep so it's basically boot caches that appeals that we're missing that is interesting because i would not expect that to matter in fact it might not even have mattered in the past but uh i will see there's this required path stuff interesting oh yeah and the parrot recovery thing is new so maybe something else changed here i represent yeah this might matter too well that's just configuration though but this platform support might matter already caches and it might want the kernel cache well those are the boot objects anyway um uh it's because it wants this file to bless things is the issue in fact we might need to just put this stuff in here and then might just uh do the right thing and install everything for us which will make life easier so we probably want user stand on firmware for sure so let's put that back uh hopefully not update though no i think update stuff isn't here see can it even bless this stuff like with the uh boot info boot caches there's got to be some command that they used to do this anyway not mode for work to boot from file sit boot let's do a thing yeah bootability you do is that a thing that's interesting they have a some stuff here proper restore bless to clee it would be nice to know where that thing is i want to fight macos oh that's a different thing though yeah x86 is a apple silicon personalizes a thing would be nice to have us too but uh personalize is not a thing here where is it oh it's one of those undocumented options that's great mount mode okay so what if i do because this one you command that that will do a lot of fun things eventually is invalid cool um see this might do a lot of the work that i was planning to do by hand because i was not expecting apple to give us enough i was not counting on apple it was an ass command to do it um the given secure boot bundle is invalid probably because we're missing things here or because this bless is too old that could be also be it because this is a i think d trace this or something uh signed ap ticket so the signing server yeah okay probably because this is uh and what did this do did they just call a different stat what did this actually do because that's just kind of interesting actually actually do i even need this what did that do bless significa could not be found and there occurred that might be different though uh hold on this is secure boot bundle yeah we don't have these bundle files though do we oh is it a knife 386 uh but it's not there though unless it was this stuff i think it's actually difficult to the server though maybe it did no there's a network d thing going on there though it might just be because this is not being signed anymore i'm just getting the uh local stuff which is not what i want actually yeah this might be interesting command to look at later okay that that one does work and it does mess with volumes pre-boot but is that even the hold on yeah volume's free but is correct um anyway that should be fine and then systematical services platform support and system version so i'm pretty sure i can delete almost everything here let's see if that still works and then before i delete anything let's see if it actually boots well i need to uh change the startup disk first of course yeah he likes that so let's see what we have right now uh yeah obviously we don't need any of that junk but okay let's just leave that on there for now and i kind of want to stream this log because there might be some interesting things happening because i was going to try to personalize things to uh set that up ah yes i did expect some stuff like that to happen let's see what any errors have been there uh i probably do actually need to ruin in recovery mode to make this work anyway so that's nothing like exactly uh surprising or not if they're private yeah thank you users for mount point oh it wants a user database right um od database path oh this might be new actually um i know that one of the things that that uh it's supposed to do and this might help us do a clean linux install actually i think one of the things it's supposed to do is uh like import the like the user database right so now the question is can i like initialize a new open directory database or something because obviously i want to copy one but for now we can copy one though but uh so we can just do like volumes linux data uh private var db uh yes local oh what's that that might be convenient uh is that like an initialization thing does anyone know about this or is that just from an update it might just be for an update that would actually make sense that it's like yeah was that created july 15th that sounds like about when i upgraded mac os so that makes sense okay let's just uh copy that for now two volumes minutes two private various local i'm gonna need to create that first but oh is that literally just how it is is it literally just like aren't you lists what is that anyway okay so it's got some stuff but i should be able to just fake all of this in that case there's nothing interesting here it could just be an empty database or something yeah you'll name people whatever computers name uid gate are the passwords here by the way that's probably the thing for the sep and then does this actually have passwords in here uh come on dash help that's the password is that actually blank or is that just the is that just how it works here ah probably this one right there's a curb razor thin i'm not sure what that is actually there's account policy data also but anyway um now that i copied that let's see what happens aha yes that's fine um but i can authorize users which means it's gonna yeah this is actually kind of new i'm pretty sure this was broken in the past um and that's also why i need to copy this i definitely did not have to copy this last time i did this so this is important for us because it means that eventually we're going to want to actually have a linux user that is authorized for um like has the uh what's the name of that thing owner identity key so on this system yeah so this makes sense because in fact this might allow us to do a proper uh a proper install of everything yeah because if we do this and we have a user then we can create a password for it and then yeah the only issue is that uh no it should work from recovery mode yeah probably actually i'm not sure well let's do it manually for now because if this works i can uh then start working on a script to do this and then we could have our installer like prompt you for a password set the password on the volume properly and then that would uh allow you to do that but actually let's not do that for now okay it's rebooting booting is definitely not going to work because we don't have you know like a file system both you know it's not even in that's not a snapshot so i expect it to panic um but the important thing is that if i can get into the paired recovery if booting well first of all i need to find out if it created the um the boot policy properly um and now we're going to end up in the rescue mode probably directly yes and in this case okay it only likes those two which is fine uh and that one had this password i don't know what it's doing now i've got a mouse cursor though oh okay the reboot doing something okay what is it doing it's not rebooting though this one to the mouse okay black screen i don't know what it's doing is it like in a boot loop it might be though it's not showing uh oh okay something happened yes i know that um but that's expected so now the question is where are we first of all what recovery is this and i don't know how to find that out actually uh but let's see what uh bp utils exist aha we have a new boot policy so that's good that got created and was it b7 8 was the one we wanted i think um was there a way of finding out hold on let's [Music] list info disk um 3s1 oh c6a sorry number two yeah so obviously every other security is enabled um and like nothing's gonna work in this state but the next stage image four has all that is there and now the question is can i actually i don't know what the start of this point is actually um can i find out via nvram uh print offer more variables i think this is volume there we go voluminous ef something for something c6a ef ef408 c6af is that correct yeah four is that where it was yeah so that looks like it's correct so in that case uh this is not gonna work with bputil but kc a dash n i want the password for mark i guess so let's try giving it the password that was one thing that's one question that i had is whether i can use another volume so let's try the um no okay okay that one worked which is the password actually for okay fail to create no yes ap boom okay i thought that this makes that's what i expected so i need to shut down and actually do um and actually go to one tr i need to hold down the power button if you don't do that it doesn't work but that's okay so the important part is that now when i go to options here this recovery has to be the paired recovery for this os and in fact the question is what uh actually i'm going to know if this is a recurring or not from monterey beta yeah okay so this is definitely the right recovery because it's talking about monterey so the recovery thing worked we are booting into the recovery of uh the new thing so now this should work uh one tr used to be uh a separate partition but now they change this in monterrey and now one tr is whatever paired recovery is um being used by the os i think well actually this this system recovery would also be monterey in this case i think so i'm not even sure which one is booted but it should be the one for this os i think i don't know how to find that out uh like because mount won't tell me what's yeah it won't it won't tell me oh but look system volumes data private temp recovery is from the linux 2 volume set so that's promising that does suggest that it is actually the right volume so there you go i think that actually did work so two uh it wants which one now the username password story is going to be a whole different question and eventually i'm probably going to want to like completely wipe this mac and do it from scratch install and make sure everything works okay so this should downgrade security and then we can install mini which means i'm going to have to put my web server thing in here uh i get many builds yes fus is fully untrusted os that is taking longer than usual okay there we go i don't think i care about crs at this point uh because uh it's you know we're not even booting macos at this point so then um i don't know why it's that slow i remember that like last time also it took a while to get that okay me tell me if you could vote i think you need that one and then many actually that was the path arguments i know it's on the wiki but uh let's see yes uh so here's another question this one prompts me for the username if i give it mark well this the issue that uses the username for everything um let me try the password for the other account no hold on yes no try the old password for that no okay so it does one see i don't know why because did it actually import it might have actually imported this user from the volume but then i don't know it's a bit confusing uh and eventually i'm gonna have to figure this out by just wiping the whole machine and trying again it's with like possibly different usernames and different passwords just to make sure that everything makes sense okay and then just restart to do it and there you go so as far as setting up the partitions and files this works the next part would be getting those files not from an existing os but from the uh install thing um but it's 9 30 here and i should think about getting some uh some dinner but this was good it also means that nothing is horribly broken in monterey and uh initial should do the right thing but just to give you an overview of what's going to go on here um basically those p-lists and stuff can be created or copied from the ipsw and then the other stuff the image four files with the firmware those can be created with image for tool from stuff in the ipsw so in principle all of that should be should be doable and i'm going to leave that for uh next time but uh yeah cool so manual install works all right see you all later you

Channel: marcan

Views: 1,636

Keywords:

Id: uqPLyBS20PA

Length: 128min 43sec (7723 seconds)

Published: Wed Aug 04 2021