Re: csh Cannot open /etc/termcap after starting "screen"
Hi, On Thu, Jun 16, 2011 at 13:15 -0700, Jeremy Chadwick wrote: > Example: run mutt from within GNU screen while connected to > the system with PuTTY, then copy some of the terminal content and paste > it somewhere. Wow, look at all those extraneous spaces at the end of > lines, which you now gloriously have to manually remove. While I don't want to stand in the way of your rant, this is actually a bug/problem of mutt. -- mutt is really printing spaces there, so it is (IMHO) correct that copy&paste copies spaces. CU, Sec (using screen since 1994) -- | Kevin Dalley on Melissa being Open Source: While the Melissa license is a bit unclear, Melissa aggressively encourages free distribution of its source code. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Constant rebooting after power loss
Hi, On Fri, Apr 01, 2011 at 13:27 +0200, Marko Lerota wrote: > Today one of my home servers lost power two times in a short > period of time. After that, the system just couldn't get up. > Background checks couldn't get started. The messages was how > / /tmp /var etc...had to much errors. And at the end, always > got this: "automatic reboot will start in 15sec". > > I went to single user mode, and ran FSCK manually. That solved > the problem. But the server was down for 2 hours. If you want to get rid of the reboot loop, set: background_fsck="NO" Then it will either come up, or ask for help if anything fails. If you absolutely want the server to come up, you can set this fsck_y_enable="YES" Assuming you're in the habit of answering "yes" to fsck's questions, this will do it automatically in case of problems. (Both settings are for /etc/rc.conf, of course) CU, Sec -- One of the strongest advantages of plain-text email is that people cannot use the typesetting features they want. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Request for testing - top 3.8b1 in the base system
Hi, On Sun, Sep 28, 2008 at 15:46 +1000, Edwin Groothuis wrote: > The new code can be found on > http://www.mavetju.org/~edwin/freebsd-top-3.8b1-A.tar.gz > Go to 3.8b1/usr.sbin/top and run "make" there to produce the binary, > then run it via "./top". compiles and runs fine on my box: FreeBSD ice 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #17: Wed Sep 3 23:59:58 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ICE amd64 > Please report any issues with it (compile time, run time) and a way > to reproduce it (if possible). Thanks for your help! The number of sleeping processes is much lower than system top: oldtop: 480 processes: 3 running, 450 sleeping, 2 stopped, 7 zombie, 18 waiting newtop: 190 processes: 3 running, 160 sleeping, 2 stopped, 7 zombie, 18 waiting Interestingly, the system top appears to be the one in error: ice:~>ps auxww|wc -l 194 Other than that, i could see no obvious problems. CU, Sec -- I think the IDE issue is a good point. People with IDE hardware in their machines should be punished by making them wait to boot... -- [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
snapshots and disk usage
Hi, I am using ufs snapshots on RELENG_7 for some time now, and am generally happy with it. I have noticed a strange behaviour when removing large amount of files, and wanted to ask if this is expected. Before starting, we check the free space on /usr: | ice:/usr>df -h . | Filesystem SizeUsed Avail Capacity Mounted on | /dev/ad4s2.elid9.7G7.6G1.3G64%/usr Then delete /usr/obj and run df again: | ice:/usr>sudo rm -rf obj 2>/dev/null | ice:/usr>df -h . | Filesystem SizeUsed Avail Capacity Mounted on | /dev/ad4s2.elid9.7G5.7G3.2G64%/usr This is unexpected. With snapshots, removing something should not release space. Sure enough, in the course of the next minute, the fake free space vanishes | ice:/usr>df -h . | Filesystem SizeUsed Avail Capacity Mounted on | /dev/ad4s2.elid9.7G5.9G3.0G66%/usr | ice:/usr>df -h . | Filesystem SizeUsed Avail Capacity Mounted on | /dev/ad4s2.elid9.7G6.6G2.3G74%/usr | ice:/usr>df -h . | Filesystem SizeUsed Avail Capacity Mounted on | /dev/ad4s2.elid9.7G8.6G269M97%/usr and all the free space is allocated in the snapshot: | ice:~>sudo snapshot list | Filesystem User User% Snap Snap% Snapshot | /usr 8GB 89.3% 2GB 21.5% daily.1 | /usr 8GB 89.3%344MB3.5% daily.0 | /usr 8GB 89.3%344MB3.5% weekly.0 | /usr 8GB 89.3%344MB3.5% hourly.1 | /usr 8GB 89.3% 7MB0.1% hourly.0 My understanding so far was that df may underreport free space, but i find overreporting it a bit troublesome. -- What would happen if I tried to use that space before it was allocated to the snapshot? Case in point: I created a few unkillable hung process on /usr a few weeks ago, by running make world which was running out of diskspace, and deleting files from another windows. -- At leat thats what I think has happened. CU, Sec -- Consider the need for having to type "www.domain.name" a little IQ test that you have to take before you can access my web site.' -- Wietse ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
firewire related hang.
I just installed FreeBSD-7 on an amd64 box. The new motherboard has firewire builtin. I wanted to disable dma via firewire, but as soon as I add hw.firewire.phydma_enable=0 to /boot/loader.conf (which is what the man page suggests) The box hangs on boot. It detects the firewire controller, after that the sata disk and then hangs. Is this a known problem? Is there anything I can do to help debug this? Lastly, if this is not easily fixable, would removing the firewire driver from my kernel disable the DMA attack? CU, Sec -- Whatever the virtues of balance, it's just a pleasant form of insanity. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail
At 09:11 AM 03/03/2003 -0800, FreeBSD Security Advisories wrote: >Module: contrib_sendmail >Announced: 2003-03-03 >Credits:Mark Dowd (ISS) >Affects:All releases prior to 4.8-RELEASE and 5.0-RELEASE-p4 > FreeBSD 4-STABLE prior to the correction date >Corrected: 2003-03-03 >1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_0, I still have a FreeBSD-2.8 (-STABLE) system running which includes sendmail-8.8.8. As the patches on sendmail.org only apply to sendmail-8.9 - sendmail-8.12, i ported the patch. Perhaps someone else needs this patch, so I've put it up for ftp at ftp://ftp.42.org/sendmail.8.8.8.patch As I don't have an example E-Mail to test, I can not _guarantee_ that this fixes it. But given the fact that I only had to change two lines (which both were function declarations) from the official supported patch, I'm sure that this patch fixes the problem. CU, Sec -- ``oh no! the gronkulator is broken!'' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: disable mousepad taps on Dell Inspiron
On Fri, Jan 12, 2001 at 09:50:40PM -0600, Stephen Montgomery-Smith wrote: > I have submitted another PR describing how to do this: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 I wanted to disable the 'tap' functionality on my vaio laptop. After reading the moused-manpage I realized that it might be possible without hacking the psm source if my pad sends the tap as button 4 and tried moused -m 4=0 which works like a charm for me. I'm very happy now :) CU, Sec -- You haven't seen _multitasking_ until you have seen Doom and Quake run side by side. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
