> On Monday 11 June 2018 18:42:41 Kate Draven wrote:
>
> > > Kate Draven wrote:
> > > > Hi people (and others)
> > >
> > > I am not aware that cats are members of this list :)
> > >
> > >
> > > --------------------------------------------------------------------
> > >-
> >
> > If cats had their way, they would be overlords.
> > And yes, they have infiltrated the organization.
> >
> > Kate
>
> And they, I take it, have delegated the food bowl and excrement pan
> maintenance to you? Its a dirty job, but I suppose somebody has to do
> it.
>
> --
> Cheers, Gene Heskett
> --
And I have to feed them too...
So, not takers on how to disable auto mounting of external HDs?
Kate
> On Monday 11 June 2018 16:51:26 Kate Draven wrote:
> > > On Monday 11 June 2018 18:42:41 Kate Draven wrote:
> > > > > Kate Draven wrote:
> > > > > > Hi people (and others)
> > > > >
> > > > > I am not aware that cats are members of this list :)
> > > > >
> > > > >
> > > > > --------------------------------------------------------------------
> > > > >-
> > > >
> > > > If cats had their way, they would be overlords.
> > > > And yes, they have infiltrated the organization.
> > > >
> > > > Kate
> > >
> > > And they, I take it, have delegated the food bowl and excrement pan
> > > maintenance to you? Its a dirty job, but I suppose somebody has to do
> > > it.
> > >
> > > --
> > > Cheers, Gene Heskett
> > > --
> >
> > And I have to feed them too...
> >
> > So, not takers on how to disable auto mounting of external HDs?
> >
> > Kate
> >
>
> I believe that you can disable automounting by opening up Konqueror:
> media:/
> Right-click on the icon for that item, then you can go to
> Properties > Mounting
> and check your mount options.
>
> Try doing as your username first; if you still have problems, then open up
> Konqueror as root:
> tdesu konqueror
> and try again. (Of course, all the usual precautions about running anything
as
> root.) Messing up your mount options can make external HDDs a headache.
>
> If this doesn't work, then you probably want to examine these files:
> /etc/fstab
> /etc/mtab
> However, I try not to mess with these, if everything else has been running
> fine until now. If you try to disable automount for a new HDD, you may
> inadvertently change mounting options for other drives, which will be worse.
>
> Bill
>
>
>
> ---------------------------------------------------------------------
Thanks lad, I'll give it a go in the morning.
Update everyone then.
Kate
> On Monday 11 June 2018 19:51:26 Kate Draven wrote:
>
> > > On Monday 11 June 2018 18:42:41 Kate Draven wrote:
> > > > > Kate Draven wrote:
> > > > > > Hi people (and others)
> > > > >
> > > > > I am not aware that cats are members of this list :)
> > > > >
> > > > >
> > > > > ----------------------------------------------------------------
> > > > >---- -
> > > >
> > > > If cats had their way, they would be overlords.
> > > > And yes, they have infiltrated the organization.
> > > >
> > > > Kate
> > >
> > > And they, I take it, have delegated the food bowl and excrement pan
> > > maintenance to you? Its a dirty job, but I suppose somebody has to
> > > do it.
> > >
> > > --
> > > Cheers, Gene Heskett
> > > --
> >
> > And I have to feed them too...
> >
> > So, not takers on how to disable auto mounting of external HDs?
> >
> > Kate
> >
> Heck, right now I've two, decade old red sata, both of which has succumed
> to the ravages of the red dye used in the cable. So before I can update
> from wheezy, I'll have to find someplace that has sata cables that
> aren't that hot red color. If you have some red ones in your systems,
> order replacements that are any color but red, because you WILL replace
> the reds ones sooner or later, usually under 5 years later.
>
> Thats another way of saying I am not automounting 2 of the 3 drives in a
> hot swap cage.
>
> Now we're back on topic, sorta, but I'm no help. But I also have a very
> faded memory of doing something in /lib/udev/rules.d to stop that, but
> its much of a half decade back up the log and even then my short term
> memory was starting to get fuzzy. And I don't see an obviously out of
> date, newer version of anything disk related in /lib/udev/rules.d. That
> may not be where I putzed with it. Poor memory, the curse of the
> so-called golden years.
>
> What ever, it was interfering with the blkid based mounting
> in /etc/fstab.
>
> --
> Cheers, Gene Heskett
> --
I was thinking the same thing, using blkid, but I have to first deal with the
dreaded automount. The problem with that is, the drives are never the same.
These are client drive (mostly crackmonkeys) in need of data retrieval.
Someone will have an answer.
As for ancient computers. Glad to see I'm not the only Dr Frankenstein here.
Me first computer was comprised of about 27 different computers I found in
the rubbish over a period of months about 30 something years back. Still
doing it, I've built some amazing machines. A lot of them even worked without
blazing into a fireballs.
Kate
> said Kate Draven:
>
> | If cats had their way, they would be overlords.
> | And yes, they have infiltrated the organization.
>
> yes. and have produced the well-known mail client "claws."
> --=20
> dep
>
Only Hypno Toad can save us now.
Kate
> Kate Draven wrote:
>
> > Hi people (and others)
>
> I am not aware that cats are members of this list :)
>
>
> ---------------------------------------------------------------------
If cats had their way, they would be overlords.
And yes, they have infiltrated the organization.
Kate
> I'm using the source code for the open-source Thompson-Davis Editor
> <http://adoxa.altervista.org/tde/>, "a simple, public domain, multi-file,
> multi-window binary and text file editor written for IBM PCs and close
> compatibles running DOS, Win32 (console) or Linux" to learn C and curses
> programming.
> You may have noticed its coincidental acronym :-) and yes, it stores it's
> configuration information in $TDEHOME. TDE is small but non-trivial, and I
> think it will be a good resource for someone like me, who is attempting to
> get a grip on programming in the *nix environment; it's not so big as to be
> overwhelming, yet not as useless as HelloWorld.c.
> Thoughts?
>
> Leslie
>
>
>
> ---------------------------------------------------------------------
I say any (almost any) learning experience is a good one.
Go for it.
Kate
> I'm not sure if this is problem that specifically concerns Trinity. I
> generally burn CDs and DVDs with k3b, and almost never use any other
program.
> (I'm using the k3b-trinity packages.) I considered trying to use the
> non-Trinity version of k3b, or to boot into a KDE desktop instead of TDE, to
> see if that works. However, I also tried with Brasero, and had similar
> problems, so I'm guessing that the problem is not just with Trinity.
>
> No problem at all burning DVDs, including dual-layer. (I don't know about
> Blu-Ray, but I don't use them.) Whenever I try to burn CDs, however, k3b
goes
> through the whole process, creating image, normalisation, etc., then crashes
> before it actually burns the CD.
>
> I ought to say that these are audio CDs. I've tried burning flac and wav
files
> to CD, both with the same bad results. Also, a few weeks back, I tried to
> copy a large collection of mp3 files to a DVD as a data disc, but the
program
> crashed before it could complete, and ruined the disc. I don't know if that
> incident could be related or not.
>
> It occurs to me to try to write a CD from the command-line, using growisofs
or
> the like, but I've never done that before.
>
> I'm running Debian Jessie 8.8.0 and Trinity r14.04.
>
> Any help or observations would be appreciated.
>
> Bill
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net> For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
> Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
> Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
>
1. You likely did this but just in case, just k3b's perms setup/
2. Check all related perms (dvdrecord, cdr* etc).
3. See if you can complete a burn as root (if you can, it's a perm problem)
4. Also try burning at half the adverted speed.
Because of today's corner cutting standards, disks are not always adverted
speeds.
Let us know what happens and good luck,
Kate
I like the desktop for Jessie, I don't feel like I'm missing anything by
using it and I'm experiencing a reproducible bug that's shared by others
in ASCII/Stretch and it gets worse using the Plasma Desktop and would
like to test the problem with TDE for Jessie. The problem is screen
blackouts both audio and video using HDMI on a smart tv, the blackouts
come and go, come and go, short blackouts using TDE and long blackouts
using Plasma.
Thank,
--
Jimmy Johnson
Devuan Jessie - TDE Trinity R14.0.4 - AMD A8-7600 - EXT4 at sda2
Registered Linux User #380263
Upgraded from Jessie + TDE Stable to Stretch + TDE PSB. Upgraded
cleanly. On first attempt TDE ran some kind of XDG compliance
enforcer.
TDM starts and I can log in. TDE spends half a minute or so
saying "starting desktop" in the usual way but then I'm left
with nothing but the cursr and a blue background.
The only anomaly I've found thus far in the logs is (IIRC) an
ASSERT of "primary_set" from randr.
Any suggestions, tips, or hints would be welcome. Difficult
to answer questions as without KMail it is taking me several
attempts to type perfect headers into telnet that the list
software will accept.
I have recent backup as a last resort but am hoping for a
way forward.
Thanks,
--Mike
Hi all,
HP Probook 6475b, Debian 9 (stretch) (MX 17.1 actually), TDE 14.0.5. The
volume buttons will move the onscreen indicator between 0% and 10%, but no
farther, and the volume setting is unaffected. The volume buttons work fine
in XFCE. Any ideas where to look for the problem?
Thanks.