On Fri, 6 Jul 2012, Polytropon wrote:
For maximum security, you can use the "old" approach of
using fdisk + disklabel (creating slice, creating partitions
within slice). This also delivers most compatibility for
other systems, if it should be needed, e. g. in a multiboot
environment.
gpart(8)
I went through this exercise to determine if there were boundary
issues installing FreeBSD on disks. I concluded that FreeBSD was
indeed installing at head boundaries. A colleague then pointed me to
http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html
which calls into question
On 07/06/2012 09:06 PM, Michael Sierchio wrote:
On Fri, Jul 6, 2012 at 11:58 AM, Eitan Adler wrote:
Slices isn't the "old" way. There is no perf advantage for dedicated
disks. Maybe you get a
few kb of extra space. Don't do it.
http://www.unixguide.net/freebsd/faq/09.03.shtml
That is EXTREME
On Fri, Jul 6, 2012 at 11:58 AM, Eitan Adler wrote:
> Slices isn't the "old" way. There is no perf advantage for dedicated
> disks. Maybe you get a
> few kb of extra space. Don't do it.
>
> http://www.unixguide.net/freebsd/faq/09.03.shtml
That is EXTREMELY old advice. The general advice, for th
On Fri, 6 Jul 2012 11:58:03 -0700, Eitan Adler wrote:
> On 6 July 2012 11:44, Rick Miller wrote:
> > Thanks for this explanation.
> >
> > Is there any performance advantage to using a "dedicated disk" layout
> > over the old way of creating a slice and having your partitions within
> > it?
>
> Sl
> Hi i want to ask a question about the new release of FreeBSD (9) is it
> posible to run this release /whit GUI/ in IBM Thinkpad 1161 217 whit this
> specs 500 mhz Intel Celeron processor 64mb Ram and 5gb HDD
I've been using even slower Thinkpads (300MHz), there are a few things
to be aware of.
On 6 July 2012 11:44, Rick Miller wrote:
> Thanks for this explanation.
>
> Is there any performance advantage to using a "dedicated disk" layout
> over the old way of creating a slice and having your partitions within
> it?
Slices isn't the "old" way. There is no perf advantage for dedicated
dis
[snip]
>> I think Ryan means partition and not slice?
>> I would not recommend no slices at all, It's deprecated to use
>> "dangerously dedicated disks"
>
> First of all, it's "dedicated disks", there's nothing dangerous
> related. :-)
>
> If you are using the MBR approach ("old way"), you can do
On 07/06/2012 08:25 PM, Polytropon wrote:
On Fri, 06 Jul 2012 19:47:27 +0200, Bas Smeelen wrote:
On 07/06/2012 07:28 PM, Robert Huff wrote:
Ryan Coleman writes:
> Anyway just don't make slices at all if your disk is dedicated
> to FreeBSD
Except for swap, right?
Why do y
On 07/06/2012 07:25 PM, Walter Hurry wrote:
On Fri, 06 Jul 2012 18:55:27 +0200, Bas Smeelen wrote:
Are you root when mounting on the client?
From looking at your prompt # I think you are, but I ask just to make
sure.
You can also take a look at
http://www.freebsd.org/doc/en_US.ISO8859-1/boo
On Fri, 06 Jul 2012 19:47:27 +0200, Bas Smeelen wrote:
> On 07/06/2012 07:28 PM, Robert Huff wrote:
> > Ryan Coleman writes:
> >
> >> > Anyway just don't make slices at all if your disk is dedicated
> >> > to FreeBSD
> >>
> >> Except for swap, right?
> > Why do you say that?
> >
> >
>
On Fri, Jul 6, 2012 at 8:10 AM, Michael Ross wrote:
> Hi,
>
> the manpage says for ``gmirror label'':
>
> The order of components is important,
> because a component's priority is based on its position
> (starting from 0 to 255).
>
>
> so I would expect to have different p
I think Ryan means partition and not slice?
I would not recommend no slices at all, It's deprecated to use "dangerously
dedicated disks"
Starting with 9 I don't see slices in mount ouput anymore but still there are
FreeBSD partitions in slices (which is a partitions in dos terms)
Example / is
Anyway just don't make slices at all if your disk is dedicated to FreeBSD
Except for swap, right?
wrong.
i said slices (==DOS/Windoze MBR partitions), not disklabel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
On Fri, Jul 6, 2012 at 11:19 AM, Ryan Coleman wrote:
> Sector 64 is sector 63 when you start at 0.
OMG, so right...I cannot believe that went over my head! Thanks for
pointing it out. It lets me know that diskPartitionEditor is
automatically selecting start and end sectors at boundaries. Thank
On 07/06/2012 07:28 PM, Robert Huff wrote:
Ryan Coleman writes:
> Anyway just don't make slices at all if your disk is dedicated
> to FreeBSD
Except for swap, right?
Why do you say that?
Robert huff
I think Ryan means partition and not sl
On Fri, 06 Jul 2012 18:55:27 +0200, Bas Smeelen wrote:
> Are you root when mounting on the client?
> From looking at your prompt # I think you are, but I ask just to make
> sure.
> You can also take a look at
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-
nfs.html
> in the
Ryan Coleman writes:
> > Anyway just don't make slices at all if your disk is dedicated
> > to FreeBSD
>
> Except for swap, right?
Why do you say that?
Robert huff
___
freebsd-questions@freebsd.org ma
On Fri, 06 Jul 2012 12:42:02 -0400, kpneal wrote:
> On Fri, Jul 06, 2012 at 04:03:27PM +, Walter Hurry wrote:
>> I am running FreeBSD 9.0-RELEASE (64 bit), with a VirtualBox VM also
>> running the same.
>>
>> On the host I am running NFS server:
>>
>> $ showmount -e Exports list on localhost
On 07/06/2012 06:03 PM, Walter Hurry wrote:
I am running FreeBSD 9.0-RELEASE (64 bit), with a VirtualBox VM also
running the same.
On the host I am running NFS server:
$ showmount -e
Exports list on localhost:
/usr/home Everyone
But when I try to mount is on the client
On Fri, Jul 6, 2012 at 6:44 PM, Wojciech Puchar
wrote:
>>> Not had tme to pursued it though.
>>> & I dont feel like exporting that data public
>>> in case its already gone too far.
>>
>>
>> You don't have to export it at all.
>> Can you confirm the data within is the same as say the same
>> file i
On 7/6/2012 11:43 AM, Wojciech Puchar wrote:
automatically start partitions at head boundaries? The reason I ask
is because I am most familiar with sector 64 being the start of a head
boundary as opposed to 63. Is my understanding incorrect?
yes. 63 is normal.
Anyway just don't make slices at
Not had tme to pursued it though.
& I dont feel like exporting that data public
in case its already gone too far.
You don't have to export it at all.
Can you confirm the data within is the same as say the same
file in /etc or ~/.ssh? If that's really the case, it's a problem.
the real problem i
automatically start partitions at head boundaries? The reason I ask
is because I am most familiar with sector 64 being the start of a head
boundary as opposed to 63. Is my understanding incorrect?
yes. 63 is normal.
Anyway just don't make slices at all if your disk is dedicated to FreeBSD
I am running FreeBSD 9.0-RELEASE (64 bit), with a VirtualBox VM also
running the same.
On the host I am running NFS server:
$ showmount -e
Exports list on localhost:
/usr/home Everyone
But when I try to mount is on the client (the VM guest) I get this:
# mount xx:/
On Wed, Jul 04, 2012 at 11:27:44PM +0100, RW wrote:
> On Wed, 4 Jul 2012 22:34:21 +0200
> Actually Opera already has a setting: "Enable plug-ins only on
> demand" (under preferences->advanced->content). It disables all
> plugins by default and you can click on an individual placeholder to
>
On Fri, Jul 6, 2012 at 5:02 PM, Carmel wrote:
> I am running FreeBSD-8.3 STABLE amd64. I continually see this error
> message in the "/var/log/messages" file:
>
> (npviewer.bin): syscall pipe2 not implemented
>
> The program crashes continually also. I have tried doing an R&R without
> favorable
Carmel writes:
> I am running FreeBSD-8.3 STABLE amd64. I continually see this
> error message in the "/var/log/messages" file:
>
> (npviewer.bin): syscall pipe2 not implemented
>
> The program crashes continually also. I have tried doing an R&R
> without favorable results. Does anyone h
Hi All,
Installing FreeBSD 8.x I select "A" at the fdisk partition editor to
use the entire disk. It creates an unused slice with offset 0 and 63
sectors in size. Then partition 1 starts at sector 63 and utilizes
the remaining disk space. Does sysinstall's diskPartitonEditor macro
automatically
I am running FreeBSD-8.3 STABLE amd64. I continually see this error
message in the "/var/log/messages" file:
(npviewer.bin): syscall pipe2 not implemented
The program crashes continually also. I have tried doing an R&R without
favorable results. Does anyone have any idea what the problem might be
Hi,
the manpage says for ``gmirror label'':
The order of components is important,
because a component's priority is based on its position
(starting from 0 to 255).
so I would expect to have different priorities for the components,
yet both are listed with a priority of
On Fri, Jul 6, 2012 at 2:42 AM, Julian H. Stacey wrote:
> Hi,
> Reference:
>> From: Carsten Mattner
>> Date: Fri, 6 Jul 2012 00:28:32 +0200
>> Message-id:
>>
>
> Carsten Mattner wrote:
>> On Thu, Jul 5, 2012 at 4:39 PM, Wojciech Puchar
>> wrote:
>> >>> As for reading anything
Tnx!
Worked like a charm, with skipped init and other checks, just the
control point parts:
<...>
int optval=1;
setsockopt(root_socket, IPPROTO_IP, IP_RECVDSTADDR,
&optval, sizeof(optval))
<...>
char t[200];
unsigned int sender_len;
On Fri, 06 Jul 2012 04:05:36 -0400, Thomas Mueller wrote:
> On part 1, it might be possible to build things on the old
> machine, but only little things.
It _will_ work, it just will take some time. If that isn't
a major concern -- no problem. If the machine is low on RAM,
there should at least be
On Thu, 5 Jul 2012 22:00:11 +0300 (EEST), Ivan Ivanov wrote:
> Hi i want to ask a question about the new release of FreeBSD (9)
> is it posible to run this release /whit GUI/ in IBM Thinkpad 1161
> 217 whit this specs 500 mhz Intel Celeron processor 64mb Ram and
> 5gb HDD
Polytropon responded:
>
1. You won't be able to build things from source on that
machine. Consider using packages for installation, or a
second system to build and export (via NFS) the data required.
You can but... too slow
3. For using your applications within the GUI, choose a
good window manager, e. g. FVWM or XFC
36 matches
Mail list logo