Hi,
There has been quite a while since the SSP glue has been committed in
the tree. Yet there has always been a gloomy corner case since then
that was reported from time to time, mainly by port maintainers, which
has been hard to reproduce. This is the main showstopper to enable SSP
for ports by
On 24/05/2013 18:57, Welcome, Traiano wrote:
> You appear not to realize that to even begin working with one of the existing
> projects, you'd best have a solid understanding of OSes to begin with,
> which brings up an interesting catch -22 that goes something like:
>
> "You can't join the clu
"Welcome, Traiano" wrote:
> May I ask where you get the divine wisdom to know where I "would be better
> working with" ? don't you think that would be best left up to me?
etc ... elided
As politeness fails: Waste your own time as you want. Don't waste
FreeBSD people's time, asking advice how
Jorge Alberto Garcia wrote:
>
> Hello Joshua, i think you should try XV6, i am pretty one person can
> understand it to get a general yet down to the earth felling about a unix
> like system; then try with Minix2
>
> http://pdos.csail.mit.edu/6.828/2012/xv6.html
>
> Tnx.
> -J.A. Garcia
Great to
I've been running my systems with this modification since Feb 2012 and
have seen no problems beyond file(1) usage on /usr/lib/libc.so in
openssl's configure.
I've taken ports/168010 and ports/138228 for exp-runs. I want to get
(optional) SSP support into ports this year.
I'll start a libc.ld exp-
I heard there was some discussion at BSDCan about the direction of a
future FreeBSD installer. Considering we currently have bsdinstall,
pc-sysinstall, and an effort to revive sysinstall, I'd be interested to
know what was decided (if anything) and whether I could help make
progress towards ge
On Sat, May 25, 2013 at 8:43 AM, Bruce Cran wrote:
>
> I heard there was some discussion at BSDCan about the direction of a future
> FreeBSD installer. Considering we currently have bsdinstall, pc-sysinstall,
> and an effort to revive sysinstall, I'd be interested to know what was
> decided (i
It's not a X-Fi sound card at all. Its chip is CA0106-WBTLF (from
Wikipedia). But it's the only sound card available on ExpressCard,
so it's kinda a great choice for laptop users.
Is that possible to add its support into FreeBSD OSS?
On my FreeBSD 8.4 machine, it's recognized as
May 25 12:36:2
On 25/05/2013 17:15, Matt Olander wrote:
From my vague recollection, we discussed improving bsdinstall by tying
it in with pc-sysinstall, which we've been threatening to do for at
least a year. Also, there was much discussion about Devin's bsdconfig
perhaps tying in with a Google SoC Project.
I
On Sat, May 25, 2013 at 09:03:57AM -0500, Bryan Drewery wrote:
> I've been running my systems with this modification since Feb 2012 and
> have seen no problems beyond file(1) usage on /usr/lib/libc.so in
> openssl's configure.
>
> I've taken ports/168010 and ports/138228 for exp-runs. I want to ge
Hello FreeBSD devs,
I have found a performance improvement to libc's strnlen().
lib/libc/string/strnlen.c is a trivial byte-by-byte implementation,
where strlen.c has a smarter word-by-word implementation. I have
implemented strnlen similarly to strlen. It runs about 4x as fast, at
the cost o
On 05/25/13 13:26, Bruce Cran wrote:
On 25/05/2013 17:15, Matt Olander wrote:
From my vague recollection, we discussed improving bsdinstall by tying
it in with pc-sysinstall, which we've been threatening to do for at
least a year. Also, there was much discussion about Devin's bsdconfig
perhaps
On 26.05.13 01:07, Nathan Whitehorn wrote:
> I'm not aware of any movement there (on either side of the table). I'd
> personally be very suspicious of an all-sh(1) future -- by far the
> cleanest parts of bsdinstall are in C -- and this is especially true for
> interacting with geom. That said, si
Please don't turn this into an architecture dependent mess. PCBSD is i386 &
AMD64 only.
On Sat, May 25, 2013 at 9:01 PM, Dirk Engling wrote:
> On 26.05.13 01:07, Nathan Whitehorn wrote:
>
> > I'm not aware of any movement there (on either side of the table). I'd
> > personally be very suspiciou
On May 25, 2013, at 9:15 AM, Matt Olander wrote:
> On Sat, May 25, 2013 at 8:43 AM, Bruce Cran wrote:
>>
>> I heard there was some discussion at BSDCan about the direction of a future
>> FreeBSD installer. Considering we currently have bsdinstall, pc-sysinstall,
>> and an effort to revive sy
On May 25, 2013, at 11:26 AM, Bruce Cran wrote:
> On 25/05/2013 17:15, Matt Olander wrote:
>> From my vague recollection, we discussed improving bsdinstall by tying
>> it in with pc-sysinstall, which we've been threatening to do for at
>> least a year. Also, there was much discussion about Devin'
On May 25, 2013, at 4:07 PM, Nathan Whitehorn wrote:
> On 05/25/13 13:26, Bruce Cran wrote:
>> On 25/05/2013 17:15, Matt Olander wrote:
>>> From my vague recollection, we discussed improving bsdinstall by tying
>>> it in with pc-sysinstall, which we've been threatening to do for at
>>> least a ye
On May 25, 2013, at 6:01 PM, Dirk Engling wrote:
> On 26.05.13 01:07, Nathan Whitehorn wrote:
>
>> I'm not aware of any movement there (on either side of the table). I'd
>> personally be very suspicious of an all-sh(1) future -- by far the
>> cleanest parts of bsdinstall are in C -- and this is
On May 25, 2013, at 7:51 PM, Super Bisquit wrote:
> Please don't turn this into an architecture dependent mess. PCBSD is i386 &
> AMD64 only.
>
There's a GSoC project (of which I'm potential mentor) to fix that.
However, you are entirely right… we can't in all seriousness even think about
usi
On 05/25/2013 10:27 PM, Lee Thomas wrote:
> Hello FreeBSD devs,
>
> I have found a performance improvement to libc's strnlen().
> lib/libc/string/strnlen.c is a trivial byte-by-byte implementation,
> where strlen.c has a smarter word-by-word implementation. I have
> implemented strnlen similarly t
20 matches
Mail list logo