Hey.
Was the 13 beta 2 AMD64 image compiled and released with debug settings
active ? EFI portion of the boot is an order of magnitude at least
slower than Beta 1.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
Hey guys,
What are the config knobs for enabling the veriexec driver and veriexec
mac modules for testing and playing with this new subystem ? User mode
knob for user mode tool and lib is documented in man src.conf Thanks !
___
freebsd-current@free
We're missing a fair bit of information to come to any conclusion yet.
Cy, did you used it when loading the wifi drivers automatically with
devmatcher ? Cause if you run GENERIC, chances are that you will not
see any weird behavior. Most wifi drivers are compiled in kernel in this
case.
No, that's not what's happening. wlan0 isn't racing anything, because
it's no longer listed in ifconfig
But when is created lagg0 ? Acording rc output on screen , creation of
cloned interface lagg0 takes place before wlan0 is created. Then this
means SIOCLAGPORT will fail with Invalid argume
This was all it was asked. Thanks.
> Im saying that feedback has been heard and understood and providing more
> now while things are in flux to try to address those issues is not
likely
> to be fruitful.
> Warner
>
> Links:
> --
> [1] mailto:dan_parte...@rdsor.ro
It's lack of communication.
> *This* is the reason that *this* and similar topics become so heated;
> People who are part of a "community", such as FreeBSD. Want to feel
> they are part of the "big picture", and immediately feel resentment,
It is in fact much more than that. Surely there are
>
> Not taking a side on this discussion, yet… but the first thing that
I do not believe there are sides to take, because I am absolutely positive
everybody in this thread wants only whats better for FreeBSD, so there is
only one side. It is an aspect which in the heat of emotions some people
se
This is one of the issue I perceive with using scripts/ intermediate
programs
as a glue, a problem which does not exist when the daemons are integrated
tighter. You basically give up all the power which arises from
inter-operating
daemons give to the system.
It is also the main problem FreeB
> Ideally, when the automounter daemon starts, it should
> connect to devd via an IPC channel and request notification of the
specific
> events that it wants
I was under the impression that devd.seqpacket.pipe accomplishes this.
Am I right in assuming that the issue is that devd forwards ALL even
> If these informations were more public I think there will be less
> annoyed posts in mailinglist and more constructive critics / ideas /
> patches.
>
And there other issues arising from the lack of communication:
How exactly bugs / incomplete features are treated in FreeBSD ? Many
times th
>
> "I've given your response all the consideration that I think it's due.
> Please have
> a nice day."
Thank you, Warner. Knowing you did, brings warm feelings in my hearth.
Please have a nice day.
___
freebsd-current@freebsd.org mailing list
https:
On Wed, 20 Apr 2016 04:07:11 +, Glen Barber wrote:
> On Wed, Apr 20, 2016 at 06:59:38AM +0300, dan_partelly wrote:
>>
>> >
>> > Sadly the tenor and tone of the discussion isn’t one where progress
is
>> > made. The tone has been a bit toxic and de
>
> Sadly the tenor and tone of the discussion isn’t one where progress is
> made. The tone has been a bit toxic and demanding, which grinds people
into
> dust, rather than motivating them to fix things. You might call it a
> discussion, but it reads to me more as a bunch of angry villagers
storm
On Tue, 19 Apr 2016 20:09:30 +, "Poul-Henning Kamp"
wrote:
> As far as I know, nobody is taking the source code or the Makefiles
> away, so if somebody doesn't like the system being distributed with
> pkg, they can very well roll their own.
>
> It's nice to see the level of enthusiasm the Fre
>
> Look, take a look at history and the Linux kernel threads story and its
> impact on FreeBSD. If you'd like I can talk about it.
>
Please, yes, I would love to hear about it.
> -Alfred
>
> ___
> freebsd-current@freebsd.org mailing list
> https
>
> What should not happen is that this incremental step forward be blocked
> by those unwilling to hash out the next steps.
>
> -Alfred
>
>
While incremental steps forward are great, how do you avoid situations
like VNET, where a "good enough" enough implementation, usable in some
scenario
I dont know if you missed the point of my message on purpose or not.
I never pretended that you can't extract that information. I maintain that
having sane defaults would empower me to almost never care about aliases,
scripts
pipes, filter , regular expressions and what not. It is great that all
For what is worth, I agree with Julian Elischer. I do not
want to see hundreds of packages over tenths of screen pages.
Computers are supposed to make our life simpler. Human time is
very expensive. CPU time, almost free. And this include that I really
shouldn't have to think for usual work of
>
> And nowhere did it say "buildworld/buildkernel would no longer work."
>
> Glen
It may very well work, but you consider a listing of hundred of packages
on a
fresh system a sane default ?
___
freebsd-current@freebsd.org mailing list
https://lis
Hi all,
At the following URL:
https://wiki.freebsd.org/201506DevSummit/libxo
the listed agenda of libxo working group include the following topic of
discussion:
Discussion: libxo in the kernel. -
Can someone please explain exactly what happens here ? Who pushed this
age
Hi Pedro,
Sure, no worries , I am grateful for all you did, couldn't ask for more.
I have yet no idea how the projects works, but in the thread in which I
questioned the wisdom of having
utilities in base spitting out JSON -- instead of properly libyifing some
utilities -- Adrian has
stated so
Software wise, your biggest competitive advantage is using a re-branded
BSD operating system.
On a more serious note, surely I understand and support this position. The
BSD license stays
for true freedom, unlike the GNU beer .
But we would never be sure that your company would say no, unless
Hi all,
I attach a patch for comments (the patch is not final is intended for
comments only, format for one thing is messed )
regarding support for !=, ==, <, >, >=, <= , ! , ~, & , | , && , ||
operators in DDB expressions.
The code was mainly pulled from Mach 3.0 kernel with a couple of bug-fix
hange and not anything WiFi
> specific. :( On Dec 17, 2013 12:04 PM, "dan_partelly" wrote:
>
> Yes, this is correct. A simple list of the interfaces with ifconfig
> makes the system recover and restart activity on the secondary port.
> Its a good starting point to hu
I guarantee you that a simple interface list with ifconfig un-stucks the
net on my setup, at lest in the case (master is wired, unplug ethernet,
fail to wireless) I agree that it doesn't makes much sense, but no matter
how unlikely it seems, it is a **fact**.
>
> I don't believe in merely
What claims you do not "believe" ? Not important anyway. This is
engineering, so you need not believe, you need to know. Go and replicate
the bug. You will know then.
>
> I don't really believe these claim.
>
> I had similar issue in the past and found an 'arp -a -d' would "fix"
> it so I di
Yes, this is correct. A simple list of the interfaces with ifconfig
makes the system recover and restart activity on the secondary port.
Its a good starting point to hunt down the problem. One of the ioctls sent
has this "side effect".
Dan
> If I am am understanding correctly, Dan and Nikolai
No problem. Can you point me to the relevant source files in the
kernel tree, please ?
Dan
On Tue, 17 Dec 2013 08:43:09 -0800, Adrian Chadd
wrote:
> I'm the wireless stack maintainer and I currently don't support that.
>
> Sorry.
>
>
>
> -a
>
> On
rface.
>
> I'm going to just state right now that using lagg as the failover
> method for doing wireless/wired integration isn't supported by me. If
> someone wants to make it supported then they need to claim it. :)
>
>
> -a
>
>
> On 17 December 2013 05:0
Hi all,
I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as
described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop.
What happens is:
If I boot the system with the Ethernet cable attached, I correctly get
lagg0 active port on master- bg0- and the network is working
30 matches
Mail list logo
