Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/atstk1002
Date: Fri, 17 Aug 2007 06:16:36 -0700 (PDT)	[thread overview]
Message-ID: <20070817131636.AA616A45BB@busybox.net> (raw)

Author: ulf
Date: 2007-08-17 06:16:36 -0700 (Fri, 17 Aug 2007)
New Revision: 19541

Log:
Update atstk1002 device table

Modified:
   trunk/buildroot/target/device/Atmel/atstk1002/device_table.txt


Changeset:
Modified: trunk/buildroot/target/device/Atmel/atstk1002/device_table.txt
===================================================================
--- trunk/buildroot/target/device/Atmel/atstk1002/device_table.txt	2007-08-17 13:02:52 UTC (rev 19540)
+++ trunk/buildroot/target/device/Atmel/atstk1002/device_table.txt	2007-08-17 13:16:36 UTC (rev 19541)
@@ -1,31 +1,31 @@
-# When building a target filesystem, it is desirable to not have to
-# become root and then run 'mknod' a thousand times.  Using a device 
-# table you can create device nodes and directories "on the fly".
+# When building a target filesystem, it is desirable to not have to become
+# root and then run 'mknod' a thousand times.  Using a device table you can
+# create device nodes and directories "on the fly".
 #
-# This is a sample device table file for use with genext2fs.  You can
-# do all sorts of interesting things with a device table file.  For
-# example, if you want to adjust the permissions on a particular file
-# you can just add an entry like:
+# This is a sample device table file for use with genext2fs.  You can do all
+# sorts of interesting things with a device table file.  For example, if you
+# want to adjust the permissions on a particular file you can just add an
+# entry like:
 #   /sbin/foobar        f       2755    0       0       -       -       -       -       -
-# and (assuming the file /sbin/foobar exists) it will be made setuid
-# root (regardless of what its permissions are on the host filesystem.
+# and (assuming the file /sbin/foobar exists) it will be made setuid root
+# (regardless of what its permissions are on the host filesystem.
 # Furthermore, you can use a single table entry to create a many device
-# minors.  For example, if I wanted to create /dev/hda and /dev/hda[0-15]
-# I could just use the following two table entries:
+# minors.  For example, if I wanted to create /dev/hda and /dev/hda[0-15] I
+# could just use the following two table entries:
 #   /dev/hda    b       640     0       0       3       0       0       0       -
 #   /dev/hda    b       640     0       0       3       1       1       1       15
-# 
+#
 # Device table entries take the form of:
 # <name>    <type>      <mode>  <uid>   <gid>   <major> <minor> <start> <inc>   <count>
-# where name is the file name,  type can be one of: 
+# where name is the file name,  type can be one of:
 #       f       A regular file
 #       d       Directory
 #       c       Character special device file
 #       b       Block special device file
 #       p       Fifo (named pipe)
-# uid is the user id for the target file, gid is the group id for the
-# target file.  The rest of the entries (major, minor, etc) apply only 
-# to device special files.
+# uid is the user id for the target file, gid is the group id for the target
+# file.  The rest of the entries (major, minor, etc) apply only to device
+# special files.
 
 # Have fun
 # -Erik Andersen <andersen@codepoet.org>
@@ -41,9 +41,10 @@
 /config		d	755	0	0	-	-	-	-	-
 /proc		d	755	0	0	-	-	-	-	-
 /lost+found	d	700	0	0	-	-	-	-	-
-/var/tmp	d	1777	0	0	-	-	-	-	-
 /var/lock	d	1777	0	0	-	-	-	-	-
+/var/log	d	755	0	0	-	-	-	-	-
 /var/run	d	1777	0	0	-	-	-	-	-
+/var/tmp	d	1777	0	0	-	-	-	-	-
 /home/avr32	d	2755	500	500	-	-	-	-	-
 /home/default	d	2755	1000	1000	-	-	-	-	-
 /www		d	755	0	0	-	-	-	-	-

             reply	other threads:[~2007-08-17 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 13:16 ulf at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20 16:47 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/atstk1002 ulf at uclibc.org
2007-09-23 10:56 ulf at uclibc.org

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=20070817131636.AA616A45BB@busybox.net \
    --to=ulf@uclibc.org \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox