makefu changed the topic of #nixos-wiki to: Welcome to the *unofficial* nixos wiki | https://nixos.wiki | chat logs: https://logs.nix.samueldr.com/nixos-wiki/
nixoswikibot has quit [Remote host closed the connection]
nixoswikibot has joined #nixos-wiki
<nixoswikibot> [[How to fetch Nixpkgs with an empty NIX PATH]] ! https://nixos.wiki/index.php?diff=5120&oldid=2873&rcid=5276 * Gabriel439 * (-2339) Simplify the instructions to just Nix 2 now that Nix 1 is fairly old now.
kalbasit has quit [Ping timeout: 240 seconds]
<nixoswikibot> [[Special:Log/newusers]] create  * Faré * New user account
orivej has joined #nixos-wiki
growpotkin has quit [Quit: ZNC 1.8.2 - https://znc.in]
growpotkin has joined #nixos-wiki
orivej has quit [Ping timeout: 256 seconds]
growpotkin has quit [Quit: ZNC 1.8.2 - https://znc.in]
nixoswikibot has quit [Remote host closed the connection]
nixoswikibot has joined #nixos-wiki
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-wiki
orivej has joined #nixos-wiki
nixoswikibot has quit [Remote host closed the connection]
nixoswikibot has joined #nixos-wiki
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-wiki
growpotkin has joined #nixos-wiki
kalbasit has joined #nixos-wiki
<nixoswikibot> [[NixOS on ARM/PINE64 ROCKPro64]] https://nixos.wiki/index.php?diff=5121&oldid=3670&rcid=5278 * Mic92 * (+177) Mention nixos-aarch64-images
<nixoswikibot> [[NixOS on ARM/Libre Computer ROC-RK3399-PC]] https://nixos.wiki/index.php?diff=5122&oldid=4033&rcid=5279 * Mic92 * (+228) /* Installation instructions */
<samueldr> ^ that board still has issues with mainline
<samueldr> so I don't think the image will work
<samueldr> (there is no vendor kernel either)
<samueldr> Mic92: you might be interested in what I tried to start doing in the wiki
<samueldr> For allwinner (at first) I created a template for the installation instructions {{ARM/installation allwinner|variant=aarch64}}
<samueldr> this also includes a generic template
<Mic92> samueldr: do you think we should have manual installation instruction than repos just like mine?
<samueldr> I think there should be a plurality of methods
<samueldr> with the main one being whatever comes from upstream Nixpkgs
<samueldr> not sure you see what I mean?
<Mic92> samueldr: I mean if we have an automatic method to provision images, do we still need manual dd instruction in every repo?
<Mic92> or could have have just an allwinner/rockchip section somewhere
<samueldr> I think every board page should be self-sufficient
<samueldr> it might be much to ask from the user to have them know about details like SoC families being the same
<samueldr> this is why I think templating such things can help
<Mic92> samueldr: they don't really need to if we have something like that: https://github.com/Mic92/nixos-aarch64-images#example
<samueldr> and there should always be a method that works from Nixpkgs / cache.nixos.org data only, without needing extra bits
<samueldr> yeah
<Mic92> samueldr: should I just start uploading those images somewhere?
<samueldr> that's your own opinion, but really it should somehow be done under the nixos.org umbrella
<samueldr> I mean, you do what you think is right
<samueldr> but I wouldn't recommend starting from binary artifacts from third parties, even trusted one
<samueldr> I want to break the cycle so commonly seen in SBCs
<samueldr> "just download that spooky image that a user has made"
<samueldr> Nix gives us that ability through the transparency of the derivations
<samueldr> so your project is so close to being perfect for that
* samueldr opened the page
<samueldr> roc-pc-rk3399 and pinebook pro won't work
<Mic92> samueldr: well. I would do it in CI, so someone could clone and reproduce the image themself.
<samueldr> because of the kernel
<Mic92> yeah, for those dd also would not work.
<samueldr> when using the mainline-built image
<Mic92> It's just sometimes having too much choice makes it hard for new users.
<samueldr> I know
<samueldr> I really think that until something done under the nixos.org umbreall is done, it should be another option
<samueldr> umbrella*
* samueldr sighs
<samueldr> I'd really like to have more time to dedicate to that
<samueldr> in the past few months it's been basically none
<samueldr> without testing, looks good
<samueldr> though obviously only works as long as it's the last partition
<Mic92> samueldr: what happens if it is not the last?
<samueldr> I don't lnow
<Mic92> I think it also should work in that case
<samueldr> probably a no-op
<samueldr> "work" being that it won't break horribly
<Mic92> it takes the minor number of the root partition.
<samueldr> I meant generally, not the method
<samueldr> if the image was somehow built with a partition after that partition, it won't be able to expand
<samueldr> but that's normal
<Mic92> ah
<Mic92> But this is how we likely built our installer images
<samueldr> yes
<samueldr> not a problem
<samueldr> just stating a fact
<samueldr> which, really, isn't really an issue in your change
<samueldr> your change is goo
<samueldr> good*
<samueldr> (assuming it works)
{\_\} has quit [Remote host closed the connection]
orivej has quit [Ping timeout: 264 seconds]
<Mic92> Got that
<Mic92> samueldr: does the image leaves space for the bootloader here? https://nixos.wiki/wiki/NixOS_on_ARM/PINE_A64-LTS
<Mic92> at which offset does it start? Is this still the boot sector?
<samueldr> what do you mean?
<samueldr> ah
<samueldr> I think I see
<samueldr> [MBR][ empty region ][ raspbery pi boot partition ][ actual rootfs // ]
<samueldr> the empty region was designed for allwinner boards
<samueldr> it hasn't changed since the time dezgeg added that
<Mic92> ok
<samueldr> u-boot for allwinner is really small, and totally fits in the "way-too-big" empty region
{\_\} has joined #nixos-wiki
kalbasit has quit [Remote host closed the connection]
kalbasit has joined #nixos-wiki
lassulus has quit [Remote host closed the connection]
lassulus has joined #nixos-wiki
zimbatm has quit [Ping timeout: 272 seconds]