Menu
▾
▴
linuxconsole-dev
|
From: Zoltan B. <zb...@fr...> - 2006-05-07 10:18:52
Attachments:
faketty.patch
|
Hi, first, I would like to thank you for the faketty module, I stopped maintaining the ruby patch and was able to quickly restore my multihead machine after upgrading to FC5. I would like to know what do you think about the following modifications. - Instead of the "ftty%d" device names, use "tty%d", count from the number of normal TTY devices and up, e.g. ftty0 -> tty64, etc. - RC script now don't delete tty devices to create symlinks. - Also, RC script can use the "chkconfig" facility, use "make install-service-rh" to install it that way. Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi |
|
From: Matt K. <mat...@bt...> - 2006-05-07 21:26:13
|
Zoltan Boszormenyi wrote: > Hi, > > first, I would like to thank you for the faketty module, > I stopped maintaining the ruby patch and was able to quickly > restore my multihead machine after upgrading to FC5. > > I would like to know what do you think about the following modifications. > > - Instead of the "ftty%d" device names, use "tty%d", > count from the number of normal TTY devices and up, > e.g. ftty0 -> tty64, etc. > - RC script now don't delete tty devices to create symlinks. > - Also, RC script can use the "chkconfig" facility, use > "make install-service-rh" to install it that way. Maybe a better way of doing this is to use the lsb service install scripts (lsbinstall and friends). The packages for the relevant platforms would need to depend on the lsb-core package, but I suspect that is easier to work with than trying to support all the different distro's ways of installing init scripts. Matt |
|
From: Aivils S. <ai...@un...> - 2006-05-10 11:28:57
|
On Sv=C4=93tdiena, 7. Maijs 2006 13:18, Zoltan Boszormenyi wrote: > Hi, > > first, I would like to thank you for the faketty module, > I stopped maintaining the ruby patch and was able to quickly > restore my multihead machine after upgrading to FC5. > > I would like to know what do you think about the following modifications. > > - Instead of the "ftty%d" device names, use "tty%d", > count from the number of normal TTY devices and up, > e.g. ftty0 -> tty64, etc. Do You think continuation of classic row of TTY device files is good idea? Will any X use TTY number higher than 63? > - RC script now don't delete tty devices to create symlinks. > - Also, RC script can use the "chkconfig" facility, use > "make install-service-rh" to install it that way. > I never use another distro but redhat/mandrake only. Exists any distro friendly install script? Aivils |
|
From: Zoltan B. <zb...@fr...> - 2006-05-10 21:15:18
|
Aivils Stoss =C3=ADrta: > On Sv=C4=93tdiena, 7. Maijs 2006 13:18, Zoltan Boszormenyi wrote: > =20 >> Hi, >> >> first, I would like to thank you for the faketty module, >> I stopped maintaining the ruby patch and was able to quickly >> restore my multihead machine after upgrading to FC5. >> >> I would like to know what do you think about the following modificatio= ns. >> >> - Instead of the "ftty%d" device names, use "tty%d", >> count from the number of normal TTY devices and up, >> e.g. ftty0 -> tty64, etc. >> =20 > > Do You think continuation of classic row of TTY device files is good id= ea? > Will any X use TTY number higher than 63? > =20 Xorg 7.x uses it happily. I don't think this is different from earlier 6.= x or XFree86 4.x. One has to test it, though. >> - RC script now don't delete tty devices to create symlinks. >> - Also, RC script can use the "chkconfig" facility, use >> "make install-service-rh" to install it that way. >> >> =20 > > I never use another distro but redhat/mandrake only. Exists any > distro friendly install script? > =20 Does mandrake have "chkconfig"? Best regards, Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi |
|
From: Aivils S. <ai...@un...> - 2006-05-11 13:27:33
|
On Ceturtdiena, 11. Maijs 2006 00:14, Zoltan Boszormenyi wrote: > Aivils Stoss =C3=ADrta: > > On Sv=C4=93tdiena, 7. Maijs 2006 13:18, Zoltan Boszormenyi wrote: > >> Hi, > >> > >> first, I would like to thank you for the faketty module, > >> I stopped maintaining the ruby patch and was able to quickly > >> restore my multihead machine after upgrading to FC5. > >> > >> I would like to know what do you think about the following > >> modifications. > >> > >> - Instead of the "ftty%d" device names, use "tty%d", > >> count from the number of normal TTY devices and up, > >> e.g. ftty0 -> tty64, etc. > > > > Do You think continuation of classic row of TTY device files is good > > idea? Will any X use TTY number higher than 63? > > Xorg 7.x uses it happily. I don't think this is different from earlier 6.x > or XFree86 4.x. One has to test it, though. Well. Since Xfree 3.0.0 is 0 up to 99 two ciphers supported (vtXX). > > >> - RC script now don't delete tty devices to create symlinks. > >> - Also, RC script can use the "chkconfig" facility, use > >> "make install-service-rh" to install it that way. > > > > I never use another distro but redhat/mandrake only. Exists any > > distro friendly install script? > > Does mandrake have "chkconfig"? Yes. But it have redhat like distros only.=20 > Best regards, > Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi |
|
From: Hugo V. <hvw...@ya...> - 2006-05-10 19:46:33
|
--- Zoltan Boszormenyi <zb...@fr...> wrote: > Hi, > > first, I would like to thank you for the faketty > module, > I stopped maintaining the ruby patch and was able to > quickly > restore my multihead machine after upgrading to FC5. > > I would like to know what do you think about the > following modifications. > > - Instead of the "ftty%d" device names, use "tty%d", > count from the number of normal TTY devices and > up, > e.g. ftty0 -> tty64, etc. > - RC script now don't delete tty devices to create > symlinks. > - Also, RC script can use the "chkconfig" facility, > use > "make install-service-rh" to install it that way. > > Best regards, > Zolt�n B�sz�rm�nyi And the reason for changes? I kind of like it the way it is. Hugo __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Zoltan B. <zb...@fr...> - 2006-05-10 21:15:18
|
Hugo Vanwoerkom =EDrta: > --- Zoltan Boszormenyi <zb...@fr...> wrote: > > =20 >> Hi, >> >> first, I would like to thank you for the faketty >> module, >> I stopped maintaining the ruby patch and was able to >> quickly >> restore my multihead machine after upgrading to FC5. >> >> I would like to know what do you think about the >> following modifications. >> >> - Instead of the "ftty%d" device names, use "tty%d", >> count from the number of normal TTY devices and >> up, >> e.g. ftty0 -> tty64, etc. >> - RC script now don't delete tty devices to create >> symlinks. >> - Also, RC script can use the "chkconfig" facility, >> use >> "make install-service-rh" to install it that way. >> >> Best regards, >> Zolt=EF=BF=BDn B=EF=BF=BDsz=EF=BF=BDrm=EF=BF=BDnyi >> =20 > > > And the reason for changes? I kind of like it the way > it is. > > Hugo > =20 Reason #1: It's not really legal to delete device nodes that are controlled by another driver. Reason #2: Given #1 above, it would be more useful to just create links as /dev/tty64 and up and still have ftty devices. It would be best to use an udev rule, but I haven't seen any way to do it. E.g. suppose that SYMLINK command can use options, and %m gives you the minor number of the device it has just created, this latter being an existing udev feature. Now, a rule like this would d= o: KERNEL=3D=3D"ftty" GROUP=3D"tty" MODE=3D"0660", SYMLINK=3D"tty(64+%m)" But you cannot really detect the maximum number of the TTY device nodes just by looking at them, something else may have deleted them, too. As I see now, the only reliable way to detect the next number is using "MAX_NR_CONSOLES + 1" for the running kernel. I would be happy to be proven wrong, though. Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi |
|
From: Aivils S. <ai...@un...> - 2006-05-11 13:21:18
|
On Ceturtdiena, 11. Maijs 2006 00:15, Zoltan Boszormenyi wrote: > Hugo Vanwoerkom =EDrta: > > --- Zoltan Boszormenyi <zb...@fr...> wrote: > >> Hi, > >> > >> first, I would like to thank you for the faketty > >> module, > >> I stopped maintaining the ruby patch and was able to > >> quickly > >> restore my multihead machine after upgrading to FC5. > >> > >> I would like to know what do you think about the > >> following modifications. > >> > >> - Instead of the "ftty%d" device names, use "tty%d", > >> count from the number of normal TTY devices and > >> up, > >> e.g. ftty0 -> tty64, etc. > >> - RC script now don't delete tty devices to create > >> symlinks. > >> - Also, RC script can use the "chkconfig" facility, > >> use > >> "make install-service-rh" to install it that way. > >> > >> Best regards, > >> Zolt=EF=BF=BDn B=EF=BF=BDsz=EF=BF=BDrm=EF=BF=BDnyi > > > > And the reason for changes? I kind of like it the way > > it is. > > > > Hugo > > Reason #1: It's not really legal to delete device nodes that are > controlled by another driver. Driver didn't control device node, which is tricky access of special features. Node was created by system operator (nowadays smart script) can be deleted by system operator. Agree, deleting is not correct against another drivers. Of course faketty starting script created without long thinking. Not once opened nodes deleted careless. > Reason #2: Given #1 above, it would be more useful to just > create links as /dev/tty64 and up and still have ftty devices. > It would be best to use an udev rule, but I haven't seen any way > to do it. E.g. suppose that SYMLINK command can use options, > and %m gives you the minor number of the device it has just created, > this latter being an existing udev feature. Now, a rule like this would d= o: > KERNEL=3D=3D"ftty" GROUP=3D"tty" MODE=3D"0660", SYMLINK=3D"tty(64+%m)" > > But you cannot really detect the maximum number of the TTY device nodes > just by looking at them, something else may have deleted them, too. > As I see now, the only reliable way to detect the next number is using > "MAX_NR_CONSOLES + 1" for the running kernel. > I would be happy to be proven wrong, though. I suppose this is spliting of hairs. Should we ask for name to Linus Torvald? i read out linux/Documentation/devices.txt again, but that does not give solution for me. i have not plans to include faketty in mainstream kernel. faketty have public release. Aivils Stoss |
|
From: Zoltan B. <zb...@fr...> - 2006-05-13 08:08:56
|
Hi,
Aivils Stoss =EDrta:
> On Ceturtdiena, 11. Maijs 2006 00:15, Zoltan Boszormenyi wrote:
> =20
>> Hugo Vanwoerkom =EDrta:
>> =20
>>> --- Zoltan Boszormenyi <zb...@fr...> wrote:
>>> =20
>>>> Hi,
>>>>
>>>> first, I would like to thank you for the faketty
>>>> module,
>>>> I stopped maintaining the ruby patch and was able to
>>>> quickly
>>>> restore my multihead machine after upgrading to FC5.
>>>>
>>>> I would like to know what do you think about the
>>>> following modifications.
>>>>
>>>> - Instead of the "ftty%d" device names, use "tty%d",
>>>> count from the number of normal TTY devices and
>>>> up,
>>>> e.g. ftty0 -> tty64, etc.
>>>> - RC script now don't delete tty devices to create
>>>> symlinks.
>>>> - Also, RC script can use the "chkconfig" facility,
>>>> use
>>>> "make install-service-rh" to install it that way.
>>>>
>>>> Best regards,
>>>> Zolt=EF=BF=BDn B=EF=BF=BDsz=EF=BF=BDrm=EF=BF=BDnyi
>>>> =20
>>> And the reason for changes? I kind of like it the way
>>> it is.
>>>
>>> Hugo
>>> =20
>> Reason #1: It's not really legal to delete device nodes that are
>> controlled by another driver.
>> =20
>
> Driver didn't control device node, which is tricky access of
> special features. Node was created by system operator (nowadays smart
> script) can be deleted by system operator. Agree, deleting is not
> correct against another drivers.
> Of course faketty starting script created without long thinking.
> Not once opened nodes deleted careless.
>
> =20
>> Reason #2: Given #1 above, it would be more useful to just
>> create links as /dev/tty64 and up and still have ftty devices.
>> It would be best to use an udev rule, but I haven't seen any way
>> to do it. E.g. suppose that SYMLINK command can use options,
>> and %m gives you the minor number of the device it has just created,
>> this latter being an existing udev feature. Now, a rule like this woul=
d do:
>> KERNEL=3D=3D"ftty" GROUP=3D"tty" MODE=3D"0660", SYMLINK=3D"tty(64+%m)"
>>
>> But you cannot really detect the maximum number of the TTY device node=
s
>> just by looking at them, something else may have deleted them, too.
>> As I see now, the only reliable way to detect the next number is using
>> "MAX_NR_CONSOLES + 1" for the running kernel.
>> I would be happy to be proven wrong, though.
>> =20
>
> I suppose this is spliting of hairs. Should we ask for name to Linus
> Torvald? i read out linux/Documentation/devices.txt again, but that doe=
s
> not give solution for me. i have not plans to include faketty in
> mainstream kernel. faketty have public release.
>
> Aivils Stoss
> =20
I just learned that patching faketty is not necessary.
XOrg/XFree86 has two keyboard drivers, the built-in "keyboard" and
the loadable "kbd". If you use the "kbd" driver, you can specify
the device it has to drive, so e.g. this works:
Section "InputDevice"
Identifier "kbd0"
Driver "kbd"
Device "/dev/ftty0"
...
EndSection
Multiple keyboards could be assigned to an X server,
so e.g. as my USB keyboard provides two input devices,
one for the normal keys and I guess the other for the
multimedia keys, both could be assigned to one of the X servers.
The bttv card's input device also could be used, so LIRC enabled
software can be used, too.
So, deleting /dev/tty5* isn't necessary either, one has to specify
the device in the InputDevice sectionin xorg.conf/XF86Config
instead of the Xserver command line as vtX.
Sorry for the noise.
Best regards,
Zolt=E1n B=F6sz=F6rm=E9nyi
|
|
From: Aivils S. <ai...@un...> - 2006-05-15 08:54:03
|
On Sestdiena, 13. Maijs 2006 11:08, Zoltan Boszormenyi wrote: > Hi, > > Aivils Stoss =EDrta: > > On Ceturtdiena, 11. Maijs 2006 00:15, Zoltan Boszormenyi wrote: > >> Hugo Vanwoerkom =EDrta: > >>> --- Zoltan Boszormenyi <zb...@fr...> wrote: > >>>> Hi, > >>>> > >>>> first, I would like to thank you for the faketty > >>>> module, > >>>> I stopped maintaining the ruby patch and was able to > >>>> quickly > >>>> restore my multihead machine after upgrading to FC5. > >>>> > >>>> I would like to know what do you think about the > >>>> following modifications. > >>>> > >>>> - Instead of the "ftty%d" device names, use "tty%d", > >>>> count from the number of normal TTY devices and > >>>> up, > >>>> e.g. ftty0 -> tty64, etc. > >>>> - RC script now don't delete tty devices to create > >>>> symlinks. > >>>> - Also, RC script can use the "chkconfig" facility, > >>>> use > >>>> "make install-service-rh" to install it that way. > >>>> > >>>> Best regards, > >>>> Zolt=EF=BF=BDn B=EF=BF=BDsz=EF=BF=BDrm=EF=BF=BDnyi > >>> > >>> And the reason for changes? I kind of like it the way > >>> it is. > >>> > >>> Hugo > >> > >> Reason #1: It's not really legal to delete device nodes that are > >> controlled by another driver. > > > > Driver didn't control device node, which is tricky access of > > special features. Node was created by system operator (nowadays smart > > script) can be deleted by system operator. Agree, deleting is not > > correct against another drivers. > > Of course faketty starting script created without long thinking. > > Not once opened nodes deleted careless. > > > >> Reason #2: Given #1 above, it would be more useful to just > >> create links as /dev/tty64 and up and still have ftty devices. > >> It would be best to use an udev rule, but I haven't seen any way > >> to do it. E.g. suppose that SYMLINK command can use options, > >> and %m gives you the minor number of the device it has just created, > >> this latter being an existing udev feature. Now, a rule like this would > >> do: KERNEL=3D=3D"ftty" GROUP=3D"tty" MODE=3D"0660", SYMLINK=3D"tty(64+= %m)" > >> > >> But you cannot really detect the maximum number of the TTY device nodes > >> just by looking at them, something else may have deleted them, too. > >> As I see now, the only reliable way to detect the next number is using > >> "MAX_NR_CONSOLES + 1" for the running kernel. > >> I would be happy to be proven wrong, though. > > > > I suppose this is spliting of hairs. Should we ask for name to Linus > > Torvald? i read out linux/Documentation/devices.txt again, but that does > > not give solution for me. i have not plans to include faketty in > > mainstream kernel. faketty have public release. > > > > Aivils Stoss > > I just learned that patching faketty is not necessary. > XOrg/XFree86 has two keyboard drivers, the built-in "keyboard" and > the loadable "kbd". If you use the "kbd" driver, you can specify > the device it has to drive, so e.g. this works: > > Section "InputDevice" > Identifier "kbd0" > Driver "kbd" > Device "/dev/ftty0" > ... > EndSection > > Multiple keyboards could be assigned to an X server, > so e.g. as my USB keyboard provides two input devices, > one for the normal keys and I guess the other for the > multimedia keys, both could be assigned to one of the X servers. > The bttv card's input device also could be used, so LIRC enabled > software can be used, too. > > So, deleting /dev/tty5* isn't necessary either, one has to specify > the device in the InputDevice sectionin xorg.conf/XF86Config > instead of the Xserver command line as vtX. Wow! I first time read about keyboard device specifying. I should update documentation any way. Older X like 6.8.2 couldn't use this nice feature because open ttyXX every time, is in use that or another keyboard driver. Older X does not have -sharetty option for simultaneous run. Aivils > Sorry for the noise. > > Best regards, > Zolt=E1n B=F6sz=F6rm=E9nyi |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X