IRC channel logs

2014-08-27.log

back to list of logs

<ph4nt0mas>sneek: later tell civodul hello, did you check any of the patches I sent about glibc/hurd or crossbase? http://lists.gnu.org/archive/html/guix-devel/2014-07/msg00140.html http://lists.gnu.org/archive/html/guix-devel/2014-07/msg00273.html
<sneek>Got it.
<civodul>Hello Guix!
<Svetlana>civodul, hi!
<Svetlana>I've cloned guix and I think our previous conversation stopped there
<Svetlana>(about having a cloned guix pkg manager on a non-guix OS, and a usb drive with guix OS on it; missing gnu-disk-image when i try to boot it)
<DusXMT>Svetlana: just to make sure it's not something obvious, are you sure your USB drive's partition with guix is labeled "gnu-disk-image"?
<DusXMT>If yes, my other theory is that the system doesn't detect your USB drive on boot-up (missing drivers in the kernel?)
<Svetlana><civodul> and then run "blkid -L gnu-disk-image"
<Svetlana><civodul> that should print "/dev/sdb1"
<Svetlana><Svetlana> yes, i confirm i can see sdb1 now, and that it does print /dev/sdb1
<Svetlana>how do I check for 'does it detect usb drive?' from the scheme prompt that it gives?
<Svetlana>civodul suggested ``,use (guix build linux-initrd)'' and ``(find-partition-by-label "gnu-disk-image")'', but I've not tried that yet (I could try and take notes of what it says, hopefully not many lines)
<DusXMT>I myslf don't knoe exactly how, but you can list directory content in scheme, I'd list /dev to see what sdX devicesthere are. The initrd doesn't come with a shell, so that's the only way I think it can be done
<Svetlana>ah. how can I list directory content in scheme?
<civodul>Svetlana: sorry for the loooong delay
<civodul>that's another reason why email sometimes works better for me ;-)
<Svetlana>that is not a problem at all; my temperament is way slower than that
<civodul>so yes, find-partition-by-label would be the thing
<civodul>if you could try it from the Scheme prompt, that'd be great
<Svetlana>yes, and any pointers how to do ``lsblk'' or similar in scheme?
<civodul>but DusXMT's guess that some drivers are missing could be correct
<Svetlana>i.e. list available devices and their names
<civodul>there's 'disk-partitions' in that (guix build linux-initrd) module
<Svetlana>``(disk-partitions)''?
<civodul>yes
<civodul>from the prompt, you could also try:
<civodul>(ext2-superblock-volume-name (read-ext2-superblock "/dev/sda1"))
<civodul>or sdb1, whichever is supposed to be correct
<Svetlana>ok I took notes, will reboot and see what i get
<civodul>thanks
*civodul is now a happy user of guix.el :-)
<Svetlana>.el = ?
<Svetlana>language code?
<DusXMT>emacs lisp
<Svetlana>oooh.
<Svetlana>apparently it only detects my usb flash drive and my logitech usb mouse after bugging out with the error about gnu-disk-image not found -- and the commands return sdb1 fine in scheme (except the last long one which says something about unbound variable)
<Svetlana>so i see the error, then scheme prompt, then some more of logs in a format similar to the earlier ones -- this time about 2 usb devices
<civodul>Svetlana: so detection happens *after* the error, right?
<civodul>and find-partition-by-label does work at the prompt?
<Svetlana>yes
<Svetlana>yes, again
<civodul>ok :-)
<civodul>in linux-initrd.scm, there's a variable called 'max-trial'
<civodul>currently, the thing waits for at least 6 seconds before errorring out
<civodul>we could still increase it, if need be
<civodul>is it an old machine?
<civodul>or are there many USB devices plugged in?
<Svetlana>2 -- usb kb which it did fail to detect entirely (but it's not a big problem since the laptop has a builtin one anyway), and a usb mouse which it said it detected properly
<Svetlana>and 3rd one is the usb drive
<Svetlana>i could try to take out the usb keyboard and see whether that makes it a bit happier
<alezost>civodul: ah, I see your message in ML, glad that the problem disappeared :)
<alezost>civodul: But I didn't really understand the message about "package.el" replacement
<civodul>hey alezost
<civodul>alezost: when you install something from package.el, the elisp files are compiled and loaded directly in the running emacs
<civodul>guix.el could do the same, i think
<civodul>Svetlana: maybe it's just that we need to increase the timeout
<civodul>i could try to build a new image for you, with a higher timeout
<civodul>(but i'm short on disk space right now...)
<alezost>civodul: sorry, perhaps I'm just not able to comprehend it right now as I am all in "Makefile.am" and "configure.ac": that's a very interesting and huge subject
<Svetlana>ok; i'll try without usb kb and yell back -- unlikely to help but may be worth a try
*Svetlana reboots
*Svetlana eyes 'makefile'
<Svetlana>(as other things, a horrid concept until one reads a /complete/ manual)
<civodul>alezost: :-)
<civodul>Svetlana: you only need a few lines of Makefile.am normally, no configure.ac
<civodul>sorry, alezost ↑
<civodul>alezost: specifically, you need lisp_DATA = ... and MODULES += ...
<civodul>and that should be about it
<alezost>civodul: actually there's some more that need to be done, I'll push it soon to a separate branch and I'll send a message about that
<Svetlana>2 more detail. 1) the error is not 'gnu-disk-image not found', it is 'failed to resolve partition `gnu-disk-image`'; 2) the error message is preceded by a handful of warnings about it being unable to find /dev/sda6
<Svetlana>sda6 is a swap partition created and used by the os I'm chatting here from
<Svetlana>(and unplugging the keyboard didn't make a difference)
<civodul>Svetlana: what is the exact warning?
<Svetlana>'warning: /dev/sda6 not found' iirc
<civodul>ah, ok
<civodul>that's fine
<civodul>yes, it's from partition-label-predicate
<civodul>Svetlana: normally the kernel message that says that the USB thing was detected is preceded by a timestamps like [12.4324345435]; what is that timestamp for you?
*civodul goes for lunch
<Svetlana>will check (I should probably start taking pictures :)
<Svetlana>16.57 apparently (http://gnu.svetlana.fastmail.com.au/guix/#single:IMG_0098.jpg)
<civodul>Svetlana: indeed, 16 seconds, that's a lot more than i'd expect
<civodul>we can increase the timeout to 20s, then
<Svetlana>ack
<civodul>thanks for the screenshots, BTW
<alezost>civodul: should I mention all new files in a commit message (like "* emacs/guix.el: New file." for each one)
<civodul>alezost: yes
<civodul>you can check standards.info for details
<civodul>alezost: another thing for your to-do list ;-) : after 'guix pull', you'd have to restart the Guile process, so that it can actually load the new (gnu packages ...) modules
<alezost>civodul: ok, thanks, I think in the worst case the new branch may be deleted
<alezost>civodul: yes, for every action Outside "Guix REPL", it needs to be restarted
<civodul>after 'guix pull' you mean, right?
<civodul>also a 'u' binding in the package list, to mark for upgrading
<civodul>and 'U' to the installed package list, to mark all obsolete packages for upgrading
<civodul>ok i'll stop now :-)
<alezost>civodul: and what about unmarking?
<civodul>ah right
<civodul>or C-u u
<civodul>dunno
<civodul>something like that
<civodul>this is starting to look really nice, i like it
<alezost>that's why I didn't bind u/U for upgrading: because I don't know where to move unmarking
<civodul>i would use U for unmarking, no?
<civodul>aah, no
<civodul>hmm
<civodul>key bindings are a difficult issue ;-)
<alezost>anyway all keybindings may be modified by a user
<civodul>yes
<civodul>but getting the defaults right is important, IMO
<alezost>civodul: surely, I think we may raise that question on ML later
<alezost>I mean when there will be more than 2 users :)
<civodul>yup :-)
***Basstard1 is now known as Basstard`
<alezost>civodul: I have pushed the branch and sent a message to guix-devel
<alezost>civodul: about "guix pull": do you mean there is a way to reread (gnu packages ...) without restarting a REPL?
<civodul>alezost: i mean there is *no* way to reread (gnu packages ...) without restarting the REPL
<civodul>well, that's not completely true, but still
<alezost>civodul: hm, so what was you suggestion? To restart it automatically somehow?
<civodul>alezost: yes: if/when there's a "guix pull" command in guix.el, call geiser-restart-repl or something like that once it has completed
<alezost>civodul: but there is no support for "guix pull" in guix.el (how did you do that?), besides a user may run "guix pull" in a console (I mean outside geiser REPL)
<civodul>alezost: yes, so that remark is for when there is support for "guix pull" in guix.el
<civodul>it's a reminder for the future
<civodul>:-)
<alezost>civodul: ok :) noted
*alezost thinks it would be great to add davexunit's web interface to guix repo as well
<civodul>+1