X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail.wtbts.no (mail.wtbts.no [213.234.126.131]) by lists.alpinelinux.org (Postfix) with ESMTP id D691720C847 for ; Mon, 2 May 2011 16:26:34 +0000 (UTC) Received: from localhost (bsna.nor.wtbts.net [127.0.0.1]) by mail.wtbts.no (Postfix) with ESMTP id B3DF4AE4002; Mon, 2 May 2011 16:26:33 +0000 (UTC) X-Virus-Scanned: Yes Received: from mail.wtbts.no ([127.0.0.1]) by localhost (bsna.nor.wtbts.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1fuaESYVWTZl; Mon, 2 May 2011 16:26:32 +0000 (UTC) Received: from mail.ytre.org (extmail.nor.wtbts.net [10.65.72.14]) by mail.wtbts.no (Postfix) with ESMTP id 7BB0EAE4001; Mon, 2 May 2011 16:26:32 +0000 (UTC) Received: from mail.ytre.org (localhost [127.0.0.1]) by mail.ytre.org (Postfix) with ESMTP id 43A33621BD355; Mon, 2 May 2011 16:26:32 +0000 (UTC) Received: from ncopa-desktop.nor.wtbts.net (unknown [10.65.65.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ncopa@ytre.org) by mail.ytre.org (Postfix) with ESMTPSA id ED12F621BD354; Mon, 2 May 2011 16:26:31 +0000 (UTC) Date: Mon, 2 May 2011 18:23:18 +0200 From: Natanael Copa To: jeremy@thomersonfamily.com Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Alpine 2.2 Release Candidate 2 Message-ID: <20110502182318.64a36618@ncopa-desktop.nor.wtbts.net> In-Reply-To: References: <20110429170228.2e7eabdc@ncopa-desktop.nor.wtbts.net> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.0; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP On Fri, 29 Apr 2011 11:18:26 -0400 Jeremy Thomerson wrote: > ncopa and list, > > I installed RC1 last night on a newly-built home file server. Here > are some things I noticed or had questions about: > > First, a little general info. I was building on a mini-itx Intel > motherboard / CPU combo, with a single 2TB drive that I wanted to be > data-only. I couldn't get it to boot from a card reader / SD card > combo, but I think that's probably a bios thing. I booted from a USB > thumb drive. I ran setup-alpine immediately after booting the first > time. I tried using the setup-disk that runs at the end of > setup-alpine to configure my disk. I wanted to run from ram, from > the USB thumbdrive, and use the HD for data-only, mostly just file > storage. > > 1. I was surprised that when setup-disk ran, it didn't show me any > attributes of the disk to help me pick the right one. It just > asks you to pick a disk (in my case sda or sdf) and you will erase > everything. Showing me the disk size or name would have helped > tremendously to make sure that I picked the HD and not the USB drive. USB drive should not show up as "available". But you are right, we need info about the disks you can chose between. Should been fixed here: http://git.alpinelinux.org/cgit/alpine-conf.git/commit/?id=7e49567801ddc247abfd436c763649b2019c4784 > 2. There's a minor typo in setup-disk. It said "used for either > traditional disk install data-only". It appears to be missing the > word "or" > 3. When running setup-disk, got the following error: "Can't > open /usr/share/syslinux/mbr.bin" Perhaps syslinux isn't installed > by default? > 4. setup-disk failed altogether for me. mkfs dumped it's > usage screen as if it had bad parameters sent to it. Should been fixed now. > 5. Setting up the repos was really slick! But, (extremely minor), > it ended up with a double forward slash. This doesn't seem to affect > anything, and I just manually removed it. ugh.. forgot this one. > 6. lbu commit gives you the option of usb or sda. But on mine, I > have to use "usbdisk", even though /etc/fstab says that the mount is > "usb" (for some reason, despite /etc/fstab saying /dev/usb > and /media/usb, my usb thumb drive shows up in /media/usbdisk) I think thats due to syslinux.cfg. Try use alpine_dev=usb in syslinux.cfg > > That's what I noticed. Most are extremely minor. My box will not > reboot at all. If I issue "reboot", it will halt, but not power > cycle. I'm going to try to investigate that more this weekend. dunno what this is. > Can I just do "apk update; apk upgrade" to get to RC2? since you boot from usb, no. try: setup-bootable -u http://$mirror/alpine/v2.2/releases/..../alpine.iso 2.2.0_rc3 is building as we speak -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---