Re: About building release for using sysinstall
On Tue, 28 Feb 2012 19:13:56 +0100, ego...@ramattack.net wrote:
Sorry but, perhaps should I write this another FreeBSD mailing
list?... perhaps this one, it's not it's place... if this can be the
situation, please tell me which mailing list to send to this
suggestion.
Thanks a lot for you're time,
Best regards.
On Mon, 27 Feb 2012 11:22:25 +0100, ego...@ramattack.net wrote:
Good morning,
I have launched :
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
"freebsd-hackers-unsubscr...@freebsd.org"
Finally have been able to build a RELENG_9_0 release with isos,
sysinstall and livefs disc with the following changes applied :
generarelease90# pwd
/usr/src/release/amd64
generarelease90# cvs diff -r 1.14.2.1.2.1 -r 1.14.2.1.2.2
mkisoimages.sh
Index: mkisoimages.sh
===
RCS file: /expert/ncvs/src/release/amd64/mkisoimages.sh,v
retrieving revision 1.14.2.1.2.1
retrieving revision 1.14.2.1.2.2
diff -r1.14.2.1.2.1 -r1.14.2.1.2.2
7c7
< # $FreeBSD: src/release/amd64/mkisoimages.sh,v 1.14.2.1.2.1
2011/11/11 04:20:22 kensmith Exp $
---
# $FreeBSD: src/release/amd64/mkisoimages.sh,v 1.14.2.1.2.2
2012/03/06 08:27:38 portero Exp $
42d41
< echo "/dev/iso9660/`echo $LABEL | tr '[:lower:]' '[:upper:]'` /
cd9660 ro 0 0" > $1/etc/fstab
44d42
< rm $1/etc/fstab
generarelease90# cd ..
generarelease90# cvs diff -r 1.5.2.1.2.2 -r 1.5.2.1.2.3
Makefile.sysinstall
Index: Makefile.sysinstall
===
RCS file: /expert/ncvs/src/release/Attic/Makefile.sysinstall,v
retrieving revision 1.5.2.1.2.2
retrieving revision 1.5.2.1.2.3
diff -r1.5.2.1.2.2 -r1.5.2.1.2.3
1c1
< # $FreeBSD: src/release/Makefile.sysinstall,v 1.5.2.1.2.2 2012/01/02
04:11:22 kensmith Exp $
---
# $FreeBSD: src/release/Makefile.sysinstall,v 1.5.2.1.2.3 2012/03/06
08:26:49 portero Exp $
1152,1155d1151
<@sh ${.CURDIR}/${TARGET}/mkisoimages.sh \
Re: Graphical Terminal Environment
On 3/7/2012 2:06 PM, Peter Jeremy wrote: > If you're looking for something minimal, vector support should be one of the > first things to go. At small sizes (in terms of dots), the best fonts are all > bitmaps, rather than vector descriptions. One of the features of TrueType and > Postscript is that a vendor can provide hand-tweaked bitmap glyphs for small > sizes of a vector font. Likewise the VT100 demonstrated that you don't need > vector line drawing to draw boxes. Some points to keep in mind: Anything > beyond what is supported in your VESA BIOS requires custom support for your > specific video chip. This is part of the code in x11-drivers/xf86-video-*. LCD > monitors look fairly poor unless driven at their native resolution so, unless > your VESA BIOS provide a mode that suits your monitor, you will need custom > driver code. I do plan on writing a small little driver for NVIDIA cards (it's what I have). I'm assuming it can't be terribly hard to detect the monitor's resolution, set to that resolution, then start displaying dots... you never know though... I'll be having a fun time with nouveau for the next few weeks :) -Brandon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Graphical Terminal Environment
On 2012-Mar-06 14:08:51 -0500, Brandon Falk wrote: >When I mention lines, circles, etc I was thinking moreso at the very low level >of fonts being drawn by lines and dots (although I would like to branch it >eventually to support 2d graphics where people could maybe make some 2d games, >but keep the high-res terminal on the side to keep it minimal). I also may want >to draw some lines to border terminal windows (screen would eliminate this >obviously). If you're looking for something minimal, vector support should be one of the first things to go. At small sizes (in terms of dots), the best fonts are all bitmaps, rather than vector descriptions. One of the features of TrueType and Postscript is that a vendor can provide hand-tweaked bitmap glyphs for small sizes of a vector font. Likewise the VT100 demonstrated that you don't need vector line drawing to draw boxes. Some points to keep in mind: Anything beyond what is supported in your VESA BIOS requires custom support for your specific video chip. This is part of the code in x11-drivers/xf86-video-*. LCD monitors look fairly poor unless driven at their native resolution so, unless your VESA BIOS provide a mode that suits your monitor, you will need custom driver code. -- Peter Jeremy pgpavw3qB3HKy.pgp Description: PGP signature
USENIX TaPP '12 Call for Papers Submission Deadline Approaching
We're writing to remind that the deadline for the 4th USENIX Workshop on the Theory and Practice of Provenance (TaPP '12) is approaching. Please submit your work by Saturday, March 31, 2012, at 5:00 p.m. EDT. http://www.usenix.org/tapp12/cfpb The Program Committee seeks short papers and vision papers describing challenges for provenance research, brief descriptions of new applications, proposals for mini-tutorials, pie-in-the sky research ideas, and anything that will create a successful workshop. TaPP '12 will bring together researchers and practitioners doing innovative work in the area of provenance. With the deluge of digital data we are currently experiencing, it has become increasingly important to capture and understand the origins and derivation of data--its provenance. Provenance provides important documentation that is an essential part of the quality of data, and it is essential to the trust we put in, for example, the data we find on the Web and the data that is derived from scientific experiments. The workshop may cover any topic related to theoretical or practical aspects of provenance, including but not limited to: provenance in databases, workflows, programming languages, security, software engineering, or systems; provenance on the Web; real-world applications of or requirements for provenance. Please adhere to these guidelines on how and what to submit: * Submissions should be self-contained and no more than 4 pages. * If supporting material is needed, an extra 4 pages may be submitted, but the committee will not be obliged to read them. * All submissions should clearly indicate whether they are intended for inclusion in the proceedings. More information and submission guidelines are available at http://www.usenix.org/tapp12/cfpb We look forward to receiving your submissions! Sincerely, Umut A. Acar, Max Planck Institute for Software Systems Todd J. Green, University of California, Davis, and LogicBlox TaPP '12 Program Co-Chairs tapp12cha...@usenix.org -- TaPP '12 Call for Papers 4th USENIX Workshop on the Theory and Practice of Provenance (TaPP '12) June 14-15, 2012, Boston, MA http://www.usenix.org/tapp12/cfpb Submission deadline: March 31, 2012, 5:00 p.m. EDT -- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Graphical Terminal Environment
On Tue, 06 Mar 2012 14:08:51 EST Brandon Falk wrote: >You seem to understand exactly want I want. Just small font terminals on all >screens, and I was actually thinking `screen` would do the trick for the >splitting/management of them. As for stripping down X, I might do so as a proof >of concept, but in the end I want to develop my own for my own learning. > >When I mention lines, circles, etc I was thinking moreso at the very low level >of fonts being drawn by lines and dots (although I would like to branch it >eventually to support 2d graphics where people could maybe make some 2d games, >but keep the high-res terminal on the side to keep it minimal). I also may want >to draw some lines to border terminal windows (screen would eliminate this >obviously). You might want to look at /dev/draw of plan9. And rio, as someone else also suggested. /sys/src/9/port/devdraw.c on plan9 is only about 2200 lines. You may also wish to read Rob Pike's paper on 8 1/2 and man pages for draw(2), draw(3), graphics(2) and rio(1) @ cat-v.org. See rio presentation @ http://herpolhode.com/rob/lec5.pdf as it lays out window system design issues very nicely. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
