Pawel Jakub Dawidek wrote
in <20120628230725.gb1...@garage.freebsd.pl>:
pj> PS. We are discussing two totally different things here:
pj> 1. Is placing GPT on anything but raw disk violates the spec? I can
pj>agree that it does and I'm happy with gpart(8) growing a warning.
I agree that th
On Jun 28, 2012, at 4:07 PM, Pawel Jakub Dawidek wrote:
>>
>> I would be having less problems if the mirroring didn't force the backup
>> GPT header in anything but the last sector. [...]
>
> GPT backup header is placed in the last sector of the mirror device,
> just like the user asked. Gmirror
On Thu, Jun 28, 2012 at 02:54:43PM -0700, Marcel Moolenaar wrote:
> On Jun 28, 2012, at 12:49 PM, Alexander Leidinger wrote:
> > Or are you suggesting to
> > convince all BIOS vendors to include the ability to boot from some kind
> > of FreeBSD private partitioning scheme (not MBR as it is not
> >
Pawel Jakub Dawidek wrote:
On Thu, Jun 28, 2012 at 08:33:17AM -0700, Marcel Moolenaar wrote:
On Jun 28, 2012, at 3:10 AM, Stefan Esser wrote:
All of the above is ugly, U'm afraid :(
Indeed. The only sane way is to put the metadata in a partition of its own.
Every compliant OS will respect t
On Jun 28, 2012, at 12:49 PM, Alexander Leidinger wrote:
> On Thu, 28 Jun 2012 08:33:17 -0700 Marcel Moolenaar
> wrote:
>
>> My advise is to leave disk mirroring to H/W or firmware solutions and
>> use FreeBSD mirroring for FreeBSD partitions only. If you want to
>> mirror the whole disk, don't
On Jun 28, 2012, at 10:25 AM, Pawel Jakub Dawidek wrote:
> On Thu, Jun 28, 2012 at 08:33:17AM -0700, Marcel Moolenaar wrote:
>>
>> On Jun 28, 2012, at 3:10 AM, Stefan Esser wrote:
>>>
>>> All of the above is ugly, U'm afraid :(
>>
>> Indeed. The only sane way is to put the metadata in a partit
On Thu, 28 Jun 2012 08:33:17 -0700 Marcel Moolenaar
wrote:
> My advise is to leave disk mirroring to H/W or firmware solutions and
> use FreeBSD mirroring for FreeBSD partitions only. If you want to
> mirror the whole disk, don't partition the disk with non-FreeBSD
> partitioning schemes and part
The Name Service Cache Daemon (NSCD) is useful, but may get in your
way if you modify data that is cached and have the cache return stale
data until expiry.
One common scenario is an installation script that creates the
required user account, but first checks whether the account name
is currently
On Thu, Jun 28, 2012 at 08:33:17AM -0700, Marcel Moolenaar wrote:
>
> On Jun 28, 2012, at 3:10 AM, Stefan Esser wrote:
> >
> > All of the above is ugly, U'm afraid :(
>
> Indeed. The only sane way is to put the metadata in a partition of its own.
> Every compliant OS will respect that and conseq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-06-28 11:18:45 -0400, Andrew Boyer wrote:
> On Jun 28, 2012, at 10:46 AM, Steve Rikli wrote:
>
>> On Thu, Jun 28, 2012 at 09:58:13AM -0400, John Baldwin wrote:
>>> On Tuesday, June 26, 2012 3:41:10 pm Ping Chen wrote:
I am a bit con
These schemes to just put the metadata in some special location
and have all the tools know about it create a lot of problems.
There is always some tool that doesn't know. There is always
some human that doesn't know. Telling the difference between
real metadata and some other data that happens to
On Jun 28, 2012, at 3:10 AM, Stefan Esser wrote:
>
> All of the above is ugly, U'm afraid :(
Indeed. The only sane way is to put the metadata in a partition of its own.
Every compliant OS will respect that and consequently will not scribble over
the data unintentionally. Any other scheme that pu
On Jun 28, 2012, at 11:18 AM, Andrew Boyer wrote:
> It gets its info from the BIOS, which probed the SPD on each EEPROM at boot
> time.
Meant to say "SPD EEPROM on each DIMM."
-A
--
Andrew Boyerabo...@averesystems.com
___
On Jun 28, 2012, at 10:46 AM, Steve Rikli wrote:
> On Thu, Jun 28, 2012 at 09:58:13AM -0400, John Baldwin wrote:
>> On Tuesday, June 26, 2012 3:41:10 pm Ping Chen wrote:
>>>
>>> I am a bit confused with all these variables defined in
>>> freebsd(especially in freebsd 6.1): Which one of this repr
On Thu, Jun 28, 2012 at 09:58:13AM -0400, John Baldwin wrote:
> On Tuesday, June 26, 2012 3:41:10 pm Ping Chen wrote:
> >
> > I am a bit confused with all these variables defined in
> > freebsd(especially in freebsd 6.1): Which one of this represents the
> > real memory of a system? Say we bought a
On Tuesday, June 26, 2012 3:41:10 pm Ping Chen wrote:
> Hi,
>I am a bit confused with all these variables defined in
freebsd(especially in freebsd 6.1): Which one of this represents the real
memory of a system? Say we bought a system with 4G ram, which one tells me the
RAM is 4G?
>
> Accor
Received this yesterday, about Linux's plans for supporting secure
booting with EFI. I've looked into it as a possibility for FreeBSD, but
I won't be in a position to do anything about it for some time.
But the possibilities are enticing to say the least.
Original Message
Su
On 28.06.2012 14:35, Wojciech Puchar wrote:
>> Just modify GEOM classes that keep state at the end of a partition to
>> leave some spare area *behind* the GEOM data. I.e.:
>>
>
> what is really a problem aat all?
>
> just leave as is. If someone want's use gpart and mirror then mirroring every
>
Just modify GEOM classes that keep state at the end of a partition to
leave some spare area *behind* the GEOM data. I.e.:
what is really a problem aat all?
just leave as is. If someone want's use gpart and mirror then mirroring
every partition is simpler. usually not every partition needs to
On Wed, Jun 27, 2012 at 2:39 PM, Poul-Henning Kamp wrote:
>
> I would like to point out that all other operating system which has
> had this precise problem, have solved it by adding a bootfs partition
> to hold the kernel+modules required to truly understand the disk-layout ?
I have seen some fo
Sorry for following up to self, but ...
I just noticed somebody else suggesting the same method
(put GMIRROR configuration below Secondary GPT header),
but I think there is a problem:
If GMIRROR is used to mirror whole GPT partitioned drives,
then you want the GPT sectors to be considered part of
Am 27.06.2012 21:14, schrieb Marcel Moolenaar:
>
> On Jun 27, 2012, at 12:08 PM, Christian Laursen wrote:
>
>> On 06/27/12 16:28, John Baldwin wrote:
>>> On Wednesday, June 27, 2012 8:45:45 am Andrey V. Elsukov wrote:
>>>
When we are in the FreeBSD, our loader can detect that device size
>>>
0xff0005c82200 dirhash (dirhash)
@/usr/src/sys/ufs/ufs/ufs_dirhash.c:285
http://ipv4.sources.zabbadoz.net/freebsd/lor/261.html
so - it's "fine".
few more when mounting or unmounting (i'm not sure) pendrive.
Jun 27 18:57:09 foo kernel: lock order reversal:
Jun 27 18:57:09 foo kernel
23 matches
Mail list logo
