Date: Tue, 14 Feb 2012 18:18:35 +0100 From: rank1seeker@gmail.com To: hackers@freebsd.org Subject: 9.0 observations Message-ID: <20120214.171835.987.1@DOMY-PC> In-Reply-To: <CAMBSHm9tsHAy%2BWPCzTkhk_Z2h%2Bw83LvuOM%2BxPmu%2B%2B4_n--y-6w@mail.gmail.com> References: <20120119005658.218280@gmx.com> <alpine.BSF.2.00.1201191511470.19710@kozubik.com> <4F19188A.4090907@herveybayaustralia.com.au> <4F213CEB.4020207@herveybayaustralia.com.au> <alpine.BSF.2.00.1202082202530.19710@kozubik.com> <CAMBSHm9tsHAy%2BWPCzTkhk_Z2h%2Bw83LvuOM%2BxPmu%2B%2B4_n--y-6w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--------=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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120214.171835.987.1>