<MichaelEden[m]>
how is NixOS on the PineBook Pro? I just ordered oen
vika_nezrimaya has quit [Ping timeout: 276 seconds]
<samueldr>
unknown!
<samueldr>
considering none have shipped yet
<samueldr>
though the first part of the first batch is expected to ship this week
<samueldr>
heh :)
<MichaelEden[m]>
oh oops, I thought some had gone out already
<MichaelEden[m]>
I'm sure it'll be fine!
<samueldr>
there are two main bits that it will all hinge on
<samueldr>
1) the u-boot fork's state
<samueldr>
2) upstream kernel state
<samueldr>
I think it's likely to be fine from what it looked like at first
<samueldr>
the u-boot is stored on SPI flash, and IIRC it's known to be a u-boot with EFI support
<MichaelEden[m]>
yeah, I think the RK3399 is already somewhat upstreamed in kernel
<samueldr>
yeah, and getting better
<Ashy>
it wasnt completely smooth sailing on my rockpro64 a few months back when i was last testing it
<Ashy>
ayufan's kernel patches weren't yet mainlined so i had to use his uboot/kernel to boot the nixos partition
<Ashy>
which sounds even messier than i remember it, should have done a wiki post at the time :/
<samueldr>
yeah, that's why I'm not 100% confident, but only "likely" fine
<samueldr>
it's almost 100% sure all the pieces will be there
<samueldr>
it's more about how much of it is left not upstreamed
<samueldr>
meanwhile, compared to some other rk3399 boards, where there's still nothing really :/
<Ashy>
that was with emmc rather than sdcard though, i've got a spare sdcard now and the latest kernel has marched on since then, i'll have to try again this weekend
<Ashy>
panfrost has also marched on a lot since then
<samueldr>
Thra11 and lopsided98 have been contributing to the page :)
<samueldr>
only missing your additions :)
<samueldr>
and ;)
<Ashy>
yeah hehe, that page is also full of fairly high level hints about what to do
<Ashy>
rather than a ready to go bash snippet to fill an sdcard/emmc with a bootable nixos config for it
<samueldr>
and a good thing for the pinebook pro is that it, in most ways, build upon their existing knowledge of the rk3399
<Ashy>
i'll block some time out saturday to have a play again and see if i can expand that wiki page with some simple steps
<Ashy>
it's a sweet board otherwise
<Ashy>
especially with the m.2 adaptor
ris has quit [Ping timeout: 276 seconds]
<t184256>
DigitalKiwi: no, I have no idea why are looking in that place, actually. The location is /data/data/com.termux.nix/files/, and if you want to put something on external storage, you need to 1) grant permissions for storage in the app info 2) manually put something to /sdcard/
<t184256>
*you are
<Ashy>
there's a script on the real termux: termux-setup-storage
<Ashy>
not sure if that's in the termux nix fork
<DigitalKiwi>
i went to the settings -> app -> permissions -> grand storage yeah
<t184256>
That's everything that this script does, displays a pop-up for that one
<t184256>
My fork doesn't have it, or any of the helpers. Or any ability to call into any outside code, basically =( something that I haven't figured out yet
<DigitalKiwi>
can it run systemd stuff
<t184256>
theoretically at best. need to look how it is handled in more classic single user installs
* DigitalKiwi
wants to run syncthing :(
<t184256>
DigitalKiwi: ummm, there's a cool easy way to do that, and it's called Syncthing-Android =) with nice GUI and battery/data saving policies
<t184256>
Not sure what you would gain by running the nix version, but you'll lose aplenty
<DigitalKiwi>
yeah but the files i want to sync are in the com.termux.nix/files/ which afaik doesn't actually exist
<DigitalKiwi>
(that answers your question about why i was looking for them)
<t184256>
Move them to sdcard and symlink them from /data/data/com.termux.nix/files? That's what I do.
<{^_^}>
t184256/nix-on-droid-bootstrap#10 (by Gerschtli, 2 weeks ago, open): Remove hardcoded paths in .login-inner and fixed links in /bin/sh and /usr/bin/env
<t184256>
My approach is to regularly back up stuff and just wipe the app data (because I have to do it anyway to test new builds as I don't have dedicated hardware for that)
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-aarch64
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 268 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 268 seconds]
zupo has joined #nixos-aarch64
<DigitalKiwi>
t184256: ha! i got it
<t184256>
DigitalKiwi: got what?
<DigitalKiwi>
ssh in and have it setup a bash environment
<t184256>
How do you run sshd, do you invoke it directly?
<t184256>
Yeah. A lot of system-management stuff is not expected to work
<t184256>
Well, great to know! Also, enable a wake lock so that it doesn't get frozen mid-connection
<DigitalKiwi>
oh and i did the authorized_keys as standard
<DigitalKiwi>
PermitRootLogin prohibit-password
<DigitalKiwi>
PasswordAuthentication no
<DigitalKiwi>
and a Port
<DigitalKiwi>
and you have to do ssh-keygen -A at some point before sshd will work
<t184256>
Yeah, a key is a must because there ain't much to authenticate you against without it =D
<DigitalKiwi>
indeed
<t184256>
But what are the other options for? Are they necessary?
<DigitalKiwi>
the permitrootlogin one?
<DigitalKiwi>
probably not i guess if you have passwordauthentication no i'd think...
<t184256>
Yeah.
<DigitalKiwi>
cargo culted it :P
<t184256>
OK, Port is needed to take a non-privileged one, got it
<DigitalKiwi>
i modified the one from a standard Termux
<DigitalKiwi>
hmm and there may be adb commands you need to run i'm not sure...i'll find out sometime and report back
<DigitalKiwi>
has been a long day
<t184256>
I doubt that
<t184256>
Like, what for?
<DigitalKiwi>
oh, i know
<DigitalKiwi>
it was for ssh over usb
<t184256>
Uh
<t184256>
Quite a twisted setup you've got there =)
<t184256>
Congrats
<DigitalKiwi>
no no that was a separate thing
<DigitalKiwi>
other than having to launch sshd with the full path it's pretty normal
<DigitalKiwi>
though my bashrc doesn't work as well for some reason
<DigitalKiwi>
the colors are wrong?
<t184256>
IDK, is it the same in termux?
<DigitalKiwi>
i don't think i tried
<DigitalKiwi>
it'd help if i set the color
<t184256>
DigitalKiwi: could you please summarize your findings somewhere, for example, in a github wiki page? I'd love to follow your steps one day, but through nix
<DigitalKiwi>
at one point i remember (on the first one) it was removing a [ in my prompt