using vgl

1999-12-25 Thread Tim Tsai

I'm trying to do some work based on vgl but it appears that it is tied to
syscons and any vgl programs must be started off a console.  Is there any
way I can start a vgl program from a remote terminal (but have the output
be displayed on the local VGA screen) without writing a proxy of some
kind?

I peeked at the source and there are various syscons related ioctl() calls.
Any reason that /dev/io and /dev/mem wasn't used instead?

Thanks!

Tim


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Signal 11 during setup

1999-12-25 Thread Xavier O'Neill

Hello,

 I presently have FreeBSD 2.2.8 on my system.  I downloaded FreeBSD 3.4 
Release and made two floppy images on newly formated floppies (did it 
twice).  During setup on the mfsroot.flp

I get a signal 11 error (Signal 11 error, I am saving what I can. ).

From there the computer restarts.

I did all kinds of trouble shooting and diagnostics as described by the 
sig11 FAQ link i seen on the FreeBSD site.

I went to a holographic terminal to see the debugging, this error always 
happens as the /etc/fstab is being written.

I never had a problem with this computer.  It is fairly new.  A p2 300 mhz, 
with 128 MB ram

Someone told me on the FreeBSD channel (effnet) that someone on the design 
team broke it, don't know if he is a reliable source but he claimed to be a 
part of the freebsd developer team.

Thank you very much :)

warm reguard
-xavier
__
Get Your Private, Free Email at http://www.hotmail.com



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: using vgl

1999-12-25 Thread Brian Fundakowski Feldman

On Sat, 25 Dec 1999, Tim Tsai wrote:

 I'm trying to do some work based on vgl but it appears that it is tied to
 syscons and any vgl programs must be started off a console.  Is there any
 way I can start a vgl program from a remote terminal (but have the output
 be displayed on the local VGA screen) without writing a proxy of some
 kind?

Err... why do you want to do that?  Even if it's a big program, it should
be properly written so that the frontend and backend can be separate
and network-transparent, if that's to be its purpose.  So the big question
is, why aren't you using X11?

 
 I peeked at the source and there are various syscons related ioctl() calls.
 Any reason that /dev/io and /dev/mem wasn't used instead?

That's simple.  We're not trying to move to making things MORE platform-
specific.

 
 Thanks!
 
 Tim

-- 
 Brian Fundakowski Feldman   \  FreeBSD: The Power to Serve!  /
 [EMAIL PROTECTED]`--'



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: device name of floppy disk

1999-12-25 Thread Brian Fundakowski Feldman

On Sat, 25 Dec 1999, KATO Takenori wrote:

 The MAKEDEV has such lines as:
 
   # ln -f ${name}${unit}.1200 ${name}${unit}96
   # ln -f r${name}${unit}.1200 r${name}${unit}96
   # ln -f ${name}${unit}.1200 ${name}${unit}96ds15
   # ln -f r${name}${unit}.1200 r${name}${unit}96ds15
   # ln -f ${name}${unit}.1200 ${name}${unit}135ds15
   # ln -f r${name}${unit}.1200 r${name}${unit}135ds15
 
 for floppy disk device.  I have questions about these lines.
 
 1. What is meanings of the name?  I cannot understand meanings of
`96', `96ds15' and `135ds15'.

They're all synonymous, so I'd say that they're different names for a
double-sided, high density 5.25" floppy.  The difference between 135
and 96 is probably sector sizes.  In any case, I wouldn't worry over
them at all.

 2. Why they are commented out?

Obsolescence, I'd think.

 3. Are these entries mandatory for all floppy disk devices?  (Should I 
make such lines when I add new mode for floppy disk?)

When's the last time you saw new modes for 5.25" floppies?  I'm not
being sarcastic;  I'm just pointing out that they're all obsolete.

 
 Thanks.
 
 ---+--+
 KATO Takenori [EMAIL PROTECTED]  |FreeBSD   |
 Dept. Earth Planet. Sci, Nagoya Univ.  |The power to serve!   |
 Nagoya, 464-8602, Japan|  http://www.FreeBSD.org/ |
|http://www.jp.FreeBSD.org/|
  FreeBSD(98) 3.3R-Rev. 01 available!   +==+

-- 
 Brian Fundakowski Feldman   \  FreeBSD: The Power to Serve!  /
 [EMAIL PROTECTED]`--'



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: using vgl

