Date: Sun, 5 Mar 2000 10:46:15 -0600 (CST) From: Ryan Thompson <ryan@sasknow.com> To: Doug Young <dougy@gargoyle.apana.org.au> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Remote Control Message-ID: <Pine.BSF.4.21.0003051022170.1260-100000@stimpy.sasknow.com> In-Reply-To: <015d01bf86b5$c2f0d970$847e03cb@ROADRUNNER>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Young wrote to freebsd-questions@FreeBSD.ORG: > I'd appreciate some advice / comments on running applications on > a FreeBSD machine from other machines on the LAN & even > over the internet if possible. I realize some things can be done > using good old telnet, but occasionally I find things that don't > respond ... eg "/stand/sysinstall" only gets so far and refuses to > take any notice. Why? Perhaps your terminal is incorrectly configured. I've ran through just about everything in sysinstall from a remote network over plain ol' telnet without problems. (Of course, I used the X configure shell script instead of XF86Setup :-) > I figure at least some of the problem is related to the inability of my > telnet setup to recognize colors, Perhaps more accurately, your telnet program is talking a different terminal language than your login shell is. vt100 is the defacto standard for remote access stuff, and your terminal program should support it. If you're not using it, you should. Most "smart" terminal programs, if they do not support colour, at least ignore the escape codes to save your screen from the mess. > but I don't know if there's a way around that Try a better terminal emulator :-) If you're connecting from a UNIX console seat, you should have no troubles. If you're connecting from Windows or some crappier X terminal emulators, some additional setup might be required. Crappy as it is though, I used Windows' stock telnet to configure, and launch a production webserver with a few dozen other packages (then) running 2.2.8 from halfway around the world, after a base distribution had been installed from the other end. If I could do that in a 12 hour shift from a constantly crashing 95 machine at my other job at the time, on a slow LAN through multiple restrictive firewalls while getting up every five minutes to change binders, go weld or bail someone out of trouble, YOU should be able to piddle around on a few machines. > & if thats the only limiting factor in running applications > remotely. Probably. You'll have problems gaining root access remotely. Use SSH. If you really can't do that, add yourself to the wheel group and use su. > I also tried a few X-window servers in MS Windows > boxes but all the ones I've tried have proved far too messy to > configure / use / license.... seems those sorts of things are far > more trouble than they are worth. http://www.tucows.com/, pick a local mirror, and check out Server Tools:X Servers:XWin Pro On MY system, in Saskatchewan Canada (maybe a bit far :-): http://sasknow.tucows.com/adnload/nt/dlxwinpront.html ... for Windows NT. It'll work like conventional X and have client windows pop up, or it'll stick your login desktop manager windowed or full-screen, and hide your taskbar. Cursors and all, you'd never know you're not in X. > IS there a way to run EVERYTHING in a non-X FreeBSD system > from elsewhere using only telnet ?? I'd still recommend SSH for the added security and X tunneling... But I have multiple headless servers around here, and more that I administer remotely, using nothing more than ssh hostname -l root. If you want even better, and are near the machines you are running, you can use a serial console that will even allow you to be in on bootup and single-user stuff. -- Ryan Thompson <ryan@sasknow.com> Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003051022170.1260-100000>