https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082007-07-06T16:56:02ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=31612007-07-06T16:56:02Zcorecode
<ul></ul><p>We need device cloning :/ sigh... all our troubles would be gone![tm]</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=31632007-07-06T18:47:01Zc.turner
<ul></ul><p>yeah - I guess not having to worry about it at all is one way around<br />it</p>
<p>right now, thinking simple though - not trying to get too distracted<br />noodling around on it .. might investigate this over time though..</p>
<p>also - does everything on submit@ become a 'bug' - if so I'll stay to<br />users / kernel for these kinds of questions, at least until I have a<br />patch of course.</p>
<p>Thanks,</p>
<p>- Chris</p> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=31672007-07-08T02:18:00Zdillon
<ul></ul><p>What we really need is devfs. Device cloning itself is really easy, but<br /> to do it right we want a direct file descriptor device interface so<br /> the device can be assigned to the (private) file pointer instead of to<br /> the (shared) vnode. devfs is needed because when we bypass the vnode<br /> the access and modified times will no longer get updated for devices<br /> in a normal UFS based /dev filesystem.</p>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=31722007-07-09T05:37:00Zcorecode
<ul></ul><p>would we care about these times? I mean, would we <strong>really</strong> care? On devfs, we'd lose this information on reboot as well. Or we "simply" add a sidechannel to update a [am]time on fdesc access (maybe that would fix my mmap time issue?)</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=31812007-07-10T01:57:01Zdillon
<ul></ul><p>:would we care about these times? I mean, would we <strong>really</strong> care? On dev=<br />:fs, we'd lose this information on reboot as well. Or we "simply" add a s=<br />:idechannel to update a [am]time on fdesc access (maybe that would fix my =<br />:mmap time issue?)<br />:<br />:cheers<br />: simon</p>
<pre><code>We want things like 'w' to properly report the idle time for tty's.</code></pre>
<pre><code>I don't think any of it needs to survive a reboot.</code></pre>
<pre><code>-Matt</code></pre> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=31822007-07-10T02:11:01Zcorecode
<ul></ul><p>Ah, I see. Can't we have a fdesc associated with a vnode which [am]time then get updated?</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=31882007-07-11T00:53:00Zdillon
<ul></ul><p>:Ah, I see. Can't we have a fdesc associated with a vnode which [am]time =<br />:then get updated?<br />:<br />:cheers<br />: simon</p>
<pre><code>We already have shortcuts for the fdesc for devices which deal with<br /> atime updates, but it's really a big mess. The only real solution<br /> is devfs. We'll need devfs in the next year (2.1-2.2ish time frame)<br /> anyhow because it is rather inconvenient to have to create large<br /> matrixes of device nodes for disk slice/partition with the new<br /> partitioning support schemes.</code></pre>
<pre><code>-Matt</code></pre> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=32192007-07-11T06:55:00Zwa1ter
<ul></ul><p>Have you looked at udev? It's all done in userland so I'm guessing there<br />is nothing linux-specific about it. It works well for me, but the config<br />files are a nightmare.</p> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=71182009-08-23T17:13:31Ztuxillo
<ul></ul><p>Now that DFBSD has devfs, can this be closed?</p> DragonFlyBSD - Bug #721: idea: vnconfig '-l' ?https://bugs.dragonflybsd.org/issues/721?journal_id=71232009-08-24T04:41:48Zc.turner
<ul></ul><p>actually, I committed a patch for this (or at least submitted one that <br />was committed)<br />in around the 1.10 days -<br />didn't get back to closing it. my apologies.</p>
<p>with that in mind, I'm waaay behind on dragonfly testing/coding -<br />not sure if it still works w/devfs, though my assumption is that<br />it would..</p>
<p>think the feature is still useful & shouldn't be removed - unless devfs<br />removes vn devices after use..</p>
<p>will close in 1d - need password reset email & perhaps<br />there are other comments</p>
<p>Thanks,</p>
<p>- Chris</p>
<p>Antonio Huete Jimenez (via DragonFly issue tracker) wrote:</p>
<blockquote>
<p>Antonio Huete Jimenez <<a class="email" href="mailto:tuxillo@quantumachine.net">tuxillo@quantumachine.net</a>> added the comment:</p>
<p>Now that DFBSD has devfs, can this be closed?</p>
<p>_<em><i></em></i>__<em>_</em>_________________________________________<br />DragonFly issue tracker <<a class="email" href="mailto:bugs@lists.dragonflybsd.org">bugs@lists.dragonflybsd.org</a>><br /><<a class="external" href="http://bugs.dragonflybsd.org/issue721">http://bugs.dragonflybsd.org/issue721</a>><br />_<em><i></em></i>__<em>_</em>_________________________________________</p>
</blockquote>