Re: default pager (csh)
On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On 19 Feb 2015, at 09:16, Julian Elischer jul...@freebsd.org wrote: On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. Yeah, that drives me nuts too, Debian had (has?) this and it's a no-go for me. Changing options for man would be nice though, so finding something near the end of the page won't exit the pager. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
Hi Adrian, On Wed, Feb 18, 2015 at 10:09 PM, Adrian Chadd adr...@freebsd.org wrote: Hi, Since this is the (at least) second round of x2apic support broke me changes, can we please either back them out or set it to default to '0' for now? I don't think that is necessary. This is -current and there is a tunable to disable x2apic on platforms that are experiencing issues. More importantly the issues that have been reported are being resolved in a timely manner (for e.g., suspend/resume). best Neel Thanks, -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
On Thu, Feb 19, 2015 at 11:50:49AM -0800, Neel Natu wrote: Hi Adrian, On Wed, Feb 18, 2015 at 10:09 PM, Adrian Chadd adr...@freebsd.org wrote: Hi, Since this is the (at least) second round of x2apic support broke me changes, can we please either back them out or set it to default to '0' for now? I don't think that is necessary. This is -current and there is a tunable to disable x2apic on platforms that are experiencing issues. More importantly the issues that have been reported are being resolved in a timely manner (for e.g., suspend/resume). There is only one really enigmatic issue, it was reported that sandy bridge laptop being unable to start APs. Koop stopped responding, so the issue is not progresed. My current idea is that a cause might be reduced intervals between init/startup ipis due to x2apic not requiring wait for icr idle. Anyway, I do not see it worth even discussing the revert or default' frobbing for now. The commit went mostly event-less for such kind of change. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Build failed in Jenkins: FreeBSD_HEAD-tests2 #725
See https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/725/ -- [...truncated 62 lines...] Event timer HPET1 frequency 1000 Hz quality 450 Event timer HPET2 frequency 1000 Hz quality 450 Event timer HPET3 frequency 1000 Hz quality 450 Event timer HPET4 frequency 1000 Hz quality 450 Event timer HPET5 frequency 1000 Hz quality 450 Event timer HPET6 frequency 1000 Hz quality 450 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 32-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 virtio_pci0: VirtIO PCI Network adapter port 0x2000-0x201f mem 0xc000-0xc0001fff irq 16 at device 2.0 on pci0 vtnet0: VirtIO Networking Adapter on virtio_pci0 virtio_pci0: host features: 0x1018020 NotifyOnEmpty,Status,MrgRxBuf,MacAddress virtio_pci0: negotiated features: 0x18020 Status,MrgRxBuf,MacAddress vtnet0: Ethernet address: 58:9c:fc:00:00:2e 001.45 [ 427] vtnet_netmap_attach max rings 1 001.46 [2717] netmap_attach success for vtnet0 tx 1/1024 rx 1/1024 queues/slots 001.47 [ 432] vtnet_netmap_attach virtio attached txq=1, txd=1024 rxq=1, rxd=1024 ahci0: Intel ICH8 AHCI SATA controller mem 0xc0002000-0xc00023ff irq 17 at device 3.0 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich0: AHCI channel at channel 0 on ahci0 uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) uart1: 16550 or compatible port 0x2f8-0x2ff irq 3 on acpi0 qpi0: QPI system bus on motherboard vga0: Generic ISA VGA at port 0x3b0-0x3bb iomem 0xb-0xb7fff on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: cannot reserve I/O port range Timecounters tick every 1.000 msec ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: BHYVE SATA DISK 001 ATA-8 SATA 2.x device ada0: Serial Number 123456 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 2048MB (4194304 512 byte sectors: 16H 63S/T 4161C) ada0: Previously was known as ad4 random: unblocking device. SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ufs/TESTROOT [rw]... Setting hostuuid: a26265ab-b820-11e4-a5fc-589cfc2e. Setting hostid: 0x48907087. No suitable dump device was found. Starting file system checks: /dev/ufs/TESTROOT: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ufs/TESTROOT: clean, 245421 free (29 frags, 30674 blocks, 0.0% fragmentation) Mounting local file systems:. /etc/rc: WARNING: $hostname is not set -- see rc.conf(5). Feeding entropy:. Starting Network: lo0 vtnet0. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL groups: lo vtnet0: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=80028VLAN_MTU,JUMBO_MTU,LINKSTATE ether 58:9c:fc:00:00:2e nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet 10Gbase-T full-duplex status: active Starting devd. Starting Network: vtnet0. vtnet0: flags=8902BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=80028VLAN_MTU,JUMBO_MTU,LINKSTATE ether 58:9c:fc:00:00:2e nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet 10Gbase-T full-duplex status: active Starting pflogd: add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net :::0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Generating host.conf. Creating and/or trimming log fileseval: /usr/sbin/newsyslog: not found . /etc/rc: WARNING: run_rc_command: cannot run /usr/sbin/syslogd ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib 32-bit compatibility ldconfig path: /usr/lib32 Starting casperd. Clearing /tmp (X related). Updating motd:. Mounting late file systems:. Configuring vt: blanktime. /etc/rc: WARNING: run_rc_command: cannot run /usr/sbin/sendmail /etc/rc: WARNING: run_rc_command: cannot run /usr/sbin/sendmail Starting cron. Starting background file system checks in 60 seconds. Thu Feb 19 10:18:33 UTC 2015 FreeBSD/amd64 (Amnesiac) (ttyu0) login: root root FreeBSD 11.0-CURRENT (GENERIC) #85 r278988: Thu Feb 19 09:47:58 UTC 2015 Welcome to FreeBSD! Release Notes, Errata: https://www.FreeBSD.org/releases/ Security Advisories: https://www.FreeBSD.org/security/ FreeBSD Handbook: https://www.FreeBSD.org/handbook/ FreeBSD FAQ: https://www.FreeBSD.org/faq/ Questions List:
Jenkins build is back to normal : FreeBSD_HEAD #2409
See https://jenkins.freebsd.org/job/FreeBSD_HEAD/2409/changes ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Wed, 18 Feb 2015 23:45:27 -0800, Kevin Oberman rkober...@gmail.com wrote: On Wed, Feb 18, 2015 at 10:46 PM, Franco Fichtner fra...@lastsummer.de wrote: On 19 Feb 2015, at 02:27, Davide Italiano dav...@freebsd.org wrote: On Wed, Feb 18, 2015 at 5:18 PM, Adam McDougall mcdou...@egr.msu.edu wrote: The PAGER was less for about half a year and reverted. Please see: https://svnweb.freebsd.org/base?view=revisionrevision=242643 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org OK, I think this ends the discussion =) Nope, not good enough. The way I see it we achieved nothing despite the fact that several bugs are on the table. Now that we all agree more(1) is the way to go, can we please fix colouring and the pager quit issue for man pages using sensible options in more(1)? Other's should speak up for their woes with the FreeBSD defaults too. The defaults are supposed to be the best we can do. Right now, we can actually do better. :) Cheers, Franco I want my bikeshed to be purple with yellow stars. I want my PAGER to be Jim Davis's most(1). Does a LOT more than more or less. (Does have the annoying te/ti thing, though.) Displays binary. Auto-decompresses compressed files. Allows moving my line or percentage. Whole raft of neat stuff. Usually the second port (after portmaster) I install on a system since my finger type most even when I want them to type more because the system does not have most installed. I don't expect anyone else to agree and don't expect it to ever be in the base, let alone the default. Still, it's a much better pager then less, whether it's called more or not. Started using it at least 25 years ago on VMS. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Here: (.zshrc)... PAGER='cat' alias man='env PAGER=lookat man $1' That bottom one is so useful for the 's' search key... EXAMPLES for instance. Same on all keyboards... [ seems easier to read with default colors, also... ] However in some instances (screen, dvtm, tmux... ) it may have onscreen artifacts one can simply then 'sh' (untested) first... for usual 'man' instance of PAGER. /usr/ports/sysutils/lookat... [ Just re-noticed that 'cat' entry today. No idea of the difference to a default... ] ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Jenkins build is back to normal : FreeBSD_HEAD-tests2 #726
See https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/726/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This panic starts at: https://svnweb.freebsd.org/base?view=revisionrevision=278473 If I use 278472, I can boot the Xen VM normally. If I use head and set hw.x2apic_enable=0 in loader.conf and boot head (278970), it boots normally. Second issue: However, the UFS disk access is SO slow on this that it took 2+hours to do an installworld, which I couldn't abort because it had already started. I'm not sure if the UFS disk access is related at all or not. Once things are read from disk into memory they are fast and responsive (e.g. sshd, tmux, shells, etc). sean bcc royger Maybe helpful, verbose dmesg on bootup with x2apic disabled: https://people.freebsd.org/~sbruno/xen_dmesg_verbose.txt sean -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJU5mIxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kZewH/j/Fy9b8tteEM68ZGti3XZAK jLDkr8m21pFO8YxPYWrWhXp4f6pvLnTbUIjq5V+8nlCTK+douRfhy8OvG4lW2a5r Hvgwc147mDBpELtlByijsasc9ulkUveI7pSDDSu49dD8RBCOBhGjkfr4iU1tiSbI NHog3vBKk5IYV0u4pynyq1ROMESMNtHSfobt1oHgzxUS1xWHcv4YvnWK05dLM07D lU+g8sY9aBtU8L+IPlAtQW8fZFTwt1RO5oPk3BveA32KxV90vO9bJ2AyHl821/US Fo0NU8zhOuCYaSLF43xexEH1h3EQbjLJho6YslHtIaLqqE0cqpBhnbfKHsE4SmA= =H6sT -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On 20/02/2015 01:22, RW wrote: On Wed, 18 Feb 2015 19:16:59 -0600 Mike Karels wrote: Trivia: the version of more on BSD systems actually is derived from less, not the original version of more. Actually, more is less $ md5 -r `which less ` `which more ` 50404f1beaa4e1261407190a88494b59 /usr/bin/less 50404f1beaa4e1261407190a88494b59 /usr/bin/more Yes more has been less for some time, trouble is it is programmed to behave differently based on the name used to call it so they aren't the same. Try this - echo test data testfile more testfile less testfile So the debate over which is better continues Like everything, if you don't like the way it works you find a setting to make it work the way you want. Whether you ask on a mailing list or google it you will find a way to configure it your way. As long as it works, the default is of little concern to most. I don't even remember what year I set my pager to more, till I just looked I would have guessed I was using the default. Whatever intro I got started with used more as a pager and I have just used it since. I just think '| more' not '| less' -- FreeBSD - the place to B...Software Developing Shane Ambler ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
bsdconfig not able to get packages from freebsd ftp site
hi all: i am trying install packages with bsdconfig on freebsd 10.1 and failed. it stuck at the following message for a while : Attempting to update repository catalogue from selected media finally it gave up with following message: No pkg(8) database found thanks. _dave ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, Feb 19, 2015 at 5:10 PM, Warren Block wbl...@wonkity.com wrote: On Thu, 19 Feb 2015, Julian Elischer wrote: On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. It doesn't do that on csh. Or maybe I figured out how to prevent it long ago and forgot, but all I use is this: setenv PAGER less -RS You probably did what I used to do. Modify the termcaps/terminfo to eliminate this behavior. See Exorcising the Evil Alternate Screen http://shallowsky.com/linux/noaltscreen.html. In the past, FreeBSD disabled this by default. It was changed several years ago, but you can change it back as per the aboved referenced article. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, Feb 19, 2015 at 7:45 PM, Kevin Oberman rkober...@gmail.com wrote: On Thu, Feb 19, 2015 at 5:10 PM, Warren Block wbl...@wonkity.com wrote: On Thu, 19 Feb 2015, Julian Elischer wrote: On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. It doesn't do that on csh. Or maybe I figured out how to prevent it long ago and forgot, but all I use is this: setenv PAGER less -RS You probably did what I used to do. Modify the termcaps/terminfo to eliminate this behavior. See Exorcising the Evil Alternate Screen http://shallowsky.com/linux/noaltscreen.html. In the past, FreeBSD disabled this by default. It was changed several years ago, but you can change it back as per the above referenced article. Well, I just looked at this and it looks like FreeBSD is using termcap, not terminfo. So you can fix this by defining TERM to a version of xterm that does not define alternate screen. I use xterm which, rather surprisingly, does not define ti or te. Neither do any of the xterm variants that I can find in termcap. (N.B. I am NOT running xterm. I am using mate-terminal, but it still works.) rxvt variants do define them, as do a great many others. Take a look at /usr/share/misc/termcap. Just remember that editing it does nothing until termcap.db is rebuilt. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, 19 Feb 2015 18:10:36 -0700 (MST) Warren Block wbl...@wonkity.com wrote On Thu, 19 Feb 2015, Julian Elischer wrote: On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. It doesn't do that on csh. Or maybe I figured out how to prevent it long ago and forgot, but all I use is this: setenv PAGER less -RS Ugh. It would kill me to *re*read the man pages, once and awhile. Thanks, Warren! --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, 19 Feb 2015, RW wrote: On Wed, 18 Feb 2015 19:16:59 -0600 Mike Karels wrote: Trivia: the version of more on BSD systems actually is derived from less, not the original version of more. Actually, more is less Fortunately we don't set LESSOPEN by default like some (most?) Linux distributions. http://seclists.org/oss-sec/2014/q4/769 Maybe this feature should even be disabled when in more mode. //Marcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Wed, 18 Feb 2015 19:16:59 -0600 Mike Karels wrote: Trivia: the version of more on BSD systems actually is derived from less, not the original version of more. Actually, more is less $ md5 -r `which less ` `which more ` 50404f1beaa4e1261407190a88494b59 /usr/bin/less 50404f1beaa4e1261407190a88494b59 /usr/bin/more ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, 2015-02-19 at 07:46 +0100, Franco Fichtner wrote: On 19 Feb 2015, at 02:27, Davide Italiano dav...@freebsd.org wrote: On Wed, Feb 18, 2015 at 5:18 PM, Adam McDougall mcdou...@egr.msu.edu wrote: The PAGER was less for about half a year and reverted. Please see: https://svnweb.freebsd.org/base?view=revisionrevision=242643 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org OK, I think this ends the discussion =) Nope, not good enough. The way I see it we achieved nothing despite the fact that several bugs are on the table. Now that we all agree more(1) is the way to go, can we please fix colouring and the pager quit issue for man pages using sensible options in more(1)? Other's should speak up for their woes with the FreeBSD defaults too. The defaults are supposed to be the best we can do. Right now, we can actually do better. :) I sure hope fix coloring is shorthand for don't you dare turn on any of that color crap without the user's permission. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, 19 Feb 2015 00:16:55 -0800 Julian Elischer jul...@freebsd.org wrote On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. Indeed. Quite annoying. I just had an interesting thought after reading most of this thread/bikeshed; Theoretical, mind you. But would it be remotely possible to [in (t)csh(1)] choose a pager on-the-fly (dynamically)? In other words; bind keys to a chosen pager; ^M switches to more(1) ^L switched to less(1) I've done no *actual* research [yet] but just thought I'd bring it up. As it seemed worth a shot, as it would satisfy *anyone's* need. :) --Chris ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, 19 Feb 2015, Ian Lepore wrote: On Thu, 2015-02-19 at 07:46 +0100, Franco Fichtner wrote: On 19 Feb 2015, at 02:27, Davide Italiano dav...@freebsd.org wrote: On Wed, Feb 18, 2015 at 5:18 PM, Adam McDougall mcdou...@egr.msu.edu wrote: The PAGER was less for about half a year and reverted. Please see: https://svnweb.freebsd.org/base?view=revisionrevision=242643 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org OK, I think this ends the discussion =) Nope, not good enough. The way I see it we achieved nothing despite the fact that several bugs are on the table. Now that we all agree more(1) is the way to go, can we please fix colouring and the pager quit issue for man pages using sensible options in more(1)? Other's should speak up for their woes with the FreeBSD defaults too. The defaults are supposed to be the best we can do. Right now, we can actually do better. :) I sure hope fix coloring is shorthand for don't you dare turn on any of that color crap without the user's permission. Agree! Leave pager alone. And I kind of like that PAGER exits when you get to the end, but perhaps I'm in the minority on that. The thing I can't stand is losing all contents of 'man' when you exit the pager, so I'm with Julian on that too. -- DE ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Xen HVM Panic, HEAD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This panic starts at: https://svnweb.freebsd.org/base?view=revisionrevision=278473 If I use 278472, I can boot the Xen VM normally. If I use head and set hw.x2apic_enable=0 in loader.conf and boot head (278970), it boots normally. Second issue: However, the UFS disk access is SO slow on this that it took 2+hours to do an installworld, which I couldn't abort because it had already started. I'm not sure if the UFS disk access is related at all or not. Once things are read from disk into memory they are fast and responsive (e.g. sshd, tmux, shells, etc). sean bcc royger BTW, my kernconf for this contains: include GENERIC ident BLOG nooptions DDB nooptions GDB nooptions DEADLKRES nooptions INVARIANTS # Enable calls of extra sanity checking nooptions INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect deadlocks and cycles nooptions WITNESS_SKIPSPIN# Don't run witness on spinlocks for speed nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zone -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQF8BAEBCgBmBQJU5iDJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kiOEIAM5UWud6DGlGgQM5PsHmP4nO LMiAyq2bIE/MtaR13IZL1hv9zBKHAYva9CyaAiAVDFtOSP6nR+/zcxi2SlkNbO9Z lmERNmIs2AvfZiX/+krqVJXcI0MoeXO+9WSpz1SuUo1kXRaWXYNuTDw2qG0lbG/e 282EyNBIg4Jz+KfcTK/cmKQCc1jCMA7Fwym1G7Lwfd8HwxaqJFGa446Y6vle8UZt BSa52DOUP5D0RswByXzNS4aqMI9fLJRcTQZSrY15lUAYmi8uF37n+u8KH7dzbRM+ czW3vJpwckJieA5h+EmV0bABplT3L80/JhdA6vXF98kgrq+6b7xPVowmmvxECfQ= =MPg8 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On Thu, Feb 19, 2015 at 3:36 PM, Daniel Eischen deisc...@freebsd.org wrote: On Thu, 19 Feb 2015, Alfred Perlstein wrote: Not as annoying as people who don't search the web for an answer for things. ~ % export PAGER=less -X everyone please stop crying over small changes, it really sucks. Not sure what you are saying, but the question posed is changing the default pager. So that means: o all users who like the current more(1) behavior have to define and override PAGER. o all users who like the less(1) behavior remove their override of PAGER Or leave things alone, and users who want less(1) behavior override PAGER, which they've probably already done if it's that annoying to them. The answer seems pretty simple to me. -- DE I still want my purple and yellow bikeshed and most(1). sarcasm No matter when happens, a lot of people will need to undertake the massive and painful effort of defining PAGER. I realize this is a terrible burden for may of them. /sarcasm Let's call the whole thing off and maybe do something useful. -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Pluggable frame buffer devices
On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: Hi, I've added support for USB display link adapters to FreeBSD-11-current, but the kernel panics once vt_fb_attach(info) is called from fbd_register(struct fb_info* info) when the USB device is plugged or udl.ko is loaded. Is this a known issue? REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c --HPS I just bought a DisplayLink adapter that's compatible. Compiling a new kernel with device udl brings this error: -- stage 3.2: building everything -- linking kernel.debug udl.o: In function `udl_attach': /usr/src/sys/dev/usb/video/udl.c:(.text+0xa07): undefined reference to `edid_parse' /usr/src/sys/dev/usb/video/udl.c:(.text+0xa0f): undefined reference to `edid_print' --- kernel.debug --- *** [kernel.debug] Error code 1 Thanks, Shawn signature.asc Description: This is a digitally signed message part.
Re: default pager (csh)
On Thu, 19 Feb 2015, Julian Elischer wrote: On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. It doesn't do that on csh. Or maybe I figured out how to prevent it long ago and forgot, but all I use is this: setenv PAGER less -RS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Pluggable frame buffer devices
On Thursday, February 19, 2015 07:04:50 PM Shawn Webb wrote: On Sunday, February 15, 2015 11:14:47 PM Hans Petter Selasky wrote: Hi, I've added support for USB display link adapters to FreeBSD-11-current, but the kernel panics once vt_fb_attach(info) is called from fbd_register(struct fb_info* info) when the USB device is plugged or udl.ko is loaded. Is this a known issue? REF: https://svnweb.freebsd.org/base/head/sys/dev/usb/video/udl.c --HPS I just bought a DisplayLink adapter that's compatible. Compiling a new kernel with device udl brings this error: -- stage 3.2: building everything -- linking kernel.debug udl.o: In function `udl_attach': /usr/src/sys/dev/usb/video/udl.c:(.text+0xa07): undefined reference to `edid_parse' /usr/src/sys/dev/usb/video/udl.c:(.text+0xa0f): undefined reference to `edid_print' --- kernel.debug --- *** [kernel.debug] Error code 1 Thanks, Shawn I got it building. I had to add device videomode to my kernel as well. It looks like when I plug in the device I bought, identifying the device just stalls out. Log posted below: [3] uhub3: vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.05, addr 2 on usbus2 [3] ugen1.2: vendor 0x8087 at usbus1 [3] uhub4: vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.05, addr 2 on usbus1 [3] uhub4: 6 ports with 6 removable, self powered [3] ugen0.3: Generic at usbus0 [4] Root mount waiting for: usbus2 usbus0 [5] Root mount waiting for: usbus2 usbus0 [6] Root mount waiting for: usbus2 usbus0 [6] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [7] Root mount waiting for: usbus2 usbus0 [7] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [8] uhub_attach: Getting USB 2.0 HUB descriptor failed,error=USB_ERR_TIMEOUT [8] device_attach: uhub3 attach returned 6 [8] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [9] Root mount waiting for: usbus0 [10] Root mount waiting for: usbus0 [10] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [10] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [11] Root mount waiting for: usbus0 [11] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [12] Root mount waiting for: usbus0 [12] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [13] Root mount waiting for: usbus0 [14] usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) [14] Root mount waiting for: usbus0 [14] usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_TIMEOUT [14] ugen0.4: Unknown at usbus0 (disconnected) [14] uhub_reattach_port: could not allocate new device [15] Root mount waiting for: usbus0 [16] Root mount waiting for: usbus0 [17] Root mount waiting for: usbus0 [18] Root mount waiting for: usbus0 [19] Root mount waiting for: usbus0 [20] Root mount waiting for: usbus0 [21] usbd_setup_device_desc: getting device descriptor at addr 4 failed, USB_ERR_TIMEOUT [21] usbd_req_re_enumerate: addr=4, set address failed! (USB_ERR_IOERROR, ignored) signature.asc Description: This is a digitally signed message part.
Re: default pager (csh)
On Thu, 19 Feb 2015, Alfred Perlstein wrote: Not as annoying as people who don't search the web for an answer for things. ~ % export PAGER=less -X everyone please stop crying over small changes, it really sucks. Not sure what you are saying, but the question posed is changing the default pager. So that means: o all users who like the current more(1) behavior have to define and override PAGER. o all users who like the less(1) behavior remove their override of PAGER Or leave things alone, and users who want less(1) behavior override PAGER, which they've probably already done if it's that annoying to them. The answer seems pretty simple to me. -- DE ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: default pager (csh)
On 2/19/15 9:04 AM, Chris H wrote: On Thu, 19 Feb 2015 00:16:55 -0800 Julian Elischer jul...@freebsd.org wrote On 2/18/15 3:41 PM, Xin Li wrote: The _only_ reason that I can think of is that more(1) does not clear screen for certain terminals (done with 'ti' and 'te' sequences), while less(1) when running as less does. The less(1) behavior can be annoying to some people (sometimes even myself when using less to show contents of a file and ^Z to paste them), and unfortunately quite a few of them also happen to be the more vocal ones when it comes to a change. I find that behaviour infuriating I page down to a place to get some text on the screen to use as a reference, then exit to run a command with that information, and *bam* the info I wanted to use has gone away. Indeed. Quite annoying. I just had an interesting thought after reading most of this thread/bikeshed; Theoretical, mind you. But would it be remotely possible to [in (t)csh(1)] choose a pager on-the-fly (dynamically)? In other words; bind keys to a chosen pager; ^M switches to more(1) ^L switched to less(1) I've done no *actual* research [yet] but just thought I'd bring it up. As it seemed worth a shot, as it would satisfy *anyone's* need. :) Not as annoying as people who don't search the web for an answer for things. ~ % export PAGER=less -X everyone please stop crying over small changes, it really sucks. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
