Re: Guix pronunciation
On Sun, Mar 10, 2019 at 12:13:55PM -0400, mikadoZero wrote: > I think the confusion around the pronunciation of GIF would probably be > a worst case scenario. Non-techies rarely discuss JPEGs or PNGs, while GIFs are a cultural phenomenon. How to pronounce 'GIF'? Anyone can weigh in, and it doesn't require any technical knowledge. After 30 years, GIF has come to mean 'a brief moving image on a computer'. It's a tremendous success! A harmless controversy can be endearing :) I can't think of a single downside for GIF. On the other hand, I think the most important property of a name is that it does not change. Google indexes written words, not pronunciation. A long tail of articles and discussion of Guix is extremely valuable. signature.asc Description: PGP signature
Re: Guix trademarked by Express Logic
On Mon, Mar 11, 2019 at 08:31:40PM -0400, mikadoZero wrote: > Reading the recent press release linked it is clear that Express Logic > is continuing to invest more in their Guix trademarked product over > time. As a result of this it is increasing likely that Express Logic > could request that the Guix free software project stop using it's > trademark. Correspondingly it looks less likely that it will just go > away. We will cross this bridge when we come to it. signature.asc Description: PGP signature
Re: Express Logic claims GUIX trademark
On Mon, Mar 11, 2019 at 08:00:16PM +0100, Tobias Geerinckx-Rice wrote: > It's 4 months old. > > Meanwhile, we have: > > commit 207cba8114d354737b231e510d6110ea2a42e07b > Author: Ludovic Courtès > Date: Wed Apr 18 23:21:11 2012 +0200 > >Initial commit. > > Do 6+ years of prior public use trump registration? Not necessarily, but > it's a far cry from what the Jade-lang folks did. Sounds like we should bring up this with the FSF and see what they say. Pj.
Re: CDN Test Results - Should We Continue Using a CDN?
Hi Maxim and others, Maxim Cournoyer writes: > Chris Marusich writes: > >> [...] Starting on February 23rd, 2019 we conducted a test using >> Amazon CloudFront. [...] The test concluded on March 23rd [...]. > > I'm I living in the past, or did you mean another date than March 23rd? > :-) No, you're right: I mixed up my months. The test actually began on January 23rd, 2019, and concluded on February 23rd (31 days total). By the way, I've double checked the other statistics. They're all accurate except for the test duration, which was actually 31 days. I just mixed up the months in my head. Sorry for the confusion! -- Chris signature.asc Description: PGP signature
Re: Missed testing
jerem...@pdp10.guru writes: > For example if one were to go to the guixsd website and download the > current release, verify that it was correct, burn onto a DVD and attempt > to install with guix system init /etc/configuration/desktop.scm /mnt > --fallback results in the following error: > > /gnu/store/729zbb84cah3wf2fcsy4h17lqxxib5q-configuration-templates/desktop.scm:23:9: > error: you may need these modules in the initrd for /dev/sda1: mptspi This depends on your hardware and the modules that the kernel loaded in response upon booting. There is no way to have a static resource as the example configuration reflect the modules that can be automatically loaded by the kernel on all hardware configurations out there. -- Ricardo
boot multiple Gnu/Linux Distributions from one USB key
Hello,
I configured a usb stick to boot multiple Gnu/Linux Distributions by
following this tutorial:
https://community.linuxmint.com/tutorial/view/1846
It works for Tails, PureOS, Trisquel and Parabola
I am trying to add GuixSD.
For the menuentry, I always start from the grub.cfg embedded in the iso
file.
I add or remove options if needed.
For GuixSD, I came up with this configuration:
I used label instead of uuid.
## GUIXSD
menuentry "GUIXSD - Gnu/Linux" {
set isofile="/boot-isos/guixsd-install-0.16.0.x86_64-linux.iso"
loopback loop (hd0,1)$isofile
search --label --set GUIXSD_IMAGE
linux
(loop)/gnu/store/0zajbn9q39yva4l0zzrcshlll8qikzba-linux-libre-4.19.6/bzImage9
--root=GUIXSD_IMAGE
--system=(loop)/gnu/store/l4hgd4l7acrqwi3imav9akcvv4sbj85j-system
--load=(loop)/gnu/store/l4hgd4l7acrqwi3imav9akcvv4sbj85j-system/boot
initrd
(loop)/gnu/store/9nqaksx40zh5d6cg5rim3f3spy56bfb9-raw-initrd/initrd.cpio.gz
}
It doesn't work. I get the following error message:
waiting for partition 'GUIXSD_IMAGE' to appear...
Any help is welcome.
Is there any other way to configure multiple Gnu/Linux distros to boot
from one usb?
gnuforever
Re: CDN Test Results - Should We Continue Using a CDN?
Hello Chris! Chris Marusich writes: > Hi Guix! > > Recently, the Guix project experimented with using a CDN to improve > substitute availability and performance. This email summarizes the > results of the test for your review. I also hope this email will start > a discussion about whether or not we should continue to use a CDN. > > First, I'll summarize what we did. Starting on February 23rd, 2019 we > conducted a test using Amazon CloudFront. We configured ci.guix.info so > that all requests for substitutes via that domain name would go through > an Amazon CloudFront distribution that we set up for this purpose. The > test concluded on March 23rd, and the CDN is not currently being used. I'm I living in the past, or did you mean another date than March 23rd? :-) > Amazon CloudFront provides us with billing information and aggregate > usage statistics. Here's the information for the duration of the test: > > Duration: 28 days (February 23rd - March 23rd) > Expense: 156.88 US Dollars > Requests received: 3,732,919 > Average request size: 490 KB > Bytes transferred: 1,744.5724 GB > Bytes from misses: 684.3992 GB > Hits: 2.14 M (57.44%) > Misses: 0.99 M (26.41%) > Errors: 602.91 K (16.15%) > 2xx: 2,983.24 K (79.92%) > 3xx: 146.753 K (3.93%) > 4xx: 593.159 K (15.89%) > 5xx: 9.471 K (0.25%) > [...] > Location Request Count Request % Bytes > - > United States933,44825.01% 562.52 GB > Germany 687,54818.42% 174.53 GB > France 341,5739.15% 167.36 GB > Canada 179,6304.81% 96.31 GB [...] > Since the test has concluded, we are not currently using a CDN. Going > forward, we need to decide if we want to continue to use a CDN. Did you > notice an improvement in download speed or substitute availability > during the test period? Do you have metrics of your own that you can > share with us? If so, please share the information so we can understand > whether it's worth continuing to pay for a CDN. I haven't noticed a big difference on ci.guix.info; but then my WiFi link seems to saturate around 1 MiB or so at home, so I'm not a very demanding user ;-). Things felt as zippy as usual. > One of the reasons why we wanted to use a CDN in the first place was to > free up resources so that the community could spend more time working on > better solutions. Pardon me for asking, but how does using a CDN frees up resources? Aren't the usual infrastructure preserved (e.g., ci.guix.info)? It seems it'd be an extra layer to maintain? The heaviest bandwith usage appear to originate from areas already well served by the current infrastructure (mirror.hydra.gnu.org -> North America, ci.guix.info -> Europe), so I'm not sure spending resources on a CDN is worthwhile in this context. I'd rather see this (even modest) amount put into the hands of a motivated hacker to work on a distributed solution instead of encouraging a company which do not share our free software ideals. I'm hoping this doesn't come across as too negative! Thanks for sharing this interesting information with us. Maxim
Re: Guix trademarked by Express Logic
n...@n0.is writes: > The other Guix keeps coming up over the years. > I don't think we have to do anyting because it's 2 separate fields > of software. > No problem unless one of the Guix starts making it one. Reading the recent press release linked it is clear that Express Logic is continuing to invest more in their Guix trademarked product over time. As a result of this it is increasing likely that Express Logic could request that the Guix free software project stop using it's trademark. Correspondingly it looks less likely that it will just go away.
Re: Express Logic claims GUIX trademark
Guix, mikadoZero, I know you're not a fan of [the common pronunciation of] the name Guix, but going straight from my ironic quote of a shitty PDF to a public and ‘proactive name change’ proposal is at best premature. If it is the case that Guix the free software project does not have a trademark for Guix, then I would like to share what looks like a clear parallel. It involves another free software project that used to be called Jade. Jade did not have a trademark for Jade. A software company had the trademark for Jade. The company forced Jade to change it's name. Wow. That's super disingenuous (by ‘that’ I mean the original posts[0], which you accurately paraphrase). It certainly didn't leave me with the favourable impression of the Free software project that was probably intended. Yes, if you start a software repo in 2010 using the name that a software(!) company had registered in 2003 for their (you guessed it) software, you might be ‘forced’ to be just a bit more original. The heart truly weeps. At least they restyled themselves Pug and not UnderDog. So no, and luckily for everyone, there are few parallels to Guix to be found here. It took me all of 20 seconds to find the actual GUIX trademark registration[1], so we can stop basing this discussion on regrettable typographical choices in press releases. It's 4 months old. Meanwhile, we have: commit 207cba8114d354737b231e510d6110ea2a42e07b Author: Ludovic Courtès Date: Wed Apr 18 23:21:11 2012 +0200 Initial commit. Do 6+ years of prior public use trump registration? Not necessarily, but it's a far cry from what the Jade-lang folks did. I think we should talk to a lawyer. Kind regards, T G-R [0]: https://github.com/pugjs/pug/issues/2184 [1]: http://tsdr.uspto.gov/#caseNumber=87948650&caseType=SERIAL_NO&searchType=statusSearch
Re: Guix pronunciation
On Sun, Mar 10, 2019 at 12:13:55PM -0400, mikadoZero wrote: > I think the confusion around the pronunciation of GIF would probably be > a worst case scenario. Non-techies rarely discuss JPEGs or PNGs, while 'GIF' is a cultural phenomenon. How to pronounce GIF? Everyone has an opinion on this and it does not require any technical knowledge. 'GIF' has come to mean 'a short moving image on a computer'. I think it's a great success. A harmless controversy can be endearing :)
Missed testing
I know this probably is not a popular premise but we really need to take the time to actually test our example configurations prior to including them in our releases. For example if one were to go to the guixsd website and download the current release, verify that it was correct, burn onto a DVD and attempt to install with guix system init /etc/configuration/desktop.scm /mnt --fallback results in the following error: /gnu/store/729zbb84cah3wf2fcsy4h17lqxxib5q-configuration-templates/desktop.scm:23:9: error: you may need these modules in the initrd for /dev/sda1: mptspi hint: Try adding them to the 'initrd-modules' field of your 'operating-system' declaration, along these lines: (operating-system ;; ... (initrd-modules (append (list "mptspi") %base-initrd-modules))) If you think this diagnostic is inaccurate, use the '--skip-checks' option of 'guix system' So if I copy the code into the file, it stops recognizing users but if I --skip-checks the system installs but boots to a guile repl It takes a bit to find ,help works and then ,bournish only to discover no readline (so have to type everything by hand everytime) and no tab completion Which would have been fine if less/more was available or that pipes (|) worked or if cryptsetup was in the path so I wouldn't have to type the following line: /gnu/store/slpv4rzcmf6lfzzjlhm4d3r1pkb2cx00-cryptsetup-static-1.7.5/sbin/cryptsetup Then I discover /dev/sda1 isn't even exist!!! There is no documentation on how to mount and boot, let alone how to get shepherd to prompt for credentials for the luks volume... If nothing else we either need to include in the documentation how to mount a luks volume and resume boot or ensure it works everytime. -Jeremiah
Re: Guix trademarked by Express Logic
mikadoZero writes: > Jelle Licht writes: >> I really think that "software" is much too broad a category to consider >> for a trademark clash in this case. From what I can see, there is barely >> any overlap between our Guix and the GUIX product that Express Logic is >> working on. This might just be my vocational bias in action as a >> software engineer though, and of course; I Am Not A Lawyer. > > There was likely no overlap between Jade the free software project and > Jade the company's offerings. Regardless Jade the company forced Jade > the free software project to rename itself. > It rather seems that under threat of litigation, the Jade project was bullied into changing their name. I understand why the Jade maintainers decided on the name change, but I think the wrong lesson to take home from this story is to actively enable these litigation-happy companies to continue this behaviour. Additionally, it seems Guix-the-project has earlier mentions than GUIX-the-product online as well (but again, IANAL).
Re: Guix pronunciation
mikadoZero writes: > In my initial message I should have explained why I am not a fan of Guix > pronounced "geeks". It is because the pronunciation is the same as the > plural of the word geek. The word geek has an ambiguous definition. > https://en.wikipedia.org/wiki/Geek When Guix is pronounced "geeks" > there are negative connotation. > > The current participants in the Guix community have a self selection > bias by using alpha or beta software. This could shows itself through a > focus on the positive definition of geek. However I am alone in > perceiving the negative connotations and sentiment of the word geek. Not alone. I have used Guix for 3+ years. For quite some time I thought it was "gix" which seemed fine to me. Eventually I discovered it is "geeks". I am sorry to say this seems like a sick "inside joke" to me. Unfortunately it is difficult to have a productive discussion of the subject: Those working on Guix may be offended by what feels like criticism. And those turned-off by geeks have probably already self-un-selected from the project. FWIW, I have mentioned my use of something called "geeks" to a few professional friends. Each thought it weird that I would want to put effort into something with this name. It just doesn't sound serious to them. So I share your concern. IMO calling Guix "geeks" is unfortunate. I fear it will adversely impact Guix' acceptance and growth. - George
Re: Guix trademarked by Express Logic
Jelle Licht writes: > I really think that "software" is much too broad a category to consider > for a trademark clash in this case. From what I can see, there is barely > any overlap between our Guix and the GUIX product that Express Logic is > working on. This might just be my vocational bias in action as a > software engineer though, and of course; I Am Not A Lawyer. There was likely no overlap between Jade the free software project and Jade the company's offerings. Regardless Jade the company forced Jade the free software project to rename itself. Pug (previously Jade) github.com/pugjs/pug Jade the company jadeworld.com
Re: Guix pronunciation
Hi! > Also where I live, in South America, in the Aburrá Valley, The term > "geek" is used in its English form by some people to describe themselves > as people who are very interested in technology and its specifics. Another South American :) As regards the name, I have always pronounced it like geeks without even realizing the same pronunciation until I read it. I think it is a nice name, and I agree that people here use the word not in a negative form, a geek is a person that is a huge fan of technology, I don't feel it is bad, it is not offensive for me at all, or unprofessional, but if I had not read that, I would have never associated it. Maybe you should remove the footnote :) Regards :)
Re: Guix trademarked by Express Logic
Jelle Licht transcribed 1.9K bytes: > mikadoZero writes: > > > I have search guix-devel for this and did not find it. I would like to > > [ snip ] > Thanks for looking into this. > > > # Proactive name change > > > > Looking at the pug thread above shows that it would have been nice if > > Jade had not been forced to change their name so quickly and could have > > engaged it's community further on ideas for a new name. > > > > This raises the idea that proactively changing Guix's name might be > > better than reacting to a forced name change. A benefit to a proactive > > name change is being able to chose the timing. So for example the name > > change could be planned to coincide with the 1.0 release which I have > > heard is approaching. Similar to a butterfly emerging from a > > chrysalis. Maybe there is a opportunity here and this could be turned > > into a nice announcement. > > I humbly disagree with proactively doing anything of the sorts; first of > all, there are two separate issues (as you mentioned): > - Are we allowed to call Guix Guix? > - Do we want to call Guix Guix? > > As such, I think it is premature to proactively change something which > *might* not even be a (legal) problem at all, let alone something > desired by the community. I *do* agree that these questions should > probably be answered before 1.0 comes around. > > > [ snip ] > > # Contacting Express Logic > > > > Also it might be good to reach out to Express Logic as they may not > > actually have any problem with the Guix free software project using the > > name they have trademarked. > > I really think that "software" is much too broad a category to consider > for a trademark clash in this case. From what I can see, there is barely > any overlap between our Guix and the GUIX product that Express Logic is > working on. This might just be my vocational bias in action as a > software engineer though, and of course; I Am Not A Lawyer. The other Guix keeps coming up over the years. I don't think we have to do anyting because it's 2 separate fields of software. No problem unless one of the Guix starts making it one. > > > > # Summary > > > > I am not recommending any specific course of action. I just want to > > start a discussion. > > Point taken :-). > >
Re: Guix pronunciation
Hello mikadoZero writes: > Doing this duckduckgo site search: `geeks > site:https://www.gnu.org/software/guix/` gives me only one match. Which > is footnote 1 of section 1 Introduction of the manual. I do not know of > anywhere else where the pronunciation of Guix is explicitly stated. > > I would like to know what other think about making the pronunciation of > Guix obvious to anyone who visits the website. The reasoning for this is > because the pronunciation of Guix as "geeks" is not intuitive. I > think a lot of people will assume it is pronounced some other way. For > example "gwixs" or "gooixs". I was not sure how to say Guix before > watching a talk on Guix. It is also easy for people to miss that single > footnote in the manual on how to pronounce Guix. > > I think the confusion around the pronunciation of GIF would probably be > a worst case scenario. > https://en.wikipedia.org/wiki/Graphics_Interchange_Format#Pronunciation_of_GIF > > Here are two projects that have non obvious pronunciation that address > this issue directly on their project homepage: > > https://asciinema.org/ > http://www.lighttpd.net/ > I understand your concern but in my opinion, Guix doesn't really need to enforce or be protective regarding a particular pronunciation. It's an international and multicultural project, we all more than probably don't have the same accent and wont't ever pronounce it the same way and I think it's fine. :) If someone asks for the correct way to pronounce Guix, IMHO "However you wish" is ok and if a user needs more, the footnote in the manual can give some "historical" insights. I feel like it's more aligned with what Guix is. (in opposition to what a company would do) But, really, if the need arises, I don't mind. Just giving my two cents. Good evening, Lprndn
Re: CDN Test Results - Should We Continue Using a CDN?
Thank you for correcting my false assumptions and sharing that link. Ricardo Wurmus writes: > mikadoZero writes: > >> In "14.4.1 Software Freedom" of the Guix manual it says that Guix is free >> software and follows the free software distribution guidelines. >> >> Is using a proprietary non free CDN as a core part of Guix's >> infrastructure in conflict with Guix's software freedom? > > Two things: > > 1) It is not a core part of Guix’s infrastructure. People who want to > bypass the CDN can do so by fetching substitutes from berlin.guixsd.org > instead of ci.guix.info. People can also opt out of getting substitutes > all together or choose to get them from some other build farm. (The > build farm is little more than another Guix user.) > > 2) “proprietary” / “non-free” terminology does not apply to services. > See also > https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.html > > This is a case of “Service as a Hardware Substitute” where we pay to use > hardware that we do not physically control to substitute for having to > own and maintain hardware at a large number of physical locations in the > world. > >> Using a proprietary CDN has the potential for an unplanned increase in >> workload. This is because of the combination of vendor lock in and >> product line discontinuation. Which could create unplanned rework of >> setting up a CDN elsewhere. This hinders Guix's resource planning by >> introducing the potential for surprise rework. > > There is no vendor lock in. We can drop and have dropped the use of a > CDN without service interruption. If the CDN service were to be > discontinued we would simply revert to not offering package distribution > via CDN.
Re: Guix trademarked by Express Logic
mikadoZero writes: > I have search guix-devel for this and did not find it. I would like to > [ snip ] Thanks for looking into this. > # Proactive name change > > Looking at the pug thread above shows that it would have been nice if > Jade had not been forced to change their name so quickly and could have > engaged it's community further on ideas for a new name. > > This raises the idea that proactively changing Guix's name might be > better than reacting to a forced name change. A benefit to a proactive > name change is being able to chose the timing. So for example the name > change could be planned to coincide with the 1.0 release which I have > heard is approaching. Similar to a butterfly emerging from a > chrysalis. Maybe there is a opportunity here and this could be turned > into a nice announcement. I humbly disagree with proactively doing anything of the sorts; first of all, there are two separate issues (as you mentioned): - Are we allowed to call Guix Guix? - Do we want to call Guix Guix? As such, I think it is premature to proactively change something which *might* not even be a (legal) problem at all, let alone something desired by the community. I *do* agree that these questions should probably be answered before 1.0 comes around. > [ snip ] > # Contacting Express Logic > > Also it might be good to reach out to Express Logic as they may not > actually have any problem with the Guix free software project using the > name they have trademarked. I really think that "software" is much too broad a category to consider for a trademark clash in this case. From what I can see, there is barely any overlap between our Guix and the GUIX product that Express Logic is working on. This might just be my vocational bias in action as a software engineer though, and of course; I Am Not A Lawyer. > > # Summary > > I am not recommending any specific course of action. I just want to > start a discussion. Point taken :-).
Guix trademarked by Express Logic
I have search guix-devel for this and did not find it. I would like to know what people think about these topics: * does the Guix free software project have a trademark? * proactive name change * reacting to a forced name change * talking with Forbes Lindsey of Jade to gain insights * talking with Express Logic about their Guix trademark # Guix is trademarked That Guix is trademarked by Express Logic was brought to my attention by in this message: https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00122.html Thank you Tobias Geerinckx-Rice for mentioning this. Looking into this further here is additional information. Express Logic website: https://rtos.com/ Here is a press releases about Express Logic's Guix trademarked software product: https://www.marketwatch.com/press-release/express-logics-guix-becomes-the-first-deeply-embedded-gui-solution-certified-to-sil-4-asil-d-and-medical-class-c-for-safety-critical-iot-systems-2019-02-27 # Does Guix have a trademark? Does the Guix free software project have a trademark for Guix? There is only one search result for Guix's website using the term trademark. It is in the manual "14.4.1 Software Freedom" and is not relevant to the question at hand. I see no indication that the Guix free software project has trademarked Guix. # A parallel in free software If it is the case that Guix the free software project does not have a trademark for Guix, then I would like to share what looks like a clear parallel. It involves another free software project that used to be called Jade. Jade did not have a trademark for Jade. A software company had the trademark for Jade. The company forced Jade to change it's name. Assuming Guix does not have a trademark then it looks like it is the same situation without yet having been forced to change it's name. Here is a link to an issue on Pug's (Jade's new name) GitHub page discussing their forced name change: github.com/pug/issues/2184 # Proactive name change Looking at the pug thread above shows that it would have been nice if Jade had not been forced to change their name so quickly and could have engaged it's community further on ideas for a new name. This raises the idea that proactively changing Guix's name might be better than reacting to a forced name change. A benefit to a proactive name change is being able to chose the timing. So for example the name change could be planned to coincide with the 1.0 release which I have heard is approaching. Similar to a butterfly emerging from a chrysalis. Maybe there is a opportunity here and this could be turned into a nice announcement. # Learning from Jade >From that thread it looks like Forbes Lindsey was the person that the company's lawyers were sending letters to. They might be a good person to talk as they may be able to share some interesting insights that would likely be directly relevant to the Guix. # Contacting Express Logic Also it might be good to reach out to Express Logic as they may not actually have any problem with the Guix free software project using the name they have trademarked. # Summary I am not recommending any specific course of action. I just want to start a discussion. Also in the interest of transparency I am linking to messages I recently wrote where I am open about my bias of not being a fan of Guix pronounced as "geeks". https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00121.html https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00134.html
Re: CDN Test Results - Should We Continue Using a CDN?
mikadoZero writes: > In "14.4.1 Software Freedom" of the Guix manual it says that Guix is free > software and follows the free software distribution guidelines. > > Is using a proprietary non free CDN as a core part of Guix's > infrastructure in conflict with Guix's software freedom? Two things: 1) It is not a core part of Guix’s infrastructure. People who want to bypass the CDN can do so by fetching substitutes from berlin.guixsd.org instead of ci.guix.info. People can also opt out of getting substitutes all together or choose to get them from some other build farm. (The build farm is little more than another Guix user.) 2) “proprietary” / “non-free” terminology does not apply to services. See also https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.html This is a case of “Service as a Hardware Substitute” where we pay to use hardware that we do not physically control to substitute for having to own and maintain hardware at a large number of physical locations in the world. > Using a proprietary CDN has the potential for an unplanned increase in > workload. This is because of the combination of vendor lock in and > product line discontinuation. Which could create unplanned rework of > setting up a CDN elsewhere. This hinders Guix's resource planning by > introducing the potential for surprise rework. There is no vendor lock in. We can drop and have dropped the use of a CDN without service interruption. If the CDN service were to be discontinued we would simply revert to not offering package distribution via CDN. -- Ricardo
Re: CDN Test Results - Should We Continue Using a CDN?
Chris Marusich writes: > Since the test has concluded, we are not currently using a CDN. Going > forward, we need to decide if we want to continue to use a CDN. In "14.4.1 Software Freedom" of the Guix manual it says that Guix is free software and follows the free software distribution guidelines. Is using a proprietary non free CDN as a core part of Guix's infrastructure in conflict with Guix's software freedom? Using a proprietary CDN has the potential for an unplanned increase in workload. This is because of the combination of vendor lock in and product line discontinuation. Which could create unplanned rework of setting up a CDN elsewhere. This hinders Guix's resource planning by introducing the potential for surprise rework. Are there any free software content delivery networks? > One of the reasons why we wanted to use a CDN in the first place was to > free up resources so that the community could spend more time working on > better solutions. For example, some people have expressed an interest > in a distributed or peer-to-peer substitute mechanism using IPFS or > GNUnet. In fact, Ludo paved the way for this by submitting patches to > distribute substitutes over IPFS: > > https://issues.guix.info/issue/33899 > > However, it seems his work hasn't succeeded in exciting people enough to > carry the momentum forward. We need more people who are interested in > this and can work on it! Otherwise, it may never become a reality. So > if you care about distributed or peer-to-peer substitutes, please help! This is interesting. Peer-to-peer substitutes using free software is well aligned with Guix as a free software project. I would want to use this method if it was available. Has there been any progress on this since the end of that thread? Any guesses about how difficult this may be to complete and how much work might be required?
Re: building "guix deploy"
Ludovic Courtès writes:
> Hi there!
Hi Ludo! Thanks for your reply.
> "Thompson, David" skribis:
>
>> Chris Webber and I spent the morning chatting about how we want to
>> approach making "guix deploy" a reality and then started hacking on it
>> in the afternoon. Although we weren't able to complete a working
>> prototype by the end of the day, we were able to get pretty close. We
>> created a 'guix deploy' CLI to build derivations for any number of
>> remote systems on a local workstation and initiate the transfer to the
>> remote systems, but we encountered a difficult to debug SSH error that
>> blocked our progress:
>>
>> sending 85 store items (0 MiB) to 'test.activitypub.rocks'...
>> exporting path
>> `/gnu/store/ylcdmrj3vf00ixdcjvkl3mbs8f5i9w8l-git-minimal-2.20.1.drv'
>> ;;; [2019/03/09 17:32:48.792589, 0] write_to_channel_port: [GSSH
>> ERROR] Remote channel is closed: #> 541a220>
>> Backtrace:
>> 10 (apply-smob/1 #)
>> In ice-9/boot-9.scm:
>> 705:2 9 (call-with-prompt _ _ #)
>> In ice-9/eval.scm:
>> 619:8 8 (_ #(#(#)))
>> In guix/ui.scm:
>> 1654:12 7 (run-guix-command _ . _)
>> In guix/scripts/deploy.scm:
>> 72:8 6 (guix-deploy . _)
>> In srfi/srfi-1.scm:
>> 640:9 5 (for-each # …)
>> In guix/scripts/deploy.scm:
>> 74:20 4 (_ _)
>> In gnu/machine.scm:
>> 58:22 3 (_ _ _ _)
>> In guix/ssh.scm:
>> 313:4 2 (send-files # _ _ # _ # …)
>> In guix/store.scm:
>>1504:7 1 (export-paths # _ # …)
>> In unknown file:
>>0 (put-bytevector # …)
>>
>> ERROR: In procedure put-bytevector:
>> Throw to key `guile-ssh-error' with args `("write_to_channel_port"
>> "Remote channel is closed" #
>> #f)'.
>>
>> If anyone knows what might be going on here and how we could resolve
>> it, your input would be much appreciated! We verified via the sshd
>> logs that we were indeed successfully establishing a connection.
>
> Error reporting in (guix ssh) is, ahem, not as good as it could be.
>
> Apparently the SSH channel was closed prematurely, which could be due to
> a number of things:
>
> 1. Are ‘guix’ and ‘guile’ in $PATH on the remote machine, for
> non-interactive shells?
>
> 2. Is ‘guix repl’ available in the remote machine?
>
> You can test this with:
>
> ssh HOST guile --version
> ssh HOST guix repl --version
Yep, both respond with
guile (GNU Guile) 2.2.4
and
guix (GNU Guix) 0.16.0-10.2637cfd
respectively.
> Also, does ‘guix copy’ fail similarly when sending files to that host?
It seems it does:
cwebber@jasmine:~/devel/librelounge-audio$ guix copy
--to=test.activitypub.rocks pidgin
guile: warning: failed to install locale
sending 37 store items (336 MiB) to 'test.activitypub.rocks'...
;;; [2019/03/11 10:39:25.573104, 0] write_to_channel_port: [GSSH ERROR] Remote
channel is closed: #
Backtrace:
11 (primitive-load "/home/cwebber/.config/guix/current/bin…")
In guix/ui.scm:
1654:12 10 (run-guix-command _ . _)
In ice-9/boot-9.scm:
829:9 9 (catch _ _ # …)
829:9 8 (catch _ _ # …)
In guix/status.scm:
810:4 7 (call-with-status-report _ _)
In guix/scripts/copy.scm:
81:27 6 (send-to-remote-host _ _)
In guix/ssh.scm:
313:4 5 (send-files # _ _ # _ # …)
In guix/store.scm:
1505:12 4 (export-paths # _ # …)
1485:22 3 (export-path # _ # …)
683:13 2 (process-stderr _ _)
646:10 1 (dump-port # # …)
In unknown file:
0 (put-bytevector # …)
ERROR: In procedure put-bytevector:
Throw to key `guile-ssh-error' with args `("write_to_channel_port" "Remote
channel is closed" # #f)'.
I wonder what got screwed up!
>> Once we're past this blocking issue and are able to transfer OS
>> closures to remote systems, we plan to write a modified version of
>> switch-to-system that uses guile-ssh to switch remote symlinks for the
>> active system and run the activation script. We'll save
>> upgrade-shepherd-services for later, as it is quite a bit more
>> complex.
>
> My plan is to have ‘guix system reconfigure --host=host.example.org’.
> To do that, I thought about the following plan:
>
> 1. Isolate the effectful part of reconfigure (basically
> ‘switch-to-system’).
>
> 2. Implement ‘remote-eval’, which takes a gexp and an SSH session and
> evaluates the expression remotely, copying the gexp inputs as
> needed.
>
> 3. Have ‘reconfigure’ use either ‘eval’ or ‘remote-eval’ to evaluate
> the effectful bits of reconfigure.
This sounds like the right approach to me.
> #1 is a bit annoying because we need to untangle code so that we can
> easily put it all “on the build side.” In particular, I think we’ll
> have to change (guix graph), used by ‘upgrade-shepherd-services’, so
> that it no longer depends on ‘%store-monad’.
>
> That said, it’s probably a good idea to take a shorter path in the
> meantime to unlock progress on ‘guix deploy’!
>
>> There's not a lot of code yet, but you can check it out in the
>> wip-deploy2 branch. Currently, the only supported use-case is running
>>
Request for commit access
Hi Guix, May I request commit access for the Guix repositories? This access would be primarily for maintaining and addding packages in the (gnu packages maths/engineering/simulation) modules. Also, I am preparing to do the narration for the Guix videos. With commit access, I will be able to push the audio files directly to videos.git. I have an account on Savannah and have uploaded my OpenPGP key. Best regards, Paul Garlick.
Re: Patch adding POWER9 cross compile support
On Sun, Mar 10, 2019 at 09:20:04PM +0100, Tobias Platen wrote:
> I ran configure on my Talos II, and got the following error message.
>
> checking for the Guix system type... powerpc64le-linux
> configure: error: `powerpc64le-linux' is not a supported platform.
> See "GNU Distribution" in the manual, or try `--with-courage'.
>
> Guix already knows about this architecture, but building glibc will fail if
> gcc does not have the float128 datatype. Once I saw this link[1] on the guix
> mailing list, I knew how to solve the build error.
>
> For the second question I could not find an answer.
>
> [1] http://lists.busybox.net/pipermail/buildroot/2017-September/201379.html
>
> Tobias
>
> On 03/10/2019 06:27 PM, Ludovic Courtès wrote:
> > Hi Tobias,
> >
> > Tobias Platen skribis:
> >
> > > On 03/06/2019 02:54 PM, Ludovic Courtès wrote:
> > > > + ,@(if (string-prefix? "powerpc9-"
> > > > target)
> > > > + ;; On POWER9 we need this because
> > > > XXX.
> > > > + '("--with-long-double-128")
> > > > + '())
> > > > +
> > > It needs to be ppc64el I think. I will later do a test in a big endian
> > > vm. POWER9 is a bi-endian architecture, and most distros only support
> > > little-endian. POWER4 only supports big-endian, and is still supported
> > > by some distros. After testing I will send an updated patch.
> >
> > I don’t think that answers my questions. :-)
> >
> > Those were:
> >
> >1. What GNU triplet do you use?
>
> >
> >2. What the reason for this extra configure flag, so we can add it in
> > the comment above in place of XXX?
> >
> > TIA!
> >
> > Ludo’.
> >
> diff --git a/gnu/packages/cross-base.scm b/gnu/packages/cross-base.scm
> index 6a09272..0992259 100644
> --- a/gnu/packages/cross-base.scm
> +++ b/gnu/packages/cross-base.scm
> @@ -138,6 +138,10 @@ base compiler and using LIBC (which may be either a libc
> package or #f.)"
> "--disable-libquadmath"
> "--disable-decimal-float" ;would need libc
> "--disable-libcilkrts"
> + ,@(if (string-prefix? "powerpc64le-" target)
> + ;; On POWER9 (little endian) glibc needs the
> 128 bit long double type.
> + '("--with-long-double-128")
> + '())
>
> ;; When target is any OS other than 'none'
> these
> ;; libraries will fail if there is no libc
In the off chance we ever wish to support powerpc64 big endian, I
suggest instead using (string-prefix? "powerpc64*-" target)
As far as '--with-long-double-128', I think it's worth finding out which
architectures accept it and allowing it for all of those, rather than
making it powerpc64le only.
--
Efraim Flashner אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
