All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: tharbaugh@lnxi.com
Cc: linux-kernel@vger.kernel.org, klibc@zytor.com, akpm@digeo.com,
	azarah@nosferatu.za.org
Subject: Re: [PATCH] gen_init_cpio-slink_pipe_sock
Date: Fri, 12 Nov 2004 15:42:10 -0500	[thread overview]
Message-ID: <41952022.1050607@pobox.com> (raw)
In-Reply-To: <1100290509.3171.8.camel@tubarao>

Thayne Harbaugh wrote:
> diff -ur linux-2.6.10-rc1.orig/drivers/block/Kconfig linux-2.6.10-rc1/drivers/block/Kconfig
> --- linux-2.6.10-rc1.orig/drivers/block/Kconfig	2004-11-12 11:03:52.657108248 -0700
> +++ linux-2.6.10-rc1/drivers/block/Kconfig	2004-11-12 11:07:28.458301480 -0700
> @@ -363,10 +363,14 @@
>  	    file <name> <location> <mode> <uid> <gid>
>  	    dir <name> <mode> <uid> <gid>
>  	    nod <name> <mode> <uid> <gid> <dev_type> <maj> <min>
> +	    slink <name> <target> <mode> <uid> <gid>
> +	    pipe <name> <mode> <uid> <gid>
> +	    sock <name> <mode> <uid> <gid>
>  
>  	  Where:
> -	    <name>      name of the file/dir/nod in the archive
> +	    <name>      name of the file/dir/nod/etc in the archive
>  	    <location>  location of the file in the current filesystem
> +	    <target>    link target
>  	    <mode>      mode/permissions of the file
>  	    <uid>       user id (0=root)
>  	    <gid>       group id (0=root)

This info should get moved out of Kconfig, and into a Documentation/* 
text file somewhere.



> +/*
> + * Original work by Jeff Garzick

Please spell my last name correctly :)

  reply	other threads:[~2004-11-12 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 20:15 [PATCH] gen_init_cpio-slink_pipe_sock Thayne Harbaugh
2004-11-12 20:42 ` Jeff Garzik [this message]
2004-11-12 20:27   ` Thayne Harbaugh
2004-11-15 15:04   ` Thayne Harbaugh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41952022.1050607@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@digeo.com \
    --cc=azarah@nosferatu.za.org \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tharbaugh@lnxi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.