From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John D. Boy" Subject: Installing GuixSD over existing system resulting in strange behavior Date: Tue, 22 Oct 2019 20:51:26 +0000 Message-ID: <5653d0cf-b932-4a71-889d-f83729b04da2@www.fastmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:48491) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iN18C-0002QX-3c for help-guix@gnu.org; Tue, 22 Oct 2019 16:51:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iN18A-0000AO-Rp for help-guix@gnu.org; Tue, 22 Oct 2019 16:51:51 -0400 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]:49857) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iN18A-00009s-A6 for help-guix@gnu.org; Tue, 22 Oct 2019 16:51:50 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 97333391 for ; Tue, 22 Oct 2019 16:51:47 -0400 (EDT) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org I am trying to upgrade (or "lustrate" as the NixOS people say) a Debian system running on a virtual server, roughly following existing guides by wingo and ng0. I documented how I went about this here: https://gist.github.com/jboynyc/ef312a686749de693dddc4f3a657a919 As I write in that document, initialization of GuixSD over the Debian system seems to work, and I am even able to log into the system with ssh using the provided key. Once I start doing something with the system, however, I start getting strange "No such file or directory" errors about the guix command, sshd, and any other binary I attempt to run. Booting from a live CD and poking around on the disk shows that files are in fact present in the file system. I have re-run the install at least five times, and each time I end up with the system in an unusable state. Any ideas what might be happening?