Re: Dual monitors ok, but no mouse and keyboard action on the slave screen
On Mon, 23 Apr 2012, Polytropon wrote: On Sun, 22 Apr 2012 13:43:31 +0200, Kenneth Hatteland wrote: I`ve gotten a 17 inch monitor in addition to my 22 inch working with 2 separate desktops. I plan to have stuff like wireshark etc on the smallest. But I have a problem, I can get no work done since I have no mouse or keyboard working on the 17"... Anyone have somewhere with a solution to point me towards ? There are basically two kind of two-monitor settings: One is to have the WM manage them, the other one is to "concatenate" them to one "logical screen". I've been using the "concatenated screen" with two 21" CRTs, each running at 1400x1050, so the result was a 2800x1050 ultra extended extraordinary super hyper big wide screen. :-) You can configure this in your /etc/X11/xorg.conf (which you can have X auto-generate). For example, "ServerLayout" could contain Screen 0 "Screen0" 0 0 Screen 1 "Screen1" LeftOf "Screen0" Option "Xinerama" "on" The newer way to do this is with a Virtual entry in the Screen section: Section "Monitor" Identifier "Monitor0" VendorName "HWP" ModelName"2615" Option "PreferredMode" "1920x1200" Option "Position" "1280 0" EndSection Section "Monitor" Identifier "Monitor1" VendorName "SAM" ModelName"215" Option "PreferredMode" "1280x1024" Option "Position" "0 0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Virtual 3200 1200 EndSubSection EndSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: recommendation(s) for new computer
On Fri, 20 Apr 2012, Mark Felder wrote: On Fri, 20 Apr 2012 15:34:11 -0500, Dale Scott wrote: As do Intel (video) drivers Not if they require GEM/KMS like all the modern variants do; they're not supported in FreeBSD yet. I have a laptop (Google CR48) that's running the very experimental GEM/KMS code because otherwise it's stuck with a horrible resolution. Even with a custom kernel and custom ports/X11 patches it still has quirks like not being able to get your vty back after you start X. Is there a PR on this, or at least are the developers aware of it? I could not find a PR. I am running an out-of-the-box 9.0. I tested xorg 7.5 with nothing else other than xdm installed does and got this result. This makes it impossible to investigate any other issues that might arise. My setup: FreeBSD artemis.boltsys.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 xorg-7.5.1 xdm-1.1.11 twm-1.0.7 xorg.conf Section "Monitor" #DisplaySize 410 260 # mm Identifier "Monitor0" VendorName "ACR" ModelName"AL1916W" HorizSync30.0 - 82.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Device" Identifier "Card0" Driver "radeon" VendorName "ATI Technologies Inc" BoardName "Wrestler [Radeon HD 6310]" BusID "PCI:0:1:0" EndSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Dual monitors ok, but no mouse and keyboard action on the slave screen
On Sun, 22 Apr 2012 13:43:31 +0200, Kenneth Hatteland wrote: > I`ve gotten a 17 inch monitor in addition to my 22 inch working with 2 > separate desktops. I plan to have stuff like wireshark etc on the > smallest. But I have a problem, I can get no work done since I have no > mouse or keyboard working on the 17"... > > Anyone have somewhere with a solution to point me towards ? There are basically two kind of two-monitor settings: One is to have the WM manage them, the other one is to "concatenate" them to one "logical screen". I've been using the "concatenated screen" with two 21" CRTs, each running at 1400x1050, so the result was a 2800x1050 ultra extended extraordinary super hyper big wide screen. :-) You can configure this in your /etc/X11/xorg.conf (which you can have X auto-generate). For example, "ServerLayout" could contain Screen 0 "Screen0" 0 0 Screen 1 "Screen1" LeftOf "Screen0" Option "Xinerama" "on" Then add the two "Monitor" sections according to the screen parameters (in my case, identical data). In the final "Screen" section, you can then experiment with Option "TwinView" Option "TwinViewOrientation" "LeftOf" Option "ConnectedMonitor" "CRT, CRT" depending on your actual connection setup. You can find more inspiration here: Dual head issues, non-xinerama setup possible? http://forums.freebsd.org/showthread.php?t=11567 Dual monitor setup http://lists.freebsd.org/pipermail/freebsd-mobile/2005-January/005613.html Dual monitors xorg.conf http://lists.freebsd.org/pipermail/freebsd-questions/2005-May/087929.html Using two monitors with X.org http://www.freebsddiary.org/xorg-two-screens.php Many things to consider depend on your actual setting (which hardware you have, what WM you use and which behaviour you want). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: find sources to build Handbook and FAQ for FreeBSD?
Antonio Olivares writes: > Does anyone know where the source(s) for the FreeBSD Handbook and > FreeBSD FAQ are found? The best approach for you is probably the supfile in /usr/share/examples/cvsup/doc-supfile Which is documented in the in the fdp-primer, the FreeBSD Handbook... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Invitation to APAC Oil & Gas Deepwater Forum 2012 - KL
The Deepwater Forum 2012 To view this as a webpage, read here 3 - 4 July 2012, Kuala Lumpur - Malaysia: Spearhead Your Deepwater Equipment Integrity and Disaster Management Without A Hitch Dear Oil & Gas Peer, “Deepwater oil-drilling is of extreme importance to us. How do we prevent incidents while drilling in 8316 feet of water, then deeper into the substrata?" Equip ourselves with proven technologies and strategize sustainable implementation mean everything to us. But how should we deal with it? Attend to meet the deepwater oil-drilling experts (representing their regional oil & gas companies) and learn how to drill even deeper depths with the best practices: A Future Outlook on Deepwater Projects in Asia Dual Gradient Drilling Understanding Pore Pressure Prediction for Drilling Operations Drilling in a High Pressure High Temperature (HPHT) Environment Increasing Drilling Tool Reliability in Harsh Environments Maintaining the Integrity of Your Topside and Deepwater Equipment Deepwater Drilling Hazard Management Well Integrity Management Increasing Deepwater Production Rates through Efficient Well Intervention The Roles of Remotely Operated Vehicles (ROV) and Autonomous Underwater Vehicles (AUV) Deepwater Operations Support Multiphase Metering - selecting the right system suited to your needs Flow Assurance Challenges in the Deepwater Environment Hydrate Remediation in Flowlines Subsea Separation - Key Lessons from Experiences Implementing Integrity Management for Deepwater Projects...and more Organizing Committee: Download Agenda NOW! Note: Forward this to your deepwater oil-drilling team members also. Best of Luck, Mr. Kyle Law kyle@fleminggulf.com Hope it is helpful for you. I apologise if you're not the intended recipient. If you wish to unsubscribe, here you are. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: converting UTF-8 to HTML
On Sun, 22 Apr 2012, Matthew Seaman wrote: On 22/04/2012 10:17, Erik Nørgaard wrote: UTF-8 is variable with, ascii characters are stored as single bytes (not sure about iso-8859-1) while other characters are stored as two byte chars. ascii uses the low 128 values that you can assign to an unsigned char, ie. those where the high-order bit is zero. Programming a text-only display to assume everything is UTF-8 would be quite viable, and backwardly compatible with ascii-only displays. The hardware doesn't exist to display UTF-8 characters in text MODE. The whole point of avoiding GUIs is rasterized and GUI fonts cannot put 4000 characters on a screen as legibly as VGA does (not to mention the performance hit the rasterization and GUIs deliver). One look at recent Linux distributions which make it all but impossible to reach text MODE because they had the thought that sticking a rasterized white-on-black font on the screen (via yet another kernel module) would be "just as good" as VGA should amply demonstrate the point. Yeah, you need that crap if you are running a server in Outer Fubaristan where there are 38 languages written in 49 different alphabets -- but crippling text mode is not worth while for most people, especially people who work in text. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: converting UTF-8 to HTML
On 22/04/2012 13:06, Polytropon wrote: How about the "extended ASCII character set" that has a mixture of "non-US glyphs" and semi-graphic symbols? http://asciiset.com/extended.gif I can't even write my name in that character set. As long as there are multiple charactersets you will have the problem of some characters being shown wrong. This is nothing particular for UTF-8, you have the problem even when choosing between the 10+ different ISO-8859. The only thing that UTF-8 introduce is the variable byte length characters so you can't equate no. bytes with no. characters. Cheers, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: converting UTF-8 to HTML
On 22/04/2012 12:06, Polytropon wrote: > How about the "extended ASCII character set" that has a mixture > of "non-US glyphs" and semi-graphic symbols? > > http://asciiset.com/extended.gif > > This default layout isn't tied to a specific encoding, if I > remember correctly, or is it? Accessing the set as seen in the > picture allows using "special character" from many languages, > such as german umlauts and eszett, greek gamma and phi, > danish o-slash, swedish a-circle and even the yen symbol. > And the nice semi-graphic symbols to draw boxes and backgrounds, > as well as card deck symbols or the "lazy L". Yeah. It's just a compromise 1-byte per glyph character set designed to support the wealthier bits of Western Europe as well as the USA, from back when the cost of supporting all sorts of different locales was really expensive compared to the expected sales of equipment in them. Doesn't have a € symbol as far as I can see. I doubt it would go down well in Łódź either. Nor Αθήνα as it doesn't have a complete Greek alphabet. Most of the Greek letters are there to support their use as mathematical symbols. It was a reasonable compromise back in the late 1980's but if anyone came up with this as a serious proposal today, they'd just get laughed at. Given that China and India are going to become /the/ big economies within the next several years, only having a limited anglo-centric system like that will be a significant obstacle to future popularity. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Dual monitors ok, but no mouse and keyboard action on the slave screen
I`ve gotten a 17 inch monitor in addition to my 22 inch working with 2 separate desktops. I plan to have stuff like wireshark etc on the smallest. But I have a problem, I can get no work done since I have no mouse or keyboard working on the 17"... Anyone have somewhere with a solution to point me towards ? Blessed be.. Kenneth Hatteland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: blu ray recorders
On Sun, 22 Apr 2012 01:08:02 +0200 (CEST) Wojciech Puchar articulated: >>> Even Windows can then see it properly, but FreeBSD shows multiple >>> files. >> >> Try filing a PR against it. Perhaps somebody might actually look into >> it. >> > >i've got info it is already known, but thanks anyway. Really, what PR is that? I could not find one that specifically dealt with it; although I most probably missed it. Obviously you must know which one it is. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: converting UTF-8 to HTML
On Sun, 22 Apr 2012 11:45:45 +0100, Matthew Seaman wrote: > On 22/04/2012 10:17, Erik Nørgaard wrote: > > UTF-8 is variable with, ascii characters are stored as single bytes (not > > sure about iso-8859-1) while other characters are stored as two byte chars. > > ascii uses the low 128 values that you can assign to an unsigned char, > ie. those where the high-order bit is zero. > > iso-8859-1 and the various other iso-8859-X character sets fill in the > remaining 128 characters with various other glyphs useful in latin > alphabets, so it's still one char per glyph. Other alphabets (greek, > cyrillic, etc) have similar one byte-per glyph encodings. But you have > to know what the encoding is to display the content correctly, and it is > difficult to mix chunks of text in different encodings in the same document. How about the "extended ASCII character set" that has a mixture of "non-US glyphs" and semi-graphic symbols? http://asciiset.com/extended.gif This default layout isn't tied to a specific encoding, if I remember correctly, or is it? Accessing the set as seen in the picture allows using "special character" from many languages, such as german umlauts and eszett, greek gamma and phi, danish o-slash, swedish a-circle and even the yen symbol. And the nice semi-graphic symbols to draw boxes and backgrounds, as well as card deck symbols or the "lazy L". Of course, there are no arabic or chinese letters in there, so it can be seen as a "roman-derived language" centrism (targeting europe and america in the first place). All of them are natively supported by graphic cards when running in text mode, if my assumption is correct. So this "extended set of capabilities" still is the most-minimum common functionality that one can rely on. (FreeBSD remaps some of the characters in text mode to display the semi-graphic mouse pointer, so the full set cannot be used all the time.) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: converting UTF-8 to HTML
On 22/04/2012 10:17, Erik Nørgaard wrote: > UTF-8 is variable with, ascii characters are stored as single bytes (not > sure about iso-8859-1) while other characters are stored as two byte chars. ascii uses the low 128 values that you can assign to an unsigned char, ie. those where the high-order bit is zero. iso-8859-1 and the various other iso-8859-X character sets fill in the remaining 128 characters with various other glyphs useful in latin alphabets, so it's still one char per glyph. Other alphabets (greek, cyrillic, etc) have similar one byte-per glyph encodings. But you have to know what the encoding is to display the content correctly, and it is difficult to mix chunks of text in different encodings in the same document. UTF has various different forms, based on different word sizes, but the commonly used UTF-8 works in units of 1-byte chars. However, glyphs may be represented by sequences of from 1 to 4 bytes. The 1-byte glyphs are identical to ascii. Any byte with the high-order bit set indicates the beginning of a multibyte glyph -- the number of bytes is indicated by the bit pattern of the first byte and all the other bytes of that glyph will have the high order bit set. All million-plus glyphs available through Unicode can be expressed this way, so the encoding is universal and suitable for all languages and alphabets or non-alphabetic languages. Not all possible byte sequences are valid UTF-8 text, but the design of the encoding means that an interpreter can skip over an invalid sequence of bytes and find the beginning of the next valid sequence easily. Whoever it was upthread had the misfortune to run into a text editor that just gave up and truncated their document at an invalid sequence needs to vent their ire on the lazy and stupid programmers of whatever app it was, rather than on the concept of UTF-8 itself. Yes, with UTF-8 encoded text, you can no-longer equate the number of glyphs[*] in a piece of text (and hence the space required to display the text) with the memory required to store that text. There's a lot of legacy code out there which makes this assumption, but this is overshadowed by the amount of legacy code out there which can only handle ascii text. Fixing all that code is pretty long-winded, but not conceptually too difficult. Programming a text-only display to assume everything is UTF-8 would be quite viable, and backwardly compatible with ascii-only displays. The hard part is creating a font with a more-or-less complete set of Unicode glyphs. Cheers, Matthew [*] Let's not even mention the concept of 'combining characters' here. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: converting UTF-8 to HTML
On 21/04/2012 16:10, Lars Eighner wrote: UTF-8 is a waste of storage for most people and is incompatiple with text-mode tools: it's simple another bid to make it impossible to run without a GUI. UTF-8 is variable with, ascii characters are stored as single bytes (not sure about iso-8859-1) while other characters are stored as two byte chars. If your text tools cannot display certain or all UTF-8 characters it is for one of the following reasons: it is either because the application does not support UTF-8, the display table is missing some characters, or the limited display capabilities of terminal/console mode and the complexity of that particular glyph. Neither of the first two cases are an agument against UTF-8, it's a it's an implementation issue, send a bug report or feature request to the developer. In the last case, I hope you're not saying that we should limit the fredom of expression to what can be expressed in console mode? :P Cheers, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
