date:20191213

RCA Cable to USB Video input device

2019-12-13 Thread Marc Shapiro

I want to copy some videos from VCR and DVD to my computer for editing 
(simple stuff, like removing commercials).  I found this device on Amazon:



https://www.amazon.com/Digital-Converter-Capture-Support-Android/dp/B06X42H9VZ/ref=sr_1_3?m=A3ENZ260X3A00C=ATVPDKIKX0DER=1576302348=merchant-items=1-3=1


It says in the title that it works on Linux, and at least one of the 
reviews says it works on Debian.



There seem to be a lot of sellers with what looks like this exact same 
device.


Does anyone know anything about this device, or other, similar devices.  
Is it likely to require specialized drivers, or would generic drivers be 
able to access it?


Any suggestions on editing software would also be appreciated.  I have 
done simple audio editing before, but not video.  Would the editing 
software read the data directly from the USB port, or would I need to 
access the port with other software/commands.  I don't mind using the 
command line to access the port and save the file, if necessary.



Marc

Re: apparent change in hostnames on LAN without admin intervention

2019-12-13 Thread john doe

On 12/14/2019 1:33 AM, Jape Person wrote:
> Hi folks. Did I miss something?
>
> I've had 3 Sid/testing systems running on the same LAN behind the same
> router for just shy of 3 years. Their static IP addresses have always
> been issued by the DHCP server on the router. Everything has been
> copacetic among the systems, with local and outside name resolution
> working with no issue.
>
> A little over a week ago the systems stopped being able to access each
> other by name. No changes were made in the settings or firmware of the
> router or of the local network settings on the systems.
>
> I discovered that all of the hostnames had changed from xx.local to
> xx. I've tried to determine the cause of this alteration in the
> hostnames on the LAN.
>
> Everything is working fine now that I've stopped trying to call the
> systems by the old xx.local names.
>
> Could this change be due to recent upgrades in software? (I upgrade
> every day.) I've reviewed the recent upgrades listed in
> /var/log/apt/history.log. I would have thought any deliberate change of
> this behavior would have been flagged by listchanges, but I can't find it.
>
> I'm just a home user / hobbyist, but this change occurring without any
> deliberate administrative action on my part makes the hairs stand up on
> my neck -- just a little bit.
>
> Advice or consolation would be welcomed.
>

Assuming that you are using the router from your ISP, it is possible
that the firmware has been upgraded without your nolage.

One way to prevent this could be (1), that is, use your own
router/server/gateway so you control everything on your LAN.

I use an EMTA modem only from my ISP which is plugged into a perimiter
firewall.

If you can't have an modem from your ISP, look at 'bridgemode'.

If your not comfortable building your server from scratch, you can
simply buy a router that is accepted by your ISP .

In other words, you need to choose one or the other if you go this way:
- Modem connected to router (most flexible of all)
- Combo modem/router in one box (les flexible but is more compact)

If you use DHCP static lease, you should look at what the DHCP server is
providing as hostname and 'TLD', and also in the dhcp client (dhclient'
to see what you get from the DHCP server.

The file '/etc/resolv.conf' should let you know what TLD is sent from
the DHCP server.

Debian shouldn't modify your configuration files '/etc' without your nolage.

Note that the TLD '.lan' is sometime used.

1)  https://www.xfinity.com/support/articles/list-of-approved-cable-modems

--
John Doe

Re: how to have a common prompt in bash and guake so I can view date and time as part of prompt ?

2019-12-13 Thread Vipul

> if [ "$color_prompt" = yes ]; then
> 
> PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\$
> '

You forgot to add "\d", in PS1 value, that explains different behavior
of prompt in console and Guake.

May be, this could fix the problem


if [ "$color_prompt" = yes ]; then

PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:
\d \t \[\033[01;34m\]\w\[\033[00m\$'
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h: \d \t \w\$'
fi


Now, as Wooledge suggested, replace "\d \t" with "$(date +"%d %b %Y
%H:%M:%S")".

Re: apparent change in hostnames on LAN without admin intervention

2019-12-13 Thread Jape Person

On 12/13/19 8:55 PM, David Wright wrote:

On Fri 13 Dec 2019 at 19:33:51 (-0500), Jape Person wrote:

Hi folks. Did I miss something?

Perhaps a couple of references:
https://features.icann.org/addressing-new-gtld-program-applications-corp-home-and-mail
which points out that any of .home, .mail and .corp are ideal for the
domain name of a home LAN, and RFC 6762 on Multicast DNS which
explains why .local is not a good choice.

Thank you very much, David. I'll dig into the documentation.

I could be quite wrong, but I thought that "local" was actually suggested as a domain name at one
time by the installer. (And I could be remembering a different distro, though I've been using Debian
for a long time -- at least 10 years, I think.) I suppose I just continued to use it over the years
out of habit.

I've had 3 Sid/testing systems running on the same LAN behind the same
router for just shy of 3 years. Their static IP addresses have always
been issued by the DHCP server on the router. Everything has been
copacetic among the systems, with local and outside name resolution
working with no issue.

A little over a week ago the systems stopped being able to access each
other by name. No changes were made in the settings or firmware of the
router or of the local network settings on the systems.

I discovered that all of the hostnames had changed from xx.local
to xx. I've tried to determine the cause of this alteration in the
hostnames on the LAN.

Everything is working fine now that I've stopped trying to call the
systems by the old xx.local names.

Could this change be due to recent upgrades in software? (I upgrade
every day.) I've reviewed the recent upgrades listed in
/var/log/apt/history.log. I would have thought any deliberate change
of this behavior would have been flagged by listchanges, but I can't
find it.

I'm just a home user / hobbyist, but this change occurring without any
deliberate administrative action on my part makes the hairs stand up
on my neck -- just a little bit.

Advice or consolation would be welcomed.

I tried .local quite a long while ago but it didn't work too well.
I don't know where the problem lay, and I got along with no domain
name for a longish period, but changed to .corp after I read the
first reference above. It stopped exim4 complaining too.

I have noticed that the speed of interactions (like logging on to ssh session, pinging, etc.) have
improved since .local went away.

But is it possible you've started using avahi/bonjour when previously
you didn't? Or has the router upgraded itself and now knows not to
issue names like that?

I'll check to see if avahi/bonjour are being used, but I haven't done anything deliberately to start
using them. I'm wondering if recent changes to CUPS may be implicated in some way. My Brother
printer defaults to using bonjour, but I turned it off because I deemed it to be not particularly
useful to me. It's connected by wire to the router. I live in a condo where I can see at least three
dozen (no kidding) printers advertising their services. I'm getting ready to switch everything to
wired connections.

53 matches

Mail list logo