Sponsored Content
Full Discussion: Replace NIS and RFC2307
Top Forums UNIX for Advanced & Expert Users Replace NIS and RFC2307 Post 302846747 by cambridge on Sunday 25th of August 2013 03:40:59 PM
Old 08-25-2013
Network

You're quite right of course, and a reference implementation is indeed the next thing I'm working on. This is the way I work, I design on paper first, then implement. Others may have elected to get something working first, then write down what they did, but I think this is just a matter of choice. Both are required, I think the order is not so important. By writing the Internet Drafts first, I am very clear on what I need to implement, and on exactly how all the pieces fit together.

As for you seeing no advantages in my proposed design, perhaps this is because I haven't articulated the advantages with clarity yet. One would need to read through all of my Internet Drafts thoroughly to understand the advantages, and I don't expect the layman to do that. I shall be setting out advantages in a blog post soon. Watch this space.

Best regards,
Mark.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris NIS+ and RedHat NIS+

Hello all, I'm not sure if this is the right forum, but I would like to know if Redhat running NIS ( not NIS +) would have conflict with Solaris running NIS+. Currently I am running NIS+ on Solaris but will be adding RedHat to the network. I seem to be unable to find and information regarding... (2 Replies)
Discussion started by: larry
2 Replies

2. IP Networking

differences nis nis+

Hello together. Is there someone who is able to explain me the differences between NIS and NIS+. thanks in advance joerg (2 Replies)
Discussion started by: joerg
2 Replies

3. UNIX for Dummies Questions & Answers

NIS map mail.aliases specified, but NIS not running

Hi all, I just took over the admin role from someone and I wanna setup sendmail (just to send mail from the host) however, after I config all the resolv.conf, nssitch.conf, hosts file and when I try to send a mail out, after I punched ctl-D, it returned he following, "NIS map mail.aliases... (2 Replies)
Discussion started by: stancwong
2 Replies

4. UNIX for Advanced & Expert Users

SUSE 9 and 10 NIS clients with RedHat 8.0 NIS server not working

We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave. We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation. However, no matter what i do, the SUSE machines will not talk to the NIS Servers. If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies

5. Solaris

Help regarding NIS+

Hi Guys, I have lots of doubts regarding NIS+.I also think by basics could be wrong......I am trying to pick up stuff from documents which are a bit murky. I am working on production environment so I am afraid of trial and error! Please help. 1) What is the difference between root domain master... (1 Reply)
Discussion started by: nitinkgoud
1 Replies

6. Solaris

How to configure a NIS client bound to the NIS server in another subnet?

Hi, all. I have a Solaris client here needs to bind to NIS server in another subnet. Following is the configuration i made on the client, 1) edit /etc/inet/hosts to add an entry of the NIS server -- nserver01 2) execute `domainname` to set local NIS domain to the domain of the NIS server.... (1 Reply)
Discussion started by: sn_wukong
1 Replies

7. Shell Programming and Scripting

Validating that the NIS and NIS+ services are disabled

I'm creating a scrip for auditing our AIX box's to ensure that they are built according to our system standards. I'm not sure on the logic for checking to see if the NIS and NIS+ services are disabled. any idea's? (2 Replies)
Discussion started by: sport
2 Replies

8. Solaris

nis

how to see the all nis user details and individual user details ? (0 Replies)
Discussion started by: tirupathi
0 Replies

9. Linux

NIS

Hi All, I have configured NIS server in linux rhel5 and made one client member to that server. nfs share created for users home directory i have created one nis user, user not able to change the passwd of his login. getting below mentioned error " yppasswdd not running on NIS master... (1 Reply)
Discussion started by: vinay_ks
1 Replies

10. UNIX for Advanced & Expert Users

Replacing NIS and RFC2307

Last year I posted I had written some new internet drafts designed to replace NIS and which would be the next evolution of RFC2307 (a standard describing how to represent NIS data in LDAP). DBIS is now a reality. I have just completed a fully working reference implementation, and I would... (0 Replies)
Discussion started by: cambridge
0 Replies
GIT-IMAP-SEND(1)						    Git Manual							  GIT-IMAP-SEND(1)

NAME
git-imap-send - Send a collection of patches from stdin to an IMAP folder SYNOPSIS
git imap-send DESCRIPTION
This command uploads a mailbox generated with git format-patch into an IMAP drafts folder. This allows patches to be sent as other email is when using mail clients that cannot read mailbox files directly. The command also works with any general mailbox in which emails have the fields "From", "Date", and "Subject" in that order. Typical usage is something like: git format-patch --signoff --stdout --attach origin | git imap-send CONFIGURATION
To use the tool, imap.folder and either imap.tunnel or imap.host must be set to appropriate values. Variables imap.folder The folder to drop the mails into, which is typically the Drafts folder. For example: "INBOX.Drafts", "INBOX/Drafts" or "[Gmail]/Drafts". Required to use imap-send. imap.tunnel Command used to setup a tunnel to the IMAP server through which commands will be piped instead of using a direct network connection to the server. Required when imap.host is not set to use imap-send. imap.host A URL identifying the server. Use a imap:// prefix for non-secure connections and a imaps:// prefix for secure connections. Ignored when imap.tunnel is set, but required to use imap-send otherwise. imap.user The username to use when logging in to the server. imap.pass The password to use when logging in to the server. imap.port An integer port number to connect to on the server. Defaults to 143 for imap:// hosts and 993 for imaps:// hosts. Ignored when imap.tunnel is set. imap.sslverify A boolean to enable/disable verification of the server certificate used by the SSL/TLS connection. Default is true. Ignored when imap.tunnel is set. imap.preformattedHTML A boolean to enable/disable the use of html encoding when sending a patch. An html encoded patch will be bracketed with <pre> and have a content type of text/html. Ironically, enabling this option causes Thunderbird to send the patch as a plain/text, format=fixed email. Default is false. imap.authMethod Specify authenticate method for authentication with IMAP server. Current supported method is CRAM-MD5 only. Examples Using tunnel mode: [imap] folder = "INBOX.Drafts" tunnel = "ssh -q -C user@example.com /usr/bin/imapd ./Maildir 2> /dev/null" Using direct mode: [imap] folder = "INBOX.Drafts" host = imap://imap.example.com user = bob pass = p4ssw0rd Using direct mode with SSL: [imap] folder = "INBOX.Drafts" host = imaps://imap.example.com user = bob pass = p4ssw0rd port = 123 sslverify = false CAUTION
It is still your responsibility to make sure that the email message sent by your email program meets the standards of your project. Many projects do not like patches to be attached. Some mail agents will transform patches (e.g. wrap lines, send them as format=flowed) in ways that make them fail. You will get angry flames ridiculing you if you don't check this. Thunderbird in particular is known to be problematic. Thunderbird users may wish to visit this web page for more information: http://kb.mozillazine.org/Plain_text_e-mail_-_Thunderbird#Completely_plain_email AUTHOR
Derived from isync 1.0.1 by Mike McCormack. DOCUMENTATION
Documentation by Mike McCormack GIT
Part of the git(1) suite Git 1.7.1 07/05/2010 GIT-IMAP-SEND(1)
All times are GMT -4. The time now is 04:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy