From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 14 17:18:39 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06450106566C for ; Tue, 14 Feb 2012 17:18:39 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 788038FC22 for ; Tue, 14 Feb 2012 17:18:38 +0000 (UTC) Received: by lagz14 with SMTP id z14so257816lag.13 for ; Tue, 14 Feb 2012 09:18:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; bh=+Mh/kPBhr04RrijKjN39HH5NVCHfhtfKuxKl+NXxz/I=; b=kADCn2gaobv97Q5Ug0UZ/1SouFFpU/WVkOCWtE9kmFJkTueiHLa2fUYUCNA+tAI41V aJoZ73saG8+Tvach4pwIA8vfJ3SXDvFVp3eFFtSFdMc7WQ4gk5YVlDwjzTTZz7A7hQuk JQDvmlJr0+0EoaVKLgk31xix/9a4qGpBfhnJo= Received: by 10.152.108.49 with SMTP id hh17mr15145379lab.0.1329239917229; Tue, 14 Feb 2012 09:18:37 -0800 (PST) Received: from DOMYPC ([82.193.208.173]) by mx.google.com with ESMTPS id mc3sm16792698lab.12.2012.02.14.09.18.33 (version=SSLv3 cipher=OTHER); Tue, 14 Feb 2012 09:18:35 -0800 (PST) Message-ID: <20120214.171835.987.1@DOMY-PC> From: rank1seeker@gmail.com To: hackers@freebsd.org Date: Tue, 14 Feb 2012 18:18:35 +0100 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20120119005658.218280@gmx.com> <4F19188A.4090907@herveybayaustralia.com.au> <4F213CEB.4020207@herveybayaustralia.com.au> X-Mailer: POP Peeper (3.8.1.0) Cc: Subject: 9.0 observations X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2012 17:18:39 -0000 --------=0D=0AOpenSSH:=0D=0A--------=0D=0AAfter taking advantage of new = 'KexAlgorithms'=0D=0A# sshd -T | grep KexAlgorithms=0D=0A will never = show it ...=0D=0A=0D=0A=0D=0A-----=0D=0AWiFi:=0D=0A-----=0D=0A'media = OFDM/54Mbps' breaks setup (supplied to 'ifconfig = wlan0').=0D=0A'ucastrate' and 'mcastrate' will set it = instead.=0D=0A=0D=0A=0D=0A-----=0D=0Agpart=0D=0A-----=0D=0A=0D=0AOn a MD = vnode bassed image, of size:=0D=0A=0D=0A1g or 2g:=0D=0A # gpart create = -s MBR md0=0D=0A Will create starting offset at 63 = sector=0D=0A=3D> 63 2097089 md0 MBR (1.0G)=0D=0A=3D> 63 = 4194241 md0 MBR (2.0G)=0D=0A=0D=0A1432m:=0D=0A # gpart create -s = MBR md0=0D=0A Will create starting offset at 33 sector=0D=0A=3D> = 33 2932703 md0 MBR (1.4G)=0D=0A=0D=0A=0D=0ANOW, looking at this new = interesting alignment flag (-a 4k) ...=0D=0AI started to add slices with = it and taking into consideration BOTH above cases, all it really does = under MBR, is it takes INITIAL offset and simply STAMPS it between = slices, making NONE to align(nor to offset, nor to size =3D> = mess!):=0D=0A1g or 2g:=0D=0A 63 63 - free - = (31k)=0D=0A1432m:=0D=0A 33 33 - free - = (16k)=0D=0A=0D=0A=0D=0AHowever, with GPT, all is stable:=0D=0A# gpart = create ... always sets offset to 34, regardless of img size=0D=0AAnd (-a = 4k) properly modifies BOTH slice's 'offset' and 'size', to be divisable = with 8, without residue(=3D0)=0D=0A=0D=0AIn case:=0D=0A--=0D=0A# gpart = show -p md0=0D=0A=3D> 34 2932669 md0 GPT (1.4G)=0D=0A 34 = 1024 md0p1 freebsd-boot (512k)=0D=0A 1058 6 - = free - (3.0k)=0D=0A 1064 501760 md0p2 freebsd-ufs = (245M)=0D=0A--=0D=0A6 sectors were added in favor of aligning md0p2's = offset=0D=0AHere I have a question. Is it true that FIRST slice, should = always start at 1Mb offset (-b 1M) and why?=0D=0AShould I use (-b 1M) for = first and (-a 4k) for all other added slices?=0D=0A=0D=0A=0D=0AFinally, = taking into consideration first MBR alignment issues.=0D=0AHow should one = proceed if he wants to put MBR on 4k sector = disk?=0D=0A=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6=0D=0A