3(ba...@yandex.ru) on 2018.03.29 02:10:29 +0300:
> > 3(ba...@yandex.ru) on 2018.03.28 23:03:27 +0300:
> >> > On 03/28/18 15:04, 3 wrote:
> >> >> hi guys. when the pflow option first appeared, i was surprised by the
> >> >> stupidity of those who implemented it- pflow could not be specified
> >> >>
On Thu, Mar 29, 2018 at 01:49:24AM -0300, Daniel Bolgheroni wrote:
> Hi,
>
> over the last years, OpenBSD worked so great on every ThinkPad I
> had/have, that it almost feels I'm doing something very stupid when it
> doesn't.
>
> With a X250 I got my hands on recently, on a new installation, the
Hi,
over the last years, OpenBSD worked so great on every ThinkPad I
had/have, that it almost feels I'm doing something very stupid when it
doesn't.
With a X250 I got my hands on recently, on a new installation, the
latest snapshot suspends OK, but trying to resume has no effect. The
power led k
What's happening right now is OBSD-misc is doing in 6 months
what RH and MS do in ten years. Questions like this are
like hitting the stop button on a production line :D
Peter N.M. Hansteen is keen to answer questions like this.
https://www.facebook.com/groups/openbsd.newbies/
There's a regular
> 3(ba...@yandex.ru) on 2018.03.28 23:03:27 +0300:
>> > On 03/28/18 15:04, 3 wrote:
>> >> hi guys. when the pflow option first appeared, i was surprised by the
>> >> stupidity of those who implemented it- pflow could not be specified
>> >> for block-rules, i.e. dropped packets were not taken into a
Hi all,
I am running 6.2 on x86 on an old ThinkPad.
6.1 was rock-solid and never had issues, I was able to complete the
install of 6.2 only recently, because I had issues with network and all
network cards (PCMCIA) I had at hand. No wireless card would work
properly and only one of two wired c
3(ba...@yandex.ru) on 2018.03.28 23:03:27 +0300:
> > On 03/28/18 15:04, 3 wrote:
> >> hi guys. when the pflow option first appeared, i was surprised by the
> >> stupidity of those who implemented it- pflow could not be specified
> >> for block-rules, i.e. dropped packets were not taken into account
> https://man.openbsd.org/pflow.4
> On Wed, Mar 28, 2018 at 4:03 PM, 3 wrote:
>> On 03/28/18 15:04, 3 wrote:
>>> hi guys. when the pflow option first appeared, i was surprised by the
>>> stupidity of those who implemented it- pflow could not be specified
>>> for block-rules, i.e. dropped pack
https://man.openbsd.org/pflow.4
On Wed, Mar 28, 2018 at 4:03 PM, 3 wrote:
> > On 03/28/18 15:04, 3 wrote:
> >> hi guys. when the pflow option first appeared, i was surprised by the
> >> stupidity of those who implemented it- pflow could not be specified
> >> for block-rules, i.e. dropped packets
Distros like RHEL have longer release cycles because the industry they service
demands them. The fact that the kernel project maintains releases as far back
as 2012 only re-enforces the business.
There's no need for 'puffangelism' on this subject as OBSD is by no means alone
in six-month releas
> On 03/28/18 15:04, 3 wrote:
>> hi guys. when the pflow option first appeared, i was surprised by the
>> stupidity of those who implemented it- pflow could not be specified
>> for block-rules, i.e. dropped packets were not taken into account. as
> hm. you've suffered nine years of this stupidity
Armada 3700LP chipset not supported at present.
--
Patrick Harper
paia...@fastmail.com
On Sun, 25 Mar 2018, at 22:11, Z Ero wrote:
> If yes is the on board ethernet switch supported? What wifi cards are
> supported in the miniPCIe slot?
>
Dear all,
posting to misc as I don't know if this is a bug in OpenBSD or in my
hardware.
I got this nice old "workstation" from the mid 90ies with dual P54C
processors and i430NX chipset and want to operate it in MP mode with
OpenBSD. Unfortunately this doesn't work as expected currently. I've
al
On 03/28/18 15:04, 3 wrote:
> hi guys. when the pflow option first appeared, i was surprised by the
> stupidity of those who implemented it- pflow could not be specified
> for block-rules, i.e. dropped packets were not taken into account. as
hm. you've suffered nine years of this stupidity of othe
hi guys. when the pflow option first appeared, i was surprised by the
stupidity of those who implemented it- pflow could not be specified
for block-rules, i.e. dropped packets were not taken into account. as
a result of this approach, the usefulness of pflow sought to zero for
those cases where tra
On Wed, 28 Mar 2018 11:29:50 +0200
> Everything can be improved, it's a matter of dedication ;) But make
> sure you don't compare oranges to apples.
Thanks for the insight. I shall bear this complexity in mind when
pondering further.
On 27/03/18(Tue) 18:07, Kevin Chadwick wrote:
> It seems there may be a speed issue of some kind. A past thread
> mentions raw devices being fast but doesn't ntfs-3g use raw access.
raw USB speeds are faster but not fast on OpenBSD.
> ntfs-3g is the slowest then msdos gets around 2200 Kilobytes/s
17 matches
Mail list logo
