From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 5 05:03:14 2010 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1CE910656CF for ; Sun, 5 Sep 2010 05:03:14 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5B12F8FC13 for ; Sun, 5 Sep 2010 05:03:14 +0000 (UTC) Received: by yxn35 with SMTP id 35so1437526yxn.13 for ; Sat, 04 Sep 2010 22:03:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=NkPTEaqIRfx4zZMMvHL1KLV6JESQSlcQJD6kQRR/oPs=; b=vIaD/ECo8hv9qbM/yprmY1Eo/cMP1YLnwrbUDNwx+lsurEwdtUx+Skir9eOGGvHgof /dLaQQ/xAykPmQEOOIWuahfp2v0dLTIx7bf7AAuls9nH4VtFHLqbGbdFj+NUn9j/S+UF uetXIwBoXA518wAWpBFnWUVYsyeMeXFZWlzJg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=C0R62Et36NahW6oQa94dz7uF7omyCaGdzvwpCV5jSFQl/Vr9I2I9FODXub5dIM8bks DxwrYqtxhed/0q319ZxBSZ2npXbOTwFcFD2hsiQIqdnfMKGUBP2hASV00Q6iFl1GnU0I 4pB0mIOaTy96txsA4EiaMEy/lZCdSFAJ7vj3E= Received: by 10.100.239.17 with SMTP id m17mr1626828anh.137.1283661261368; Sat, 04 Sep 2010 21:34:21 -0700 (PDT) Received: from [192.168.1.5] ([186.125.42.254]) by mx.google.com with ESMTPS id w10sm6185817ank.14.2010.09.04.21.34.20 (version=SSLv3 cipher=RC4-MD5); Sat, 04 Sep 2010 21:34:20 -0700 (PDT) Message-ID: <4C831DC8.40802@gmail.com> Date: Sun, 05 Sep 2010 01:34:16 -0300 From: Gonzalo Nemmi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: hackers@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: Following on =?iso-8859-1?q?Ed=B4s_simple_and_hopefully_usable_Fr?= =?iso-8859-1?q?eeBSD_live_CD_=2E=2E=2E?= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2010 05:03:14 -0000 Would it be possible to have "hybrid" FreeBSD live CD/DVDs (as seen on Mandriva Linux)? That is to say, would it be possible to have .iso images that could be just dumped on a USB stick and then boot from it to either run a liveFS or go stright for a disc1.iso or plain full dvd1.iso install? http://wiki.mandriva.com/en/Installing_Mandriva_Linux#Installation_from_a_USB_stick http://ftp.riken.jp/Linux/MandrivaLinux/official/iso/2010.0/mandriva-seed.sh http://ftp.riken.jp/Linux/MandrivaLinux/official/iso/2010.0/mandriva-seed-windows.zip I´ve tested mandriva´s liveCD (Mandriva ONE)from a USB stick and did two full installs (Mandriva Powerpack) using the same method and frankly: I found that having "hybrid" isos and a tool like "Mandriva Seed" (even as simple as it is ...) is incredibly handy ... Best Regards Gonzalo Nemmi From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 5 12:22:19 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0661E1065679 for ; Sun, 5 Sep 2010 12:22:19 +0000 (UTC) (envelope-from andymac@bullseye.apana.org.au) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by mx1.freebsd.org (Postfix) with ESMTP id 86A7D8FC13 for ; Sun, 5 Sep 2010 12:22:18 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmwFAGoig0x5LcmZ/2dsb2JhbACTbo0pcrdfhT0EhWWDcA Received: from ppp121-45-201-153.lns20.cbr1.internode.on.net (HELO bullseye.apana.org.au) ([121.45.201.153]) by ipmail06.adl2.internode.on.net with ESMTP; 05 Sep 2010 21:37:00 +0930 Received: from [192.168.63.10] (tenring.andymac.org [192.168.63.10]) by bullseye.apana.org.au (8.14.2/8.14.2) with ESMTP id o85C9YBx051042 for ; Sun, 5 Sep 2010 22:09:34 +1000 (EST) (envelope-from andymac@bullseye.andymac.org) Message-ID: <4C8383CD.7020500@bullseye.andymac.org> Date: Sun, 05 Sep 2010 21:49:33 +1000 From: Andrew MacIntyre User-Agent: Thunderbird 2.0.0.23 (OS/2/20090822) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4C7726F0.10001@erdgeist.org> <4C776025.8000609@gmail.com> <4C7776FA.5070601@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: disassembler X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2010 12:22:19 -0000 Aryeh Friedman wrote: > I should of said USB drive I just think of all USB drives as "flash" > drives... it is a Lacie external drive If this is a 3.5" drive with an external power supply, then the drive itself might be okay but the circuitry adapting it to the USB connector might have developed a problem - I not long ago had this happen to me, and the drive, when extracted (with some difficulty) from the case, could be accessed when connected directly to a P-ATA interface. -- ------------------------------------------------------------------------- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 5 20:37:57 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id CFF181065695; Sun, 5 Sep 2010 20:37:57 +0000 (UTC) Date: Sun, 5 Sep 2010 20:37:57 +0000 From: Alexander Best To: Dag-Erling =?iso-8859-15?Q?Sm=F8rgrav?= Message-ID: <20100905203757.GA11586@freebsd.org> References: <20100831180103.GA92584@freebsd.org> <86fwxt5ng1.fsf@ds4.des.no> <20100901222834.GA66517@freebsd.org> <864oe8mpga.fsf@ds4.des.no> <20100902114655.GA9071@freebsd.org> <8639tsl5q0.fsf@ds4.des.no> <20100902122348.GA38047@freebsd.org> <86pqwwjoef.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86pqwwjoef.fsf@ds4.des.no> Cc: freebsd-hackers@freebsd.org Subject: Re: expand_number() for fetch'es -B and -S switches X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2010 20:37:57 -0000 On Thu Sep 2 10, Dag-Erling Smørgrav wrote: > Alexander Best writes: > > the current maximum buffer limit of fetch(1) actually is around 1G. i > > think 1M is not enough, because if people are pulling data over fast > > lines they'll have almost constant disk writes. how about 100M then? > > ;) > > Large buffer sizes are *not* better, since fetch(1) will alternate > between filling the buffer and writing it to disk. The buffer should > not be too small, but it should not be too large either; the sweet spot > is somewhere around 128 kB. hmm. so if there should be a maximum buffer size of let's say 1 megabyte, there's no point really in having expand_number() then. so how about forgetting about expand_number() and simply introducing a maximum buffer size of 1 megabyte? everything higher than that will get reduced to 1 megabyte. just like if you want to burn a cd and specify a write speed of 1000 it simply gets reduced to someting like MAX_SPEED. also that would correspond with the semantics of the minimum buffer size. > > > on the other hand why have a maximum limit? if people want to have a > > buffer of 100 gigabyte why shouldn't they? it's their decision > > actually. > > Good point... although if they set it too high, either malloc(3) will > fail - if they're lucky - or fetch(1) will crash when the system runs > out of physical RAM and swap, and they'll have to start over. yeah. users might start using buffer sizes of a few gigabyte which will cause all kinds of problems. don't really wanna go there. > > DES > -- > Dag-Erling Smørgrav - des@des.no cheers. alex -- a13x From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 6 02:38:20 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6D1E10656BC for ; Mon, 6 Sep 2010 02:38:20 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id AB6CE8FC12 for ; Mon, 6 Sep 2010 02:38:20 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0L8A00700XVVEH00@smtpauth2.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Sun, 05 Sep 2010 20:38:19 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.10]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L8A003ATXVUHL10@smtpauth2.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Sun, 05 Sep 2010 20:38:18 -0500 (CDT) Date: Sun, 05 Sep 2010 20:38:17 -0500 From: Nathan Whitehorn To: freebsd-hackers@freebsd.org Message-id: <4C844609.9050505@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.10 X-Spam-PmxInfo: Server=avs-14, Version=5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.9.6.13015, SenderIP=76.210.68.10 X-Enigmail-Version: 1.0.1 User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100729 Thunderbird/3.0.6 Subject: UMA allocations from a specific physical range X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2010 02:38:21 -0000 PowerPC hypervisors typically provided a restricted range on memory when the MMU is disabled, as it is when initially handling exceptions. In order to restore virtual memory, the powerpc64 code needs to read a data structure called the SLB cache, which is currently allocated out of a UMA zone, and must be mapped into wired memory, ideally 1:1 physical->virtual address. Since this must be accessible in real mode, it must have a physical address in a certain range. I am trying to figure out the best way to do this. My first run at this code uses a custom UMA allocator that calls vm_phys_alloc_contig() to get a memory page. The trouble I have run into is that I cannot figure out a way to free the page. Marking the zone NOFREE is a bad solution, vm_page_free() panics the kernel due to inconsistent tracking of page wiring, and vm_phys_free_pages() causes panics in vm_page_alloc() later on ("page is not free"). What is the correct way to deallocate these pages? Or is there a different approach I should adopt? -Nathan From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 6 03:51:05 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DDC810656C1 for ; Mon, 6 Sep 2010 03:51:05 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id CFDFF8FC15 for ; Mon, 6 Sep 2010 03:51:04 +0000 (UTC) Received: by yxn35 with SMTP id 35so1634505yxn.13 for ; Sun, 05 Sep 2010 20:51:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=4AATZQjvsrm00l9IY48K/ixNoK+v2nBNYACNmyTdQtY=; b=UTUIqTQgOFpCcYUgw6d6OXMJot8x3RSTu6sLenJFlnRSwYXCbAYrpb4OKCmphstNpI C9S88kLFM9Wkd166RE5sBo9K+s5tWZJ51TJV1BbsjtylEQ+CRcm+1AeELgzXMJvRRIe+ Fp4xHtEKwp2ZEXBgFqLmIot31yftOQtEMsi1I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=wWIZwcnCiAScAR06NKAmdz6BpzfC8sPpKbVNae2LelfzFMRqs3rJ4oLWgkV2Hoqk1b SIZrHfMIKz0db5bkYhORgnTKfnUpdpRuv1FgxFEo8qpYiUR/AXjMv2FibYLGa05i/PiO x5vdDfSWO5Msp2ck646eQ484+PjfJiJOOmSso= MIME-Version: 1.0 Received: by 10.100.164.4 with SMTP id m4mr2490235ane.135.1283745063605; Sun, 05 Sep 2010 20:51:03 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.100.126.20 with HTTP; Sun, 5 Sep 2010 20:51:03 -0700 (PDT) In-Reply-To: <4C844609.9050505@freebsd.org> References: <4C844609.9050505@freebsd.org> Date: Mon, 6 Sep 2010 03:51:03 +0000 X-Google-Sender-Auth: POTI0Ml5ooT63vXo2uN3yuMMKfE Message-ID: From: mdf@FreeBSD.org To: Nathan Whitehorn Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: UMA allocations from a specific physical range X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2010 03:51:05 -0000 On Mon, Sep 6, 2010 at 1:38 AM, Nathan Whitehorn wrote: > PowerPC hypervisors typically provided a restricted range on memory when > the MMU is disabled, as it is when initially handling exceptions. In > order to restore virtual memory, the powerpc64 code needs to read a data > structure called the SLB cache, which is currently allocated out of a > UMA zone, and must be mapped into wired memory, ideally 1:1 > physical->virtual address. Since this must be accessible in real mode, > it must have a physical address in a certain range. I am trying to > figure out the best way to do this. > > My first run at this code uses a custom UMA allocator that calls > vm_phys_alloc_contig() to get a memory page. The trouble I have run into > is that I cannot figure out a way to free the page. Marking the zone > NOFREE is a bad solution, vm_page_free() panics the kernel due to > inconsistent tracking of page wiring, and vm_phys_free_pages() causes > panics in vm_page_alloc() later on ("page is not free"). What is the > correct way to deallocate these pages? Or is there a different approach > I should adopt? I assume this is for the SLB flih? What AIX did was to have a 1-1 simple esid to vsid translation for kernel addresses, reserve the first 16 SLB entries for various uses, including one for the current process's process private segment, and if the slb miss was on a process address we'd turn on translation and look up the answer, the tables holding the answer being in the process private segment effective address space so we wouldn't take another slb miss. This required one level deep recursion in the slb slih, in case there was a miss on kernel data with xlate on in the SLB slih. For historical reasons due to the per-process segment table for POWER3, we also had a one-page hashed lookup table per process that we stored the real address of in the process private segment, so the assembly code in the flih looked here before turning on MSR_DR IIRC. I was trying to find ways to kill this code when I left IBM, since we'd ended support for POWER3 a few years earlier. I haven't had the time to look at FreeBSD ppc64 sources; how large are the uma-allocated slb entries and what is stored in them? The struct and filename is sufficient, though I don't have convenient access to sources until Tuesday. V=R space is rather limited (well, depending on a lot of factors; for AIX on Power5 and later the hypervisor only gave us 128M, though for ppc64 on a Mac G4 I assume all of memory can be mapped V=R if desired) so it was best to find a non V=R solution if possible. Turning on translation in the flih after some setup and recursion stopping is one of the easier ways, and also has the advantage of not needing to either have separate code or macro access to data structures used in both V and R modes. Cheers, matthew From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 6 04:28:05 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25DB210656D5 for ; Mon, 6 Sep 2010 04:28:05 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id EBF268FC1E for ; Mon, 6 Sep 2010 04:28:04 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0L8B00M005QSCX00@smtpauth3.wiscmail.wisc.edu>; Sun, 05 Sep 2010 23:28:04 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.10]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L8B00JRP5QQU410@smtpauth3.wiscmail.wisc.edu>; Sun, 05 Sep 2010 23:28:03 -0500 (CDT) Date: Sun, 05 Sep 2010 23:28:02 -0500 From: Nathan Whitehorn In-reply-to: To: mdf@FreeBSD.org Message-id: <4C846DD2.4000507@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.10 X-Spam-PmxInfo: Server=avs-10, Version=5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.9.6.41815, SenderIP=76.210.68.10 X-Enigmail-Version: 1.0.1 References: <4C844609.9050505@freebsd.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100729 Thunderbird/3.0.6 Cc: freebsd-hackers@freebsd.org Subject: Re: UMA allocations from a specific physical range X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2010 04:28:05 -0000 On 09/05/10 22:51, mdf@FreeBSD.org wrote: > On Mon, Sep 6, 2010 at 1:38 AM, Nathan Whitehorn wrote: > >> PowerPC hypervisors typically provided a restricted range on memory when >> the MMU is disabled, as it is when initially handling exceptions. In >> order to restore virtual memory, the powerpc64 code needs to read a data >> structure called the SLB cache, which is currently allocated out of a >> UMA zone, and must be mapped into wired memory, ideally 1:1 >> physical->virtual address. Since this must be accessible in real mode, >> it must have a physical address in a certain range. I am trying to >> figure out the best way to do this. >> >> My first run at this code uses a custom UMA allocator that calls >> vm_phys_alloc_contig() to get a memory page. The trouble I have run into >> is that I cannot figure out a way to free the page. Marking the zone >> NOFREE is a bad solution, vm_page_free() panics the kernel due to >> inconsistent tracking of page wiring, and vm_phys_free_pages() causes >> panics in vm_page_alloc() later on ("page is not free"). What is the >> correct way to deallocate these pages? Or is there a different approach >> I should adopt? >> > I assume this is for the SLB flih? > > What AIX did was to have a 1-1 simple esid to vsid translation for > kernel addresses, reserve the first 16 SLB entries for various uses, > including one for the current process's process private segment, and > if the slb miss was on a process address we'd turn on translation and > look up the answer, the tables holding the answer being in the process > private segment effective address space so we wouldn't take another > slb miss. This required one level deep recursion in the slb slih, in > case there was a miss on kernel data with xlate on in the SLB slih. > Yes, that's correct. FreeBSD has the same 1-to-1 translation for the kernel, but the entire address space is switched out for user processes (no part of the kernel is mapped into user processes), so the code to load the user SLB entries has to be able to execute with the MMU off, lest it disappear underneath itself. > For historical reasons due to the per-process segment table for > POWER3, we also had a one-page hashed lookup table per process that we > stored the real address of in the process private segment, so the > assembly code in the flih looked here before turning on MSR_DR IIRC. > I was trying to find ways to kill this code when I left IBM, since > we'd ended support for POWER3 a few years earlier. > > I haven't had the time to look at FreeBSD ppc64 sources; how large are > the uma-allocated slb entries and what is stored in them? The struct > and filename is sufficient, though I don't have convenient access to > sources until Tuesday. > The entries are each 1 KB, and there is one for each pmap. Each consists of 64 16-byte SLBE/SLBV pairs. These buffers are just a carbon copy of what should be in the SLB after a context switch to that map. > V=R space is rather limited (well, depending on a lot of factors; for > AIX on Power5 and later the hypervisor only gave us 128M, though for > ppc64 on a Mac G4 I assume all of memory can be mapped V=R if desired) > so it was best to find a non V=R solution if possible. Turning on > translation in the flih after some setup and recursion stopping is one > of the easier ways, and also has the advantage of not needing to > either have separate code or macro access to data structures used in > both V and R modes. > On the PS3 (the target in this case), the hypervisor also limits us to 128 MB. The one and only kernel data structure that needs to be used in this mode is this SLB cache object, so I was hoping for a simple solution to just put them all in the real-mode accessible region. -Nathan From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 6 04:48:40 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06DD810656C9; Mon, 6 Sep 2010 04:48:40 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9F7E08FC14; Mon, 6 Sep 2010 04:48:39 +0000 (UTC) Received: by gwb15 with SMTP id 15so1673038gwb.13 for ; Sun, 05 Sep 2010 21:48:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=TrYr5VTbzb4a6a+Dd/NVJGORIWTMgbumwcO/sGBSfnw=; b=x028gy25PiFIoa20YR5pfEEONireK5XdgvD0TCcLuuUizy7OHRruAY+UpNsFqr+CVn q6qpb6dyI/P8rgkMYegLual2x1b6WBswSvzl7vIDijJOKZD4IFjetdNg9fm254Zqam/T Lusvubkowd3C1lCT7knU4oFFpe9sWHt+Y0K+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=YMx/K2BFbiTxn8cIySiI6WaxRm02417RQ4dUtxIl83HygK+dP8eEMFhw3rxS67+Sjg nPaMSCb78mwcTAJdfpvCDrzbAxIlpmj71DQFHHrcVUZ7mSxhhiOqDTbkxEpzY5pSY+s5 H1zrSpxkDlCUji7nyR9pL/L7sNqea+4s8gpAs= MIME-Version: 1.0 Received: by 10.101.171.39 with SMTP id y39mr520895ano.259.1283748518763; Sun, 05 Sep 2010 21:48:38 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.100.126.20 with HTTP; Sun, 5 Sep 2010 21:48:38 -0700 (PDT) In-Reply-To: <4C846DD2.4000507@freebsd.org> References: <4C844609.9050505@freebsd.org> <4C846DD2.4000507@freebsd.org> Date: Mon, 6 Sep 2010 04:48:38 +0000 X-Google-Sender-Auth: II0G9yNbg0VeRmRr03NKwS5ek4Q Message-ID: From: mdf@FreeBSD.org To: Nathan Whitehorn Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: UMA allocations from a specific physical range X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2010 04:48:40 -0000 On Mon, Sep 6, 2010 at 4:28 AM, Nathan Whitehorn w= rote: > On 09/05/10 22:51, mdf@FreeBSD.org wrote: >> On Mon, Sep 6, 2010 at 1:38 AM, Nathan Whitehorn wrote: >> >>> PowerPC hypervisors typically provided a restricted range on memory whe= n >>> the MMU is disabled, as it is when initially handling exceptions. In >>> order to restore virtual memory, the powerpc64 code needs to read a dat= a >>> structure called the SLB cache, which is currently allocated out of a >>> UMA zone, and must be mapped into wired memory, ideally 1:1 >>> physical->virtual address. Since this must be accessible in real mode, >>> it must have a physical address in a certain range. I am trying to >>> figure out the best way to do this. >>> >>> My first run at this code uses a custom UMA allocator that calls >>> vm_phys_alloc_contig() to get a memory page. The trouble I have run int= o >>> is that I cannot figure out a way to free the page. Marking the zone >>> NOFREE is a bad solution, vm_page_free() panics the kernel due to >>> inconsistent tracking of page wiring, and vm_phys_free_pages() causes >>> panics in vm_page_alloc() later on ("page is not free"). What is the >>> correct way to deallocate these pages? Or is there a different approach >>> I should adopt? >>> >> I assume this is for the SLB flih? >> >> What AIX did was to have a 1-1 simple esid to vsid translation for >> kernel addresses, reserve the first 16 SLB entries for various uses, >> including one for the current process's process private segment, and >> if the slb miss was on a process address we'd turn on translation and >> look up the answer, the tables holding the answer being in the process >> private segment effective address space so we wouldn't take another >> slb miss. =A0This required one level deep recursion in the slb slih, in >> case there was a miss on kernel data with xlate on in the SLB slih. >> > Yes, that's correct. FreeBSD has the same 1-to-1 translation for the > kernel, but the entire address space is switched out for user processes > (no part of the kernel is mapped into user processes), so the code to > load the user SLB entries has to be able to execute with the MMU off, > lest it disappear underneath itself. Okay. For AIX the kernel text/data in esid 0 was always in slb entry 0 (so it wasn't affected by slbia) and also was mapped into the process address space. So we had to be careful with KsKp bits to prevent access to anything the user couldn't see. The code for memcpy and friends was at fixed addresses in the kernel segment so the compiler knew to jump there, and there was also a user-readable _system_configuration struct. Even with no address sharing, the SLB flih could load entries for the kernel and turn on translation, but it would be trickier. >> For historical reasons due to the per-process segment table for >> POWER3, we also had a one-page hashed lookup table per process that we >> stored the real address of in the process private segment, so the >> assembly code in the flih looked here before turning on MSR_DR IIRC. >> I was trying to find ways to kill this code when I left IBM, since >> we'd ended support for POWER3 a few years earlier. >> >> I haven't had the time to look at FreeBSD ppc64 sources; how large are >> the uma-allocated slb entries and what is stored in them? =A0The struct >> and filename is sufficient, though I don't have convenient access to >> sources until Tuesday. >> > The entries are each 1 KB, and there is one for each pmap. Each consists > of 64 16-byte SLBE/SLBV pairs. These buffers are just a carbon copy of > what should be in the SLB after a context switch to that map. But if this is for the flih, the esid that was faulted on won't be in that struct, right? Aren't you trying to look up in some table to load an slb entry? >> V=3DR space is rather limited (well, depending on a lot of factors; for >> AIX on Power5 and later the hypervisor only gave us 128M, though for >> ppc64 on a Mac G4 I assume all of memory can be mapped V=3DR if desired) >> so it was best to find a non V=3DR solution if possible. =A0Turning on >> translation in the flih after some setup and recursion stopping is one >> of the easier ways, and also has the advantage of not needing to >> either have separate code or macro access to data structures used in >> both V and R modes. >> > On the PS3 (the target in this case), the hypervisor also limits us to > 128 MB. The one and only kernel data structure that needs to be used in > this mode is this SLB cache object, so I was hoping for a simple > solution to just put them all in the real-mode accessible region. Well, I assume if you're willing to use 4k then it should't be hard to allocate a whole page in the V=3DR region. Perhaps other useful data for the process could be added to this page? Admittedly, this is a bit of a digression. The internals of UMA always leave me confused, so I try to avoid thinking about it. :-) IIRC the memory from vm_phys_alloc_contig() can be released like any other page; the interface should just be fetching a specific page. How far off is the page wire count? I'm assuming it's hitting the assert that it's > 1? I think vm_page_free() is the right interface to free the page again, so the wire count being off presumably means someone else wired it on you; do you know what code did it? If no one else has a reference to the page anymore then setting the wire count to 1, while a hack, should be safe. Cheers, matthew From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 6 06:13:39 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FF0110656EC; Mon, 6 Sep 2010 06:13:39 +0000 (UTC) (envelope-from alan.l.cox@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id EEE098FC15; Mon, 6 Sep 2010 06:13:38 +0000 (UTC) Received: by gxk24 with SMTP id 24so1768534gxk.13 for ; Sun, 05 Sep 2010 23:13:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=6LbV4A5uVEuvtJQItBtYRLF1orAYjbPLFRzmnvxA4vQ=; b=JCiAt/l2wHMvE8T6p1c8Ea6mpOiNUVHZfOqEiiiV+5C5TLFVusu9O0tQgbshwdUpID gp2cmt5EzwfB1J7xoq/6rFAkq1U4RbVk8YMZnqpWEYdsiIrQOAhhN4EeXoMD14ajNLve cJQzasYRiwfrgo8HDH9Ad8yO24Fihg0Nj5l/o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=bXceiDjmGuXzvlFu1G/pnqps9y3y5tTIvd55JJJKCLWj5d4JtYHsx1qZAFyTdMOqjH qU9EX/uBzQhXp3cIUIu+v48wIFpYmrQesLLb7QtR2p82E4r1kY/sG0Zc/zOt6m+4jDDu G1sGoiEZyDTInjwGAd/PDqLNO/CHiiDw4qNY8= Received: by 10.151.41.4 with SMTP id t4mr792818ybj.116.1283752204286; Sun, 05 Sep 2010 22:50:04 -0700 (PDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) by mx.google.com with ESMTPS id x3sm3186028ybl.22.2010.09.05.22.50.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 05 Sep 2010 22:50:02 -0700 (PDT) Message-ID: <4C8480EF.7050700@gmail.com> Date: Mon, 06 Sep 2010 00:49:35 -0500 From: Alan Cox User-Agent: Thunderbird 2.0.0.24 (X11/20100725) MIME-Version: 1.0 To: mdf@FreeBSD.org References: <4C844609.9050505@freebsd.org> <4C846DD2.4000507@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Nathan Whitehorn Subject: Re: UMA allocations from a specific physical range X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alc@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2010 06:13:39 -0000 mdf@FreeBSD.org wrote: [snip] > IIRC the memory from vm_phys_alloc_contig() can be released like any > other page; the interface should just be fetching a specific page. > How far off is the page wire count? I'm assuming it's hitting the > assert that it's > 1? > > I think vm_page_free() is the right interface to free the page again, > so the wire count being off presumably means someone else wired it on > you; do you know what code did it? If no one else has a reference to > the page anymore then setting the wire count to 1, while a hack, > should be safe. > > Yes, vm_page_free() can be used to free a single page that was returned by vm_phys_alloc_contig(). Alan From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 7 01:22:44 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E22810656D6 for ; Tue, 7 Sep 2010 01:22:44 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id E757B8FC0A for ; Tue, 7 Sep 2010 01:22:43 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0L8C00E00RTV9T00@smtpauth3.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Mon, 06 Sep 2010 20:22:43 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.10]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L8C00615RTTZ350@smtpauth3.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Mon, 06 Sep 2010 20:22:42 -0500 (CDT) Date: Mon, 06 Sep 2010 20:22:41 -0500 From: Nathan Whitehorn To: freebsd-hackers@freebsd.org Message-id: <4C8593E1.5080000@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.10 X-Spam-PmxInfo: Server=avs-11, Version=5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.9.7.11515, SenderIP=76.210.68.10 X-Enigmail-Version: 1.0.1 User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100729 Thunderbird/3.0.6 Subject: PS3 livelock and pmap_remove() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2010 01:22:44 -0000 Now that my SLB allocation issue is solved, with help with Matthew and Alan, I have another VM puzzler. I have a simple program that tries to use all the memory on the system, which isn't very much on the PS3, so I use it to test swap as well. Shortly after it begins paging, the system locks up completely. I managed to duplicate this behavior on an emulator, and found out what it is actually doing. Somehow pmap_remove() is being called with arguments pmap_remove(userpmap, PAGE_SIZE, VM_MAXUSER_ADDRESS = USRSTACK). For powerpc64, VM_MAXUSER_ADDRESS is 0x7ffffffffffff000, so there are 10^15 pages to unmap in that range and it was busy taking until the end of time unmapping them all. Here's the trace from KDB: moea64_remove() pmap_remove() vm_daemon() fork_exit() fork_trampoline() ----end----- Does anyone have any idea why this is happening? Thanks, -Nathan From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 7 03:24:53 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9780E10656AB for ; Tue, 7 Sep 2010 03:24:53 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id 6BF168FC0A for ; Tue, 7 Sep 2010 03:24:53 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0L8C00700XHGAO00@smtpauth2.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Mon, 06 Sep 2010 22:24:52 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.10]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L8C005NWXHECS00@smtpauth2.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Mon, 06 Sep 2010 22:24:51 -0500 (CDT) Date: Mon, 06 Sep 2010 22:24:49 -0500 From: Nathan Whitehorn In-reply-to: <4C8593E1.5080000@freebsd.org> To: freebsd-hackers@freebsd.org Message-id: <4C85B081.3040100@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.10 X-Spam-PmxInfo: Server=avs-14, Version=5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.9.7.31215, SenderIP=76.210.68.10 X-Enigmail-Version: 1.0.1 References: <4C8593E1.5080000@freebsd.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100729 Thunderbird/3.0.6 Subject: Re: PS3 livelock and pmap_remove() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2010 03:24:53 -0000 On 09/06/10 20:22, Nathan Whitehorn wrote: > Now that my SLB allocation issue is solved, with help with Matthew and > Alan, I have another VM puzzler. > > I have a simple program that tries to use all the memory on the system, > which isn't very much on the PS3, so I use it to test swap as well. > Shortly after it begins paging, the system locks up completely. I > managed to duplicate this behavior on an emulator, and found out what it > is actually doing. Somehow pmap_remove() is being called with arguments > pmap_remove(userpmap, PAGE_SIZE, VM_MAXUSER_ADDRESS = USRSTACK). For > powerpc64, VM_MAXUSER_ADDRESS is 0x7ffffffffffff000, so there are 10^15 > pages to unmap in that range and it was busy taking until the end of > time unmapping them all. > > Here's the trace from KDB: > > moea64_remove() > pmap_remove() > vm_daemon() > fork_exit() > fork_trampoline() > ----end----- > > Does anyone have any idea why this is happening? > > The culprit here is lines 703-706 of vm/vm_pageout.c: if (desired == 0 && nothingwired) { pmap_remove(vm_map_pmap(map), vm_map_min(map), vm_map_max(map)); } It would be much better if it did this in sections, the way vm_map_delete does. I'll take a crack at this, though any suggestions for proper implementation would be appreciated. -nathan From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 7 14:29:44 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D190510656CA for ; Tue, 7 Sep 2010 14:29:44 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id A1FB08FC12 for ; Tue, 7 Sep 2010 14:29:44 +0000 (UTC) MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_9Kg2DhUa2PtRVOyOKbWdzw)" Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0L8D00A4US9BW600@smtpauth3.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Tue, 07 Sep 2010 09:29:35 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.10]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L8D0050WS969H70@smtpauth3.wiscmail.wisc.edu> for freebsd-hackers@freebsd.org; Tue, 07 Sep 2010 09:29:31 -0500 (CDT) Date: Tue, 07 Sep 2010 09:29:30 -0500 From: Nathan Whitehorn In-reply-to: <4C85B081.3040100@freebsd.org> To: freebsd-hackers@freebsd.org Message-id: <4C864C4A.2050600@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.10 X-Spam-PmxInfo: Server=avs-11, Version=5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.9.7.141814, SenderIP=76.210.68.10 X-Enigmail-Version: 1.0.1 References: <4C8593E1.5080000@freebsd.org> <4C85B081.3040100@freebsd.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100729 Thunderbird/3.0.6 Subject: Re: PS3 livelock and pmap_remove() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2010 14:29:45 -0000 This is a multi-part message in MIME format. --Boundary_(ID_9Kg2DhUa2PtRVOyOKbWdzw) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT On 09/06/10 22:24, Nathan Whitehorn wrote: > On 09/06/10 20:22, Nathan Whitehorn wrote: > >> Now that my SLB allocation issue is solved, with help with Matthew and >> Alan, I have another VM puzzler. >> >> I have a simple program that tries to use all the memory on the system, >> which isn't very much on the PS3, so I use it to test swap as well. >> Shortly after it begins paging, the system locks up completely. I >> managed to duplicate this behavior on an emulator, and found out what it >> is actually doing. Somehow pmap_remove() is being called with arguments >> pmap_remove(userpmap, PAGE_SIZE, VM_MAXUSER_ADDRESS = USRSTACK). For >> powerpc64, VM_MAXUSER_ADDRESS is 0x7ffffffffffff000, so there are 10^15 >> pages to unmap in that range and it was busy taking until the end of >> time unmapping them all. >> >> Here's the trace from KDB: >> >> moea64_remove() >> pmap_remove() >> vm_daemon() >> fork_exit() >> fork_trampoline() >> ----end----- >> >> Does anyone have any idea why this is happening? >> >> >> > The culprit here is lines 703-706 of vm/vm_pageout.c: > > if (desired == 0 && nothingwired) { > pmap_remove(vm_map_pmap(map), vm_map_min(map), > vm_map_max(map)); > } > > It would be much better if it did this in sections, the way > vm_map_delete does. I'll take a crack at this, though any suggestions > for proper implementation would be appreciated. > -nathan > I've attached a patch that reimplements this by unmapping each map_entry separately, which solves the problem on PowerPC and I believe is functionally equivalent. My PS3 successfully completes a buildworld with this patch. Are there any objections to me committing it? -Nathan --Boundary_(ID_9Kg2DhUa2PtRVOyOKbWdzw) Content-type: text/plain; name=vm-pageout.diff Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=vm-pageout.diff Index: vm/vm_pageout.c =================================================================== --- vm/vm_pageout.c (revision 212277) +++ vm/vm_pageout.c (working copy) @@ -701,8 +701,11 @@ * table pages. */ if (desired == 0 && nothingwired) { - pmap_remove(vm_map_pmap(map), vm_map_min(map), - vm_map_max(map)); + tmpe = map->header.next; + while (tmpe != &map->header) { + pmap_remove(vm_map_pmap(map), tmpe->start, tmpe->end); + tmpe = tmpe->next; + } } vm_map_unlock(map); } --Boundary_(ID_9Kg2DhUa2PtRVOyOKbWdzw)-- From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 8 09:27:21 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3BE010656A6; Wed, 8 Sep 2010 09:27:21 +0000 (UTC) (envelope-from giovanni.trematerra@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 19B008FC12; Wed, 8 Sep 2010 09:27:20 +0000 (UTC) Received: by wyb33 with SMTP id 33so8265354wyb.13 for ; Wed, 08 Sep 2010 02:27:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=r4GhfEUrg748Zk40qixJw4knaFOPjJZgmOItzNZBpf4=; b=GCi4t/JfHqaM3GYyeQxWGihZMs0xq47OK6Sam7I2/uwCIuOgjwUs9/6t/11+t4hp5M RqEP+c6Clgt3LeZpg3fxRQ+hUOpUpurerHg7sazHcRyJ0eUOrZVuf57EDhHDZ28MSpQD l6jS441eMN7IKZh000ZSUse91tHphylLJi+us= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=FyyXdYlRcppn+qOjbZwusg5zotmuWk9tziO9q6DMExTjL7Im10TOTjMoQqWyjyODac dCm8YeTrp2xP/Rs0m6+xwaGXcUWg5Y5gJL4RWFcY3/sL+R1wx2TJ6mLhsLESS1BiBmkT stShGYa1lvKN5KWING6yOYa/KHCiNgFbgxXoI= MIME-Version: 1.0 Received: by 10.227.44.6 with SMTP id y6mr6792wbe.17.1283936693072; Wed, 08 Sep 2010 02:04:53 -0700 (PDT) Sender: giovanni.trematerra@gmail.com Received: by 10.227.135.210 with HTTP; Wed, 8 Sep 2010 02:04:52 -0700 (PDT) In-Reply-To: <20100831232913.GA8129@phemt.homenet.telecomitalia.it.lan> References: <201008310753.49567.jhb@freebsd.org> <20100831232913.GA8129@phemt.homenet.telecomitalia.it.lan> Date: Wed, 8 Sep 2010 11:04:52 +0200 X-Google-Sender-Auth: vDwfveCEz9tiTKQVZUIiU0U3jbQ Message-ID: From: Giovanni Trematerra To: Davide Italiano Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Attilio Rao , freebsd-hackers@freebsd.org, glen.j.barber@gmail.com, Garrett Cooper Subject: Re: System freezes unexpectly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 09:27:21 -0000 On Wed, Sep 1, 2010 at 1:29 AM, Davide Italiano wrote: > On 31/08/10 07:53, John Baldwin wrote: >> On Monday, August 30, 2010 12:45:40 pm Garrett Cooper wrote: >> > On Mon, Aug 30, 2010 at 9:24 AM, Davide Italiano >> > wrote: >> > > removing ~/.mozilla works fine. I think that problem's related to >> > > add-on Xmarks I've been installer or to "Restore session" >> > > functionality >> > >> > It would have been interesting to capture what `froze' the machine, in >> > particular because it could have been a valuable bug for either >> > Mozilla to capture and fix, or for us to capture and fix. Unless your >> > machine doesn't meet the hardware requirements, I don't see a reason >> > why a userland application should lock up a system. >> > >> > There are other ways you can debug this further, using -safe-mode as a >> > next step, then choose to not restore the last session (which is >> > available from within the javascript settings file -- nsPrefs.js?). >> >> If only firefox is frozen, then you can always ssh in from another machi= ne and >> use top/ps, etc., or even gdb on the firefox process itself. >> >> -- >> John Baldwin >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.or= g" > > I tried to ssh from another machine or ping but I can't perform this oper= ation (hostname lookup failure). > I also noticed that the cause of the problem is pretty surely Xmarks. So,= if I remove ~/.mozilla firefox3 works again. When I reinstall Xmarks the s= ystem freezes. > Attilio Rao (rookie), an italian kernel developer suggest me to recompile= the kernel using the options, KDB, DDB, GDB, KDB_UNATTENDED (in particular= the last one, that reboot the machine if a panic occurs), but I didn't obt= ain nothin' useful, because isn't a panic (the machine doesn't reboot) neit= her dmesg is more verbose about the problem. I also tried to recompile fire= fox from ports w/ DEBUG flag enable, but I don't see anythin' good launchin= g firefox from xterm. > If I'm not wrong Xmarks firefox add-on hasn't a native FreeBSD port so perhaps the issue lies into linuxator. -- Gianni From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 8 09:41:27 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A6A610657C2; Wed, 8 Sep 2010 09:41:27 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 59B218FC1A; Wed, 8 Sep 2010 09:41:27 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 305731FFC34; Wed, 8 Sep 2010 09:41:26 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 06DC78457A; Wed, 8 Sep 2010 11:41:25 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Alexander Best References: <20100831180103.GA92584@freebsd.org> <86fwxt5ng1.fsf@ds4.des.no> <20100901222834.GA66517@freebsd.org> <864oe8mpga.fsf@ds4.des.no> <20100902114655.GA9071@freebsd.org> <8639tsl5q0.fsf@ds4.des.no> <20100902122348.GA38047@freebsd.org> <86pqwwjoef.fsf@ds4.des.no> <20100905203757.GA11586@freebsd.org> Date: Wed, 08 Sep 2010 11:41:25 +0200 In-Reply-To: <20100905203757.GA11586@freebsd.org> (Alexander Best's message of "Sun, 5 Sep 2010 20:37:57 +0000") Message-ID: <86r5h4shbu.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: expand_number() for fetch'es -B and -S switches X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 09:41:27 -0000 Alexander Best writes: > so how about forgetting about expand_number() and simply introducing a > maximum buffer size of 1 megabyte? so how about just leaving the code alone? :) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 8 10:50:50 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 435F810656F1; Wed, 8 Sep 2010 10:50:50 +0000 (UTC) Date: Wed, 8 Sep 2010 10:50:50 +0000 From: Alexander Best To: Dag-Erling =?iso-8859-15?Q?Sm=F8rgrav?= Message-ID: <20100908105050.GA4892@freebsd.org> References: <20100831180103.GA92584@freebsd.org> <86fwxt5ng1.fsf@ds4.des.no> <20100901222834.GA66517@freebsd.org> <864oe8mpga.fsf@ds4.des.no> <20100902114655.GA9071@freebsd.org> <8639tsl5q0.fsf@ds4.des.no> <20100902122348.GA38047@freebsd.org> <86pqwwjoef.fsf@ds4.des.no> <20100905203757.GA11586@freebsd.org> <86r5h4shbu.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86r5h4shbu.fsf@ds4.des.no> Cc: freebsd-hackers@freebsd.org Subject: Re: expand_number() for fetch'es -B and -S switches X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 10:50:50 -0000 On Wed Sep 8 10, Dag-Erling Smørgrav wrote: > Alexander Best writes: > > so how about forgetting about expand_number() and simply introducing a > > maximum buffer size of 1 megabyte? > > so how about just leaving the code alone? :) i thought you wanted to have a maximum buffer size of 1MB in fetch? right now -B can be any value and it's quite easy to trigger ENOMEM. cheers. alex > > DES > -- > Dag-Erling Smørgrav - des@des.no -- a13x From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 8 11:48:51 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DFF3106566C; Wed, 8 Sep 2010 11:48:51 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id C08988FC08; Wed, 8 Sep 2010 11:48:50 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 016171FFC36; Wed, 8 Sep 2010 11:48:49 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id BA3F6844EB; Wed, 8 Sep 2010 13:48:49 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Alexander Best References: <20100831180103.GA92584@freebsd.org> <86fwxt5ng1.fsf@ds4.des.no> <20100901222834.GA66517@freebsd.org> <864oe8mpga.fsf@ds4.des.no> <20100902114655.GA9071@freebsd.org> <8639tsl5q0.fsf@ds4.des.no> <20100902122348.GA38047@freebsd.org> <86pqwwjoef.fsf@ds4.des.no> <20100905203757.GA11586@freebsd.org> <86r5h4shbu.fsf@ds4.des.no> <20100908105050.GA4892@freebsd.org> Date: Wed, 08 Sep 2010 13:48:49 +0200 In-Reply-To: <20100908105050.GA4892@freebsd.org> (Alexander Best's message of "Wed, 8 Sep 2010 10:50:50 +0000") Message-ID: <8662ygihge.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: expand_number() for fetch'es -B and -S switches X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 11:48:51 -0000 Alexander Best writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Alexander Best writes: > > > so how about forgetting about expand_number() and simply > > > introducing a maximum buffer size of 1 megabyte? > > so how about just leaving the code alone? :) > i thought you wanted to have a maximum buffer size of 1MB in fetch? Yes, I was just commenting on the highly roundabout way we followed only to end up almost at the status quo. > right now -B can be any value and it's quite easy to trigger ENOMEM. "don't do that, then!" My suggestion is that if you're going to change it at all, use expand_number() *and* limit it to 1 MB. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 8 13:43:50 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 293BF10656E6; Wed, 8 Sep 2010 13:43:50 +0000 (UTC) Date: Wed, 8 Sep 2010 13:43:50 +0000 From: Alexander Best To: Dag-Erling =?iso-8859-15?Q?Sm=F8rgrav?= Message-ID: <20100908134350.GA34547@freebsd.org> References: <20100901222834.GA66517@freebsd.org> <864oe8mpga.fsf@ds4.des.no> <20100902114655.GA9071@freebsd.org> <8639tsl5q0.fsf@ds4.des.no> <20100902122348.GA38047@freebsd.org> <86pqwwjoef.fsf@ds4.des.no> <20100905203757.GA11586@freebsd.org> <86r5h4shbu.fsf@ds4.des.no> <20100908105050.GA4892@freebsd.org> <8662ygihge.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8662ygihge.fsf@ds4.des.no> Cc: freebsd-hackers@freebsd.org Subject: Re: expand_number() for fetch'es -B and -S switches X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 13:43:50 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Wed Sep 8 10, Dag-Erling Smørgrav wrote: > Alexander Best writes: > > Dag-Erling Smørgrav writes: > > > Alexander Best writes: > > > > so how about forgetting about expand_number() and simply > > > > introducing a maximum buffer size of 1 megabyte? > > > so how about just leaving the code alone? :) > > i thought you wanted to have a maximum buffer size of 1MB in fetch? > > Yes, I was just commenting on the highly roundabout way we followed only > to end up almost at the status quo. > > > right now -B can be any value and it's quite easy to trigger ENOMEM. > > "don't do that, then!" > > My suggestion is that if you're going to change it at all, use > expand_number() *and* limit it to 1 MB. hmmm...i guess it's best to leave it as it is now, because: 1) it's not really worth adding expand_number(), if the limit is 1m. the difference between typing '-B 1m' and '-B 1048576' is rather minor. 2) adding a fetch(1) entry, telling the user that in fact he can use '-B 1g', but this get's silently reduced to 1m would make things more complicated. since, as you pointed out, using a buffer > 1m isn't going to improve anything, there's no point in making it easier for the user to use higher values than this (i.e. by introducing expand_number()). sorry for all the hassle. ;) ps: you might still want to consider adding the attached patch, which makes it more apparent that the -S switch causes problems. `fetch -B 10000 -S 145l86` e.g. will output: "fetch: invalid size (145l86)", however the user might not now which of the switches caused 'fetch' to fail. cheers. alex > > DES > -- > Dag-Erling Smørgrav - des@des.no -- a13x --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="fetch.diff" diff --git a/usr.bin/fetch/fetch.c b/usr.bin/fetch/fetch.c index 7553bd8..852e948 100644 --- a/usr.bin/fetch/fetch.c +++ b/usr.bin/fetch/fetch.c @@ -842,7 +842,7 @@ main(int argc, char *argv[]) case 'S': S_size = (off_t)strtol(optarg, &end, 10); if (*optarg == '\0' || *end != '\0') - errx(1, "invalid size (%s)", optarg); + errx(1, "invalid file size (%s)", optarg); break; case 's': s_flag = 1; --k+w/mQv8wyuph6w0-- From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 8 18:42:48 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C57210656AE; Wed, 8 Sep 2010 18:42:48 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1A2238FC12; Wed, 8 Sep 2010 18:42:47 +0000 (UTC) Received: by elvis.mu.org (Postfix, from userid 1192) id 121AD1A4008; Wed, 8 Sep 2010 11:26:05 -0700 (PDT) Date: Wed, 8 Sep 2010 11:26:05 -0700 From: Alfred Perlstein To: sbruno@freebsd.org Message-ID: <20100908182605.GI69795@elvis.mu.org> References: <1277475474.2411.4.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1277475474.2411.4.camel@localhost.localdomain> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers Subject: Re: What is the exected behavior with the NMI button? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 18:42:48 -0000 * Sean Bruno [100625 07:18] wrote: > While trying to get a deadlock sorted out in the GPROF code, I attempted > to use this fancy shmancy NMI button on my Dell server. > > I noted that, not unlike the goggles, it did nothing once the system was > deadlocked. I noted that when the system was running normally, an NMI > log message would be spewed to the console. > > What is supposed to happen in these two cases when we toggle the NMI > button? If you have DDB in kernel and machdep.panic_on_nmi: 1 machdep.kdb_on_nmi: 1 are set, you should get debugger. -Alfred > > Sean > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- - Alfred Perlstein .- AMA, VMOA #5191, 03 vmax, 92 gs500, 85 ch250, 07 zx10 .- FreeBSD committer From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 03:27:33 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 684E7106566C for ; Fri, 10 Sep 2010 03:27:33 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7E1B98FC12 for ; Fri, 10 Sep 2010 03:27:32 +0000 (UTC) Received: by iwn34 with SMTP id 34so2025032iwn.13 for ; Thu, 09 Sep 2010 20:27:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=lBUTGe2mxKOE8PCxz7QRuoVP2jWiQk/BSfthLazROfc=; b=FqS3JKInobiJ4Lpp4yKXO5Zlg/sje8MHIYpgJd9eLjEjtwLZb884bYhAvls/fYAOxc 338cTHl+0fA85dp+AJiSRw/zqbAx/r0P/Lc0I2n5NalTUjPVhq8tOAEgFCM75nKhJk4+ Y/uEJk+rdJZF9e/1tnSsOJo+84i4g8GN3IRIM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=yFqWRHaAlVr0byzAtQW1Zf0Sznbs2Ss432VOQdKrJDKHPgy6RsU7ITJVg6M6xheaao X+fXwux8sBcpoChQimUU0FCBUBpDWVzcbb3DVZHnDxYEVMEvxoYY8/TIOAfOBCDwXmpH evd/DgHD2K3WSVkvC7N5+8CFWLLz32c6rS4qk= MIME-Version: 1.0 Received: by 10.231.31.135 with SMTP id y7mr184955ibc.139.1284089251864; Thu, 09 Sep 2010 20:27:31 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Thu, 9 Sep 2010 20:27:31 -0700 (PDT) Date: Thu, 9 Sep 2010 23:27:31 -0400 Message-ID: From: Aryeh Friedman To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 03:27:33 -0000 I have a directory that must not exist on logout and rm -rf is not sufficent to do it because the contents need to be processed by our version control system. The real life scenario is our version control system stores the repo for a given project encrypted but for techinical reasons it needs to keep the checkouted files in plain text (they are all in the same dir) and I want to *NEVER* have the plain text checkouted files in my dir when I logout, *BUT* instead of just deleting it I need to check them in... so how do I make my .logout so if the file exists it will not exit and give a error saying that dir is still there? (minor but unimportant side effect of the version control system is the dir will have a different name everytime it is made but always the same prefix) From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 03:34:50 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B9C0106566C for ; Fri, 10 Sep 2010 03:34:50 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id D84CB8FC22 for ; Fri, 10 Sep 2010 03:34:49 +0000 (UTC) Received: (qmail 55475 invoked by uid 1000); 10 Sep 2010 03:34:49 -0000 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Fri, 10 Sep 2010 15:34:45 +1200 (NZST) From: Atom Smasher In-Reply-To: Message-ID: <1009101529500.2000@smasher> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: To: Aryeh Friedman X-POM: The Moon is Waxing Crescent (5% of Full) X-Hashcash: 1:20:1009100334:aryeh.friedman@gmail.com::QeAKxPL9/O91pua9:000000000 0000000000000000000000006k2G X-Hashcash: 1:20:1009100334:freebsd-hackers@freebsd.org::fGKwi8nFuYMYRb0u:000000 0000000000000000000000009sUm Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 03:34:50 -0000 On Thu, 9 Sep 2010, Aryeh Friedman wrote: > I have a directory that must not exist on logout and rm -rf is not > sufficent to do it because the contents need to be processed by our > version control system. ===================== what i would do... make an alias or function of "logout" and/or "exit" in the init file that's parsed when the shell starts. alias it to a script or assign it to a function that does what you need. if your shell supports logging out with ^D (or any other keybinding) then the details may be shell-specific, but the idea would be to either disable it, or bind it to the script. -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." -- George Bernard Shaw From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 07:41:27 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D262C1065670 for ; Fri, 10 Sep 2010 07:41:27 +0000 (UTC) (envelope-from thespin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 983658FC0C for ; Fri, 10 Sep 2010 07:41:27 +0000 (UTC) Received: by iwn34 with SMTP id 34so2235944iwn.13 for ; Fri, 10 Sep 2010 00:41:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bMc3u6SqyBKBeHGAodyOtz/qXsYJjUYGfE4JXa9WmkI=; b=FM6nO2vb4UPgnNM0n+AgvjYp9W0YdCO/LoUslIaOO9givIJAWXpQwMwlc/PDr64x31 KWqWJjJDKR4zFRzPe44D5ATDsRmjsE9rm+F49K+dvYmAPCtZ7fBxmjHg0EA7iH5Kdn1s QbZCcItXvx7vEvBTI4PaLf6Vs28vL+iUgGVt8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=s4ZokGYD62Eq9EZG3LtGNth76EcvsaNf4h6puQD5otXtZXnA4j4dRmbPOBY4H1cCcE QIpj0NpckhzEDA7aOvuInaEGg7587CRI+bcRqSWKN/tXqvWRaLQ2cwb//EOGmDf0psKz rXIC9FoM/UxMB+jwt2cnfIDW7/HsDVRxO8NSM= MIME-Version: 1.0 Received: by 10.231.171.18 with SMTP id f18mr591628ibz.9.1284102880029; Fri, 10 Sep 2010 00:14:40 -0700 (PDT) Received: by 10.231.13.73 with HTTP; Fri, 10 Sep 2010 00:14:39 -0700 (PDT) In-Reply-To: <1009101529500.2000@smasher> References: <1009101529500.2000@smasher> Date: Fri, 10 Sep 2010 00:14:39 -0700 Message-ID: From: Evan Geller To: Atom Smasher Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Aryeh Friedman Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 07:41:27 -0000 Perhaps you could write something to wrap your shell... basically you could set your login shell to this wrapper. First thing the wrapper would do is exec and wait on the shell, and when the shell exits, check what needs to be checked, and should any of these checks fail, respawn the shell and dump the user back into their login shell. That way you can't neglect any funky corner cases of the shell exiting... the shell exits, the checks happen. In this example, the user is forced to exit 3 times. The experience is pretty seemless, the only issue is that the user will lose their environment after failing and ending up back in the new respawned shell, but I don't see how this would be an issue if the user is hastefully logging out. shell-A$ for i in 1 2 3; do bash; echo poop; done child-1-of-A$ exit exit poop child-2-of-A$ exit exit poop child-3-of-A$ exit exit poop shell-A$ exit exit parent-of-A% exit E On Thu, Sep 9, 2010 at 8:34 PM, Atom Smasher wrote: > On Thu, 9 Sep 2010, Aryeh Friedman wrote: > >> I have a directory that must not exist on logout and rm -rf is not >> sufficent to do it because the contents need to be processed by our vers= ion >> control system. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > what i would do... make an alias or function of "logout" and/or "exit" in > the init file that's parsed when the shell starts. alias it to a script o= r > assign it to a function that does what you need. > > if your shell supports logging out with ^D (or any other keybinding) then > the details may be shell-specific, but the idea would be to either disabl= e > it, or bind it to the script. > > > -- > =A0 =A0 =A0 =A0...atom > > =A0________________________ > =A0http://atom.smasher.org/ > =A0762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 > =A0------------------------------------------------- > > =A0 =A0 =A0 =A0"The reasonable man adapts himself to the world; the > =A0 =A0 =A0 =A0 unreasonable one persists in trying to adapt the world to > =A0 =A0 =A0 =A0 himself. Therefore all progress depends on the > =A0 =A0 =A0 =A0 unreasonable man." > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0-- George Bernard Shaw > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > --=20 --- Evan Geller thespin@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 11:43:32 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C9CB1065694 for ; Fri, 10 Sep 2010 11:43:32 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id DA7FA8FC15 for ; Fri, 10 Sep 2010 11:43:31 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ou20w-0003vW-EZ for freebsd-hackers@freebsd.org; Fri, 10 Sep 2010 13:43:30 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 10 Sep 2010 13:43:30 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 10 Sep 2010 13:43:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Fri, 10 Sep 2010 13:43:22 +0200 Lines: 30 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100518 Thunderbird/3.0.4 In-Reply-To: X-Enigmail-Version: 1.0.1 Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 11:43:32 -0000 On 09/10/10 05:27, Aryeh Friedman wrote: > I have a directory that must not exist on logout and rm -rf is not > sufficent to do it because the contents need to be processed by our > version control system. The real life scenario is our version > control system stores the repo for a given project encrypted but for > techinical reasons it needs to keep the checkouted files in plain text > (they are all in the same dir) and I want to *NEVER* have the plain > text checkouted files in my dir when I logout, *BUT* instead of just > deleting it I need to check them in... so how do I make my .logout so > if the file exists it will not exit and give a error saying that dir > is still there? (minor but unimportant side effect of the version > control system is the dir will have a different name everytime it is > made but always the same prefix) Have you thought about what should happen if for example, the login session is forcefully terminated by either of: 1) power outage of the server 2) power outage on the client 3) network problems (ssh or TCP connection drop) 4) administrative command (e.g. root executes "killall $shell") ? I don't think there is a way to protect from all of those, so any effort in protecting from only part of the problem looks useless. On the other hand, if partial solutions satisfy your requirements, maybe you can do something with http://glebkurtsou.blogspot.com/search/label/pefs . From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 12:11:40 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1DFD10656A7 for ; Fri, 10 Sep 2010 12:11:40 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 55D2C8FC12 for ; Fri, 10 Sep 2010 12:11:38 +0000 (UTC) Received: (qmail 45614 invoked by uid 1000); 10 Sep 2010 12:11:37 -0000 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Sat, 11 Sep 2010 00:11:37 +1200 (NZST) From: Atom Smasher In-Reply-To: Message-ID: <1009110004520.2000@smasher> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: To: Ivan Voras X-POM: The Moon is Waxing Crescent (7% of Full) X-Hashcash: 1:20:1009101211:ivoras@freebsd.org::42x4J8mSW5t9PzQT:000000000000000 00000000000000000000000037jd X-Hashcash: 1:20:1009101211:freebsd-hackers@freebsd.org::Vh+w+txH1yRrnvSV:000000 0000000000000000000000002UOm Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 12:11:40 -0000 On Fri, 10 Sep 2010, Ivan Voras wrote: > 1) power outage of the server > 2) power outage on the client > 3) network problems (ssh or TCP connection drop) > 4) administrative command (e.g. root executes "killall $shell") > > ? > > I don't think there is a way to protect from all of those, so any effort > in protecting from only part of the problem looks useless. ======================== you forgot cosmic rays, nuclear war and zombie apocalypse, among other failure modes. *NOTHING* is capable of protecting against everything; a good solution will most always have pitfalls; as a sysadmin/engineer/manager one has to either accept the pitfalls or find a more acceptable solution, which usually means different pitfalls. that doesn't mean a given solution is useless. -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "I am committed to helping Ohio deliver its electoral votes to the president [Bush] next year" -- Walden O'Dell, CEO of Diebold August 2003 From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 13:51:57 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9268106564A for ; Fri, 10 Sep 2010 13:51:57 +0000 (UTC) (envelope-from freebsd-questions@pp.dyndns.biz) Received: from smtprelay-h31.telenor.se (smtprelay-h31.telenor.se [213.150.131.4]) by mx1.freebsd.org (Postfix) with ESMTP id 51DE38FC16 for ; Fri, 10 Sep 2010 13:51:57 +0000 (UTC) Received: from ipb1.telenor.se (ipb1.telenor.se [195.54.127.164]) by smtprelay-h31.telenor.se (Postfix) with ESMTP id 17A3AE8A45; Fri, 10 Sep 2010 15:21:44 +0200 (CEST) X-SENDER-IP: [85.226.59.55] X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak8wAF7NiUxV4js3PGdsb2JhbACDGJ4oDAEBAQE1LatHkVKBIoMndASNHA X-IronPort-AV: E=Sophos;i="4.56,346,1280700000"; d="scan'208";a="129037859" Received: from c-373be255.107-1-64736c10.cust.bredbandsbolaget.se (HELO gatekeeper.pp.dyndns.biz) ([85.226.59.55]) by ipb1.telenor.se with ESMTP; 10 Sep 2010 15:21:44 +0200 Received: from [192.168.69.67] (phobos [192.168.69.67]) by gatekeeper.pp.dyndns.biz (8.14.4/8.14.4) with ESMTP id o8ADLgAd036919; Fri, 10 Sep 2010 15:21:42 +0200 (CEST) (envelope-from freebsd-questions@pp.dyndns.biz) Message-ID: <4C8A30E6.5090009@pp.dyndns.biz> Date: Fri, 10 Sep 2010 15:21:42 +0200 From: =?UTF-8?B?TW9yZ2FuIFdlc3N0csO2bQ==?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.7) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.1 MIME-Version: 1.0 To: FreeBSD Questions References: <4C8825E7.5080000@pp.dyndns.biz> <4C88E666.2030208@pp.dyndns.biz> In-Reply-To: <4C88E666.2030208@pp.dyndns.biz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Fri, 10 Sep 2010 15:24:51 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Any way to force AHCI mode on ICH8? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 13:51:58 -0000 On 2010-09-09 15:51, Morgan Wesström wrote: > On 2010-09-09 13:04, Ivan Voras wrote: >> On 09/09/10 02:10, Morgan Wesström wrote: >>> I run FreeBSD 8.1 on an old Asus P5B-VM motherboard with ICH8. Its AMI >>> BIOS lacks an option to enable AHCI mode. Intel's datasheet for the ICH8 >>> family specifies that this feature exists on the ICH8, and the option is >>> available in the BIOS for the identical (apart from form factor) P5B >>> motherboard. >>> >>> http://www.intel.com/Assets/PDF/datasheet/313056.pdf >>> >>> I've contacted Asus support for an updated BIOS but I don't have much >>> hope I will ever see one. Would it be possible to patch the FreeBSD >>> kernel to enable AHCI mode somehow during boot? >> >> You mean except adding: >> >> ahci_load="YES" >> >> to /boot/loader.conf ? > > Yes, I meant if there was a way to programmatically switch the ICH8 into > AHCI mode before loading ahci(4). The BIOS on this motherboard only > provides a "legacy" and an "enhanced" option for the SATA controller. > Neither option turns on AHCI mode so ata(4) attaches to the controller. > There's also a JMicron controller, providing an eSATA connector, on this > motherboard. It is AHCI compatible and ahci(4) attaches correctly to it. > It would've been nice to be able to use NCQ and hotplug on the other > SATA connectors too since the ICH8 has those features. > Cross-posting this to freebsd-hackers in case that is a more appropriate list. On page 486, in the Intel I/O Controller Hub 8 (ICH8) Datasheet, there's a description of the address map register that controls the SATA mode selection (SMS). http://www.intel.com/assets/pdf/datasheet/313056.pdf I quote note 7: "Software shall not manipulate SMS during runtime operation (i.e., the OS will not do this). The BIOS may choose to switch from one mode to another during POST." That note is probably there for a reason but what would life be without experimentation? :-) This is of course far beyond my level of expertise, but would it be possible to flip the necessary register bit very early on in the boot process to turn the SATA controller into AHCI mode? Has anyone done anything like this and what part of the kernel or boot loader would be most appropriate to patch? I have no problem applying a patch and recompiling what's needed if anyone could provide the necessary code. Regards Morgan From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 16:18:09 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9DF1106564A for ; Fri, 10 Sep 2010 16:18:09 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9C8518FC1F for ; Fri, 10 Sep 2010 16:18:09 +0000 (UTC) Received: by qwg5 with SMTP id 5so1744970qwg.13 for ; Fri, 10 Sep 2010 09:18:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=K7cmTSn2zEY2FYnSEViGDutWuJVqmSzplqXzLW3ED+U=; b=v9Mrv/XvaCrPsoL5TwwRdmIy3zjDH4Tcv6vuhms73yw+C4PaWzIMksMu7piNlRnqGx 5InmtnjEn+JP4hHRu1K5wRRvm3lm2WZjXNyIGa8ZZhIyVc16CioOLzZIPAt6/yrAIs8K wihXd2Fro3N+dJyehzt3hLQb4gM9KTFLZpH2A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=SEZzrIjXViSdLJQBAjxIrMysWkQieCMzXw9+mtuC48okpuEfj+lr6sWuzwQl+bTYqV y7WRFOLKlnWQQsrAtLKl+Y4COGckqZucrDofcQNz0SEH1/I6BcD3E+X4EZWACHtsovdM eaoaAxrdCaxDfSKRzT/Jndba3AFj9NRghtVv0= Received: by 10.224.96.146 with SMTP id h18mr551502qan.85.1284135486505; Fri, 10 Sep 2010 09:18:06 -0700 (PDT) MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.229.188.204 with HTTP; Fri, 10 Sep 2010 09:17:46 -0700 (PDT) In-Reply-To: <1009110004520.2000@smasher> References: <1009110004520.2000@smasher> From: Ivan Voras Date: Fri, 10 Sep 2010 18:17:46 +0200 X-Google-Sender-Auth: HZOcYKXUp7vLkWeOaBEXMz8_Xe8 Message-ID: To: Atom Smasher Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 16:18:10 -0000 On 10 September 2010 14:11, Atom Smasher wrote: > On Fri, 10 Sep 2010, Ivan Voras wrote: > >> 1) power outage of the server >> 2) power outage on the client >> 3) network problems (ssh or TCP connection drop) >> 4) administrative command (e.g. root executes "killall $shell") >> >> ? >> >> I don't think there is a way to protect from all of those, so any effort >> in protecting from only part of the problem looks useless. > > ======================== > > you forgot cosmic rays, nuclear war and zombie apocalypse, among other > failure modes. *NOTHING* is capable of protecting against everything; a good > solution will most always have pitfalls; as a sysadmin/engineer/manager one > has to either accept the pitfalls or find a more acceptable solution, which > usually means different pitfalls. that doesn't mean a given solution is > useless. On the other hand, things such as power outages, network blackouts and and root security compromises have been statistically shown to appear more often than zombie apocalypses, so I'd guess, though of course without absolute certainty, that those problem should be solved first :) Otherwise, it's just as effective as putting a README file in the home directory saying "please go away" :) From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 17:03:50 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73CAA106564A for ; Fri, 10 Sep 2010 17:03:50 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 059CC8FC0A for ; Fri, 10 Sep 2010 17:03:49 +0000 (UTC) Received: by fxm4 with SMTP id 4so2207648fxm.13 for ; Fri, 10 Sep 2010 10:03:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=2t7V+3GAWzdtmey+Zi1E3OlcZ8gbbc5XtPcSZXvD0w8=; b=otyQYb7c8ic5ivDOehD/tGZqo22PDbZVRJZ1iNDZ7by2WkA2a4T0q0qKJuXTvj5pcG hoySYNVezB3o5+WixCIhfuTayXW75IGWHQQIl00Lhv3Uy2/8ZhyWOKxj4vlIdHkImmfX YpC51b8CjpqQSwVhcwloVlwWBNNhpHIbr42Hk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=lWshpyqKkx9rLLGonlzSh5BKNs7JH/xRqjDf/XB139b63fTZZoZZTYmPAaStbCwkg9 BIRS7qX5fTi8zBLksgjOYQkpXWnP5/wvF3HpxmpEuI9dWvjFjvjkytQ3i3HyRNE2EBIt T+NSxwGGfaURpbfZgMNFbW+CG9fdIwfyXEGvk= MIME-Version: 1.0 Received: by 10.204.82.137 with SMTP id b9mr723240bkl.127.1284138228826; Fri, 10 Sep 2010 10:03:48 -0700 (PDT) Sender: yanegomi@gmail.com Received: by 10.204.113.79 with HTTP; Fri, 10 Sep 2010 10:03:48 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Sep 2010 10:03:48 -0700 X-Google-Sender-Auth: mYcIFoG_3qQq3bDhx9h28-GQRk0 Message-ID: From: Garrett Cooper To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 17:03:50 -0000 On Thu, Sep 9, 2010 at 8:27 PM, Aryeh Friedman w= rote: > I have a directory that must not exist on logout and rm -rf is not > sufficent to do it because the contents need to be processed by our > version control system. =A0 The real life scenario is our version > control system stores the repo for a given project encrypted but for > techinical reasons it needs to keep the checkouted files in plain text > (they are all in the same dir) and I want to *NEVER* have the plain > text checkouted files in my dir when I logout, *BUT* instead of just > deleting it I need to check them in... =A0so how do I make my .logout so > if the file exists it will not exit and give a error saying that dir > is still there? (minor but unimportant side effect of the version > control system is the dir will have a different name everytime it is > made but always the same prefix) This is probably a silly suggestion, but as I see it there is another option: a periodic script which goes and commits the files if the sessions go away (via crontab, or whatever). In particular, this would solve the problem if one of the sessions you had quit, but you had more than one session open to the machine. Of course if you didn't care about the contents of the files you could take a different approach and employ something similar in .login, but it doesn't sound like that's what you want to do either, and that wouldn't solve the multi-session problem... Cheers, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 17:09:22 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5956D106566B for ; Fri, 10 Sep 2010 17:09:22 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 004FD8FC08 for ; Fri, 10 Sep 2010 17:09:21 +0000 (UTC) Received: by gwb15 with SMTP id 15so1127567gwb.13 for ; Fri, 10 Sep 2010 10:09:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nhMCGlMLUxMIIypmo66FmS2qRMKzpzTYeVUYFCLTpBg=; b=EIZaOemOLuYo/jdDdlZv95ff53E0BgovrEKdSkBBJXVef5JCYo/jPWAQYOEail01oQ 3zuyw4NB0z3FMZMUO2m8IZG/MOvRublnddoKFoHhjtAh4msJOsIfRaPDBgr6p9HkZxUY PjTKo7NgFHZjZ1TjFpPnarRFHKqFbyK6ME7cg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sHN20mCf85lm+/T8kWAc0G23fAl5m2ElNk1rCh8CtlSgD+lVdw6iN9HG7eBbFcmpb0 DMQD0MK9MpqE5cMMY2jV8ave2i0NJdENCei6i8zcot31CqMY267NyAiN4WZ95hQVmjNV mxP6S31EDAuq9qaQss3+IEqG7ZFrjpXEi57WE= MIME-Version: 1.0 Received: by 10.151.82.14 with SMTP id j14mr1161296ybl.307.1284138561106; Fri, 10 Sep 2010 10:09:21 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Fri, 10 Sep 2010 10:09:20 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Sep 2010 13:09:20 -0400 Message-ID: From: Aryeh Friedman To: Garrett Cooper Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 17:09:22 -0000 The problem with that is our version control system (devel/aegis) purposely does not allow arbitary checkins... there is a whole procedure of you have to prove it compiles and passes at least one new test and then an other person needs to review the change and then and only then can it be checked in (and even here you need to repeat the proof of build and one new test [same as the ones above] to ensure that passing the test was not a fluke of your local environment)... this project is setup so I play all 3 roles on it but all three phases have to be formally done to check it in... btw the whole goal here (unlike non-atomic VCS's like SVN [git does it to some extent] the goal here is to make sure that nothing breaks the baseline [the fully tested and reviewed repo]). On Fri, Sep 10, 2010 at 1:03 PM, Garrett Cooper wrote= : > On Thu, Sep 9, 2010 at 8:27 PM, Aryeh Friedman = wrote: >> I have a directory that must not exist on logout and rm -rf is not >> sufficent to do it because the contents need to be processed by our >> version control system. =A0 The real life scenario is our version >> control system stores the repo for a given project encrypted but for >> techinical reasons it needs to keep the checkouted files in plain text >> (they are all in the same dir) and I want to *NEVER* have the plain >> text checkouted files in my dir when I logout, *BUT* instead of just >> deleting it I need to check them in... =A0so how do I make my .logout so >> if the file exists it will not exit and give a error saying that dir >> is still there? (minor but unimportant side effect of the version >> control system is the dir will have a different name everytime it is >> made but always the same prefix) > > =A0 =A0This is probably a silly suggestion, but as I see it there is > another option: a periodic script which goes and commits the files if > the sessions go away (via crontab, or whatever). In particular, this > would solve the problem if one of the sessions you had quit, but you > had more than one session open to the machine. > =A0 =A0Of course if you didn't care about the contents of the files you > could take a different approach and employ something similar in > .login, but it doesn't sound like that's what you want to do either, > and that wouldn't solve the multi-session problem... > Cheers, > -Garrett > From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 19:25:55 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3090D106566B for ; Fri, 10 Sep 2010 19:25:55 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 023108FC22 for ; Fri, 10 Sep 2010 19:25:54 +0000 (UTC) Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o8AJ75PY011071 for ; Fri, 10 Sep 2010 12:07:06 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4C8A81D9.5020905@rawbw.com> Date: Fri, 10 Sep 2010 12:07:05 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.12) Gecko/20100908 Thunderbird/3.0.7 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Why I can't trace linux process's childs with truss? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 19:25:55 -0000 I am trying to get the log of all system calls that skype makes with truss -f /usr/local/share/skype/skype For some reason the resulting log only has the leading process calls and nothing from it's 8 childs. Truss doesn't show any 'cloned' processes. Is this a bug in truss that it doesn't follow 'cloned' processes? Is there any workaround or other way I can debug skype? strace doesn't work on amd64. I am primarily interested why it can't read /dev/video0 device, created by webcamd. Yuri From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 19:46:01 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDC2E1065674 for ; Fri, 10 Sep 2010 19:46:01 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id A59B88FC1A for ; Fri, 10 Sep 2010 19:46:01 +0000 (UTC) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mx1.stack.nl (Postfix) with ESMTP id AE42C35A86D; Fri, 10 Sep 2010 21:46:00 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 1677) id A543F17267; Fri, 10 Sep 2010 21:46:00 +0200 (CEST) Date: Fri, 10 Sep 2010 21:46:00 +0200 From: Jilles Tjoelker To: Yuri Message-ID: <20100910194600.GB60815@stack.nl> References: <4C8A81D9.5020905@rawbw.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C8A81D9.5020905@rawbw.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-hackers@freebsd.org Subject: Re: Why I can't trace linux process's childs with truss? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 19:46:01 -0000 On Fri, Sep 10, 2010 at 12:07:05PM -0700, Yuri wrote: > I am trying to get the log of all system calls that skype makes with > truss -f /usr/local/share/skype/skype > For some reason the resulting log only has the leading process calls and > nothing from it's 8 childs. > Truss doesn't show any 'cloned' processes. Is this a bug in truss that > it doesn't follow 'cloned' processes? > Is there any workaround or other way I can debug skype? strace doesn't > work on amd64. > I am primarily interested why it can't read /dev/video0 device, created > by webcamd. Try using ktrace instead of truss. You will need devel/linux_kdump from ports to decode the resulting ktrace.out. Alternatively, if you're familiar with dtrace, you could try that. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 21:15:19 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EA4C106566B for ; Fri, 10 Sep 2010 21:15:19 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9FCBA8FC0C for ; Fri, 10 Sep 2010 21:15:18 +0000 (UTC) Received: by bwz20 with SMTP id 20so3123762bwz.13 for ; Fri, 10 Sep 2010 14:15:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=rd3ct2tLuKDkvV0q4g93aifrCVneQpWaQfurdziBHPo=; b=P/y8ByEhsp0Nn0FqPxe+Lf9agaPWowM++zg8WQDNO5xkJD+/UYoAn3g4wBjQ2J7L3P gG3PpzAD2mr1XOGz7tlOUr9Hp/K5oN5nmqP7aARgsQkwp5ieNFiTEcuhfcP4UALwCywM v4rug4Kq8KVGdOyYIP99FqmM17oj269Dv5NvM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=B3EbvpLHJaJPO7/XAgW8oa019w7unGCFuKKa3gP1FWmUM9oLJGbYobSRIhncIGaU5e r6HyRCc05JcPeikTmdkITlJvl2s20TOhV3Z1RtqY3qEjbLRSyFkvy7ScVcX5+ttJaGR5 3Xifzt9OAq18nDvUsei7l5wl7BPnLUCttiElg= MIME-Version: 1.0 Received: by 10.204.117.205 with SMTP id s13mr908224bkq.140.1284153317500; Fri, 10 Sep 2010 14:15:17 -0700 (PDT) Sender: yanegomi@gmail.com Received: by 10.204.113.79 with HTTP; Fri, 10 Sep 2010 14:15:17 -0700 (PDT) In-Reply-To: <4C8A81D9.5020905@rawbw.com> References: <4C8A81D9.5020905@rawbw.com> Date: Fri, 10 Sep 2010 14:15:17 -0700 X-Google-Sender-Auth: 6jAOn-_ormYm_XQ7ngvIvYFzWuU Message-ID: From: Garrett Cooper To: Yuri Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Why I can't trace linux process's childs with truss? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 21:15:19 -0000 On Fri, Sep 10, 2010 at 12:07 PM, Yuri wrote: > I am trying to get the log of all system calls that skype makes with truss > -f /usr/local/share/skype/skype > For some reason the resulting log only has the leading process calls and > nothing from it's 8 childs. > Truss doesn't show any 'cloned' processes. Is this a bug in truss that it > doesn't follow 'cloned' processes? > > Is there any workaround or other way I can debug skype? strace doesn't work > on amd64. > I am primarily interested why it can't read /dev/video0 device, created by > webcamd. It doesn't look like ptrace support has been added into the linuxulator, yet.. but I could be wrong. -Garrett From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 23:26:33 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4B451065672 for ; Fri, 10 Sep 2010 23:26:33 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 949E88FC1F for ; Fri, 10 Sep 2010 23:26:33 +0000 (UTC) Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta05.westchester.pa.mail.comcast.net with comcast id 5AN71f0021GhbT855BDHKG; Fri, 10 Sep 2010 23:13:17 +0000 Received: from comcast.net ([98.203.142.76]) by omta07.westchester.pa.mail.comcast.net with comcast id 5BDF1f0061f6R9u3TBDGPb; Fri, 10 Sep 2010 23:13:17 +0000 Received: by comcast.net (sSMTP sendmail emulation); Fri, 10 Sep 2010 16:13:13 -0700 Date: Fri, 10 Sep 2010 16:13:13 -0700 From: Charlie Kester To: freebsd-hackers@freebsd.org Message-ID: <20100910231313.GC6385@comcast.net> Mail-Followup-To: freebsd-hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Mailer: Mutt 1.5.20 X-Composer: Vim 7.2 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 23:26:33 -0000 On Fri 10 Sep 2010 at 10:09:20 PDT Aryeh Friedman wrote: >The problem with that is our version control system (devel/aegis) >purposely does not allow arbitary checkins... there is a whole >procedure of you have to prove it compiles and passes at least one new >test and then an other person needs to review the change and then and >only then can it be checked in (and even here you need to repeat the >proof of build and one new test [same as the ones above] to ensure >that passing the test was not a fluke of your local environment)... >this project is setup so I play all 3 roles on it but all three phases >have to be formally done to check it in... btw the whole goal here >(unlike non-atomic VCS's like SVN [git does it to some extent] the >goal here is to make sure that nothing breaks the baseline [the fully >tested and reviewed repo]). Is this something for your personal use, or are you looking for a solution that can be deployed throughout your company? If the latter, it seems to me that by making it more onerous to logout, you're simply going to be encouraging more people to leave their desks without logging out. Do you have a plan for securing their unattended but still logged-in workstations? Even if you do secure the workstations, what have you actually achieved? Somebody could still check out some files, go home for the weekend, then call in sick on Monday and Tuesday. The files are checked out all this time, and as far as I can see, the situation is no better than if he'd logged out Friday afternoon without checking in the files. You should probably think about these scenarios even if you were intending to implement this for your personal use only. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 10 23:55:27 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C24F1065673 for ; Fri, 10 Sep 2010 23:55:27 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC5F58FC15 for ; Fri, 10 Sep 2010 23:55:26 +0000 (UTC) Received: by vws7 with SMTP id 7so3539599vws.13 for ; Fri, 10 Sep 2010 16:55:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=80TK+wvFQ6ftw5aAlx1rBoVq4YwrGOmwm98NEO0uaC8=; b=CG2LvguGbyStdDoQVVrs1Y4WQf/jP9sQO7EpkFtUJ033RylmydR34f0yY6LkPCaDpm z/45/8JKd6xBOOOM002NWqiRCDJlkldMWLS7CyZwrUppfo8Mrh+4u4i3bY5fVaaN1r9e nYSGoVUEVwMBckheTrDMWVSNjUD/2tZRtzP68= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=U/U3Un3QsrqWg8ZgziVscwyOMlNZI+M5ES8VmeOQtQxuviuVbqjkZxUIh7ugl3ecn/ ZNiB5z1Ze5e6ASM2LEVNSlxzklyGiMjXDo5Q0DK5mQhVlzH5oIueGv/4fn3nT+LFTKME 3f6swkRLGNNt9K/JmY+9PxGC52C+Sw2LffzjE= Received: by 10.220.49.28 with SMTP id t28mr813897vcf.233.1284162926008; Fri, 10 Sep 2010 16:55:26 -0700 (PDT) Received: from kan.dnsalias.net (c-24-63-226-98.hsd1.ma.comcast.net [24.63.226.98]) by mx.google.com with ESMTPS id e18sm1609978vcs.21.2010.09.10.16.55.24 (version=SSLv3 cipher=RC4-MD5); Fri, 10 Sep 2010 16:55:24 -0700 (PDT) Date: Fri, 10 Sep 2010 19:55:18 -0400 From: Alexander Kabaev To: Garrett Cooper Message-ID: <20100910195518.4d35b3b1@kan.dnsalias.net> In-Reply-To: References: <4C8A81D9.5020905@rawbw.com> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/346t9.Yi/zk/5x/4F7CjMhz"; protocol="application/pgp-signature" Cc: Yuri , freebsd-hackers@freebsd.org Subject: Re: Why I can't trace linux process's childs with truss? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 23:55:27 -0000 --Sig_/346t9.Yi/zk/5x/4F7CjMhz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 10 Sep 2010 14:15:17 -0700 Garrett Cooper wrote: > On Fri, Sep 10, 2010 at 12:07 PM, Yuri wrote: > > I am trying to get the log of all system calls that skype makes > > with truss -f /usr/local/share/skype/skype > > For some reason the resulting log only has the leading process > > calls and nothing from it's 8 childs. > > Truss doesn't show any 'cloned' processes. Is this a bug in truss > > that it doesn't follow 'cloned' processes? > > > > Is there any workaround or other way I can debug skype? strace > > doesn't work on amd64. > > I am primarily interested why it can't read /dev/video0 device, > > created by webcamd. >=20 > It doesn't look like ptrace support has been added into the > linuxulator, yet.. but I could be wrong. > -Garrett You are. ptrace is supported by linuxulator for a while now. The originator problem is likely because he is trying truss, which is not Linux-aware. ktrace/linux_kdump combo should work. --=20 Alexander Kabaev --Sig_/346t9.Yi/zk/5x/4F7CjMhz Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iD8DBQFMisVqQ6z1jMm+XZYRAiC0AJ9CbSOMFm3VUgVkzJUqgdE4MbYFsQCfZ6zv lIw3GdWaaF9/rQQ4QmAItkI= =vmeG -----END PGP SIGNATURE----- --Sig_/346t9.Yi/zk/5x/4F7CjMhz-- From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 02:21:25 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7891F106566B for ; Sat, 11 Sep 2010 02:21:25 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 38E608FC0C for ; Sat, 11 Sep 2010 02:21:24 +0000 (UTC) Received: by iwn34 with SMTP id 34so3219490iwn.13 for ; Fri, 10 Sep 2010 19:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=TF2CmX86sATkLIyh2db0E0wnS9gS5T8q5ftsq1SXJ7I=; b=AJw4vtk5KLDYY+lc5isLcHfIiI9wlCiyHQ+/zJ1GkEzwqKNpHopzjXSO/qemrqoIJb AQfOwRD9gA+aBCupPZ2XoCUcjZwPUkUXNR+yKuF2LHQgGl9sEjt17upc20h34SWGZPJQ w0YvXyKqcmowf6zG9VfNIbXVjlUbYP5UmYF0U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=CAQ/xgJTUsL8PpwC7O4Yjbs8/IpC8FjSe9v4dbtbnardnUOVX7LAvUPdfm2zTCVhT0 NzcH99JcpW0jZrsTZe37alk7o1RgeTduxVqHvXDRL8+ru2rW5qPffEL8Rxb8Zb03IGMl 7F2CT6OT4fnv4MYviIKc0vvgCzWYyTfR7K5N8= Received: by 10.231.33.129 with SMTP id h1mr1608952ibd.140.1284171684484; Fri, 10 Sep 2010 19:21:24 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-137-20.dsl.klmzmi.sbcglobal.net [99.181.137.20]) by mx.google.com with ESMTPS id g31sm2950364ibh.10.2010.09.10.19.21.23 (version=SSLv3 cipher=RC4-MD5); Fri, 10 Sep 2010 19:21:23 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C8AE7A2.1090802@DataIX.net> Date: Fri, 10 Sep 2010 22:21:22 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100908 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Aryeh Friedman References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 02:21:25 -0000 On 09/09/2010 23:27, Aryeh Friedman wrote: > I have a directory that must not exist on logout and rm -rf is not > sufficent to do it because the contents need to be processed by our > version control system. The real life scenario is our version > control system stores the repo for a given project encrypted but for > techinical reasons it needs to keep the checkouted files in plain text > (they are all in the same dir) and I want to *NEVER* have the plain > text checkouted files in my dir when I logout, *BUT* instead of just > deleting it I need to check them in... so how do I make my .logout so > if the file exists it will not exit and give a error saying that dir > is still there? (minor but unimportant side effect of the version > control system is the dir will have a different name everytime it is > made but always the same prefix) > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" trap '/path/to/your_wrapper_script.HERE' 2 Should execute the contents of that script on every logout. Whether that script is a line by line action or a fully qualified script with functions to call different actions are up to you. Good luck, -- jhell,v From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 02:30:40 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02AB1106564A for ; Sat, 11 Sep 2010 02:30:40 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id A04F88FC08 for ; Sat, 11 Sep 2010 02:30:39 +0000 (UTC) Received: by gwb15 with SMTP id 15so1336682gwb.13 for ; Fri, 10 Sep 2010 19:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=qBu1w9MXTucl1yDi/AvmyfeCDtGM0r8zkKt6mFXxl8Y=; b=uMHx8lX8o8zH3vXfkbGvtZCX41PxUWC6V3TxMLVEKiPEsRjFm6gQ6lAIo8FaFuNS7V GeE6R0hQEhEsEzWQtZIQ9J1xCyg/i4Nj3FON6v30ZkQYsic/hr5mpEXj3rgrVN2YlXh4 4aFQovyJswlZ1bBf1QWI6xqeXWvyW2w7Z32ek= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=mGNI9EHQA9XLfGZooKOcpZZI69Hh8eKayHM7FOMKnMAZS0euqQ6fnukLoSW0Gn03xs RFyOr0dFvUmWo209sEKVezOziLcTEmVvtRn62g30TZzL0gLd071dDWkvclfWyCbdO5Jf KePYgW2nHV5zxpqT4vWGKrpMz9Vn33IIhOFgE= Received: by 10.100.136.7 with SMTP id j7mr1493469and.252.1284172238679; Fri, 10 Sep 2010 19:30:38 -0700 (PDT) Received: from centel.dataix.local ([99.181.137.20]) by mx.google.com with ESMTPS id d4sm4901322and.19.2010.09.10.19.30.37 (version=SSLv3 cipher=RC4-MD5); Fri, 10 Sep 2010 19:30:37 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C8AE9CB.9070008@DataIX.net> Date: Fri, 10 Sep 2010 22:30:35 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100908 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Aryeh Friedman References: <4C8AE7A2.1090802@DataIX.net> In-Reply-To: <4C8AE7A2.1090802@DataIX.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 02:30:40 -0000 On 09/10/2010 22:21, jhell wrote: > On 09/09/2010 23:27, Aryeh Friedman wrote: >> I have a directory that must not exist on logout and rm -rf is not >> sufficent to do it because the contents need to be processed by our >> version control system. The real life scenario is our version >> control system stores the repo for a given project encrypted but for >> techinical reasons it needs to keep the checkouted files in plain text >> (they are all in the same dir) and I want to *NEVER* have the plain >> text checkouted files in my dir when I logout, *BUT* instead of just >> deleting it I need to check them in... so how do I make my .logout so >> if the file exists it will not exit and give a error saying that dir >> is still there? (minor but unimportant side effect of the version >> control system is the dir will have a different name everytime it is >> made but always the same prefix) >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > trap '/path/to/your_wrapper_script.HERE' 2 > This should be: trap '/path/to/script' EXIT > Should execute the contents of that script on every logout. Whether that > script is a line by line action or a fully qualified script with > functions to call different actions are up to you. > > Good luck, > -- jhell,v From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 06:07:04 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55B611065670 for ; Sat, 11 Sep 2010 06:07:04 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 9944D8FC19 for ; Sat, 11 Sep 2010 06:07:03 +0000 (UTC) Received: (qmail 74218 invoked by uid 110); 11 Sep 2010 05:40:22 -0000 Received: from unknown (HELO desktop1) (simon@optinet.com@69.113.73.210) by cobra.acceleratedweb.net with SMTP; 11 Sep 2010 05:40:22 -0000 From: "Simon" To: "freebsd-hackers@freebsd.org" Date: Sat, 11 Sep 2010 01:40:28 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;3) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20100911060704.55B611065670@hub.freebsd.org> Subject: MCE Decoding - MCA: Bank 8, Status 0xcc0031800001009f/0xc8000980000200cf X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 06:07:04 -0000 Hello, Can someone please help me decode these two errors on FreeBSD 8.1-R: MCA: Bank 8, Status 0xcc0031800001009f MCA: Global Cap 0x0000000000001c09, Status 0x0000000000000000 MCA: Vendor "GenuineIntel", ID 0x106a5, APIC ID 16 MCA: CPU 0 COR (198) OVER RD channel ?? memory error MCA: Address 0x1b6188d80 MCA: Misc 0x72ae242000000084 MCA: Bank 8, Status 0xc8000980000200cf MCA: Global Cap 0x0000000000001c09, Status 0x0000000000000000 MCA: Vendor "GenuineIntel", ID 0x106a5, APIC ID 16 MCA: CPU 0 COR (38) OVER MS channel ?? memory error MCA: Misc 0x72ae242000000140 Thank you, Simon From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 09:11:19 2010 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43C8B1065673 for ; Sat, 11 Sep 2010 09:11:19 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id CC65D8FC25 for ; Sat, 11 Sep 2010 09:11:18 +0000 (UTC) Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o8B9BHs8065306; Sat, 11 Sep 2010 02:11:18 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4C8B47B5.60906@rawbw.com> Date: Sat, 11 Sep 2010 02:11:17 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.12) Gecko/20100908 Thunderbird/3.0.7 MIME-Version: 1.0 To: Alexander Kabaev References: <4C8A81D9.5020905@rawbw.com> <20100910195518.4d35b3b1@kan.dnsalias.net> In-Reply-To: <20100910195518.4d35b3b1@kan.dnsalias.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Garrett Cooper Subject: Re: Why I can't trace linux process's childs with truss? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 09:11:19 -0000 On 09/10/2010 16:55, Alexander Kabaev wrote: > You are. ptrace is supported by linuxulator for a while now. The > originator problem is likely because he is trying truss, which is not > Linux-aware. ktrace/linux_kdump combo should work. > I tried this: ktrace -d /usr/local/share/skype/skype Resulting trace again shows only the main process, not it's descendants, despite -d flag. Same in the case of calling with pid: ktrace -d -p . Yuri From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 09:36:52 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7D5F1065674 for ; Sat, 11 Sep 2010 09:36:52 +0000 (UTC) (envelope-from roam@ringlet.net) Received: from erengrad.hoster.bg (erengrad.hoster.bg [77.77.142.9]) by mx1.freebsd.org (Postfix) with ESMTP id 347F88FC13 for ; Sat, 11 Sep 2010 09:36:51 +0000 (UTC) Received: from middenheim.hoster.bg (middenheim.hoster.bg [77.77.142.11]) by erengrad.hoster.bg (Postfix) with ESMTP id 4A2B7DC1E0 for ; Sat, 11 Sep 2010 12:07:57 +0300 (EEST) Received: from straylight.ringlet.net (unknown [94.155.53.142]) (Authenticated sender: roam@hoster.bg) by mail.hoster.bg (Postfix) with ESMTP id D05BE5C37E for ; Sat, 11 Sep 2010 12:07:39 +0300 (EEST) Received: from roam (uid 1000) (envelope-from roam@ringlet.net) id 4160bd by straylight.ringlet.net (DragonFly Mail Agent) Sat, 11 Sep 2010 12:07:39 +0300 Date: Sat, 11 Sep 2010 12:07:39 +0300 From: Peter Pentchev To: jhell Message-ID: <20100911090739.GA3797@straylight.ringlet.net> Mail-Followup-To: jhell , Aryeh Friedman , freebsd-hackers@freebsd.org References: <4C8AE7A2.1090802@DataIX.net> <4C8AE9CB.9070008@DataIX.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: <4C8AE9CB.9070008@DataIX.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-MailScanner-ID: D05BE5C37E.C73ED X-hoster-MailScanner: Found to be clean X-hoster-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=0.001, required 10, autolearn=disabled, UNPARSEABLE_RELAY 0.00) X-hoster-MailScanner-From: roam@ringlet.net X-hoster-MailScanner-To: freebsd-hackers@freebsd.org X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, Aryeh Friedman Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 09:36:52 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 10, 2010 at 10:30:35PM -0400, jhell wrote: > On 09/10/2010 22:21, jhell wrote: > > On 09/09/2010 23:27, Aryeh Friedman wrote: > >> I have a directory that must not exist on logout and rm -rf is not > >> sufficent to do it because the contents need to be processed by our > >> version control system. The real life scenario is our version > >> control system stores the repo for a given project encrypted but for > >> techinical reasons it needs to keep the checkouted files in plain text > >> (they are all in the same dir) and I want to *NEVER* have the plain > >> text checkouted files in my dir when I logout, *BUT* instead of just > >> deleting it I need to check them in... so how do I make my .logout so > >> if the file exists it will not exit and give a error saying that dir > >> is still there? (minor but unimportant side effect of the version > >> control system is the dir will have a different name everytime it is > >> made but always the same prefix) > >> _______________________________________________ > >> freebsd-hackers@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.= org" > >=20 > > trap '/path/to/your_wrapper_script.HERE' 2 > >=20 >=20 > This should be: >=20 > trap '/path/to/script' EXIT >=20 > > Should execute the contents of that script on every logout. Whether that > > script is a line by line action or a fully qualified script with > > functions to call different actions are up to you. =2E..but, of course, that's only until people learn that they can bypass th= is by something like 'kill -FPE $$'. G'luck, Peter --=20 Peter Pentchev roam@space.bg roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If wishes were fishes, the antecedent of this conditional would be true. --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCgAGBQJMi0bOAAoJEGUe77AlJ98TlZgQALEt6CdZ0qAczCYq9+JuUtGu dDLeZrkjnpB7iVVKbqjtiQrfIKGEOhdxQKpDAKNj6Z7YUXzQyngJ8vzWBHGeaGHm DpBvJmE3sLctGEQ7ExZZocx4CID1umEwvL3siS7IdYN50IzXWoMJyBWUimhNnZRo KO/419q7MTluzYX+cRguMcp+0NV3jnlfQT611N5uESazjHoeMkOmM/kLaVQ2O2cE MDp7jRXG0UnmGz0kc+7qJuR36Z4cfutgXcw3qZZ6lNe4T8xnJlmCbawkLg/pV+pb 8pBK1iFgp2k6HX9Nr3EM/G4SzyeMtOSL3upHrYdsn25LdOJEFDFe6MGHyLGJahwi Z17pdXxhD7TW6cRvPuAvTM6eTlE4mTzaZrnv4tcjxQH05okoFlMwW51za+dWSkkH +mAzGBAxHcjBMxGH+jKQmmNgjl7zr/iJUT9mGJhu4a6s7YNm5KQ5CqCoUA8v8gWG iPHqPLk8XHArPqJS4GpCwiVSg9Li2a4RGftpBaxzg0R5UE9WeZBczIhMsGCSGquM IOzYF+ZMvI2wM14hJEPByqUi4Vav0uGqd4Pw2cz+s2m2vIXAirhck0e3p1bcdO3c 4+L0qz8HsSn7VEIj7szYt4pNZCLXQ1TKS6BCmJE/0wAVULSyv87tbqyIAZp+/cJt YmOvc2DPIbuCDi4l21EK =dZLP -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 10:32:49 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1CF9106564A for ; Sat, 11 Sep 2010 10:32:49 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 2CAC28FC0C for ; Sat, 11 Sep 2010 10:32:46 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o8BAWgBq083107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Sep 2010 13:32:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id o8BAWgYV097084; Sat, 11 Sep 2010 13:32:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o8BAWgNf097083; Sat, 11 Sep 2010 13:32:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 11 Sep 2010 13:32:42 +0300 From: Kostik Belousov To: Yuri Message-ID: <20100911103242.GV2465@deviant.kiev.zoral.com.ua> References: <4C8A81D9.5020905@rawbw.com> <20100910195518.4d35b3b1@kan.dnsalias.net> <4C8B47B5.60906@rawbw.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KxKI/R+N9hudrWbn" Content-Disposition: inline In-Reply-To: <4C8B47B5.60906@rawbw.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Why I can't trace linux process's childs with truss? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 10:32:49 -0000 --KxKI/R+N9hudrWbn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 11, 2010 at 02:11:17AM -0700, Yuri wrote: > On 09/10/2010 16:55, Alexander Kabaev wrote: > >You are. ptrace is supported by linuxulator for a while now. The > >originator problem is likely because he is trying truss, which is not > >Linux-aware. ktrace/linux_kdump combo should work. > > =20 >=20 > I tried this: ktrace -d /usr/local/share/skype/skype > Resulting trace again shows only the main process, not it's descendants,= =20 > despite -d flag. > Same in the case of calling with pid: ktrace -d -p . -d means "current descendants". On the other hand, -i is "inherit by all future children". --KxKI/R+N9hudrWbn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkyLWsoACgkQC3+MBN1Mb4jvOgCfZvSLJFBFSTwkNV3TLDPVzZaF kNIAnicJqx9sKhbeDxqr/qQNujWLceDq =WTpA -----END PGP SIGNATURE----- --KxKI/R+N9hudrWbn-- From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 10:53:35 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35E401065672 for ; Sat, 11 Sep 2010 10:53:35 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id E8B628FC15 for ; Sat, 11 Sep 2010 10:53:34 +0000 (UTC) Received: by iwn34 with SMTP id 34so3574954iwn.13 for ; Sat, 11 Sep 2010 03:53:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=J+rSXTNOlgFyfL+BkyIy5NrcY2oy5pwf17v6DawXf7s=; b=pPKhmtiXTvKja+zTERRS6SnEoKfa+LkH7Cjr4mn8A9BpN7LiVenloUhn5cvrjHPWGd iCbVZA0DiPdr7xsNQmVAV5JkPWIK7JxdzQBF65Zt5nAbrnJ73DPf+4BFdiBX05hqFIP8 uqVlmP2W5E+B+ZE6cje71H0hSRIilLnYTL8FA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=oPOOTNuty32gN61b1SHuf7ZKEjvFPdsTScoOoOoKpaOVezLvcQQKHCb9wc/57/Ap30 WDYZcoiEs/7VHtksh1tI1sKPvZnvP+uh/MmPmkVmR0p3n7hMEf9rGtgvbl20m3T2FAgs pKFACeeR/qFhQGr15m6cuqEa9SVU59p0r1wu4= Received: by 10.231.177.40 with SMTP id bg40mr2305166ibb.150.1284202414279; Sat, 11 Sep 2010 03:53:34 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-137-20.dsl.klmzmi.sbcglobal.net [99.181.137.20]) by mx.google.com with ESMTPS id h8sm3502033ibk.9.2010.09.11.03.53.32 (version=SSLv3 cipher=RC4-MD5); Sat, 11 Sep 2010 03:53:33 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C8B5FAB.1010502@DataIX.net> Date: Sat, 11 Sep 2010 06:53:31 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100908 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Aryeh Friedman , freebsd-hackers@freebsd.org References: <4C8AE7A2.1090802@DataIX.net> <4C8AE9CB.9070008@DataIX.net> <20100911090739.GA3797@straylight.ringlet.net> In-Reply-To: <20100911090739.GA3797@straylight.ringlet.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 10:53:35 -0000 On 09/11/2010 05:07, Peter Pentchev wrote: > > ...but, of course, that's only until people learn that they can > bypass this by something like 'kill -FPE $$'. > Have you tried that ? If the person/developer is looking into it that far where they need to subvert the logout process then there is probably a pretty good reason for doing so and would be expected that they bring it to the admins attention or file a PR. There is only just so much you can do before you start to modify the code in the shell itself so the user cant execute another shell upon login and kill their shell before other scripts run on logout. Firstly this just sounds like a case where the admin needs to provide a equally sound and safe way of making sure everything is cleaned up on logout and is offering a global way of doing it so the developer will not forget. trap 'echo "Sorry FPE not allowed. ;)"' FPE ( kill -l ) will list the rest of the signals you can trap too. And you can get pretty evil with this. But for the short term. for sig in `jot 31 1`; do trap 'echo "WARN:$$ Please use ^D or logout(1) instead."' ${sig} done Of course not all of those signals will cause a logout to happen but have fun with it. Regards, -- jhell,v From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 11:07:01 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D30EF106566B for ; Sat, 11 Sep 2010 11:07:01 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9ABF18FC1B for ; Sat, 11 Sep 2010 11:07:01 +0000 (UTC) Received: by iwn34 with SMTP id 34so3585306iwn.13 for ; Sat, 11 Sep 2010 04:07:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=RdGMTWnTi4aO2f/Y2wYXyc8ZQ7nB9AR+Ph9o9BP8sRI=; b=n+Wameofk+VzTKRLbfU0A596RT2osOCT8lEY+n4EQs79jMZmeWNVJ02o4PsYDRSht9 bJk542tamoBQ0rfKEh1CMxTY0y/axSXp7Izjmr1llinPYI2iwZkG3Mzs8qmRDZhxjMtS T/T/AQYuR2GaOhnIjaQWW60YBZSLaNKWabNZo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mDKERbAgF3UkEm5oWOCJfHh/uILpWPQootZhmBWnEPoi/ssbMpO0A6UbbYOPpJoYPU BOjxSk0ImLt/0pIbNUl9fsnQombMIxpwH7QttSf26+PkxkDeBC8845HWLqzEVMaq7af1 7eOxNAsOuX+XWQncj0tuFbQAYtRc3d6JukPio= MIME-Version: 1.0 Received: by 10.231.160.17 with SMTP id l17mr2623193ibx.102.1284203220945; Sat, 11 Sep 2010 04:07:00 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Sat, 11 Sep 2010 04:07:00 -0700 (PDT) In-Reply-To: <4C8B5FAB.1010502@DataIX.net> References: <4C8AE7A2.1090802@DataIX.net> <4C8AE9CB.9070008@DataIX.net> <20100911090739.GA3797@straylight.ringlet.net> <4C8B5FAB.1010502@DataIX.net> Date: Sat, 11 Sep 2010 07:07:00 -0400 Message-ID: From: Aryeh Friedman To: jhell Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 11:07:01 -0000 > > Firstly this just sounds like a case where the admin needs to provide a > equally sound and safe way of making sure everything is cleaned up on > logout and is offering a global way of doing it so the developer will > not forget. In this case the admin and developer are the same person... namely at the clients request I am the only person allowed to work on the project and I just want to make it so I can't accidently do something like control-d or something like that and leave a plain text version of a project that has a very strict NDA laying around (liquidated damages of $250k)... the scenrio is we a are a team (each one of us is in diff city) of freelance CS people and all use the same server for all our development to make cooperation possible when needed (not in this case) have centralized backups, etc. and as mentioned on this one project the client has forced me to sign a NDA saying I can't even show the code to the other team members without the client's permission and thus am storing the repo using security/fuse-encfs, but since the version control system (devel/aegis) requires creating a development directory that is not encrypted I want to force/remind myself to checkin what ever I was working into the encrypted repo when I go "home" (it is a home office ;-)) at night or out to lunch From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 11:13:25 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 436A4106566C for ; Sat, 11 Sep 2010 11:13:25 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 086668FC13 for ; Sat, 11 Sep 2010 11:13:24 +0000 (UTC) Received: by iwn34 with SMTP id 34so3590632iwn.13 for ; Sat, 11 Sep 2010 04:13:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=hhcQf0mJAcPYyRKYdh2e9qKYXfddlCAVDs4wTz6uWig=; b=Zsss9gtMMe4Re3wy1YRYyHE6pQooUIEr0n2uHey5wUaunGAKO1x0MaoiJEBQJ56bN+ e9srpZBKGF7Ggva+yEmWflF5nzHC0yhf7zEVr/tR1ljW40mkXYTzq6GtsRhSEoHtm970 4hjMAHQw4RIzW2FpO2Gst0jvjvyugPV04gFHU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=X0c9rlYvatiYaU3SxAODWyHR9aRpSoP14+VMB7GadT1UWF6/eVaRWAcaV1tohkzDuz Z6IlAtND1w/P+/Mmddl2P11ChcG4kNn2VcWApHw4C+7hHMlM4Svm+eLkqqPRYO9P8eHd oJYNUec9eSzt/kIeSbqpgsHM43mk7LnfW/3s8= MIME-Version: 1.0 Received: by 10.231.16.75 with SMTP id n11mr2312197iba.49.1284203601316; Sat, 11 Sep 2010 04:13:21 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Sat, 11 Sep 2010 04:13:21 -0700 (PDT) In-Reply-To: References: <4C8AE7A2.1090802@DataIX.net> <4C8AE9CB.9070008@DataIX.net> <20100911090739.GA3797@straylight.ringlet.net> <4C8B5FAB.1010502@DataIX.net> Date: Sat, 11 Sep 2010 07:13:21 -0400 Message-ID: From: Aryeh Friedman To: jhell Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 11:13:25 -0000 On Sat, Sep 11, 2010 at 7:07 AM, Aryeh Friedman wrote: >> >> Firstly this just sounds like a case where the admin needs to provide a >> equally sound and safe way of making sure everything is cleaned up on >> logout and is offering a global way of doing it so the developer will >> not forget. > > In this case the admin and developer are the same person... namely at > the clients request I am the only person allowed to work on the > project and I just want to make it so I can't accidently do something > like control-d or something like that and leave a plain text version > of a project that has a very strict NDA laying around (liquidated > damages of $250k)... the scenrio is we a are a team (each one of us is > in diff city) of freelance CS people and all use the same server for > all our development to make cooperation possible when needed (not in > this case) have centralized backups, etc. and as mentioned on this one > project the client has forced me to sign a NDA saying I can't even > show the code to the other team members without the client's > permission and thus am storing the repo using security/fuse-encfs, but > since the version control system (devel/aegis) requires creating a > development directory that is not encrypted I want to force/remind > myself to checkin what ever I was working into the encrypted repo when > I go "home" (it is a home office ;-)) at night or out to lunch > Forgot to mention all these percautions are to make the client comfortable with letting me take advanatage of the server's development enviroment instead of spending almost a week configuring the same env on my desktop machine... namely I trust the other team members to not look at the code even if it was not encrypted. From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 13:54:01 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C9F6106566C for ; Sat, 11 Sep 2010 13:54:01 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1CF6F8FC0C for ; Sat, 11 Sep 2010 13:54:00 +0000 (UTC) Received: by gyg4 with SMTP id 4so1828421gyg.13 for ; Sat, 11 Sep 2010 06:53:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=GwP8JO1PuvFVyN0zkgeiwcbgGkRS7Miymss2JOAE2xM=; b=s0145hwsNvfDi23OBK1MQkgW5TcyjEGkcQCZAL4qOq8HygGiUMPM+e6c8C70A/TMDC tcRfzhD4qjXI3qsW2e2I45emK/AtzXXIWh+teVd5HCd7SMwsES/VfDeTQtt6jgdobq7d di0gaAA/Bx8uE8NjjX1bBdCcH8iWzjvHbrr3k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=dYHjC3tt5LEQC25644rz8ZAF7XVGGPCz35sdWhOWWhz5jizSW7Qtz7wfALpYvAiVoX 7m/P1bhDUDdOWbxAQ7OmLWFeFx7Hkh9WMfV7GuM/xH3mS3KXix7vCuMOoWrHZc/h2Ae7 5GykFJNb2DkU7wKekSXXjXi+krH0ObkleUgjY= Received: by 10.100.197.3 with SMTP id u3mr2006855anf.208.1284213239640; Sat, 11 Sep 2010 06:53:59 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-137-20.dsl.klmzmi.sbcglobal.net [99.181.137.20]) by mx.google.com with ESMTPS id f29sm5942548anh.11.2010.09.11.06.53.58 (version=SSLv3 cipher=RC4-MD5); Sat, 11 Sep 2010 06:53:58 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C8B89F4.2020706@DataIX.net> Date: Sat, 11 Sep 2010 09:53:56 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100908 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Aryeh Friedman References: <4C8AE7A2.1090802@DataIX.net> <4C8AE9CB.9070008@DataIX.net> <20100911090739.GA3797@straylight.ringlet.net> <4C8B5FAB.1010502@DataIX.net> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 13:54:01 -0000 On 09/11/2010 07:13, Aryeh Friedman wrote: > On Sat, Sep 11, 2010 at 7:07 AM, Aryeh Friedman > wrote: >>> >>> Firstly this just sounds like a case where the admin needs to provide a >>> equally sound and safe way of making sure everything is cleaned up on >>> logout and is offering a global way of doing it so the developer will >>> not forget. >> >> In this case the admin and developer are the same person... namely at >> the clients request I am the only person allowed to work on the >> project and I just want to make it so I can't accidently do something >> like control-d or something like that and leave a plain text version >> of a project that has a very strict NDA laying around (liquidated >> damages of $250k)... the scenrio is we a are a team (each one of us is >> in diff city) of freelance CS people and all use the same server for >> all our development to make cooperation possible when needed (not in >> this case) have centralized backups, etc. and as mentioned on this one >> project the client has forced me to sign a NDA saying I can't even >> show the code to the other team members without the client's >> permission and thus am storing the repo using security/fuse-encfs, but >> since the version control system (devel/aegis) requires creating a >> development directory that is not encrypted I want to force/remind >> myself to checkin what ever I was working into the encrypted repo when >> I go "home" (it is a home office ;-)) at night or out to lunch >> > > Forgot to mention all these percautions are to make the client > comfortable with letting me take advanatage of the server's > development enviroment instead of spending almost a week configuring > the same env on my desktop machine... namely I trust the other team > members to not look at the code even if it was not encrypted. In that case would it make sense to just use tmpfs or some other destructive file-system when it gets unmounted. Maybe one-time encryption offered by geli(8) on a mdconfig(8) swap-file for just the source that you checkout. Implement it using amd(8). Don't know if this is a possible scenario but gives you a little more to consider. Regards & good luck, -- jhell,v From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 15:11:07 2010 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52788106564A for ; Sat, 11 Sep 2010 15:11:07 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id C1C848FC08 for ; Sat, 11 Sep 2010 15:11:06 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id o8BFAned011319; Sat, 11 Sep 2010 17:11:04 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id o8BFAnJ9011318; Sat, 11 Sep 2010 17:10:49 +0200 (CEST) (envelope-from olli) Date: Sat, 11 Sep 2010 17:10:49 +0200 (CEST) Message-Id: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, aryeh.friedman@gmail.com In-Reply-To: X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Sat, 11 Sep 2010 17:11:04 +0200 (CEST) Cc: Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, aryeh.friedman@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 15:11:07 -0000 Aryeh Friedman wrote: > In this case the admin and developer are the same person... namely at > the clients request I am the only person allowed to work on the > project and I just want to make it so I can't accidently do something > like control-d or something like that and leave a plain text version > of a project that has a very strict NDA laying around (liquidated > damages of $250k)... the scenrio is we a are a team (each one of us is > in diff city) of freelance CS people and all use the same server for > all our development to make cooperation possible when needed (not in > this case) have centralized backups, etc. and as mentioned on this one > project the client has forced me to sign a NDA saying I can't even > show the code to the other team members without the client's > permission and thus am storing the repo using security/fuse-encfs, but > since the version control system (devel/aegis) requires creating a > development directory that is not encrypted I want to force/remind > myself to checkin what ever I was working into the encrypted repo when > I go "home" (it is a home office ;-)) at night or out to lunch If it's just a reminder to yourself, then I would simply remove the keybinding for ^D (or bind it to something else; the details depend on your login shell) and alias "exit" and "logout" to a script that checks the working directory of your version control system. If things have been checked in correctly, it logs you out, otherwise it prints a message and terminates, throwing you back to the shell prompt. Additionally, you could put the checked-out files on a geli-encrypted device and/or on a memory file system. That will make sure that there ist no unencrypted stuff left behind after a power-failure or crash. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Python is an experiment in how much freedom programmers need. Too much freedom and nobody can read another's code; too little and expressiveness is endangered." -- Guido van Rossum From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 15:18:59 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50DC6106566B for ; Sat, 11 Sep 2010 15:18:59 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 16B878FC12 for ; Sat, 11 Sep 2010 15:18:59 +0000 (UTC) Received: by iwn34 with SMTP id 34so3812826iwn.13 for ; Sat, 11 Sep 2010 08:18:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=cu1a5ZtfHiNWyDzDuYgZuDlMiwkZvBNeeraet8D29P4=; b=Ew6inbssyjmsUoDm6syWOAnahvTVNR43oP/Zd++ewhmDhUcY+sDPZuSOkJjPAbUpfA GKcZHGb6q041FoNWqsX1tIv2GDsJfRTaB5vq2jzXFunlpa0u9UnhHTCYnSAfSAxGZtqC +Vs68xkjSNWqLKJtryWMa+dieQAMSF6Ao9KRw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=So+G2PRfnoOqCiDuBGEvXSUrwydVnm0cQREfFwIq5bURh0z//QG7eSXmsLOGPGKWdF fGtwHrZAI+GyuXDBCsmkogV+F0KwyZhuMd/UbCC3viW1wFMFDh19j0o2/GzpSA8o7Fxm WvZ7MGvpNCQfvoPIvmxq8ABG6brBz+i3k6mbI= MIME-Version: 1.0 Received: by 10.231.160.205 with SMTP id o13mr2916659ibx.15.1284218338699; Sat, 11 Sep 2010 08:18:58 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Sat, 11 Sep 2010 08:18:58 -0700 (PDT) In-Reply-To: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> References: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> Date: Sat, 11 Sep 2010 11:18:58 -0400 Message-ID: From: Aryeh Friedman To: freebsd-hackers@freebsd.org, aryeh.friedman@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 15:18:59 -0000 I would prefer to have the plain text around after a power failure because it could be several days of work and as I said the only reason for all this is to make the client comfortable and not that I do not trust the team (I do trust them) On Sat, Sep 11, 2010 at 11:10 AM, Oliver Fromme wr= ote: > Aryeh Friedman wrote: > =A0> In this case the admin and developer are the same person... namely a= t > =A0> the clients request I am the only person allowed to work on the > =A0> project and I just want to make it so I can't accidently do somethin= g > =A0> like control-d or something like that and leave a plain text version > =A0> of a project that has a very strict NDA laying around (liquidated > =A0> damages of $250k)... the scenrio is we a are a team (each one of us = is > =A0> in diff city) of freelance CS people and all use the same server for > =A0> all our development to make cooperation possible when needed (not in > =A0> this case) have centralized backups, etc. and as mentioned on this o= ne > =A0> project the client has forced me to sign a NDA saying I can't even > =A0> show the code to the other team members without the client's > =A0> permission and thus am storing the repo using security/fuse-encfs, b= ut > =A0> since the version control system (devel/aegis) requires creating a > =A0> development directory that is not encrypted I want to force/remind > =A0> myself to checkin what ever I was working into the encrypted repo wh= en > =A0> I go "home" (it is a home office ;-)) at night or out to lunch > > If it's just a reminder to yourself, then I would simply > remove the keybinding for ^D (or bind it to something else; > the details depend on your login shell) and alias "exit" > and "logout" to a script that checks the working directory > of your version control system. =A0If things have been checked > in correctly, it logs you out, otherwise it prints a message > and terminates, throwing you back to the shell prompt. > > Additionally, you could put the checked-out files on a > geli-encrypted device and/or on a memory file system. =A0That > will make sure that there ist no unencrypted stuff left > behind after a power-failure or crash. > > Best regards > =A0 Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, =A0Gesch=E4ftsfuehr= ung: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M=FC= n- > chen, HRB 125758, =A0Gesch=E4ftsf=FChrer: Maik Bachmann, Olaf Erb, Ralf G= ebhart > > FreeBSD-Dienstleistungen, -Produkte und mehr: =A0http://www.secnetix.de/b= sd > > "Python is an experiment in how much freedom programmers need. > Too much freedom and nobody can read another's code; too little > and expressiveness is endangered." > =A0 =A0 =A0 =A0-- Guido van Rossum > From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 16:58:37 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EA5C1065670 for ; Sat, 11 Sep 2010 16:58:37 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 23C3D8FC08 for ; Sat, 11 Sep 2010 16:58:36 +0000 (UTC) Received: by ywt2 with SMTP id 2so1816655ywt.13 for ; Sat, 11 Sep 2010 09:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=rk11BL+QA0d7p8lCVfpb0mIviKUai5sEemXJqS1DSYE=; b=LCTXxA/WTGQY1KzF6qIMJAUSoX/Ab1PV4rk9G5qsvBPj4EFxLnSAHHl7PguyiI8627 wsonsDO8yNvSMG9+nTLXu6YSmcHTTXUGqKXCrhPdwmdl2UEYHwpgskSypMFSw3ptuiqi t629clJAWq7YiLMEAYiSWeTSs21miPhKhlQuw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=u8kgzUAn5HLS3UbHdRZeKRL/IxVZ4mFB79q6oZr9NcIbnSGcLuNtRW+EJNzl2j3Erf IknT4K80AYC+ndQD5pCKFerz4ORPRg0c/Pxh0sJ2G8lWmcSGAaEdN170OAhvQ1A5lnr/ akJ0y18QWLzguELA8erOw/AS4vPomdirqns8c= Received: by 10.101.28.4 with SMTP id f4mr2200725anj.181.1284222767927; Sat, 11 Sep 2010 09:32:47 -0700 (PDT) Received: from [192.168.1.3] (c-24-14-170-47.hsd1.il.comcast.net [24.14.170.47]) by mx.google.com with ESMTPS id d4sm6163129and.19.2010.09.11.09.32.46 (version=SSLv3 cipher=RC4-MD5); Sat, 11 Sep 2010 09:32:47 -0700 (PDT) Message-ID: <4C8BAF2F.4050905@gmail.com> Date: Sat, 11 Sep 2010 11:32:47 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 16:58:37 -0000 On 9/11/2010 10:18 AM, Aryeh Friedman wrote: > ys of work and as I said the only reason > for all this is to make the client comfortable and not that I do not > trust the team (I do trust them) Write a script that gets executed in the background once you log in that will periodically check to make sure you're still logged in and if not, commit and delete. If you have a power failure, the script won't be running until you log in(unlike using cron), and when you log in after a power failure it should still all be there. From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 17:06:30 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06F8B1065672 for ; Sat, 11 Sep 2010 17:06:30 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C0A978FC08 for ; Sat, 11 Sep 2010 17:06:29 +0000 (UTC) Received: by iwn34 with SMTP id 34so3909905iwn.13 for ; Sat, 11 Sep 2010 10:06:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wVjHPHVwZ9IYc1LFsRk/3tLh3mSk8f9a5WUskPo1a5A=; b=cuC0HqhninxGMYxH4CkKyvboYaVrvS1SryYmWK3gRkqLRqxQryEliJjGHpLSav0cz1 mYVeJtoFt3UBjLM/LKnhY/NENdBh9HA3oFWijQ84LalMqe73mis/pzuOzi2ld0fSLnj5 41RHCuAnMM8ZJl+Ncg240qZknAr0avaN0t+og= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tArRIsjSOprMKKqwkwUcIQcmypmWXKwx0jQk2hDVNUqOReIy17OZj2omgOkrablpc5 581ArDXKplpJ1Po+nnVRaPQ7Rt8zgeYroLiFSBJeDmFwd+/KtpDFa2AKo5XtxOW0Rjvl NZJKcmamOtYP6oYbVbXL2Sbn4Y8030ItXdJKs= MIME-Version: 1.0 Received: by 10.231.152.143 with SMTP id g15mr3122479ibw.76.1284224789156; Sat, 11 Sep 2010 10:06:29 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Sat, 11 Sep 2010 10:06:29 -0700 (PDT) In-Reply-To: <4C8BAF2F.4050905@gmail.com> References: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> <4C8BAF2F.4050905@gmail.com> Date: Sat, 11 Sep 2010 13:06:29 -0400 Message-ID: From: Aryeh Friedman To: Joshua Isom Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 17:06:30 -0000 For reasons explained in an earlier reply this is a very *BAD* idea due to how devel/aegis is structured On Sat, Sep 11, 2010 at 12:32 PM, Joshua Isom wrote: > On 9/11/2010 10:18 AM, Aryeh Friedman wrote: >> >> ys of work and as I said the only reason >> for all this is to make the client comfortable and not that I do not >> trust the team (I do trust them) > > Write a script that gets executed in the background once you log in that > will periodically check to make sure you're still logged in and if not, > commit and delete. =A0If you have a power failure, the script won't be ru= nning > until you log in(unlike using cron), and when you log in after a power > failure it should still all be there. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 23:13:08 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE673106566B for ; Sat, 11 Sep 2010 23:13:08 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id BA5C08FC14 for ; Sat, 11 Sep 2010 23:13:08 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id o8BND8lc014819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Sep 2010 16:13:08 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id o8BND89Z014817; Sat, 11 Sep 2010 16:13:08 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA18648; Sat, 11 Sep 10 16:11:44 PDT Date: Sat, 11 Sep 2010 16:11:48 -0700 From: perryh@pluto.rain.com To: aryeh.friedman@gmail.com Message-Id: <4c8c0cb4.n0Z+r+TIC4vzdXnS%perryh@pluto.rain.com> References: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 23:13:08 -0000 Aryeh Friedman wrote: > I would prefer to have the plain text around after a power failure > because it could be several days of work ... Ideally there should be _some_ mechanism for committing unfinished work to a (probably encrypted) repository on, at least, a daily basis. The more I see of this thread, the more it seems that the problem is largely the fault of the particular VCS being used. A VCS that demands a "review" step before anything can be checked in, even on a "work in progress" branch as opposed to the mainline, seems a poor fit for a project in which developers are not permitted to see one anothers code. From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 23:16:17 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40F5610656AB for ; Sat, 11 Sep 2010 23:16:17 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 05E0E8FC12 for ; Sat, 11 Sep 2010 23:16:16 +0000 (UTC) Received: by iwn34 with SMTP id 34so4190943iwn.13 for ; Sat, 11 Sep 2010 16:16:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=lSZ7r25zFeEOjNLljv8psmILUcXGgWHeu2t0lscCP90=; b=GOHBx/xbHEJHTYgCQajVfqynT6AvtJ6NE1ubjbkbJoj2+VdcABHr7RwJJfmenWvD46 AMOLlA8KRNiXzXcLB5C8HOjTkKTupn2jG00NTBEGTbGOXrQPDofpmILoOtg0d3yztd5m y+cTaf7Nge5aWIUmsC3dyUup/6MSF7eKKqEuw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=hsk7VS1dWvVDbyvZnk323L+VbCajx7xdji2QTmhmHbb4qqah4RmTPxW8L6WkdpurJz gyHYd58mPr5OynV53QbGsJcmlQw48Ft6Qz1yUK26cs60vSyRfnN9O9upcEgGwEdIm4dK fB3oqklKXn4h43tYwRa2otqzDwhyLJV4sBPLg= MIME-Version: 1.0 Received: by 10.231.59.83 with SMTP id k19mr3475675ibh.178.1284246976357; Sat, 11 Sep 2010 16:16:16 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Sat, 11 Sep 2010 16:16:16 -0700 (PDT) In-Reply-To: <4c8c0cb4.n0Z+r+TIC4vzdXnS%perryh@pluto.rain.com> References: <201009111510.o8BFAnJ9011318@lurza.secnetix.de> <4c8c0cb4.n0Z+r+TIC4vzdXnS%perryh@pluto.rain.com> Date: Sat, 11 Sep 2010 19:16:16 -0400 Message-ID: From: Aryeh Friedman To: perryh@pluto.rain.com, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 23:16:17 -0000 Since we have been using aegis for years and know it like the back of our hand I don't want to learn a new tool... but I think your right I am going to forward/cross post this entire thread to the aegis mailing list. On Sat, Sep 11, 2010 at 7:11 PM, wrote: > Aryeh Friedman wrote: > >> I would prefer to have the plain text around after a power failure >> because it could be several days of work ... > > Ideally there should be _some_ mechanism for committing unfinished > work to a (probably encrypted) repository on, at least, a daily > basis. > > The more I see of this thread, the more it seems that the problem > is largely the fault of the particular VCS being used. =A0A VCS that > demands a "review" step before anything can be checked in, even on a > "work in progress" branch as opposed to the mainline, seems a poor > fit for a project in which developers are not permitted to see one > anothers code. >