I did reply though I'm not sure what the likelihood of me making meetings is,
my time is pretty tightly constrained but it would be nice to at least
occasionally make a meeting.
Frank
> -Original Message-
> From: PLUG [mailto:plug-boun...@pdxlinux.org] On Behalf Of Russell Senior
> Sent
> I have spent months inquiring about the future of PSU as a PLUG venue and have
> nothing conclusive.
>
> I know that public transportation is important to many of you.
>
> Please advise if this address is easily accessible for you:
>
> 5500 SW Dosch Rd, Portland, OR 97239
That's pretty close
I've long been frustrated with heating and cooling at our house. The
thermostat has trouble dealing with Portland weather (need heating one day,
cooling the next). Also, with our house being a super-insulated new build,
the house doesn't naturally cool down at night. I know we could install a
smart
> Remote conferencing is becoming more important for businesses. I've not
used
> any computer-connected video camera.
>
> I'd like suggestion on what to buy and which software I should learn.
I've just been using the camera in my laptop for years. It works pretty
well, though a bit annoying bec
I have a flash drive I similarly sent through the laundry. I didn't do
anything special and I'm no longer even sure which one it was, but I did use
it after and it was fine (and likely still fine, every once in a while, when
looking for things I wind up checking out all my flash drives, if one was
> > Hmm, the crash must be causing open but unlinked inodes to be lost,
>
> Frank,
>
> I assume this is the case. When the system reboots (and it's been >200
days) the
> kernel forces a filesystem check (it's ext3 on this host).
>
> The reason I asked is curiosity what, other than a system cra
> On Fri, 28 Jun 2019, Frank Filz wrote:
>
> > How are you seeing orphaned inodes?
>
> Frank,
>
> When the kernel runs fsck on partitions.
>
> > If the filesystem transactions aren't working right, an orphan inode
> > could occur if there was a
> What happens to cause inodes to become orphaned? I assume the parents
> aren't deported from the system ... or are they?
How are you seeing orphaned inodes?
An orphan inode should be visible somehow if it represents an open but
unlinked file, in that case, that inode will disappear automaticall
> Wow,
> That brings back fond memories, model 28 and model 35 Teletype machines
and
> loading DEC machines with paper tape. Then there were the "high speed"
paper
> readers and punches at 1200 baud. Also had to deal with both 5 and 8 level
> codes. Have not seen any of that in ages. Used to have a
> I am trying to rid of some old junk - and found unopened, unused, shrink
> wrapped WinXP SP1 installation disk with the installation guide, etc.
books
> Anybody needs/wants it?
>
> This proposition is/sounds pretty bad, particularly on this email list
> - but there seems to be some old stuff
> I agree with the ESD idea. I set up my 'scope with an unshielded DMM
probe
> lead spread across the desk in front of the keyboard. I can see very fast
events
> in the few volt range, but what seems to trigger the wake from suspend are
> slower, lower events. No solid correlations, however. An
> On Thu, Nov 16, 2017 at 6:54 AM, Frank Filz
> wrote:
>
> >> For me, its the simplicity of it, and the legacy of it working for a
> >> long time, and the utter lack of modern best practices documentation.
> >> If you go looking for NFS howto's, you alm
ions better.
> >>
> >> Why not standard (these days) NFS v4? Are you avoiding it because of
> >> the name spaces preventing you mounting the exports exactly the same
> >> way as in
> >> v2 or v3?
> >>
> >> Just curious what motivates people
> Or maybe nfs3 with udp.
You need to be careful of NFS with UDP on high speed networks (Gigabit or
faster), the fragment lifetime is long enough for the 16 bit packet id to
wrap, and the result is painfully slow data transfer with a significant
possibility of data corruption (the checksum is also
14 matches
Mail list logo
