W dniu 2013-02-06 13:53, Damien Fleuriot pisze:
":" in the URL instead of "/" , possibly ?
I find it strange that there should be ":" in the URL, it is only acceptable
when denoting the destination port to connect to.
Try replacing them with slashes.
after few hours it started working... prob
On Fri, 08 Feb 2013 13:02:41 +0100, Marek Salwerowicz
wrote:
W dniu 2013-02-06 13:53, Damien Fleuriot pisze:
":" in the URL instead of "/" , possibly ?
I find it strange that there should be ":" in the URL, it is only
acceptable when denoting the destination port to connect to.
Try repl
Hello,
I think there's a confusion in the man page setfacl(1).
In my tests, "D" means "delete_child" and "d" "delete"; like it's true
for other NFSv4 implementations. But manpage tells the other way around.
Since things didn't work as expected when I followed the man page I
checked the followin
On Fri, Feb 08, 2013 at 01:19:04PM +0100, Ronald Klop wrote:
> On Fri, 08 Feb 2013 13:02:41 +0100, Marek Salwerowicz
> wrote:
>
> >W dniu 2013-02-06 13:53, Damien Fleuriot pisze:
> >>":" in the URL instead of "/" , possibly ?
> >>
> >>I find it strange that there should be ":" in the URL, it is
>
Hello,
I'd like to duplicate the following ACL:
# file: /data/shared/
# owner: harry
# group: harry
group:1stgroup:r-x---a-R-c--s:fd:allow
group:2ndgroup:rwxp--a-R-c--s:-d:allow
group:2ndgroup:D-:-d:deny
group:2ndgroup:r-a-R-c--s:f-i---:allow
Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz. 17:54:
> Hello,
>
> I'd like to duplicate the following ACL:
> # file: /data/shared/
> # owner: harry
> # group: harry
> group:1stgroup:r-x---a-R-c--s:fd:allow
> group:2ndgroup:rwxp--a-R-c--s:-d:allow
> gro
For those that may have run across the story on Slashdot about this NIC,
here is our statement:
Recently there were a few stories published, based on a blog post by an
end-user, suggesting specific network packets may cause the Intel® 82574L
Gigabit Ethernet Controller to become unresponsive until
W dniu 2013-02-08 17:52, Jeremy Chadwick pisze:
Not "probably":
http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-February/01.html
Five hours later (read closely):
http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-February/02.html
Folks should be subscribing to f
Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz. 16:08:
> Hello,
>
> I think there's a confusion in the man page setfacl(1).
>
> In my tests, "D" means "delete_child" and "d" "delete"; like it's true
> for other NFSv4 implementations. But manpage tells the other way around.
On 8 February 2013 13:46, Edward Tomasz Napierała wrote:
> Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz. 16:08:
>> Hello,
>>
>> I think there's a confusion in the man page setfacl(1).
>>
>> In my tests, "D" means "delete_child" and "d" "delete"; like it's true
>> for othe
John-Mark Gurney wrote:
> Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100:
> > John-Mark Gurney wrote:
> > > Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100:
> > > > I'm running a recent stable/9 (about 14 days old).
> > > > What's the best way to deb
I'm sorry for the late reply. I didn't have much time
this week to investigate this issue. At the moment I
implemented a work-around with an additional switch using
VLANs, but I'd really like to get the second NIC working.
YongHyeon PYUN wrote:
> On Mon, Feb 04, 2013 at 07:15:51PM +0100, Oliver
Wiadomość napisana przez Eitan Adler w dniu 8 lut 2013, o godz. 20:05:
> On 8 February 2013 13:46, Edward Tomasz Napierała wrote:
>> Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz.
>> 16:08:
>>> Hello,
>>>
>>> I think there's a confusion in the man page setfacl(1).
>>>
>
On 8 February 2013 20:42, Edward Tomasz Napierała wrote:
> Wiadomość napisana przez Eitan Adler w dniu 8 lut 2013, o godz. 20:05:
>> On 8 February 2013 13:46, Edward Tomasz Napierała wrote:
>>> Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz.
>>> 16:08:
Hello,
>>
Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4 compression.
https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM
short link: http://bpaste.net/show/76095
HTH
--
Dan Langille - http://langille.org
___
freebsd-stable@fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/08/13 14:29, Dan Langille wrote:
> Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4
> compression.
>
> https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM
>
> short link: http://bpaste.net/show/76095
Please DO
On Feb 8, 2013, at 5:52 PM, Xin Li wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 02/08/13 14:29, Dan Langille wrote:
>> Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4
>> compression.
>>
>> https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM
>
On Fri, Feb 08, 2013 at 02:52:57PM -0800, Xin Li wrote:
> On 02/08/13 14:29, Dan Langille wrote:
> > Here is a patch against FreeBSD 9.1 STABLE which implements ZFS LZ4
> > compression.
> >
> > https://plus.google.com/106386350930626759085/posts/PLbkNfndPiM
> >
> > short link: http://bpaste.net/s
On 09/02/2013, at 4:46, Jack Vogel wrote:
> recommends contacting your motherboard manufacturer if you have continued
> concerns or questions whether your products are impacted.
> Here is the link:
>
> http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For those who are inpatient, here is an overlay for LZ4 for 9-STABLE.
http://people.freebsd.org/~delphij/misc/lz4.tar.xz
Overwrite /usr/src and recompile ZFS module.
Note: before using this in any serious environment, please be sure to
test if the
20 matches
Mail list logo
