From: Rob Love <rml@ximian.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] install initscript in udev rpm
Date: Wed, 17 Dec 2003 15:46:54 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107167633008671@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107159510124551@msgid-missing>
On Wed, 2003-12-17 at 03:28, Marco d'Itri wrote:
> Here it is.
> There is a bug I have not fixed yet (it breaks if /sys/class/video4linux/
> does not exist).
Maybe this is what I am seeing, but I took a diff of the results in
/udev from the current initscript and your's, and I am missing a bunch
of stuff. The diff is below.
But this does, otherwise, work on Red Hat, although it obviously does
not follow the style or anything of the regular Red Hat initscripts.
Rob Love
--- dog 2003-12-17 10:43:28.000000000 -0500
+++ fox 2003-12-17 10:44:10.798297408 -0500
@@ -1,292 +1,5 @@
console
-hda
-hda1
-hda2
-hda3
-hdc
-loop0
-loop1
-loop2
-loop3
-loop4
-loop5
-loop6
-loop7
-md0
ptmx
-ram0
-ram1
-ram10
-ram11
-ram12
-ram13
-ram14
-ram15
-ram2
-ram3
-ram4
-ram5
-ram6
-ram7
-ram8
-ram9
-rfcomm0
-rfcomm1
-rfcomm10
-rfcomm100
-rfcomm101
-rfcomm102
-rfcomm103
-rfcomm104
-rfcomm105
-rfcomm106
-rfcomm107
-rfcomm108
-rfcomm109
-rfcomm11
-rfcomm110
-rfcomm111
-rfcomm112
-rfcomm113
-rfcomm114
-rfcomm115
-rfcomm116
-rfcomm117
-rfcomm118
-rfcomm119
-rfcomm12
-rfcomm120
-rfcomm121
-rfcomm122
-rfcomm123
-rfcomm124
-rfcomm125
-rfcomm126
-rfcomm127
-rfcomm128
-rfcomm129
-rfcomm13
-rfcomm130
-rfcomm131
-rfcomm132
-rfcomm133
-rfcomm134
-rfcomm135
-rfcomm136
-rfcomm137
-rfcomm138
-rfcomm139
-rfcomm14
-rfcomm140
-rfcomm141
-rfcomm142
-rfcomm143
-rfcomm144
-rfcomm145
-rfcomm146
-rfcomm147
-rfcomm148
-rfcomm149
-rfcomm15
-rfcomm150
-rfcomm151
-rfcomm152
-rfcomm153
-rfcomm154
-rfcomm155
-rfcomm156
-rfcomm157
-rfcomm158
-rfcomm159
-rfcomm16
-rfcomm160
-rfcomm161
-rfcomm162
-rfcomm163
-rfcomm164
-rfcomm165
-rfcomm166
-rfcomm167
-rfcomm168
-rfcomm169
-rfcomm17
-rfcomm170
-rfcomm171
-rfcomm172
-rfcomm173
-rfcomm174
-rfcomm175
-rfcomm176
-rfcomm177
-rfcomm178
-rfcomm179
-rfcomm18
-rfcomm180
-rfcomm181
-rfcomm182
-rfcomm183
-rfcomm184
-rfcomm185
-rfcomm186
-rfcomm187
-rfcomm188
-rfcomm189
-rfcomm19
-rfcomm190
-rfcomm191
-rfcomm192
-rfcomm193
-rfcomm194
-rfcomm195
-rfcomm196
-rfcomm197
-rfcomm198
-rfcomm199
-rfcomm2
-rfcomm20
-rfcomm200
-rfcomm201
-rfcomm202
-rfcomm203
-rfcomm204
-rfcomm205
-rfcomm206
-rfcomm207
-rfcomm208
-rfcomm209
-rfcomm21
-rfcomm210
-rfcomm211
-rfcomm212
-rfcomm213
-rfcomm214
-rfcomm215
-rfcomm216
-rfcomm217
-rfcomm218
-rfcomm219
-rfcomm22
-rfcomm220
-rfcomm221
-rfcomm222
-rfcomm223
-rfcomm224
-rfcomm225
-rfcomm226
-rfcomm227
-rfcomm228
-rfcomm229
-rfcomm23
-rfcomm230
-rfcomm231
-rfcomm232
-rfcomm233
-rfcomm234
-rfcomm235
-rfcomm236
-rfcomm237
-rfcomm238
-rfcomm239
-rfcomm24
-rfcomm240
-rfcomm241
-rfcomm242
-rfcomm243
-rfcomm244
-rfcomm245
-rfcomm246
-rfcomm247
-rfcomm248
-rfcomm249
-rfcomm25
-rfcomm250
-rfcomm251
-rfcomm252
-rfcomm253
-rfcomm254
-rfcomm255
-rfcomm26
-rfcomm27
-rfcomm28
-rfcomm29
-rfcomm3
-rfcomm30
-rfcomm31
-rfcomm32
-rfcomm33
-rfcomm34
-rfcomm35
-rfcomm36
-rfcomm37
-rfcomm38
-rfcomm39
-rfcomm4
-rfcomm40
-rfcomm41
-rfcomm42
-rfcomm43
-rfcomm44
-rfcomm45
-rfcomm46
-rfcomm47
-rfcomm48
-rfcomm49
-rfcomm5
-rfcomm50
-rfcomm51
-rfcomm52
-rfcomm53
-rfcomm54
-rfcomm55
-rfcomm56
-rfcomm57
-rfcomm58
-rfcomm59
-rfcomm6
-rfcomm60
-rfcomm61
-rfcomm62
-rfcomm63
-rfcomm64
-rfcomm65
-rfcomm66
-rfcomm67
-rfcomm68
-rfcomm69
-rfcomm7
-rfcomm70
-rfcomm71
-rfcomm72
-rfcomm73
-rfcomm74
-rfcomm75
-rfcomm76
-rfcomm77
-rfcomm78
-rfcomm79
-rfcomm8
-rfcomm80
-rfcomm81
-rfcomm82
-rfcomm83
-rfcomm84
-rfcomm85
-rfcomm86
-rfcomm87
-rfcomm88
-rfcomm89
-rfcomm9
-rfcomm90
-rfcomm91
-rfcomm92
-rfcomm93
-rfcomm94
-rfcomm95
-rfcomm96
-rfcomm97
-rfcomm98
-rfcomm99
-sr0
tty
tty0
tty1
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-12-17 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 17:11 [patch] install initscript in udev rpm Marco d'Itri
2003-12-16 17:23 ` Greg KH
2003-12-16 17:31 ` Rob Love
2003-12-16 23:31 ` Greg KH
2003-12-17 0:13 ` Marco d'Itri
2003-12-17 1:01 ` Greg KH
2003-12-17 8:28 ` Marco d'Itri
2003-12-17 15:46 ` Rob Love [this message]
2003-12-17 18:11 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 17:03 Rob Love
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=marc-linux-hotplug-107167633008671@msgid-missing \
--to=rml@ximian.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).