hi,
this is the output from gpart show:
=> 34 976773101 ada0 GPT (465G)
34 2048 1 freebsd-boot (1.0M)
20824194304 2 freebsd-ufs [bootme] (2.0G)
4196386 12582912 3 freebsd-swap (6.0G)
16779298 959993837 4 freebsd-zfs (457G)
=>
On Tue, 22 Jan 2013 13:21+0200, Daniel Braniss wrote:
> hi,
> this is the output from gpart show:
> => 34 976773101 ada0 GPT (465G)
> 34 2048 1 freebsd-boot (1.0M)
>20824194304 2 freebsd-ufs [bootme] (2.0G)
> 4196386 12582912 3 freebsd-s
> hi,
> this is the output from gpart show:
> => 34 976773101 ada0 GPT (465G)
> 34 2048 1 freebsd-boot (1.0M)
>20824194304 2 freebsd-ufs [bootme] (2.0G)
> 4196386 12582912 3 freebsd-swap (6.0G)
>16779298 959993837 4 freebsd-zfs
On Tue, 22 Jan 2013 12:24+0100, Trond Endrestøl wrote:
> On Tue, 22 Jan 2013 13:21+0200, Daniel Braniss wrote:
>
> > hi,
> > this is the output from gpart show:
> > => 34 976773101 ada0 GPT (465G)
> > 34 2048 1 freebsd-boot (1.0M)
> >20824194304 2 f
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
>
> --2055831798-439718327-1358853899=:41917
> Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1
> Content-ID:
> Content-Transfer-Encoding: quoted-
On 22.01.2013 16:41, Daniel Braniss wrote:
> the source pmbr.s seems to say different - 545K, but since gptboot is 15k ...
> someone should mention it in the gpart(8) man page.
It is already documented in the gpart(8) man page, twice.
--
WBR, Andrey V. Elsukov
___
On Saturday, January 19, 2013 10:12:54 am Mikolaj Golub wrote:
> Hi,
>
> Some time ago Stanislav Sedov suggested to me extending libprocstat(3)
> with functions to retrieve process command line arguments and
> environment variables.
>
> In the first approach I tried, the newly added functions
> p
On Tuesday, January 22, 2013 6:42:22 am Daniel Braniss wrote:
> > hi,
> > this is the output from gpart show:
> > => 34 976773101 ada0 GPT (465G)
> > 34 2048 1 freebsd-boot (1.0M)
> >20824194304 2 freebsd-ufs [bootme] (2.0G)
> > 4196386 125829
I started investigating ipmi, so far i can configure IP from fbsd to ipmi.
My question is how to access it? Can it be done inband attached to one oc
the Ibm nics kn the board? or knlh out oc band?
In case of oob any knows if the iLO plug is pure rj45 in ibm servers
(specially x3250/3550)?
Thanks i
On Tue, Jan 17, 2012 at 01:21:27PM +0100, Oliver Fromme wrote:
> Kostik Belousov wrote:
> > The patch misses compat32 bits and breaks compat32 ps/top.
>
> Right, thank you for pointing it out! I missed it because
> I only have i386 for testing.
>
> I've created new patch sets for releng8 and c
On Mon, Jan 21, 2013 at 11:36 PM, Peter Jeremy wrote:
> On 2013-Jan-21 12:12:45 +0100, Wojciech Puchar <
woj...@wojtek.tensor.gdynia.pl> wrote:
>>While RAID-Z is already a king of bad performance,
>
> I don't believe RAID-Z is any worse than RAID5. Do you have any actual
> measurements to back up
I tried to create my own DTrace sensors (for debugging purposes) through
adding of the simple function like this:
static u_int
xxx_my_trace(int arg) {
return 1;
}
It is listed in dtrace -l with its entry and return sensors.
8143fbtkernel xxx_my_trace entry
On Tue, Jan 22, 2013 at 12:01:06PM -0500, John Baldwin wrote:
> How is this different from kvm_getargv()? It seems to be a direct copy.
libprocstat(3) is a frontend for sysctl(3) and kvm(3) interfaces, so
it is good to extend it to cover "getarg/env" functionality.
Yes the functions look simila
On Tuesday, January 22, 2013 4:17:43 pm Mikolaj Golub wrote:
> On Tue, Jan 22, 2013 at 12:01:06PM -0500, John Baldwin wrote:
>
> > How is this different from kvm_getargv()? It seems to be a direct copy.
>
> libprocstat(3) is a frontend for sysctl(3) and kvm(3) interfaces, so
> it is good to exte
On Jan 22, 2013, at 1:48 PM, John Baldwin wrote:
>
> Well, you could make procstat open a kvm handle in both cases (open a "live"
> handle in the procstat_open_sysctl() case). It just seems rather silly to be
> duplicating code in the two interfaces. More a question for Robert: does
> libpr
Hi,
Does freebsd have some functionality similar to Linux's NMI watchdog ? I'm
aware of ichwd driver, but that depends to WDT to be available in the hardware.
Even when it is available, BIOS needs to support a mechanism to trigger a OS
level recovery to get any useful information when system i
On Mon, Jan 21, 2013 at 1:06 PM, Pawel Jakub Dawidek wrote:
> On Fri, Jan 18, 2013 at 08:26:04AM -0800, m...@freebsd.org wrote:
>> > Should it be set to a larger initial value based on min(physical,KVM)
>> > space
>> > available?
>>
>> It needs to be smaller than the physical space, [...]
>
> O
On Tue, Jan 22, 2013 at 2:41 PM, Yuri wrote:
> I tried to create my own DTrace sensors (for debugging purposes) through
> adding of the simple function like this:
> static u_int
> xxx_my_trace(int arg) {
> return 1;
> }
>
> It is listed in dtrace -l with its entry and return sensors.
> 8143
On Tue, Jan 22, 2013 at 02:17:39PM -0800, Stanislav Sedov wrote:
>
> On Jan 22, 2013, at 1:48 PM, John Baldwin wrote:
> >
> > Well, you could make procstat open a kvm handle in both cases (open a
> > "live"
> > handle in the procstat_open_sysctl() case). It just seems rather silly to
> > be
19 matches
Mail list logo
