Package: guix;
Reported by: Mark H Weaver <mhw <at> netris.org>
Date: Sun, 7 Feb 2016 21:22:02 UTC
Severity: normal
Done: ludo <at> gnu.org (Ludovic Courtès)
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22588 in the body.
You can then email your comments to 22588 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
View this report as an mbox folder, status mbox, maintainer mbox
bug-guix <at> gnu.org
:bug#22588
; Package guix
.
(Sun, 07 Feb 2016 21:22:02 GMT) Full text and rfc822 format available.Mark H Weaver <mhw <at> netris.org>
:bug-guix <at> gnu.org
.
(Sun, 07 Feb 2016 21:22:02 GMT) Full text and rfc822 format available.Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
From: Mark H Weaver <mhw <at> netris.org> To: bug-guix <at> gnu.org Subject: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Sun, 07 Feb 2016 16:21:35 -0500
I've been bitten by this once before, and a user on #guix did as well. When there are problems in the root filesystem that fsck doesn't want to fix automatically, the user is dumped into a guile prompt where PATH is not set, and it's very inconvenient to run fsck manually. This is what I just suggested that the user type, with apologies: (use-modules (ice-9 ftw) (srfi srfi-26)) (define dirs (scandir "/gnu/store" (cut string-suffix? "e2fsprogs-1.42.13" <>))) (define e2fsck (string-append "/gnu/store/" (car dirs) "/sbin/e2fsck")) (system* e2fsck "/dev/XXX") Is there a better way? Speaking from personal experience, it's very painful to do anything non-trivial in that REPL. Even just adding readline would help a lot. Maybe we should at least set PATH to include the available /bin and /sbin directories before entering the REPL. We should probably also handle errors from fsck specially. Thoughts? Mark
bug-guix <at> gnu.org
:bug#22588
; Package guix
.
(Mon, 08 Feb 2016 09:43:02 GMT) Full text and rfc822 format available.Message #8 received at 22588 <at> debbugs.gnu.org (full text, mbox):
From: ludo <at> gnu.org (Ludovic Courtès) To: Mark H Weaver <mhw <at> netris.org> Cc: 22588 <at> debbugs.gnu.org Subject: Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Mon, 08 Feb 2016 10:42:27 +0100
Mark H Weaver <mhw <at> netris.org> skribis: > I've been bitten by this once before, and a user on #guix did as well. > When there are problems in the root filesystem that fsck doesn't want to > fix automatically, the user is dumped into a guile prompt where PATH is > not set, and it's very inconvenient to run fsck manually. AFAICS, ‘PATH’ is set in ‘base-initrd’ in (gnu system linux-initrd), and ‘check-file-system’ in (gnu build file-systems) indeed expects it to be set. > This is what I just suggested that the user type, with apologies: > > (use-modules (ice-9 ftw) (srfi srfi-26)) > (define dirs (scandir "/gnu/store" (cut string-suffix? "e2fsprogs-1.42.13" <>))) > (define e2fsck (string-append "/gnu/store/" (car dirs) "/sbin/e2fsck")) > (system* e2fsck "/dev/XXX") > > Is there a better way? I think one can run: (system* "fsck.ext4" "/foo/bar") What about changing the message to explicitly mention this command? > Speaking from personal experience, it's very painful to do anything > non-trivial in that REPL. Even just adding readline would help a lot. The statically-linked Guile in the initrd lacks Readline support. We could maybe work around that, but the initrd would become much larger. > Maybe we should at least set PATH to include the available /bin and > /sbin directories before entering the REPL. Done, AFAICS. > We should probably also handle errors from fsck specially. Currently there’s no Bash in the initrd. Should we add one? Our ‘bash-static’ package takes 1.4 MiB (I don’t think we can make it smaller.) Thanks, Ludo’.
bug-guix <at> gnu.org
:bug#22588
; Package guix
.
(Mon, 08 Feb 2016 09:45:02 GMT) Full text and rfc822 format available.Message #11 received at 22588 <at> debbugs.gnu.org (full text, mbox):
From: ludo <at> gnu.org (Ludovic Courtès) To: Mark H Weaver <mhw <at> netris.org> Cc: 22588 <at> debbugs.gnu.org Subject: Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Mon, 08 Feb 2016 10:43:52 +0100
Another idea that comes to mind: what about providing a “shell” language in Guile? It would automatically tokenize what the user types in and convert it to (system* …), plus it would have a few built-in commands like ‘cd’ and ‘ls’. Ludo’.
bug-guix <at> gnu.org
:bug#22588
; Package guix
.
(Mon, 08 Feb 2016 13:50:02 GMT) Full text and rfc822 format available.Message #14 received at 22588 <at> debbugs.gnu.org (full text, mbox):
From: Mark H Weaver <mhw <at> netris.org> To: ludo <at> gnu.org (Ludovic Courtès) Cc: 22588 <at> debbugs.gnu.org Subject: Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Mon, 08 Feb 2016 08:49:24 -0500
ludo <at> gnu.org (Ludovic Courtès) writes: > Mark H Weaver <mhw <at> netris.org> skribis: > >> I've been bitten by this once before, and a user on #guix did as well. >> When there are problems in the root filesystem that fsck doesn't want to >> fix automatically, the user is dumped into a guile prompt where PATH is >> not set, and it's very inconvenient to run fsck manually. > > AFAICS, ‘PATH’ is set in ‘base-initrd’ in (gnu system linux-initrd), and > ‘check-file-system’ in (gnu build file-systems) indeed expects it to be > set. Ah, good! >> This is what I just suggested that the user type, with apologies: >> >> (use-modules (ice-9 ftw) (srfi srfi-26)) >> (define dirs (scandir "/gnu/store" (cut string-suffix? "e2fsprogs-1.42.13" <>))) >> (define e2fsck (string-append "/gnu/store/" (car dirs) "/sbin/e2fsck")) >> (system* e2fsck "/dev/XXX") >> >> Is there a better way? > > I think one can run: > > (system* "fsck.ext4" "/foo/bar") Okay, this is much better than I expected. I asked the user to try running "e2fsck", and when it wasn't found in PATH, I incorrectly assumed that PATH wasn't set. > What about changing the message to explicitly mention this command? Sure, that would be helpful. >> Speaking from personal experience, it's very painful to do anything >> non-trivial in that REPL. Even just adding readline would help a lot. > > The statically-linked Guile in the initrd lacks Readline support. We > could maybe work around that, but the initrd would become much larger. Okay, nevermind then. >> We should probably also handle errors from fsck specially. > > Currently there’s no Bash in the initrd. Should we add one? Our > ‘bash-static’ package takes 1.4 MiB (I don’t think we can make it > smaller.) I'm not sure it would help much without also adding 'coreutils'. Adding busybox might be worth considering, though. > Another idea that comes to mind: what about providing a “shell” language > in Guile? It would automatically tokenize what the user types in and > convert it to (system* …), plus it would have a few built-in commands > like ‘cd’ and ‘ls’. I like the idea of having something like this in Guile, but I'm not sure we should rush to implement a half-baked solution. When we have something decent along the lines of Scsh, then definitely! IMO, anyway, but I don't feel strongly about it. More thoughts? Thanks! Mark
bug-guix <at> gnu.org
:bug#22588
; Package guix
.
(Mon, 08 Feb 2016 18:13:04 GMT) Full text and rfc822 format available.Message #17 received at 22588 <at> debbugs.gnu.org (full text, mbox):
From: ludo <at> gnu.org (Ludovic Courtès) To: Mark H Weaver <mhw <at> netris.org> Cc: 22588 <at> debbugs.gnu.org Subject: Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Mon, 08 Feb 2016 17:48:19 +0100
[Message part 1 (text/plain, inline)]
Mark H Weaver <mhw <at> netris.org> skribis: > ludo <at> gnu.org (Ludovic Courtès) writes: [...] >> Currently there’s no Bash in the initrd. Should we add one? Our >> ‘bash-static’ package takes 1.4 MiB (I don’t think we can make it >> smaller.) > > I'm not sure it would help much without also adding 'coreutils'. Good point. >> Another idea that comes to mind: what about providing a “shell” language >> in Guile? It would automatically tokenize what the user types in and >> convert it to (system* …), plus it would have a few built-in commands >> like ‘cd’ and ‘ls’. > > I like the idea of having something like this in Guile, but I'm not sure > we should rush to implement a half-baked solution. OTOH, hacking it is very tempting, like: --8<---------------cut here---------------start------------->8--- scheme@(guile-user)> ,use (guix build bournish) scheme@(guile-user)> ,bournish Happy hacking with Bournish! To switch back, type `,L scheme'. bournish@(guile-user)> ls . gnu-dist.go r-build-system.go .. gnu-dist.scm r-build-system.scm activation.scm~ gnu-dist.scm~ relocate.scm~ bournish.scm gnu.scm~ rpath.go bournish.scm~ graft.go rpath.scm cmake-build-system.go graft.scm rpath.scm~ cmake-build-system.scm graft.scm~ ruby-build-system.go cvs.go graft.scm.115 ruby-build-system.scm cvs.scm graft.scm.bak ruby-build-system.scm.orig download.go gremlin.go ruby-build-system.scm.rej download.scm gremlin.scm store-copy.go download.scm~ gremlin.scm~ store-copy.scm download.scm.bak haskell-build-system.go store-copy.scm~ emacs-build-system.go haskell-build-system.scm svn.go emacs-build-system.scm http.scm~ svn.scm emacs-utils.go install.scm~ syscalls.go emacs-utils.scm linux-initrd.scm~ syscalls.scm ftp.scm~ perl-build-system.go syscalls.scm~ git.go perl-build-system.scm union.go git.scm perl-build-system.scm~ union.scm git.scm~ profile.go union.scm~ glib-or-gtk-build-system.gprofile.scm~ url.scm~ glib-or-gtk-build-system.sprofiles.go utils.go gnome-build-system.scm profiles.scm utils.scm gnome-build-system.scm~ profiles.scm~ utils.scm~ gnu-build-system.go pull.go vm.scm~ gnu-build-system.scm pull.scm waf-build-system.go gnu-build-system.scm~ pull.scm~ waf-build-system.scm gnu-build-system.scm.bak python-build-system.go gnu-cross-build.scm~ python-build-system.scm bournish@(guile-user)> cd / bournish@(guile-user)> pwd $2 = "/" bournish@(guile-user)> echo $PATH $LANGUAGE $3 = ("/home/ludo/soft/bin:/home/ludo/.opam/system/bin:/home/ludo/.guix-profile/bin:/home/ludo/.guix-profile/sbin:/run/setuid-programs:/run/current-system/profile/bin:/run/current-system/profile/sbin" "eo") bournish@(guile-user)> touch --version touch (GNU coreutils) 8.24 Copyright © 2015 Free Software Foundation, Inc. Ĉi tiu estas libera programaro: vi rajtas ĝin ŝanĝi kaj redistribui. La ĝusta permesilo estas GPLv3+: GNU GPL versio 3 aŭ sekva; por la kompleta (angla) teksto vidu <http://gnu.org/licenses/gpl.html>. Ĉi tiu programaro ne garantiatas, ene de la limoj de la leĝo. Verkita de Paul Rubin, Arnold Robbins, Jim Kingdon, David MacKenzie kaj Randy Smith. $4 = 0 bournish@(guile-user)> ,L scheme Happy hacking with Scheme! To switch back, type `,L bournish'. --8<---------------cut here---------------end--------------->8--- :-) The point is, if we can allow users to avoid typing in parentheses and long procedure names and quoted argument lists when all they want is to run fsck, we should do that. > When we have something decent along the lines of Scsh, then > definitely! Scsh makes it super easy to deal with Unix processes, redirections, and all that (it would be awesome to use it on the build side), but AFAIK it doesn’t try to provide a Bourne-like interface, which is what we need here. So, WDYT? :-) Ludo’.
[bournish.scm (text/plain, inline)]
;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2016 Ludovic Courtès <ludo <at> gnu.org> ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free software; you can redistribute it and/or modify it ;;; under the terms of the GNU General Public License as published by ;;; the Free Software Foundation; either version 3 of the License, or (at ;;; your option) any later version. ;;; ;;; GNU Guix is distributed in the hope that it will be useful, but ;;; WITHOUT ANY WARRANTY; without even the implied warranty of ;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;;; GNU General Public License for more details. ;;; ;;; You should have received a copy of the GNU General Public License ;;; along with GNU Guix. If not, see <http://www.gnu.org/licenses/>. (define-module (guix build bournish) #:use-module (system base language) #:use-module (system base compile) #:use-module (system repl command) #:use-module (system repl common) #:use-module (ice-9 rdelim) #:use-module (ice-9 match) #:use-module (ice-9 ftw) #:use-module (srfi srfi-1) #:use-module (srfi srfi-26) #:export (%bournish-language)) (define (expand-variable str) ;; XXX: No support for "${VAR}". (if (string-prefix? "$" str) (or (getenv (string-drop str 1)) "") str)) (define* (display-tabulated lst #:key (columns 3) (column-width (/ 78 columns))) "Display the list of string LST in COLUMNS columns of COLUMN-WIDTH characters." (define len (length lst)) (define pad (if (zero? (modulo len columns)) 0 columns)) (define items-per-column (quotient (+ len pad) columns)) (define items (list->vector lst)) (let loop ((indexes (unfold (cut >= <> columns) (cut * <> items-per-column) 1+ 0))) (unless (>= (first indexes) items-per-column) (for-each (lambda (index) (let ((item (if (< index len) (vector-ref items index) ""))) (display (string-pad-right item column-width)))) indexes) (newline) (loop (map 1+ indexes))))) (define builtin-ls (case-lambda (() (display-tabulated (scandir "."))) (files (let ((files (filter (lambda (file) (catch 'system-error (lambda () (lstat file)) (lambda args (let ((errno (system-error-errno args))) (format (current-error-port) "~a: ~a~%" file (strerror errno)) #f)))) files))) (display-tabulated files))))) (define %not-colon (char-set-complement (char-set #\:))) (define (executable-path) (match (getenv "PATH") (#f '()) (str (string-tokenize str %not-colon)))) (define (read-bournish port env) (match (map expand-variable (string-tokenize (read-line port))) (("echo" strings ...) `',strings) (("cd" dir) `(chdir ,dir)) (("pwd") `(getcwd)) (("ls" args ...) `((@@ (guix build bournish) builtin-ls) ,@args)) (("which" command) `(search-path ((@@ (guix build bournish) executable-path)) ,command)) (("help" _ ...) (display "\ Hello, this is Bournish, a minimal Bourne-like shell in Guile! The shell is good enough to navigate the file system and run commands but not much beyond that. It is meant to be used as a rescue shell in the initial RAM disk and is probably not very useful apart from that. It has a few built-in commands such as 'ls' and 'cd'; it lacks globbing, pipes---everything.\n")) ((command args ...) (let ((command (if (string-prefix? "\\" command) (string-drop command 1) command))) `(system* ,command ,@args))))) (define %bournish-language (let ((scheme (lookup-language 'scheme))) (make-language #:name 'bournish #:title "Bournish" #:reader read-bournish #:compilers (language-compilers scheme) #:decompilers (language-decompilers scheme) #:evaluator (language-evaluator scheme) #:printer (language-printer scheme) #:make-default-environment (language-make-default-environment scheme)))) ;; XXX: ",L bournish" won't work unless we call our module (language bournish ;; spec), which is kinda annoying, so provide another meta-command. (define-meta-command ((bournish guix) repl) "bournish Switch to the Bournish language." (let ((current (repl-language repl))) (format #t "Happy hacking with ~a! To switch back, type `,L ~a'.\n" (language-title %bournish-language) (language-name current)) (current-language %bournish-language) (set! (repl-language repl) %bournish-language)))
bug-guix <at> gnu.org
:bug#22588
; Package guix
.
(Mon, 08 Feb 2016 18:23:01 GMT) Full text and rfc822 format available.Message #20 received at 22588 <at> debbugs.gnu.org (full text, mbox):
From: Mark H Weaver <mhw <at> netris.org> To: ludo <at> gnu.org (Ludovic Courtès) Cc: 22588 <at> debbugs.gnu.org Subject: Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Mon, 08 Feb 2016 12:52:49 -0500
ludo <at> gnu.org (Ludovic Courtès) writes: > Mark H Weaver <mhw <at> netris.org> skribis: > >> ludo <at> gnu.org (Ludovic Courtès) writes: > > [...] > >>> Currently there’s no Bash in the initrd. Should we add one? Our >>> ‘bash-static’ package takes 1.4 MiB (I don’t think we can make it >>> smaller.) >> >> I'm not sure it would help much without also adding 'coreutils'. > > Good point. > >>> Another idea that comes to mind: what about providing a “shell” language >>> in Guile? It would automatically tokenize what the user types in and >>> convert it to (system* …), plus it would have a few built-in commands >>> like ‘cd’ and ‘ls’. >> >> I like the idea of having something like this in Guile, but I'm not sure >> we should rush to implement a half-baked solution. > > OTOH, hacking it is very tempting, like: > > scheme@(guile-user)> ,use (guix build bournish) > scheme@(guile-user)> ,bournish > Happy hacking with Bournish! To switch back, type `,L scheme'. > bournish@(guile-user)> ls > . gnu-dist.go r-build-system.go > .. gnu-dist.scm r-build-system.scm > activation.scm~ gnu-dist.scm~ relocate.scm~ > bournish.scm gnu.scm~ rpath.go > bournish.scm~ graft.go rpath.scm > cmake-build-system.go graft.scm rpath.scm~ > cmake-build-system.scm graft.scm~ ruby-build-system.go > cvs.go graft.scm.115 ruby-build-system.scm > cvs.scm graft.scm.bak ruby-build-system.scm.orig > download.go gremlin.go ruby-build-system.scm.rej > download.scm gremlin.scm store-copy.go > download.scm~ gremlin.scm~ store-copy.scm > download.scm.bak haskell-build-system.go store-copy.scm~ > emacs-build-system.go haskell-build-system.scm svn.go > emacs-build-system.scm http.scm~ svn.scm > emacs-utils.go install.scm~ syscalls.go > emacs-utils.scm linux-initrd.scm~ syscalls.scm > ftp.scm~ perl-build-system.go syscalls.scm~ > git.go perl-build-system.scm union.go > git.scm perl-build-system.scm~ union.scm > git.scm~ profile.go union.scm~ > glib-or-gtk-build-system.gprofile.scm~ url.scm~ > glib-or-gtk-build-system.sprofiles.go utils.go > gnome-build-system.scm profiles.scm utils.scm > gnome-build-system.scm~ profiles.scm~ utils.scm~ > gnu-build-system.go pull.go vm.scm~ > gnu-build-system.scm pull.scm waf-build-system.go > gnu-build-system.scm~ pull.scm~ waf-build-system.scm > gnu-build-system.scm.bak python-build-system.go > gnu-cross-build.scm~ python-build-system.scm > bournish@(guile-user)> cd / > bournish@(guile-user)> pwd > $2 = "/" > bournish@(guile-user)> echo $PATH $LANGUAGE > $3 = ("/home/ludo/soft/bin:/home/ludo/.opam/system/bin:/home/ludo/.guix-profile/bin:/home/ludo/.guix-profile/sbin:/run/setuid-programs:/run/current-system/profile/bin:/run/current-system/profile/sbin" "eo") > bournish@(guile-user)> touch --version > touch (GNU coreutils) 8.24 > Copyright © 2015 Free Software Foundation, Inc. > Ĉi tiu estas libera programaro: vi rajtas ĝin ŝanĝi kaj redistribui. > La ĝusta permesilo estas GPLv3+: GNU GPL versio 3 aŭ sekva; > por la kompleta (angla) teksto vidu <http://gnu.org/licenses/gpl.html>. > Ĉi tiu programaro ne garantiatas, ene de la limoj de la leĝo. > > Verkita de Paul Rubin, Arnold Robbins, Jim Kingdon, > David MacKenzie kaj Randy Smith. > $4 = 0 > bournish@(guile-user)> ,L scheme > Happy hacking with Scheme! To switch back, type `,L bournish'. > > :-) > > The point is, if we can allow users to avoid typing in parentheses and > long procedure names and quoted argument lists when all they want is to > run fsck, we should do that. > >> When we have something decent along the lines of Scsh, then >> definitely! > > Scsh makes it super easy to deal with Unix processes, redirections, and > all that (it would be awesome to use it on the build side), but AFAIK it > doesn’t try to provide a Bourne-like interface, which is what we need > here. > > So, WDYT? :-) Okay, I must admit that's a pretty great little hack, and a nice demo of how easy it is to hack something together like this in Guile. Let's do it :) Mark
bug-guix <at> gnu.org
:bug#22588
; Package guix
.
(Mon, 08 Feb 2016 19:43:02 GMT) Full text and rfc822 format available.Message #23 received at 22588 <at> debbugs.gnu.org (full text, mbox):
From: Christopher Allan Webber <cwebber <at> dustycloud.org> To: Ludovic Courtès <ludo <at> gnu.org> Cc: Mark H Weaver <mhw <at> netris.org>, 22588 <at> debbugs.gnu.org Subject: Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Mon, 08 Feb 2016 11:42:50 -0800
Ludovic Courtès writes: > OTOH, hacking it is very tempting, like: > > --8<---------------cut here---------------start------------->8--- > scheme@(guile-user)> ,use (guix build bournish) > scheme@(guile-user)> ,bournish > Happy hacking with Bournish! To switch back, type `,L scheme'. > bournish@(guile-user)> ls > . gnu-dist.go r-build-system.go > .. gnu-dist.scm r-build-system.scm > activation.scm~ gnu-dist.scm~ relocate.scm~ > bournish.scm gnu.scm~ rpath.go > bournish.scm~ graft.go rpath.scm > cmake-build-system.go graft.scm rpath.scm~ > cmake-build-system.scm graft.scm~ ruby-build-system.go > cvs.go graft.scm.115 ruby-build-system.scm > cvs.scm graft.scm.bak ruby-build-system.scm.orig > download.go gremlin.go ruby-build-system.scm.rej > download.scm gremlin.scm store-copy.go > download.scm~ gremlin.scm~ store-copy.scm > download.scm.bak haskell-build-system.go store-copy.scm~ > emacs-build-system.go haskell-build-system.scm svn.go > emacs-build-system.scm http.scm~ svn.scm > emacs-utils.go install.scm~ syscalls.go > emacs-utils.scm linux-initrd.scm~ syscalls.scm > ftp.scm~ perl-build-system.go syscalls.scm~ > git.go perl-build-system.scm union.go > git.scm perl-build-system.scm~ union.scm > git.scm~ profile.go union.scm~ > glib-or-gtk-build-system.gprofile.scm~ url.scm~ > glib-or-gtk-build-system.sprofiles.go utils.go > gnome-build-system.scm profiles.scm utils.scm > gnome-build-system.scm~ profiles.scm~ utils.scm~ > gnu-build-system.go pull.go vm.scm~ > gnu-build-system.scm pull.scm waf-build-system.go > gnu-build-system.scm~ pull.scm~ waf-build-system.scm > gnu-build-system.scm.bak python-build-system.go > gnu-cross-build.scm~ python-build-system.scm > bournish@(guile-user)> cd / > bournish@(guile-user)> pwd > $2 = "/" > bournish@(guile-user)> echo $PATH $LANGUAGE > $3 = ("/home/ludo/soft/bin:/home/ludo/.opam/system/bin:/home/ludo/.guix-profile/bin:/home/ludo/.guix-profile/sbin:/run/setuid-programs:/run/current-system/profile/bin:/run/current-system/profile/sbin" "eo") > bournish@(guile-user)> touch --version > touch (GNU coreutils) 8.24 > Copyright © 2015 Free Software Foundation, Inc. > Ĉi tiu estas libera programaro: vi rajtas ĝin ŝanĝi kaj redistribui. > La ĝusta permesilo estas GPLv3+: GNU GPL versio 3 aŭ sekva; > por la kompleta (angla) teksto vidu <http://gnu.org/licenses/gpl.html>. > Ĉi tiu programaro ne garantiatas, ene de la limoj de la leĝo. > > Verkita de Paul Rubin, Arnold Robbins, Jim Kingdon, > David MacKenzie kaj Randy Smith. > $4 = 0 > bournish@(guile-user)> ,L scheme > Happy hacking with Scheme! To switch back, type `,L bournish'. > --8<---------------cut here---------------end--------------->8--- > > :-) > > The point is, if we can allow users to avoid typing in parentheses and > long procedure names and quoted argument lists when all they want is to > run fsck, we should do that. Wowee! Yeah, this is pretty neat :) It's a cool demo, and also seems like a much more comfortable "emergency shell" to drop users into. +1 from me.
ludo <at> gnu.org (Ludovic Courtès)
:Mark H Weaver <mhw <at> netris.org>
:Message #28 received at 22588-done <at> debbugs.gnu.org (full text, mbox):
From: ludo <at> gnu.org (Ludovic Courtès) To: Mark H Weaver <mhw <at> netris.org> Cc: 22588-done <at> debbugs.gnu.org Subject: Re: bug#22588: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY Date: Mon, 08 Feb 2016 23:49:06 +0100
Mark H Weaver <mhw <at> netris.org> skribis: > Okay, I must admit that's a pretty great little hack, and a nice demo of > how easy it is to hack something together like this in Guile. It’s fun to think we have a compiler from a subset of Bourne shell to the Guile VM. :-) > Let's do it :) Done in 6eb4390! Thanks, Ludo’.
Debbugs Internal Request <help-debbugs <at> gnu.org>
to internal_control <at> debbugs.gnu.org
.
(Tue, 08 Mar 2016 12:24:05 GMT) Full text and rfc822 format available.
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.