From nobody Fri Mar 29 15:06:40 2024 X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by lists.alpinelinux.org (Postfix) with ESMTP id 319033617A1A for ; Wed, 26 May 2010 14:45:43 +0000 (UTC) Received: by fxm17 with SMTP id 17so1834794fxm.13 for ; Wed, 26 May 2010 07:45:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=cUjOPwb8uxH8+Fv5OkaIrqj1yBNWFhpwU+QEjiD4CGI=; b=Q3nqlxpuO0KXFJHNn/dFukKLaGKCR8EGR1Is4gUiU2xd+OH8r9ozXN/MZzDw+4MYZ2 zoo7VGmtFpg0e2R8oIbFIFJyooLqt+iYIXO1gCY+cxTAXX+8uQPP7sADP8/UsPlQ0OaW ujYzCaLtfhLC2+T9SU3HpNUTzHcajE6JCCxH0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=GnHDPcCkgc0HaRkMH+2YBF2fhj3QUBdx9sb0/1qagE92X70TlYm03g1zWnEsO0SAnF bDyjC25W5cpq07t0sNo/Q2+xfoomyPeimVMH/DNIeWPRzW+qTSJx2fCGtgRw7G6yfeLv 2sxRV4HhwSBpGkDyOzZ7sRnZC2o4fSG2euCLA= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.204.5.132 with SMTP id 4mr3195998bkv.69.1274885141494; Wed, 26 May 2010 07:45:41 -0700 (PDT) Received: by 10.204.71.16 with HTTP; Wed, 26 May 2010 07:45:41 -0700 (PDT) Date: Wed, 26 May 2010 16:45:41 +0200 Message-ID: Subject: [alpine-devel] improving setup-bootable-usb From: Natanael Copa To: Alpine Developers Content-Type: text/plain; charset=ISO-8859-1 Hi, I have renamed the setup-booable-usb tool to setup-bootable. (anyone ever used that tool btw?) I have also made some modifications to it. It can now take any (1.10.x? and newer) iso, or mounted cdrom and make a CF, harddisk or usb stick bootable from that. For example: # boot cdrom, insert usb and make it bootable: setup-bootable /media/cdrom /dev/usbdisk # make bootable CF from iso image. this will chage syslinux.cfg to use alpine_dev=sdb1:vfat setup-bootable alpine-vserver-1.10.3-x86.iso /dev/sdb1 It can also upgrade an already existing install. This will keep existing syslinux.cfg. For example: # upgrade mounted CF which we booted from, using iso image, with verbose output setup-bootable -u -v alpine-1.10.3-x86.iso /media/sda1 The upgrade process will do this: * create a temp direcotry .new on target * copy all files from iso to .new * sync, so we know files are there. * create a temp .old directory on target * move existing files/dirs to .old: boot, apks, .alpine-version * move .new files to .. * remove .old * sync and cleanup The idea is to try keep system bootable even if somethign goes wrong during the way (power failuer whatever). Its only after the first sync, while doing the renames, that things are critical. This is a very short and fast operation so chances are relatively small that things goes wrong. The setup-bootable wil be shipped with alpine-conf-2.4 (edge) but I made it available on http://dev.alpinelinux.org/~ncopa/alpine/setup-bootable (It is ofcourse also available from http://git.alpinelinux.org/cgit/alpine-conf/ ) Feedback is welcome. -- Natanael Copa --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---