El día Sunday, June 17, 2012 a las 09:16:12PM -0600, Warren Block escribió:
On Sat, 16 Jun 2012, Matthias Apitz wrote:
OK, but I wanted to have most of the space of the 4 GB SSD encrypted
with geli(8); so I should make there some slice containing /boot
(unencrypted) and a second slice
future disk layout.
/dev/ada0p1freebsd-boot
/dev/ada0p2freebsd-ufs /boot 256 Mbyte
/dev/ada0p3freebsd-ufs /private 3.5 GByte (geli encrypted)
over 200 MB wasted for /boot. what do you want to but there?
except this it is all right.
/dev/ada1p1freebsd-boot
/dev/ada1p2
On Tue, 19 Jun 2012, Matthias Apitz wrote:
El día Sunday, June 17, 2012 a las 09:16:12PM -0600, Warren Block escribió:
On Sat, 16 Jun 2012, Matthias Apitz wrote:
OK, but I wanted to have most of the space of the 4 GB SSD encrypted
with geli(8); so I should make there some slice containing
OK, but I wanted to have most of the space of the 4 GB SSD encrypted
with geli(8); so I should make there some slice containing /boot
(unencrypted) and a second slice which later will contain my HOME and
encrypted; wrong?
right.
but do not forget bootloader requires things to be in /boot
On Sat, 16 Jun 2012, Matthias Apitz wrote:
OK, but I wanted to have most of the space of the 4 GB SSD encrypted
with geli(8); so I should make there some slice containing /boot
(unencrypted) and a second slice which later will contain my HOME and
encrypted; wrong?
That's correct:
El día Wednesday, May 30, 2012 a las 07:44:37PM +0200, Wojciech Puchar escribió:
from; one has to go (by pressing ESC) to the boot menu to pick it up as
current boot device; any idea how this could be changed?
boot from 4GB. just put /boot here and add
vfs.root.mountfrom=ufs:XXX
And PLEASE DO NOT make this stupid MSDOS style slices. It is not just
unneeded but introduces mess and only mess.
just have /dev/ad0a not /dev/ad0s1a
What FreeBSD devs have to say about this?
;)
OK, but I wanted to have most of the space of the 4 GB SSD encrypted
with geli(8); so I
On Jun 16, 2012 8:26 PM, rank1see...@gmail.com wrote:
And PLEASE DO NOT make this stupid MSDOS style slices. It is not just
unneeded but introduces mess and only mess.
just have /dev/ad0a not /dev/ad0s1a
What FreeBSD devs have to say about this?
;)
I say we have GPT this decade
...
# geli attach /dev/md1
Enter passphrase:
# dd if=/dev/md1.eli of=/dev/null bs=128k count=4k
536868864 bytes transferred in 35.093015 secs (15298454 bytes/sec)
# dd if=/dev/zero of=/dev/md1.eli bs=128k count=4k
536868864 bytes transferred in 38.044995 secs (14111419 bytes/sec)
# geli detach
El día Wednesday, May 30, 2012 a las 07:44:37PM +0200, Wojciech Puchar escribió:
Concerning your hint installing the systen on the second SSD of around
16 GByte (marketing GBytes :-)), the BIOS by itself is unable to boot
right. 16 billion bytes.
A simple marketing trick to cheat you for
Concerning your hint installing the systen on the second SSD of around
16 GByte (marketing GBytes :-)), the BIOS by itself is unable to boot
right. 16 billion bytes.
A simple marketing trick to cheat you for 7.6%
I think, it's only 7.3%
$ bc
(16*1024*1024*1024-160)/160*100
El día Saturday, May 26, 2012 a las 04:01:54PM +0200, Wojciech Puchar escribió:
Why? Your laptop have most probably slow CPU and it will make everything
too slow if you make everything encrypted.
I'd suggest some experiments - create a largish RAMdisk with and without
GELI and see how
Why? Your laptop have most probably slow CPU and it will make everything
too slow if you make everything encrypted.
I'd suggest some experiments - create a largish RAMdisk with and without
GELI and see how the performance compares (this will be a lot faster than
converting your SSD as well as
On 26 May 2012 15:01, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote:
Why? Your laptop have most probably slow CPU and it will make everything
too slow if you make everything encrypted.
I'd suggest some experiments - create a largish RAMdisk with and without
GELI and see how the
use tmpfs and don't fear to add /var/tmp to it.
I would fear to add /var/tmp-- /var/tmp should persist across reboots.
Chris
as i noted - check your case.in my case it is not a problem. it your it
may.
Never blindly follow rules, good practices etc..
On 26 May 2012 16:04, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote:
use tmpfs and don't fear to add /var/tmp to it.
I would fear to add /var/tmp-- /var/tmp should persist across reboots.
Chris
as i noted - check your case.in my case it is not a problem. it your it may.
Never
On 5/24/12 5:35 AM, Warren Block wrote:
On Wed, 23 May 2012, Tim Kientzle wrote:
On May 22, 2012, at 7:40 AM, Warren Block wrote:
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Tuesday, May 22, 2012 a las 07:42:18AM -0600, Warren Block
escribió:
On Tue, 22 May 2012, Matthias Apitz
On 2012-May-18 22:54:43 +0200, Dimitry Andric d...@freebsd.org wrote:
Be sure to use -t enable when creating the filesystem:
Only if your SSD supports TRIM. Some consumer-grade SSDs don't and
get very confused if sent TRIM commands.
mine do.
___
- Original Message -
From: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
On 2012-May-18 22:54:43 +0200, Dimitry Andric d...@freebsd.org wrote:
Be sure to use -t enable when creating the filesystem:
Only if your SSD supports TRIM. Some consumer-grade SSDs don't and
get very
mine do.
The disk also has be be connected to a disk arch which supports
BIO_DELETE which ATM is only ata unless your running HEAD which
also has support in da
FreeBSD 9 support it and it do works.
___
freebsd-hackers@freebsd.org mailing list
El día Saturday, May 19, 2012 a las 08:09:01PM +0200, Matthias Apitz escribió:
My EeePC netbook shows for the two SSD:
$ uname -a
FreeBSD tiny 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r226986: Tue Nov 1
14:27:40 CET 2011 guru@caracas:/usr/obj/usr/src/sys/GENERIC i386
$ gpart show
...
Talking about another question, related to file systems on SSD:
My netbook with the two SSD has file systems mounted as:
$ df -kh
Filesystem SizeUsed Avail Capacity Mounted on
/dev/ada0s1a3.7G567M3.1G15%/
/dev/ada1s1a 14G8.7G5.9G60%/usr/local
On Fri, 25 May 2012, Matthias Apitz wrote:
Talking about another question, related to file systems on SSD:
My netbook with the two SSD has file systems mounted as:
$ df -kh
Filesystem SizeUsed Avail Capacity Mounted on
/dev/ada0s1a3.7G567M3.1G15%/
/dev/ada1s1a
On 2012-May-25 22:46:10 +0200, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
wrote:
Should I split /dev/ada1 into two separate partitions, one for real
/usr/local and one for my HOME and only crypt this with geli(8)?
i would make / on 16GB SSD (including /usr, /usr/local, don't divide
to
-Original Message-
From: owner-freebsd-hack...@freebsd.org
[mailto:owner-freebsd-hack...@freebsd.org] On Behalf Of Tim Kientzle
Sent: Thursday, May 24, 2012 12:49 AM
To: Warren Block
Cc: freebsd-hackers@freebsd.org; Matthias Apitz
Subject: Re: proper newfs options for SSD disk
On Wed, 23 May 2012, Tim Kientzle wrote:
On May 22, 2012, at 7:40 AM, Warren Block wrote:
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Tuesday, May 22, 2012 a las 07:42:18AM -0600, Warren Block escribió:
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Sunday, May 20, 2012 a las
On 2012-May-18 22:54:43 +0200, Dimitry Andric d...@freebsd.org wrote:
Be sure to use -t enable when creating the filesystem:
Only if your SSD supports TRIM. Some consumer-grade SSDs don't and
get very confused if sent TRIM commands.
--
Peter Jeremy
pgp2LuXn5iRWb.pgp
Description: PGP
On May 22, 2012, at 7:40 AM, Warren Block wrote:
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Tuesday, May 22, 2012 a las 07:42:18AM -0600, Warren Block escribió:
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Sunday, May 20, 2012 a las 03:36:01AM +0900, rozhuk...@gmail.com
El día Sunday, May 20, 2012 a las 03:36:01AM +0900, rozhuk...@gmail.com
escribió:
My EeePC netbook shows for the two SSD:
$ uname -a
FreeBSD tiny 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r226986: Tue Nov 1
14:27:40 CET 2011 guru@caracas:/usr/obj/usr/src/sys/GENERIC i386
$ gpart
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Sunday, May 20, 2012 a las 03:36:01AM +0900, rozhuk...@gmail.com
escribió:
Do not use MBR (or manually do all to align).
63 - not 4k aligned.
To create the above shown partition layout I have not used gpart(8); I
just said:
# fdisk -I
El día Tuesday, May 22, 2012 a las 07:42:18AM -0600, Warren Block escribió:
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Sunday, May 20, 2012 a las 03:36:01AM +0900, rozhuk...@gmail.com
escribió:
Do not use MBR (or manually do all to align).
63 - not 4k aligned.
To create
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Tuesday, May 22, 2012 a las 07:42:18AM -0600, Warren Block escribió:
On Tue, 22 May 2012, Matthias Apitz wrote:
El día Sunday, May 20, 2012 a las 03:36:01AM +0900, rozhuk...@gmail.com
escribió:
Do not use MBR (or manually do all to
What is wrong with this procedure?
The filesystem partitions end up at locations that aren't even multiples of
4K. This can reduce performance. How much probably depends on the SSD.
well in my case it is a multiply of any number you like
[root@wojtek ~]# bsdlabel ada0
# /dev/ada0:
8
You may be able to find the exact erase block size in the technical
documentation of your specific SSD. But the manufacturers don't always
tell. :)
b) small fragments (like 1KB) to reduce space usage, as there is no
seeking so it will not slow down but save space on relatively small SSD
I
El día Saturday, May 19, 2012 a las 10:40:32AM +0200, User Wojtek escribió:
You may be able to find the exact erase block size in the technical
documentation of your specific SSD. But the manufacturers don't always
tell. :)
...
Hi,
Some weeks ago in the context of Openmoko (my Linux
El día Sunday, May 20, 2012 a las 03:00:46AM +0900, rozhuk...@gmail.com
escribió:
Partition must be aligned to:
# gpart show
= 34 62533229 ada0 GPT (29G)
34 6- free - (3.0k) - for align
40 512 1 freebsd-boot (256k) - size 4k aligned
My EeePC netbook shows for the two SSD:
$ uname -a
FreeBSD tiny 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r226986: Tue Nov 1
14:27:40 CET 2011 guru@caracas:/usr/obj/usr/src/sys/GENERIC i386
$ gpart show
= 63 7880481 ada0 MBR (3.8G)
63 7880481 1 freebsd [active]
what are proper settings
a) 4kB fragments so everything is 4k aligned? SSD drives itself reports
as 512 byte blocks, but it is recomenned constantly on many places about
4K alignment for SSD.
b) small fragments (like 1KB) to reduce space usage, as there is no
seeking so it will not slow
On 2012-05-18 22:11, User Wojtek wrote:
what are proper settings
a) 4kB fragments so everything is 4k aligned? SSD drives itself reports
as 512 byte blocks, but it is recomenned constantly on many places about
4K alignment for SSD.
That 4k alignment is most likely meant for so-called
39 matches
Mail list logo