1999-12-25 Thread Tim Tsai

On Sat, Dec 25, 1999 at 01:07:50PM -0500, Brian Fundakowski Feldman wrote:
 On Sat, 25 Dec 1999, Tim Tsai wrote:
 
  I'm trying to do some work based on vgl but it appears that it is tied to
  syscons and any vgl programs must be started off a console.  Is there any
  way I can start a vgl program from a remote terminal (but have the output
  be displayed on the local VGA screen) without writing a proxy of some
  kind?
 
 Err... why do you want to do that?  Even if it's a big program, it should
 be properly written so that the frontend and backend can be separate
 and network-transparent, if that's to be its purpose.  So the big question
 is, why aren't you using X11?

  Because I want to?  :-)

  Okay, this particular FreeBSD box is connected to a scan converter and
the output is displayed on my TV.  Sitting in front of the console is not
real practical literally as the computer is nicely tucked away.  It just
seems weird to have vgl so tied to syscons when one of the big advantages
of Unix has always been remote accessibility.  We run more than a dozen
FreeBSD machines at work and I've never sit in front a console other than
for emergency maintenance.  Think about a possible embedded systems project
where you might use VGL to display some banners - it would make sense to
be able start/stop a vgl program without being in front of the console.

  X11 is way too big for what I need.  I just need some simple VGA graphics
on my TV.

  I suppose I'll end up writing a small console program that can start up
my program if no better solution exists.  When I said "proxy" I don't mean
client/server by any means.  I just mean a way to start a console program
without being on the console.

  Tim


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Terminal colors

1999-12-25 Thread Alexey Zelkin

hi,

 AND Say I want to change the man colors when I read mans at the console.  More
 AND precisely, I don't like that underlined text shows up as reversed (black
 AND letter on while(grey,7) backround).  How (and where) do I need to say that
 AND I want, say, yellow on black instead of reversed when displaying
 AND underlined-supposed-to-be text.  Any help is greatly appreciated.

For supported escape sequences (sequences used to change colors) you can
read screen(4) manpage.

Then read termcap(5) manpage. It will describe you termcap file structure.
Pay espessial attention for `md' (bold mode on) and `so' (standout mode on)
directives.

Contact me directly if you need more comments.

-- 
/* Alexey Zelkin[EMAIL PROTECTED]*/
/* Tavric National University   [EMAIL PROTECTED]  */
/* http://www.ccssu.crimea.ua/~phantom  [EMAIL PROTECTED] */


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Serial boot prompt messages and a modem

1999-12-25 Thread Daniel C. Sobral

Leif Neland wrote:
 
  Just configure it correctly. Don't tell it to talk to a serial device
  that will be sending it gibberish.
 
 A hack would be to have the loader emit ATE0 to protect itself from
 echoing modems.

AFAIK, it would not protect against all modems. I think Winmodems, for
instance, won't recognize that command.

 Another, but perhaps annoying would be flushing the input buffer before
 each read.

It's not enough. At the baud rates a modem work at, even when echoing,
the flush is likely to happen before the modem finishes echoing
everything.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"Nice try, Lao Che."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Serial boot prompt messages and a modem

1999-12-25 Thread Kevin Day

 
 Leif Neland wrote:
  
   Just configure it correctly. Don't tell it to talk to a serial device
   that will be sending it gibberish.
  
  A hack would be to have the loader emit ATE0 to protect itself from
  echoing modems.
 
 AFAIK, it would not protect against all modems. I think Winmodems, for
 instance, won't recognize that command.

