Microsoft Paint & NXP Semiconductors

Wed Jun 29 19:40:26 UTC 2016

*To whom it may concern*

*I found your group when one of your online subscribers had a problem in
the BSD Group. Although I did not react to his protests, I would like you
to know, that I am sympathetic to his concerns. I am however unable to
locate his email ID.*

*The purpose of this email is to let you know that I would like to assist
your GROUP with two software programs written by myself with the assistance
of my friends from University between 1989-1995. The "i squared C", bus
architecture is a proprietary architecture to NXP Semiconductors, an
offshoot of Phillips, Holland.   We wrote a non-volatile program for DC
Loads and a Microsoft solution called "PC Paint”. *

*Trust your clients & team mates have not been disappointed by our efforts.
I have no hesitation in being grateful to Microsoft Corporation, Intel
Corporation and AMD (Radeon) after all these years of their incessant
efforts to keep these technologies alive. *

*Any suggestions you may have with regards to contributing to efforts
already made would be appreciated here.*

*Regards,*
*Rajneesh *
Tel : (+91) 8711 9653 19
http://www.i2c-bus.org/i2c-bus/

http://www.telos.info/download/i2c-studioframework/

Weblog : www.rns-thoughts.blogspot.com

On 29 June 2016 at 17:30, <freebsd-hackers-request at freebsd.org> wrote:

