I just ran into the problem of not being able to SU after installing InteractiveBastille and believe that maybe it was InteractiveBastille that changed the behavoir of my ctrl+alt+Fkeys. i would be curious to know if users who do not have interactiveBastille installed and configured are able to Ctrl=alt+fkey to different terminals or if it brings their system to the state I described below. (this certainly will make me learn the command prompt ; )) On Thursday 09 August 2001 02:11, Paul wrote: > > C+A+F1 = non graphic login screen (no big deal) > > C+A+F2 = x server crash message (I don't know where these logs are so i > > can't share) > > C+A+F3-6= nongraphic login screen (same as 1) > > These are normal. The crash message in tty2 should not be there I think. > But if X works after you hit ctrl-alt-f9 that's fine. > > > C+A+F7 however, brought up what I imaginge is my ports entry log. (i > > don't know where it lives yet so can't share) But, X went away and I had > > a portsentry alert of a UDp scan by host xxx.xxx.xxx.xxx > > I know there is a text screen that shows the messages from the Xwindow > server. And you found it ;) > > > C+A+F10 -11 brings up a blinking curser after x goes away > > These are extra sessions where X can live. When you log into tty3, you can > start another X session which will live under ctrl-alt-f10, etc. > > > C+A+F12 brings up the graphical state of the system.(just like when its > > booting) > > Never saw that, I'll try it someday :) > > > Of course, C+A+F9 brings back X no matter what I tried. Strange...What > > different from my system that this doesn't work?? > > > > And is this a cool feature of portsentry that you can simply press C+A+F7 > > to see your log and then C+A+F9 to enter back into X?? > > Nope, that is pretty standard. Has nothing to do with PortSentry. > Paul
