<infinisil>
Heh, well the livestream I'll let go. But the first one really is a bit long
jasongrossman has joined #nixos-chat
Peetz0r has quit [Ping timeout: 252 seconds]
<colemickens>
random question but does anyone know of a good "app" that does a shared todo list, with recurring reminders and a "calendar" view that shows recurring tasks like GCalendar does?
<jackdk>
org-mode + git?
<colemickens>
It has to be 500% painless, sharing with non-techy family members and need something that can be instantaneous in terms of nag/dismissal.
<samueldr>
it was 10 minutes, then 15 for a short while
<samueldr>
yes, that was just a bit over EIGHT years ago
<jasongrossman>
night gchristensen
<infinisil>
samueldr: Haha whoops, reason I said 15 was because I just read this a couple minutes ago in a reddit post, I guess that wasn't a very reliable source of information
<samueldr>
:) though now you have dates!
<samueldr>
I seem to remember a time where the time limit was enforced through file size
<samueldr>
so you had harsh compressed videos for 10 hours
<infinisil>
:o
lassulus_ has joined #nixos-chat
lassulus has quit [Ping timeout: 268 seconds]
lassulus_ is now known as lassulus
Peetz0r has joined #nixos-chat
Peetz0r has quit [Read error: Connection reset by peer]
Peetz0r has joined #nixos-chat
pie__ has joined #nixos-chat
pie_ has quit [Ping timeout: 245 seconds]
jasongrossman has quit [Ping timeout: 246 seconds]
endformationage has quit [Ping timeout: 250 seconds]
<infinisil>
srhb: That makes me think, isn't all music today saved with 24 bits?
Synthetica has quit [Quit: Connection closed for inactivity]
Jackneilll has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
* samueldr
is still sour apple removed their manpage from the web
<elvishjerricco>
implicitly performed in a transaction.
<elvishjerricco>
I really wish unix-like systems had a concept of file system transactions. I want a file API where all the operations take a transaction id, none of the changes take until a commit operation is called, and committing guarantees that all the operations have synced to disk. It'd be especially nice if you could sandbox an entire process in a transaction; i.e. all of the file IO by that process and its children are
<gchristensen>
"sour apple" :D
<samueldr>
pun wasn't intended
<gchristensen>
elvishjerricco: most filesystems can't hold up their end of the bargain for twhat
<samueldr>
this makes it infinitely harder to gauge cross-platform compatibility of invocations :(
<elvishjerricco>
gchristensen: What do you mean by that?
<gchristensen>
many filesystems don't have atomic writes
<gchristensen>
samueldr: what do you want manpages for? maybe I could get them for you
<samueldr>
I think I got what I wanted, but ss64.com doesn't tell from which version their manpage are made from
Synthetica has joined #nixos-chat
<elvishjerricco>
gchristensen: I wonder if a feature like this could be added to ZFS though.
iqubic has joined #nixos-chat
<joepie91>
elvishjerricco: you could proooooobably hack something like that together using an overlayfs?
<elvishjerricco>
joepie91: I dunno. Doing the actual sync from the overlay back to the real location needs to be atomic somehow
<joepie91>
have each transaction/process invocation correspond to an overlayfs that maintains the writes, then eventually reconcile the writes to the underlying FS after commit
<joepie91>
hm, right
<joepie91>
don't know much about overlayfs, but maybe a Nix-esque approach?
<joepie91>
just updating the pointer to point at a new overlayfs
<joepie91>
as the 'main fs'
<joepie91>
no idea what kind of performance implications a stack of overlayfses might have though
<elvishjerricco>
joepie91: The other problem with that is that other processes will see the in-progress changes.
<joepie91>
not if they are running on a different overlayfs?
<elvishjerricco>
joepie91: Are you suggesting they be in different mount namespaces?
<joepie91>
elvishjerricco: I don't actually know much about overlayfs, so I can't answer that question with certainty :P but afaik overlayfs does pretty much what the name implies, ie. producing a filesystem layered on top of another one, where changes in the overlayfs *don't* modify the underlying filesystem... which means that if you use a particular overlay *only* for a specific process, then other processes won't see its in-progress changes because they'
<joepie91>
re not using that process-specific overlayfs, they only see the underlying filesystem (or maybe a different overlayfs specific to *their* process)
<matthewbauer>
samueldr: we've been slowly trying to get these manpages into nixpkgs.darwin
<matthewbauer>
if it's in hydra just use:
<matthewbauer>
MANPATH=$(nix-build -A darwin.file_cmds '<nixpkgs>' --argstr system x86_64-darwin)/share/man man dd
<matthewbauer>
I guess you have to know which package the man page is part of though
<samueldr>
those map to the OSS release from apple only I guess
<elvishjerricco>
joepie91: Right, but that overlayfs has to be mounted. So if it's mounted at /foo/bar so that I can make a process atomic on /foo/bar files, then other processes will see the in progress changes in /foo/bar, which you'd want to avoid
<samueldr>
(sorry if I sounded a bit stiff in the comment, today's not a great day)
<elvishjerricco>
So it'd need to be in its own mount namespace so that other processes don't see those files
<matthewbauer>
samueldr: yes, so it doesn't really tell you which macOS version which could be useful
<samueldr>
and won't find the other man pages, which apple's repository was good for :(
<joepie91>
elvishjerricco: ah, in that sense, then yeah
<samueldr>
e.g. xcodebuild or other silly apple-specific tools
<samueldr>
I guess one could (ab)use nix-index to index the manpages for the darwin channels...
<samueldr>
(like the prototype impl. I made for nixos/linux)
<mdash>
elvishjerricco: sharing filesystems between processes was probably a mistake
<elvishjerricco>
Yea...
<gchristensen>
all the CPU and RAM bugs have been indicating sharing anything is a mistake
<elvishjerricco>
That's it. I'm buying a new computer for every process I need to start :P
<joepie91>
elvishjerricco: raspberry pis?
<joepie91>
:P
<joepie91>
you could actually probably do this with rpis...
<elvishjerricco>
lol yea
<samueldr>
power fluctuation and EMF might be good side channels
<Synthetica>
samueldr: Ehm, all in faraday cages and on batteries?
<gchristensen>
once you're in that deep of a problem, I recommend solving it with data lakes.
<gchristensen>
wherein you throw your data (and computer) in the lake
<Synthetica>
And go live next to said lake?
<Synthetica>
Without electricity and the like, and your problems go away
<gchristensen>
that part is left as an exercise to the reader
<gchristensen>
ldlework: I'm being chainsed by my nixos challenge today. I had some, apparently, important project files on my previous laptop install and now I don't have them and can't get them, since they're on a non-internet-connected backup server!
mbauer has joined #nixos-chat
<andi->
It is amazing.. I met two random strangers that are visiting the hackerspace for the first time... Both of the recently switched to NixOS. <3
mjbauer has joined #nixos-chat
matthewbauer has quit [Ping timeout: 250 seconds]
mbauer has quit [Ping timeout: 245 seconds]
mjbauer has quit [Client Quit]
mjbauer has joined #nixos-chat
<joepie91>
andi-: how many of them made the switch at CCC? :P
<andi->
joepie91: probably not many..
<andi->
joepie91: well one of them was there..
<joepie91>
now I want to know if it was because of the install party, or unrelated :D
<andi->
That person alreayd left.. I'll make sure to ask next time I see him.
mjbauer has quit [Ping timeout: 240 seconds]
<joepie91>
:)
Synthetica has quit [Quit: Connection closed for inactivity]
Soo_Slow has joined #nixos-chat
Soo_Slow has left #nixos-chat [#nixos-chat]
__monty__ has quit [Quit: leaving]
<gchristensen>
I would like to tail -f a whole bunch of files, but with a more screen-like interface where I can swap between which one I'm looking at. any ideas?
<ldlework>
tmux?
<ldlework>
:)
<gchristensen>
I don't want to open a "pane" per file and execute tail -f manually