Hi all,
I've updated libedit to the latest version available in the netbsd cvs.
UTF8 support is disabled for now has it seems to be experimental and segfault.
I also patch and tested all the sources that used to be linked against
libreadline so that it now uses libedit making libreadline unused (I
Hi all,
I have some tentative patches which add support for creating a separate
directory containing all of the userland debugging symbols.
I posted about this a week or so ago:
http://lists.freebsd.org/pipermail/freebsd-hackers/2010-October/033437.html
Some future work will involve finding out
On Fri, Nov 05, 2010 at 04:32:56PM +0100, Baptiste Daroussin wrote:
> I've updated libedit to the latest version available in the netbsd cvs.
> UTF8 support is disabled for now has it seems to be experimental and segfault.
> I also patch and tested all the sources that used to be linked against
> l
On (05/11/2010 15:14), Mark Johnston wrote:
> Hi all,
>
> I have some tentative patches which add support for creating a separate
> directory containing all of the userland debugging symbols.
>
> I posted about this a week or so ago:
> http://lists.freebsd.org/pipermail/freebsd-hackers/2010-Octob
On Fri, Nov 05, 2010 at 10:45:19PM +0200, Gleb Kurtsou wrote:
> On (05/11/2010 15:14), Mark Johnston wrote:
> > Hi all,
> >
> > I have some tentative patches which add support for creating a separate
> > directory containing all of the userland debugging symbols.
> >
> > I posted about this a wee
Hi Kib,
On Tue, Oct 05, 2010 at 08:18:04PM +0200, Jeremie Le Hen wrote:
>
> On Mon, Sep 27, 2010 at 06:44:57PM +0300, Kostik Belousov wrote:
> > Hardcoding /usr/lib as the path to the library in the script looks
> > problematic. For the buidlworld, you are linking resulting binaries
> > with the
On Fri, 5 Nov 2010 22:39:06 +0100
Jeremie Le Hen wrote:
> Hi Kib,
>
> On Tue, Oct 05, 2010 at 08:18:04PM +0200, Jeremie Le Hen wrote:
> >
> > On Mon, Sep 27, 2010 at 06:44:57PM +0300, Kostik Belousov wrote:
> > > Hardcoding /usr/lib as the path to the library in the script looks
> > > problemat
It's been incredibly busy for us in iXsystems land, with a lot of irons in the
fire.
One of the many things we've been working on is a new installer. Several
months ago pc-sysinstall was imported into HEAD from the PC-BSD project.
pc-sysinstall is a fine tool, and very useful as the backend
On Fri, Nov 5, 2010 at 9:16 PM, Josh Paetzel wrote:
> It's been incredibly busy for us in iXsystems land, with a lot of irons in the
> fire.
>
> One of the many things we've been working on is a new installer. Several
> months ago pc-sysinstall was imported into HEAD from the PC-BSD project.
>
>
On Fri, Nov 5, 2010 at 9:47 PM, Garrett Cooper wrote:
> On Fri, Nov 5, 2010 at 9:16 PM, Josh Paetzel wrote:
>> It's been incredibly busy for us in iXsystems land, with a lot of irons in
>> the
>> fire.
>>
>> One of the many things we've been working on is a new installer. Several
>> months ago
> Just to add to that (because I do find it a novel idea), 1) how
> are you going to properly prevent man in the middle attacks (SSL, TLS,
> etc?), and 2) what webserver would you use?
https or ssh.
We're also toying with the idea of having a partition that you could
'dd' your certs and keys
On Friday, November 05, 2010 11:48:27 pm Garrett Cooper wrote:
> >Just to add to that (because I do find it a novel idea), 1) how
> > are you going to properly prevent man in the middle attacks (SSL, TLS,
> > etc?), and 2) what webserver would you use?
> >I bring up the former item becaus
On Fri, Nov 5, 2010 at 10:17 PM, Josh Paetzel wrote:
> On Friday, November 05, 2010 11:48:27 pm Garrett Cooper wrote:
>
>> > Just to add to that (because I do find it a novel idea), 1) how
>> > are you going to properly prevent man in the middle attacks (SSL, TLS,
>> > etc?), and 2) what webser
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
>> Just to add to that (because I do find it a novel idea), 1) how
>> are you going to properly prevent man in the middle attacks (SSL, TLS,
>> etc?), and 2) what webserver would you use?
>
> https or ssh.
>
> We're also toying with the idea
On Fri, Nov 5, 2010 at 11:04 PM, Garrett Cooper wrote:
> On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
>>> Just to add to that (because I do find it a novel idea), 1) how
>>> are you going to properly prevent man in the middle attacks (SSL, TLS,
>>> etc?), and 2) what webserver would yo
On 11/06/2010 00:04, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent man in the middle attacks (SSL, TLS,
etc?), and 2) what webserver would you use?
https or ssh.
On 11/06/2010 00:05, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 11:04 PM, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent man in the middle attacks (SSL, TLS,
et
17 matches
Mail list logo