<ng0>what we can do is where discussion was picked up again, things like hardening etc.. it does not fix all the problems in the world, but the right techniques will prevent a good amount of exploits
<brendyn>mark_weaver: I want to build a libre distro for schools, I suppose that can be done with any other distro but when I look at Trisquel I just see an impoverished Ubuntu. Guix is foremost libre, so it has that momentum. Guix system definitions seem to facilitate easily making preconfigured .iso files for a variety of purposes. I'd like to create a system definition that give students network logins with their
<brendyn>guix profile so they can install whatever they want but there would be no pressure on the school admin to update the root instance
<brendyn>Also, another experiment is to setup configurations with xorg_multiseat or whatever wayland equivalent so that single computers can be setup in computer labs with multiple monitors, keyboards and mice
<ng0>that's cool :) I'm trying to do something similar, though with a different purpose, the live-system is the same.
<brendyn>I have lots of ambitions but other people usually don't care so I don't know if these are good ideas
<brendyn>Current Edu- distros seem to just be Ubuntu+ random "educational" software
<lfam>brendyn: I think that a declarative system like GuixSD is a great improvement over traditional imperative systems for mass deployment
<lfam>It should reduce the workload of the administrator
<ng0>that was one reason why I picked GuixSD and NixOS for the live-system we create
<brendyn>Yeah. Ultimately I dream of convincing schools to switch entirely such that we (Australia) would create end up maintaining our own base system definition for schools that could then be setup and customised freely, but people think it is foolish to think we could ever get rid of Windows
<brendyn>Anyway, 1.0 is still a fair way off I suppose, so I intend to spend that time learning to program more
<lfam>brendyn: It's not foolish. It will be hard but it can happen.
<brendyn>lfam: Yeah, I just can't convince people by pointing out "obvious" ethical reasons, because people rationalise the status quo. Probably using the Indian schools example would be good.
<lfam>brendyn: It's worth it to spend a lot of time learning how people are persuaded, in general. I think that ethical arguments are ultimately not that powerful.
<ng0>brendyn: I am preparing packaging for SecuShare, which is still taking time for any public release candidate, and I only pick NixOS in addition to GuixSD because one option should be a live-system people can boot into a ready-to-use program on all possible platforms
<brendyn>lfam: I have read a fair bit on pyschology. I think theoretically we can design presentations better than RMS can.
<brendyn>I don't care much for spending time hating on people, but I think showing people ways they've been screwed over my M$ might be effective. People have alot of trouble understanding the being able to edit code benefits them, but I think everyone has benefited from the creation of Firefox, else the web would be ruined by now
<ng0>not to play devils advocate... but the web is ruined :) it wasn't firefox' fault though
<brendyn>Hmm, do you have any ideas for community development? I was thinking eventually we could have a sort of Planet Guix where we create and share all sorts of system definitions for fun, like we Could create a boot-to-emacs/spacemacs setup up for instantly getting started hacking on Guix
<brendyn>Ok. I didn't realise these were files that were meant to even be in the repo, just like other outputs of make
<mark_weaver>the .po files contain the translated strings. they are not merely auto-generated, although I guess 'gettext' includes tools for automatically adding new skeleton translation entries as needed, by scanning the source code for new messages.
<brendyn>I'm currently looking through Spacemacs code trying to figure out if it's easier to use Spacemacs since it fixes a few Emacs problems or use Emacs because Spacemacs breaks a few things that work fine in Emacs
<ng0>I'm just picking many things because I want to learn more.
<paroneayea>kalashkash: maybe will do closer to what you want
<kalashkash>for example, in TTY to login as root, and excecute 'echo $PATH' I get "/root/.guix-profile/bin:/run/setuid-programs:/run/current-system/profile/bin:/run/current-system/profile/sbin" but with su command, when I excecute "echo $PATH" I get "/sbin:/bin:/usr/sbin:/usr/bin"
<kalashkash>then in TTY as root I can excecute the "ls" command, but in a graphical terminal, to login as root with su command i can't excecute "ls"
<ng0>I would even use gogs when I could disable web-view for some repositories entirely. The work I mirror to notabug, gitlab, github, etc is okay to be indexed, the rest at least 1 person disagreed on public git index
<mark_weaver>jmd: I think it's safe to say that #guile has a good reputation for being friendly to questions. however, you have a history of asking lots of questions that can be very easily found in the manual, e.g. asking what procedure 'foo' does, when it's right in the index of our manual.
<jmd>I will resist the temptation to bite at that.
<mark_weaver>it's totally unfair to characterize this complaint as "the devs there have made it quite clear, that user questions are not welcome."
<jmd>Well I think both your last statements are "totally unfair" too.
<mark_weaver>okay, let's start with my last statement. please provide quotes to back up your claim that "the devs there have made it quite clear, that user questions are not welcome."
<lfam>There's a balance to be struck between answering user questions directly, so the user can keep doing what they are doing, and encouraging users to look for answers themselves in the manual, which is better for everyone in the long run.
<davexunit>user questions are certainly welcome in #guile. many people, myself included, ask many questions there.
<lfam>I often wonder when to tell new users "Okay, it's time to start looking in the manual :)"
<davexunit>yeah, at what point do you "teach a man to fish"?
<lfam>Whenever you do it, it's important to communicate that you are trying to help them, in a round-about way, by no
<mark_weaver>anyway, the reason guile says "possibly" is because top-level variables are mutable, and so the compiler can only make an educated guess about what procedure will be bound to 'pointer->procedure' when the relevant code in syscalls.scm is actually run.
<lfam>The build of slock with the patch does succeed
<lfam>Well, never mind. It's not caused by my patch. I have the same issue without the patch.
<jmd>At the risk of asking something else that might or might not be explained in the manual: I'm getting the error "guix system: error: mkdir: File exists" - now the function mkdir-p (YES I HAVE CHECKED THE MANUAL) does not specify what happens if the target already exists, but the "mkdir -p" command should not complain.