On Tuesday 15 January 2002 10:24 am, Mayuresh Kathe wrote:
> > Changing /dev entries is very very high level stuff. Leave
> > these to Linus or Alan. There are associated with devices,
> > for which the rules are specified in the kernel. You need
> > special things like mknod to make entries there.
>
> I "know" what I am doing :)
> And I don't think Linus or most other people from the traditional
> _Unix_ community would approve of my acts ;)
I agree with you there. This sort of advice seems to me is very bad.
Against hackerdom, so to speak. ;-)
BTW, mknod is not so sacrosanct as the the OP makes us believe. It
would take about 25 lines of C code to write it from scratch.
> > I haven't seen a single posting where Binand gave some way
> > to justify tinkering of /dev in kernel sources. What he did
> > give was the method of handling the problem of handling "/"
> > entries in a sed replacement operation. There was nothing
> > incorrect with what Binand posted.
>
> I applied the technique which Binand had suggested to my kernel
> source,
Finally! Now I know why people were referring to me all the time.
Mea Culpa. Spare me, m'lord...
I don't mind anyone tinkering with the kernel sources. The GPL gives
everyone the freedom to do so. If you understand what you are doing,
then there is nothing like it.
Anyway, Mayuresh, while sed'ing in the kernel source, I hope you
have handled things like:
#define DEVDIR "/dev"
#define MYDEVICE DEVDIR "/mydevice"
Or:
#define MAKEDEVNAME(device) DEVDIR #device
if (create_device (MAKEDEVNAME (fubar)) {
printk ("Creating failed...\n");
}
Binand
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
