From: Cleverson Casarin Uliana <clcaul@gmail.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] FreeBSD port
Date: Sat, 18 Jan 2014 16:09:27 -0200 [thread overview]
Message-ID: <52DAC357.3040400@gmail.com> (raw)
In-Reply-To: <877g9xuqsh.fsf@mushroom.PK5001Z>
Thank you Chris, I'll investigate the qemu option. In any case, lets
hope there appear more human resources to make such other systems more
usable as alternatives for the blind in the future.
Regards
Cleverson
Em 18/01/2014 15:46, Chris Brannon escreveu:
> Cleverson Casarin Uliana<clcaul@gmail.com> writes:
>
>> and installing/using an entire OS through SSH is not
>> practical.
>
> First, congratulations to David on getting edbrowse into the ports tree!
>
> Well, if you just want to try FreeBSD, there are always virtual machines.
> Have a look at qemu. It has a curses display driver, which you can
> select by passing -curses on the command line. Any text-mode OS should
> work. You may have trouble if the OS insists on displaying one of those
> silly splash screens. This puts the display into graphic mode and
> breaks qemu's curses driver. With Linux, this can usually be gotten
> around by passing an appropriate parameter to the kernel at boot.
> I've never had any trouble with this when running *BSD under qemu, so I
> assume they don't do the splash screen thing?
> Serial consoles are also an option. With qemu, you can redirect the
> serial port to a TCP listener, so that you can access the serial console
> via telnet. Use a Unix-domain socket and socat for greater security.
> If your hardware supports hardware virtualization, you can
> use qemu with kvm. This is much more performant than plain qemu. It
> isn't noticeably slower than running on bare metal.
> I've used qemu extensively for many things, including trying out
> various flavors of BSD. So if you want to take FreeBSD for a spin
> without installing it on actual hardware, this is a great option.
>
> -- Chris
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
next prev parent reply other threads:[~2014-01-18 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 7:01 David Vionnet
2014-01-18 17:15 ` Cleverson Casarin Uliana
2014-01-18 17:46 ` Chris Brannon
2014-01-18 18:09 ` Cleverson Casarin Uliana [this message]
2014-01-19 1:00 ` Karl Dahlke
2014-01-19 1:53 ` Chris Brannon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52DAC357.3040400@gmail.com \
--to=clcaul@gmail.com \
--cc=edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).