Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2537 comp.os.linux.misc:16561
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!EU.net!Germany.EU.net!netmbx.de!zrz.TU-Berlin.DE!zib-berlin.de!irz401!uriah!not-for-mail
From: j@uriah.sax.de (J Wunsch)
Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc
Subject: Re: Linux vs *BSD (new twist)
Date: 5 Jun 1994 16:56:57 +0200
Organization: Private U**X site; member IN e.V.
Lines: 23
Message-ID: <2ssp3pINN4ql@bonnie.sax.de>
References: <2sl6o3$pvs@aurora.engr.latech.edu> <2smc4m$daj@Mercury.mcs.com> <2sndmu$bnk@acmez.gatech.edu>
NNTP-Posting-Host: bonnie.sax.de
gt8134b@prism.gatech.edu (Robert Sanders) writes:
>>: How do you use virtual consoles on FreeBSD?
>>Compile with SYSCONS and RTFM.
>Actually, what the FM doesn't mention is that, unlike Linux consoles,
>you can't switch to a FreeBSD console unless it is "open", and the only
>way to make a console open is to make it someone's controlling tty. I
Though i'm not using syscons (i'm using pcvt where you can swith to a
non-opened vt if you like), this is mainly due to the fact that Soeren
attempted to emulate as much of the SCO console behaviour as possible.
Anyway, `cat foo > /dev/ttyvX' should also open the vt and print `foo'
on it (as long as you've got permission to do so). The problem is, if
the `cat' proceeds in rather short time, you won't be able to ever see
the output, since you don't stand a chance to switch to this vt ;-)
But this is intended, since it's SCO-like...
--
cheers, J"org work: joerg_wunsch@tcd-dresden.de
private: joerg_wunsch@uriah.sax.de
Steinbach's Guideline for Systems Programming:
Never test for an error condition you don't know how to handle.