> Send freebsd-hackers mailing list submissions to
>         freebsd-hackers at freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> or, via email, send a message with subject or body 'help' to
>         freebsd-hackers-request at freebsd.org
>
> You can reach the person managing the list at
>         freebsd-hackers-owner at freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-hackers digest..."
>
>
> Today's Topics:
>
>    1. Re: The small installations network filesystem and users.
>       (Julian Elischer)
>    2. Re: The small installations network filesystem and users.
>       (Wojciech Puchar)
>    3. Re: The small installations network filesystem and users.
>       (Wojciech Puchar)
>    4. Re: The small installations network filesystem and users.
>       (Eduardo Morras)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 28 Jun 2016 21:04:45 +0800
> From: Julian Elischer <julian at freebsd.org>
> To: Gerrit K?hn <gerrit.kuehn at aei.mpg.de>, Daniel Eischen
>         <deischen at freebsd.org>
> Cc: freebsd-fs <freebsd-fs at freebsd.org>, FreeBSD Hackers
>         <freebsd-hackers at freebsd.org>
> Subject: Re: The small installations network filesystem and users.
> Message-ID: <761f82d3-ebe9-2cba-9499-049dafbc98df at freebsd.org>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 21/06/2016 1:56 PM, Gerrit K?hn wrote:
> > On Mon, 20 Jun 2016 22:00:31 -0400 (EDT) Daniel Eischen
> > <deischen at freebsd.org> wrote about Re: The small installations network
> > filesystem and users.:
> >
> > DE> We should support LDAP client out of the box, in base.  What
> > DE> sucks now is that we need 3 packages (plus their dependencies)
> > DE> and multiple config files for ldap:
> > DE>
> > DE>    pam_ldap
> > DE>    nss_ldap
> > DE>    openldap-client
> >
> > I only have to install/config ldap-clients every now and then, but I
> would
> > also strongly favour a more "integrated" setup (if that requires having
> it
> > in base is a different question, though). A few weeks ago I used
> > nss-pam-ldapd instead of pam_ldap and nss_ldap for the first time, and it
> > appeared to work with a bit less of a hassle for me (otoh, I don't do any
> > funky things here, I just need a replacement for what we did with NIS
> > something like 20 years ago).
>
> +1
> I just had to reinstall certs for my server.  which means copying
> certs to several places (in a default config)
> sendmail and syrus ad openssl (base) all look in different places. you
> COULD make them all look in the same place
> but that requires undersanding what is going on and not just cribbing
> the config file off the net somewhere.
>
> I think ports and pkg are fine, but we need to have some more thought
> put into how they all go together.
>
> >
> >
> > cu
> >    Gerrit
> > _______________________________________________
> > freebsd-fs at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> > To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
> >
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 28 Jun 2016 17:23:22 +0200 (CEST)
> From: Wojciech Puchar <wojtek at puchar.net>
> To: Chris Watson <bsdunix44 at gmail.com>
> Cc: Zaphod Beeblebrox <zbeeble at gmail.com>, freebsd-fs
>         <freebsd-fs at freebsd.org>, FreeBSD Hackers
>         <freebsd-hackers at freebsd.org>
> Subject: Re: The small installations network filesystem and users.
> Message-ID: <alpine.BSF.2.20.1606281723010.8870 at laptop.wojtek.intra>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
>
>
> On Mon, 20 Jun 2016, Chris Watson wrote:
>
> > I'm glad you brought this up. I wanted to but I've heard it before on
> the lists and realize that there is this disconnect between the developers
> doing the actual work to implement these things and the end users.
> >
> > I have always been very grateful to all the developers who over the
> years, and I've been a FreeBSD consumer since the late 90s? And attended my
> first usenix/freenix conf in Monterrey in 2001?, have done some really hard
> work on many many things in FreeBSD. For zero pay. But the thing that has
> always bothered me about a lot of it is, it's just to complex to use for
> most end users. Not all. But people want to get work done. Sifting through
> .conf files, googling howtos, spending more time configuring it than
> installing it has always been an issue. Developers in general do not think
> like an end user. And this leads to non developers just going "screw it
> I'll just get it running on Linux with my GUI installer." Which is why
> FreeNas is so popular. It's taken a lot, not all, but a lot of the pain and
> time consuming nature of learning all the ins and outs of a NAS appliance
> from the equation.
>
> FreeBSD have very well done man pages. I simply read them.
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 28 Jun 2016 17:22:33 +0200 (CEST)
> From: Wojciech Puchar <wojtek at puchar.net>
> To: Zaphod Beeblebrox <zbeeble at gmail.com>
> Cc: freebsd-fs <freebsd-fs at freebsd.org>, FreeBSD Hackers
>         <freebsd-hackers at freebsd.org>
> Subject: Re: The small installations network filesystem and users.
> Message-ID: <alpine.BSF.2.20.1606281722050.8870 at laptop.wojtek.intra>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> > Correct me if I'm wrong, but amidst discussions of pNFS (among other
> > things) I thought I should bring up something someone said to me: and
> that
> > is (to quote him) "using NFS is too hard, I always fail."
>
> Never had problems with NFS.  And i'm using in regularly.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 28 Jun 2016 18:11:40 +0200
> From: Eduardo Morras <emorrasg at yahoo.es>
> To: freebsd-hackers at freebsd.org
> Subject: Re: The small installations network filesystem and users.
> Message-ID: <20160628181140.933d144cd5d830275e4be6c3 at yahoo.es>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, 28 Jun 2016 21:04:45 +0800
> Julian Elischer <julian at freebsd.org> wrote:
>
> > On 21/06/2016 1:56 PM, Gerrit K?hn wrote:
> > > On Mon, 20 Jun 2016 22:00:31 -0400 (EDT) Daniel Eischen
> > > <deischen at freebsd.org> wrote about Re: The small installations
> > > network filesystem and users.:
> > >
> > > DE> We should support LDAP client out of the box, in base.  What
> > > DE> sucks now is that we need 3 packages (plus their dependencies)
> > > DE> and multiple config files for ldap:
> > > DE>
> > > DE>    pam_ldap
> > > DE>    nss_ldap
> > > DE>    openldap-client
> > >
> > > I only have to install/config ldap-clients every now and then, but
> > > I would also strongly favour a more "integrated" setup (if that
> > > requires having it in base is a different question, though). A few
> > > weeks ago I used nss-pam-ldapd instead of pam_ldap and nss_ldap for
> > > the first time, and it appeared to work with a bit less of a hassle
> > > for me (otoh, I don't do any funky things here, I just need a
> > > replacement for what we did with NIS something like 20 years ago).
> >
> > +1
> > I just had to reinstall certs for my server.  which means copying
> > certs to several places (in a default config)
> > sendmail and syrus ad openssl (base) all look in different places.
> > you COULD make them all look in the same place
> > but that requires undersanding what is going on and not just cribbing
> > the config file off the net somewhere.
>
> I use dhcpd to pass that configuration. On system startup, dhclient
> asks to dhcpd server the ip, time-ntp, dns, and configuration for its
> current job (pkgs/ports to install, apache conf, postgres conf, certs,
> etc..)
> depending on it's intended current use. I followed an old paper from
> EuroBSDCon,... this
> http://2004.eurobsdcon.org/uploads/media/EBSD04_slides_41.pdf to do the
> setup. Easier and faster (at least for me) than ldap and related for
> server setup. For user management, don't know, I don't have jelly
> users, only daemons.
>
> >
> > I think ports and pkg are fine, but we need to have some more thought
> > put into how they all go together.
>
>
>
> ---   ---
> Eduardo Morras <emorrasg at yahoo.es>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
>
> ------------------------------
>
> End of freebsd-hackers Digest, Vol 689, Issue 2
> ***********************************************
>