Date: Wed, 18 Sep 1996 16:31:28 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: BRETT_GLASS@infoworld.com Cc: nate@mt.sri.com, mobile@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: PCMCIA, APM, 3C562 Message-ID: <199609180701.QAA04623@genesis.atrad.adelaide.edu.au> In-Reply-To: <9608178430.AA843015988@ccgate.infoworld.com> from "BRETT_GLASS@infoworld.com" at Sep 17, 96 05:38:53 pm
next in thread | previous in thread | raw e-mail | index | archive | help
BRETT_GLASS@infoworld.com stands accused of saying: > > >> Will the system (including PCMCIA) be able to survive a > >> suspend/resume cycle without "freaking out" or getting too busy to use > >> due > to missed items in /etc/crontab? > > > Not a problem. On my laptops (I use various ThinkPad and NEC Versa for > > development and testing) suspend/resume works 'most of the time'. I > > haven't taken the time to look more into things this summer due to other > > committments, but I hope to ramp back up again pretty quick on things. > > As far as cron goes, it'll do all the old cron jobs when it comes up (or > > at least it's supposed to.) If you're worried about old cron jobs > > getting queued up, either disable cron or don't leave your laptop > > suspended for more than 48 hours. :) > > But Michael says: > > > The system syncs on suspend, and snaps the clock when it resumes, so that > > missed cron jobs are just lost. Filesystems aren't marked clean, as that > > requires an unmount. Some PCC's require reinitialisation coming out of > > a suspend (and removing a card while suspended can cause grief), and > > support for that is in place but not implemented. > > Which is correct? I should have said "I think missed cron jobs are lost". I've never pulled mine out of suspend and had it go nuts cron-wise; but I reserve the right to be totally wrong. > You also said that the system might NOT do a sync on suspend, which > concerns me. I don't have my system here, so I can't verify this, but again I'm _fairly_ sure that it does. YMMV; I would suggest trying it 8) > Also, in response to my question about the existence of a 3C562 driver, you > said: > > > No, and I don't think you'll find one very soon. The support for > > 'sharing' interrupts doesn't work very well (at all?) right now, and > > given the task of making the existing code work better I don't see it > > happening anytime soon. > > But Michael affirmed that it might be possible to write a combination > driver that links parts of the SIO and 3Com PCMCIA Ethernet code. (Because > it would be one driver, it could dispatch the interrupts to routines from > the existing drivers.) What do you think? I guess this is a difference of interpretation. Nate can't see it happening soon because it's low on his list; I can see you doing it if you persevere with FreeBSD just because it's necessary 8) > --Brett -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609180701.QAA04623>