True, but until you've downloaded boot code to the modem, most winmodems
won't respond at all... (Also, most winmodems that I've seen don't emulate a
UART, so they won't even cause a problem)

Kevin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Serial boot prompt messages and a modem

1999-12-25 Thread Leif Neland



On Sun, 26 Dec 1999, Daniel C. Sobral wrote:

 Leif Neland wrote:
  
   Just configure it correctly. Don't tell it to talk to a serial device
   that will be sending it gibberish.
  
  A hack would be to have the loader emit ATE0 to protect itself from
  echoing modems.
 
 AFAIK, it would not protect against all modems. I think Winmodems, for
 instance, won't recognize that command.
 
A: AFAIK, winmodems are not connected to a serial port, they are internal
boards.

B: Real men don't use anything marked win* for Real Computing.

Leif




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: device name of floppy disk

1999-12-25 Thread KATO Takenori

Brian Fundakowski Feldman [EMAIL PROTECTED] wrote:

 They're all synonymous, so I'd say that they're different names for a
 double-sided, high density 5.25" floppy.  The difference between 135
 and 96 is probably sector sizes.  In any case, I wouldn't worry over
 them at all.

Thank you!  Track densities of 5" and 3.5" disks are 96 and 135 tpi,
respectively.

 When's the last time you saw new modes for 5.25" floppies?  I'm not
 being sarcastic;  I'm just pointing out that they're all obsolete.

I know following disks:

  1 8"/5" HD double side 1024 bytes/sector  8 sectors/track, 77 cylinders
  25" DD double side  512 bytes/sector  8 sectors/track, 80 cylinders
  35" DD double side  512 bytes/sector  8 sectors/track, 80 cylinders
  4  3.5" DD double side  512 bytes/sector  8 sectors/track, 80 cylinders
  5 8"/5" HD double side  256 bytes/sector 26 sectors/track, 77 cylinders
  6  3.5" HD double side  256 bytes/sector 26 sectors/track, 77 cylinders
  75" DD double side  256 bytes/sector 16 sectors/track, 77 cylinders

and so on (including DEC PDP-11 :-)).

I'm trying to add 1, 2, 3 and 4.

---+--+
KATO Takenori [EMAIL PROTECTED]  |FreeBSD   |
Dept. Earth Planet. Sci, Nagoya Univ.  |The power to serve!   |
Nagoya, 464-8602, Japan|  http://www.FreeBSD.org/ |
   |http://www.jp.FreeBSD.org/|
 FreeBSD(98) 3.3R-Rev. 01 available!   +==+


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Terminal colors

1999-12-25 Thread Chuck Robey

On Sun, 26 Dec 1999, Alexey Zelkin wrote:

 hi,
 
  AND Say I want to change the man colors when I read mans at the console.  More
  AND precisely, I don't like that underlined text shows up as reversed (black
  AND letter on while(grey,7) backround).  How (and where) do I need to say that
  AND I want, say, yellow on black instead of reversed when displaying
  AND underlined-supposed-to-be text.  Any help is greatly appreciated.
 
 For supported escape sequences (sequences used to change colors) you can
 read screen(4) manpage.
 
 Then read termcap(5) manpage. It will describe you termcap file structure.
 Pay espessial attention for `md' (bold mode on) and `so' (standout mode on)
 directives.
 
 Contact me directly if you need more comments.

And don't forget all the many different flags to xterm, you can control a
*lot* that way, if you're in X.

 
 


Chuck Robey| Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: DES routines?

1999-12-25 Thread Kris Kennaway

On Thu, 23 Dec 1999, Ptacek wrote:

 Thanks for the info, by the way I found the ecb_crypt by doing a man
 des_crypt.

Are you sure this was on a FreeBSD box? I can't see ecb_crypt listed in
our des_crypt(3) manpage, though it is on e.g. Solaris.

Kris



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message