Re: No sound with Thinkpad X60
On Fri, 22 Mar 2013 06:28:57 +0100 Bernt Hansson articulated: > 2013-03-22 00:42, Peter Harrison skrev: > > Put this in your /boot/loader.conf and report back. > > hw.snd.default_unit="0" > > Test with other nubers if 0 do not work. Using an nVidia card, I had to do the following: /etc/sysctl.conf hw.snd.default_unit=4 Rebooted and the sound worked. I never found any truly accurate information on it, it was basically just a trail and error experiment. And YES, it sucks that in all to many cases, sound doesn't "just work". -- 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: "Leaking" disk space
> A stab in the dark, but does # sync change anything Alas, no. On 21 March 2013 13:21, Bernt Hansson wrote: > On 2013-03-21 11:40, Dan Thomas wrote: >>> >>> Have you used fstat to identify the big growing file which is taking up >>> the space, and which process has the file open? >> >> >> It's not an unlinked file. I've tried using fstat and lsof to identify >> it, and there's no inodes with zero links or that don't have a >> matching file on disk. > > > A stab in the dark, but does # sync change anything. > > > >> Dan >> >> On 20 March 2013 23:08, Daniel O'Callaghan wrote: >>> >>> On 21/03/2013 3:55 AM, Dan Thomas wrote: Stopping Postgres doesn't fix it, but rebooting does which points at >>> >>> >>> Have you used fstat to identify the big growing file which is taking up >>> the >>> space, and which process has the file open? >>> A file which has been unlinked from all directories won't be seen by du, >>> but >>> it does not free disk space until no process has it open. >>> >>> USER CMD PID FD MOUNT INUM MODE SZ|DV R/W >>> root syslogd476488 /4317027 -rw-r--r-- 19776 w >>> root syslogd476489 /4317041 -rw--- 63 w >>> >>> That might help to track it down. >>> >>> Danny >>> >>> >>> ___ >>> 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" >> >> ___ >> 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" >> >> > ___ 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: Installing openssl from ports
On 22/03/2013 04:36, Jim Ballantine wrote: But when I attempt to install the latest openssl for the port system, it fails with a conflict (installs file in the same place) with heimdal. Take a close look at the message and what happens before. openssl only gives a conflict message if the base version is newer than the port. Heimdal conflicts with krb4 krb5 and srp Any other conflicts will be from dependencies, you'll need to check what port brings in a dependency that generates the conflict. ___ 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: "Leaking" disk space
On Wed, 20 Mar 2013 16:55:34 + Dan Thomas wrote: > > a) Where do you have the wal files? > > pg_xlog is symlinked to /usr/local/pglog/pg_xlog (ie, out of the > partition mounted as /usr/local/pgsql which is exhibiting this > behaviour). > As Matthew Seaman says in other answer, this is the problem. Check http://lists.freebsd.org/pipermail/freebsd-fs/2013-March/016702.html and next thread messages. It seems that writing file follow the symlink but makes a shadow/ghost file entry in original directory/disk. I see that you don't have trim enabled on the postgres fs, tunefs -p /usr/local/pgsql/ shows option t disabled. Is trim enabled on the fs where the symlink points? (Show the output of tunefs -p /dev/_don't_know_the_dev_entry_name) > b) Are you sure that unused/old wal files are erased? > > As above, but yes they seem to be being deleted properly > > c) Do you have any postgres log level activated (like the ones used > for long queries)? > > Yes we have slow query logging enabled. pg_log is symlinked out of > that partition to /usr/local/pglog/pg_log as well. > > d) Does your queries have GROUP BY on very big data sets? Those create > big temporal data files. > > Yes we do a lot of that! However there are definitely no unlinked > files, and the problem doesn't go away when pg is shut down. However a > reboot does fix it. Those questions were only to check and be sure is not a "normal" temp files problem. What does dmesg show about filesystem check? Does it mark dirty filesystem? # WARNING!! Make a backup first!!! If you stop postgres, and shoot #fsck_ffs -E /dev/mfid1s1d , does the problem solve? # END WARNING!! Please post the output of the fsck_ffs. If the fsck_ffs doesn't solve the problem, check if there exist a lost+found directory on /usr/local/pgsql/ and it's content. > > e) With question a) and b), do you use streaming replication? > > Yes we do. This problem is not present on the warm standby servers > that are being streamed to. We have failed over to the warm standbys > previously (we're currently doing this regularly to work around the > problem without too much downtime). Once we switch the warm standby to > primary, it begins leaking space. It may store old&all wal files, but it seems a bug at filesystem level. Trim support in ufs was added to 9.0 and backported to 8 and may be a candidate to watch. --- --- Eduardo Morras ___ 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: Handbook Jail Chapter rewrite available for critique
On Thu, 21 Mar 2013 11:21:29 -0400, Alejandro Imass wrote: > On Thu, Mar 21, 2013 at 3:35 AM, Ian Smith wrote: > > On Tue, 19 Mar 2013 17:53:30 +0100, Dirk Engling wrote: [.. also chopping mercilessly ..] > > > # Copyright 2010, Qjail project. All rights reserved. > > > > > > offensive. I am usually quite open with the license of my software, > > > beerware is as permissive as it gets. I just can not take some script > > > kiddie right out copying my code verbatim and selling it as his, not > > > even acknowledging me as the original author. > > > > > > Anyone here with suggestions how to properly react to this kind of > > "fork"? > > > > Yes. Publicity. Making sure the FreeBSD community gets to finds out. > > > > [...] > > > To that end I'm cross-posting this to -questions, where Mr Barbish has > > also posted about his proposed "rewrite" of Chapter 16 of the Handbook, > > which is nothing but a huge and poorly written manual for 'the qjail > > way', with its peculiar assumptions and unique "jailcell" terminology. > > "Fourth Generation", no less! > > > > +1 > > Thank you Ian for cross-posting here. > > The first thing I did when I got the new chapter for review was search > for the work EzJail and I was curious as to why EzJail is not > mentioned anywhere in this new proposal and why it isn't mentioned in > the current handbook either under in section "16.5.2 High-Level > Administrative Tools in the FreeBSD Ports Collection". If there is > __any__ tool that should be mentioned in the jails chapter it is > EzJail because it's really easy to use and does a damn good job. Actually, ezjail has been explicitly mentioned in '16.6 Application of Jails' http://www.freebsd.org/doc/handbook/jails-application.html since revision 30226 by danger, Mon May 28 20:02:46 2007 UTC, which section was just 6 weeks ago updated with a (preceding) similar port reference to qjail: http://svnweb.freebsd.org/doc?view=revision&revision=40900 [..] > NOW some things start to make sense to me, when I posted a problem > with EzJail here last year that very few people, if any, knew what I > was talking about. An how could they? if it's not mentioned anywhere > in the handbook or that jail man page(s). man pages aren't an appropriate place to recommend particular ports; there are others, and there will be more. The above are mentioned in the handbook page in the context of simpler alternatives to following the more detailed procedures presented to actually teach one how jail technology may be implemented, which - in my view - is the Good Stuff. There have been about 20 messages in freebsd-jail@ referring to ezjail this year so far before this thread, as in previous years; try browsing the archives from http://lists.freebsd.org/pipermail/freebsd-jail/ OTOH, I've seen no prior posts in jail@ about qjail before this thread. cheers, Ian ___ 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: Handbook Jail Chapter rewrite available for critique
On Fri, Mar 22, 2013 at 9:03 AM, Ian Smith wrote: > On Thu, 21 Mar 2013 11:21:29 -0400, Alejandro Imass wrote: > > On Thu, Mar 21, 2013 at 3:35 AM, Ian Smith wrote: > > > On Tue, 19 Mar 2013 17:53:30 +0100, Dirk Engling wrote: > [...] >> mentioned anywhere in this new proposal and why it isn't mentioned in >> the current handbook either under in section "16.5.2 High-Level >> Administrative Tools in the FreeBSD Ports Collection". If there is >> __any__ tool that should be mentioned in the jails chapter it is [..] > Actually, ezjail has been explicitly mentioned in '16.6 Application of > Jails' http://www.freebsd.org/doc/handbook/jails-application.html since > revision 30226 by danger, Mon May 28 20:02:46 2007 UTC, which section > was just 6 weeks ago updated with a (preceding) similar port reference > to qjail: http://svnweb.freebsd.org/doc?view=revision&revision=40900 > Never seen it before. First time I read about service jails it wasn't there. Further to my point doesn't it make more sense to mention them under "16.5.2 High-Level Administrative Tools in the FreeBSD Ports Collection" or in both places? [...] > > There have been about 20 messages in freebsd-jail@ referring to ezjail > this year so far before this thread, as in previous years; try browsing > the archives from http://lists.freebsd.org/pipermail/freebsd-jail/ > I posted on the wrong list then ;-) Subscribing today, thanks! -- Alejandro Imass ___ 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: Installing openssl from ports
The port is newer than the base version: port is 1.0.1_8 and the base is 0.9.2 Both openssl and heimdal install fine from the base system src, it's only when I try to install openssl from the ports, with heimdal installed by the base system that I get the error. When I run make install, what I get before the conflict message is: ===> Compressing manual pages for openssl-1.0.1_8zopenssl-1.0.1_8 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib Installing openssl-1.0.1_8...pkg: openssl-1.0.1_8 conflicts with heimdal-1.5.2_4 (installs files into the same place). Problematic files: /usr/local/man/man3/DH_generate_key.3.gz *** [fale-pkg] Error code 70 On Fri, Mar 22, 2013 at 8:09 AM, Shane Ambler wrote: > On 22/03/2013 04:36, Jim Ballantine wrote: > > But when I attempt to install the latest openssl for the >> port system, it fails with a conflict (installs file in the same place) >> with heimdal. >> > > Take a close look at the message and what happens before. openssl only > gives a conflict message if the base version is newer than the port. > > Heimdal conflicts with krb4 krb5 and srp > > Any other conflicts will be from dependencies, you'll need to check what > port brings in a dependency that generates the conflict. > > > ___ 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: No sound with Thinkpad X60
2013-03-22 12:31, Jerry skrev: On Fri, 22 Mar 2013 06:28:57 +0100 Bernt Hansson articulated: 2013-03-22 00:42, Peter Harrison skrev: Put this in your /boot/loader.conf and report back. hw.snd.default_unit="0" Test with other nubers if 0 do not work. Using an nVidia card, I had to do the following: /etc/sysctl.conf hw.snd.default_unit=4 Rebooted and the sound worked. I never found any truly accurate information on it, it was basically just a trail and error experiment. And YES, it sucks that in all to many cases, sound doesn't "just work". If it "just work" there is no fun. Tinkering and using a braincell, or at the most two is much more rewarding. ___ 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"
Is fdisk broken?
I recently bought a 4 TB usb disk drive and discovered that it reported a sector size of 4096 bytes instead of the traditional 512 bytes. This is apparently necessary because there may be a 32 bit sector number field somewhere in the usb mass storage protocols. It turns out that disk drive manufacturers have been producing disks with large sector sizes for some years now. The feature goes by the name "Advanced Format" and other things. Look it up in Wikipedia. FreeBSD seems to use the sector size information when interpreting MBR partition offsets and sizes. Unfortunately, when I try to use fdisk to print out the partition table on my new disk drive, fdisk just says "fdisk: could not detect sector size". Otherwise the MBR partition table seems to work correctly and newfs seems to have done the right thing. (It made the file system fragment size a multiple of the sector size and I am not getting any weird error messages out of the disk driver.) It would be nice if fdisk also worked. I do have to share the disk with other operating systems that might not understand other partition table schemes. Is may analysis of what is going on essentially correct? Can fdisk be made happy again? (At least for a few more years?) Dan Strick (mla_str...@att.net) ___ 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: Is fdisk broken?
On Fri, Mar 22, 2013 at 7:33 AM, wrote: > Can fdisk be made happy again? (At least for a few more years?) The short answer is: no. Fdisk comes from a world where even 1G drives were not yet on the horizon. Use gpart. The long answer is readily available in the forums - google is your friend. - M ___ 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: No sound with Thinkpad X60
Jerry writes: > On Fri, 22 Mar 2013 06:28:57 +0100 > Bernt Hansson articulated: > >> 2013-03-22 00:42, Peter Harrison skrev: >> >> Put this in your /boot/loader.conf and report back. >> >> hw.snd.default_unit="0" >> >> Test with other nubers if 0 do not work. > > Using an nVidia card, I had to do the following: > > /etc/sysctl.conf > hw.snd.default_unit=4 > > Rebooted and the sound worked. I never found any truly accurate > information on it, it was basically just a trail and error experiment. > And YES, it sucks that in all to many cases, sound doesn't "just work". You don't actually need to reboot for each trial. Running sysctl(8) from the command line will do. And /dev/sndstat would probably tell you the right value to try. These things are covered in the 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"
Re: Is fdisk broken?
On Fri, 22 Mar 2013 mla_str...@att.net wrote: I recently bought a 4 TB usb disk drive and discovered that it reported a sector size of 4096 bytes instead of the traditional 512 bytes. This is apparently necessary because there may be a 32 bit sector number field somewhere in the usb mass storage protocols. It turns out that disk drive manufacturers have been producing disks with large sector sizes for some years now. The feature goes by the name "Advanced Format" and other things. Look it up in Wikipedia. FreeBSD seems to use the sector size information when interpreting MBR partition offsets and sizes. Unfortunately, when I try to use fdisk to print out the partition table on my new disk drive, fdisk just says "fdisk: could not detect sector size". It has the following gratuitous breakage at 2K for its probe of the sector size: #define MAX_SEC_SIZE 2048 /* maximum section size that is supported */ #define MIN_SEC_SIZE 512/* the sector size to start sensing at */ I used 64K for the probe maximum limit when I fixed fsck_msdosfs (fsck_msdosfs doesn't has a probe and only supports sector sizes of 512 in -current). Most file systems in FreeBSD have gratuitous limits on the size in their probe for there superblock, but the limit is mostly larger than 4K. Most of them don't need to know the sector size and don't have a probe, but they read a fixed size that is larger than their superblock size, so they fail if this size is smaller than the the sector size. Otherwise the MBR partition table seems to work correctly and newfs seems to have done the right thing. (It made the file system fragment size a multiple of the sector size and I am not getting any weird error messages out of the disk driver.) It would be nice if fdisk also worked. I do have to share the disk with other operating systems that might not understand other partition table schemes. Is may analysis of what is going on essentially correct? Can fdisk be made happy again? (At least for a few more years?) Changing the above should fix fdisk for FreeBSD. A sector size of 4K gives a limit of 16TB for the partition table data structure, which is enough for a few more years with single disks. After that, double the sector size to 8K to work for another year or two. However, to share the disk you need all the other operating systems and BIOS to agree that _this_ partition table scheme (with units of 4K sectors) is what the partition table records. Bruce ___ 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"
trying freeBSD 9.1 w/o installing
HelloIn command-line form, the disk which i received in linuxpro magazine is asking for a login and password, please assist.ThanksSteve Woman is 53 But Looks 25 53/YO Mom reveals 1 simple wrinkle trick that has angered doctors... http://thirdpartyoffers.netzero.net/TGL3231/514cb693e7ed036930196st02duc ___ 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: trying freeBSD 9.1 w/o installing
On Fri, 22 Mar 2013 19:51:49 +, ivan1...@netzero.net wrote: > HelloIn command-line form, the disk which i received in linuxpro > magazine is asking for a login and password, please assist.ThanksSteve If it's a live CD, username is root. Password is not required. ___ 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"
mutt and http//url???
guys, ==many== yeears ago when i was running Only FBSD, I asked this list how i could use mutt when somebody included an http://url.com; and i got replies that worked. --sseems like the url string got moved to the end and clicking on the string exec'd firefox. in the past couple years i've sub'd to the nytimes and other places where the http string is several dozens of bytes. in my mutt at least, there are "+" marks embedded at the beginning of each new lines. so that when i mouse lick on the url, i almost invariably get either Nothing from my browswer, or the wrong page. i've googled for days. zero. im finally asking the top list on the web. can anybody clue me in? i'm using linux/gnome/mutt. but it shouldnt make any difference. [?!] tia, everybody, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-six years of service to the Unix community. ___ 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: mutt and http//url???
On Fri, 22 Mar 2013 14:36:15 -0700, Gary Kline wrote: > in the past couple years i've sub'd to the nytimes and other places > where the http string is several dozens of bytes. in my mutt > at least, there are "+" marks embedded at the beginning of each > new lines. so that when i mouse lick on the url, i almost > invariably get either Nothing from my browswer, or the wrong > page. That's to be expected. A URL covering several lines _can_ be copied (selected) when the line wrap is "uninterrupted". It will even work for double- or triple-click (select word, select line) with the normal edit buffer (left swipe to select, in Firefox middle click or mousewheel press to go to URL). As the '+' character will be part of the wrapped URL (which can span several lines), the URL will be wrong, as you've seen. > i've googled for days. zero. im finally asking the top list > on the web. can anybody clue me in? i'm using linux/gnome/mutt. > but it shouldnt make any difference. [?!] If I remember correctly, there's a way to disable the line break emphasizer ('+' character) in the display. Have you tried set markers=no in your ~/.muttrc? Or was it unset markers Something with "markers"... I'm not fully sure if this is the setting you're searching for, but go ahead and try it. -- 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: mutt and http//url???
>> On Fri, 22 Mar 2013 14:36:15 -0700, >> Gary Kline said: G> in the past couple years i've sub'd to the nytimes and other places G> where the http string is several dozens of bytes. in my mutt at least, G> there are "+" marks embedded at the beginning of each new lines. so G> that when i mouse lick on the url, Don't lick your mouse. That's gross. G> i almost invariably get either Nothing from my browswer, or the wrong G> page. You might want to try urlview, bound to Ctrl-B in mutt by default. It's a screen-oriented program for extracting URLs from text files, putting them in a menu, and letting you run a command to view a specific item. If you're on a FreeBSD system, it's in /usr/ports/textproc/urlview. -- Karl Vogel I don't speak for the USAF or my company Oh, to be only half as wonderful as my child thought I was when he was small, and only half as stupid as my teenager now thinks I am.--Rebecca Richards ___ 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: mutt and http//url???
On Sat, Mar 23, 2013 at 01:20:18AM +0100, Polytropon wrote: > On Fri, 22 Mar 2013 14:36:15 -0700, Gary Kline wrote: > > in the past couple years i've sub'd to the nytimes and other places > > where the http string is several dozens of bytes. in my mutt > > at least, there are "+" marks embedded at the beginning of each > > new lines. so that when i mouse lick on the url, i almost > > invariably get either Nothing from my browswer, or the wrong > > page. > > That's to be expected. A URL covering several lines _can_ be > copied (selected) when the line wrap is "uninterrupted". It > will even work for double- or triple-click (select word, select > line) with the normal edit buffer (left swipe to select, in > Firefox middle click or mousewheel press to go to URL). As the > '+' character will be part of the wrapped URL (which can span > several lines), the URL will be wrong, as you've seen. > > > > > i've googled for days. zero. im finally asking the top list > > on the web. can anybody clue me in? i'm using linux/gnome/mutt. > > but it shouldnt make any difference. [?!] > > If I remember correctly, there's a way to disable the line break > emphasizer ('+' character) in the display. Have you tried > > set markers=no > > in your ~/.muttrc? Or was it > > unset markers > > Something with "markers"... I'm not fully sure if this is the > setting you're searching for, but go ahead and try it. > theres a 'set markers' that defaults to yes. I edited it to no and, presto, no mo' '+' in the url strings. ---how you ever remembered the variable 'markers' is beyound me, but yup. anyway, with my konsole at std size, ~37x80, I moused dead-on the http string. same as before: the string showed up from the 'http://.' to the eol. and when I clicked, I got garbage. wait, there's more. I blew up the konsole until it filled the entire screen. [i did this once before and got the right page.] it still worked. no '+' line break, but still. it's a bear to have to enlage the xterm/konsole just to read some mail, but it works with the two embedded urls that I've tried so far. why? dunno. > > > -- > 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" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-six years of service to the Unix community. ___ 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: mutt and http//url???
On Fri, Mar 22, 2013 at 08:39:07PM -0400, Karl Vogel wrote: > >> On Fri, 22 Mar 2013 14:36:15 -0700, > >> Gary Kline said: > > G> in the past couple years i've sub'd to the nytimes and other places > G> where the http string is several dozens of bytes. in my mutt at least, > G> there are "+" marks embedded at the beginning of each new lines. so > G> that when i mouse lick on the url, > >Don't lick your mouse. That's gross. but it was so tasty! 'specially with chocolatte syrup. > G> i almost invariably get either Nothing from my browswer, or the wrong > G> page. > >You might want to try urlview, bound to Ctrl-B in mutt by default. It's a >screen-oriented program for extracting URLs from text files, putting >them in a menu, and letting you run a command to view a specific item. > >If you're on a FreeBSD system, it's in /usr/ports/textproc/urlview. this was one of the things I tried. I followed the instructions exactly--with urlview and ^B. eventually I wound up with the list but it was hard to decide which was the text! maybe leave o ne konsole wide open on my 4th workspace > -- > Karl Vogel I don't speak for the USAF or my company > > Oh, to be only half as wonderful as my child thought I was when he was small, > and only half as stupid as my teenager now thinks I am.--Rebecca Richards > ___ > 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" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-six years of service to the Unix community. ___ 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: mutt and http//url???
On Fri, 22 Mar 2013 18:18:55 -0700, Gary Kline wrote: > anyway, with my konsole at std size, ~37x80, I moused dead-on > the http string. same as before: the string showed up from the > 'http://.' to the eol. and when I clicked, I got garbage. The only way I tried (and confirmed) to deal with this particular problem is to make the "select URL" process a bit more complex (in terms of steps involed): Use a triple-click to select the whole (multi-line) URL, OR select it manually. Doing so with a held-down left mouse button will transfer the selected text into the edit buffer. In this specific case where the '+' characters have been eliminated, the line breaks will also _not_ be part of the edit buffer content. I've tried this by selecting a multi-line URL in a normal X terminal (xterm) and pasting it to a GUI text editor - result: one line, as intended. Now if I do a middle-click in the web browser (Opera in my case), it will navigate to that URL in the current tab (or open a new tab for it if I click on an empty space on the tab bar). The same concept applies to Firefox, but you need to have one instance of it started. Click the middle mouse button (or if you don't have one, press down the mouse wheel). Now Firefox will receive the full URL and go to that web page. However, this is, as you see, a bit more complicated. You can still try it and verify if it will work in your setting. > wait, there's more. I blew up the konsole until it filled the > entire screen. [i did this once before and got the right page.] > it still worked. no '+' line break, but still. That's an interesting workaround, but also makes things unneccessarily complicated. An intermediate solution could be to maximize the whole terminal application and use virtual desktops (workspaces) to switch between MUA and web browser. Still that's suboptimum. -- 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: Handbook Jail Chapter rewrite available for critique (fwd)
Joe, your mailer dropped -questions from the ccs on your response. Fixed, Ian -- Forwarded message -- Date: Fri, 22 Mar 2013 18:12:18 -0400 From: Fbsd8 To: freebsd-j...@freebsd.org Cc: Ian Smith , Dirk Engling Subject: Re: Handbook Jail Chapter rewrite available for critique Ian Smith wrote: > On Tue, 19 Mar 2013 17:53:30 +0100, Dirk Engling wrote: > > On 18.03.13 20:16, s...@tormail.org wrote: > > > > to configure things themselves. In my experience, ezjail is a much > better > > > solution. I also see that you are the maintainer/author of qjail and like > > > to shovel your opinion as the only solution, both in this "rewrite" and > > > all over the FreeBSD forums. > > > Taking a look at the qjail code I can not help to notice several odd > > similarities with the ezjail-admin script, down to the very basic bail > > out routines. I would not go so far to claim it was just a global > > search/replace job but to me the code looks familiar enough to find the > > > # Copyright 2010, Qjail project. All rights reserved. > > > offensive. I am usually quite open with the license of my software, > > beerware is as permissive as it gets. I just can not take some script > > kiddie right out copying my code verbatim and selling it as his, not > > even acknowledging me as the original author. > > > Anyone here with suggestions how to properly react to this kind of > "fork"? > > Yes. Publicity. Making sure the FreeBSD community gets to finds out. > > You may be polite and un-selfserving enough to not go so far Dirk, but I will. > Huge swathes of qjail are direct copies of your code, in most cases only with > the names of the variables changed from ezjail_* to qjail_*. I found it cute > renaming 'flavour' to the American spelling. > > Anyone looking at bin/qjail from qjail-2.1.tbz alongside the latest > ezjail-admin (mine downloaded from your cvsweb) cannot fail to notice > within the first couple of screens. Sure there are changes, additions and > deletions, but to fail to acknowledge the original authorship of this code, > and the implication that Joe Barbish (aka 'Qjail project') is its original > author is entirely outrageous; not ethical, even if legal. > > To that end I'm cross-posting this to -questions, where Mr Barbish has also > posted about his proposed "rewrite" of Chapter 16 of the Handbook, which is > nothing but a huge and poorly written manual for 'the qjail way', with its > peculiar assumptions and unique "jailcell" terminology. "Fourth Generation", > no less! > > The idea that the "doc gang" would entertain the idea of removing all of the > worthy content of the present Chapter 16 - even if it does need some updating > - and replace it with this effort is laughable, yet stranger things have > happened if there's any disconnect between developers and documenters .. > witness the Handbook firewalls section, by Joe Barbish. > > cheers, Ian > Boy this simple critique request sure has gotten out of hand. So lets set the record straight. On the subject ezjail not being referenced in the document like it is in the current version of the online handbook is just a writing content error. The document being critiqued is the first public draft. Pointing out over sights like not included ezjail in that section is the type of constructive feedback that is desired. Any inference it was done on purpose is just crazy. When it comes to the question of the handbook jail chapter needing updating, A member of the document team has already offered to partner up with me to get it added to the handbook as fast as possible. To me that means the document team is already aware the current handbook jail chapter is outdated and has just been waiting for someone to write a update which is just what I did. If you people have a beef with that, take it up with the document team not me. If any of you think you can do a better job then NOW is the time to step up or shut up. On the subject of qjail being a fork of ezjail, of course it is. Qjail was developed by the qjail project team who are a group of FreeBSD users who live around Angeles City, Philippines. Of the seven members 2 are foreigners living in the area, one American and one British. Our British member concluded that the author of ezjail must be British based solely on the spelling of the flavour directory. He also convinced us that his Beerware license was British humor, a joke, and should not be taken serous. In our review of other jail ports we did not see this Beerware license again or for that matter, see it in any of the 5000+ ports we looked at or use. So the group coincided to the British members view point as sound advice. If you inspect the qjail source, you should recognize the comments at the beginning as a copy of what is included in every FreeBSD config file. It was inserted in the front like they have. We though that was how you make software opensource which was the intention. There are no formal copyri
Don't replay to spam
The original "trying freeBSD 9.1 [...]" mail is spam, since the original message had a "signature" about face lifting or something like that. Take a look at http://lists.freebsd.org/pipermail/freebsd-questions/2013-March/249992.html Once you visited the page from the link in the signature, you even can't leave this page. It's hard to train spam filters, if people reply to spam. Regards, Ralf ___ 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"