Re: Recommended SSDs and 4-bay internal dock

2023-01-11 Thread David Christensen

On 1/11/23 06:58, Tom Browder wrote:

I plan to install a 4-bay, hot swappable SSD dock to replace the existing
DVD in my only 5.5" externally accesible bay.  To fill it, I will get up to
four 2.5 inch SSDs of 1 Tb: MX500 by Crucial. My plan is to use the SSDs
for backup, but not in a RAID configuration.

I would appreciate opinions on my choice of SSD, as well as which brand of
dock is recommended: ICY DOCK versus StarTech. On Amazon, the ICY DOCK
mentions a lithium battery but the StarTech doesn't, and I'm not sure why
it's needed.

Thanks.

-Tom



I have been using StarTech drive racks for many years.  Out of two dozen 
or so 3.5" HDD racks over the past ~20 years, perhaps a half dozen fans 
wore out and one PCB died.  All the other issues were drives, cables, 
HBA's, and/or PEBKAC.



As other readers have mentioned, failure modes of HDD's are reasonably 
well understood; as are recovery options.  AIUI solid-state devices are 
all-or-nothing -- they work and then they become bricks.  I use internal 
3.5" HDD's in ZFS mirrors for live data, backups, archives, and images. 
I also use single 3.5" HDD's in StarTech DRW150SATBK racks for near-site 
and off-site duplicates.  The speed of SSD's is appealing for remote 
site work, but I would want two SSD's for safety.



David



Re: need kino. or a substitute that can work with a sonyhi-8metal720 by handicam.

2023-01-11 Thread gene heskett

On 1/11/23 18:55, Greg Wooledge wrote:

On Wed, Jan 11, 2023 at 06:45:15PM -0500, gene heskett wrote:

fw0 is probably the card itself, fw0 is still there if the camera is
unplugged. And has been there since 12/23/22 when I last rebooted. I have to
plug it into the camera AND turn it on to get fw1.  Owned by root:video, and
there is no user "video" in /etc/group or /etc/passwd. WT 


There should be a group named video in /etc/group.  This is a standard
Debian group name, placed there during installation.  It originates in
the /usr/share/base-passwd/group.master file, and is copied to /etc/group
by the base-passwd.postinst script, if the /etc/group file is not
already present.

During a standard installation, the "initial user" (the one created during
installation, with UID 1000) gets added to this group.

unicorn:~$ grep video /etc/group
video:x:44:greg

Perhaps you're looking at one of your non-Debian systems, in which case
the groups may be different.

.
debian bullseye, and I didn't scroll down far enough in /etc/group, 
video is there and I'm a member.  So there is another blocker somewhere.
dmesg is fussing it can't read the firmware or something like that, 
maybe the card has puked? IDK

dmesg says:

[1676013.767923] firewire_core :06:00.0: rediscovered device fw0
[1676013.767934] firewire_core :06:00.0: phy config: new root=ffc1, 
gap_count=5

[1676014.279918] firewire_core :06:00.0: rediscovered device fw0
[1676014.371301] firewire_core :06:00.0: created device fw1: GUID 
08004601044684e4, S100
[1676016.871908] firewire_core :06:00.0: giving up on node ffc0: 
reading config rom failed: bus reset


Thank You.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: need kino. or a substitute that can work with a sony hi-8metal720 by handicam.

2023-01-11 Thread gene heskett

On 1/11/23 18:25, Jeffrey Walton wrote:

On Wed, Jan 11, 2023 at 5:47 PM Klaus Singvogel
 wrote:


gene heskett wrote:

Installed all that I *think* about 30 pkgs, dmesg says new device fw1, and
it exists now in /dev/, but VLC can't open device, see logs but other than
the plug in report, no connection.


The advice of Jeffrey Walton to change the permission would be my first help 
too.

fw1 indicates to be a FireWire device, so I'm out; never possessed one.

But I stumble about the uncommon naming: usually it's fw0, not fw1.
Do you have a second FireWire device already plugged in, or can the naming 
somehow else be explained (by slot number)?
If not, I would suggest a reboot of the machine, because I assume a jam in the 
kernel then.

But as said, no experience here.

Maybe someone else can step in?


It didn't occur to me fw was firewire. According to this old Ubuntu
page, there is a firewire group.[1] I can't find a similar Debian wiki
page.

If Gene is already in the firewire group, then I would look at udev
rules. udev may be setting permissions to root:root instead of
root:firewire.


Its setting perms to root:video, and video does not exist in /etc/group.

Now what?

Thank you.



[1] https://help.ubuntu.com/community/FireWire/oldPages/Firewire01

Jeff

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: need kino. or a substitute that can work with a sony hi-8metal720 by handicam.

2023-01-11 Thread Greg Wooledge
On Wed, Jan 11, 2023 at 06:45:15PM -0500, gene heskett wrote:
> fw0 is probably the card itself, fw0 is still there if the camera is
> unplugged. And has been there since 12/23/22 when I last rebooted. I have to
> plug it into the camera AND turn it on to get fw1.  Owned by root:video, and
> there is no user "video" in /etc/group or /etc/passwd. WT 

There should be a group named video in /etc/group.  This is a standard
Debian group name, placed there during installation.  It originates in
the /usr/share/base-passwd/group.master file, and is copied to /etc/group
by the base-passwd.postinst script, if the /etc/group file is not
already present.

During a standard installation, the "initial user" (the one created during
installation, with UID 1000) gets added to this group.

unicorn:~$ grep video /etc/group
video:x:44:greg

Perhaps you're looking at one of your non-Debian systems, in which case
the groups may be different.



Re: need kino. or a substitute that can work with a sony hi-8metal720 by handicam.

2023-01-11 Thread gene heskett

On 1/11/23 17:47, Klaus Singvogel wrote:

gene heskett wrote:

Installed all that I *think* about 30 pkgs, dmesg says new device fw1, and
it exists now in /dev/, but VLC can't open device, see logs but other than
the plug in report, no connection.


The advice of Jeffrey Walton to change the permission would be my first help 
too.

fw1 indicates to be a FireWire device, so I'm out; never possessed one.

But I stumble about the uncommon naming: usually it's fw0, not fw1.
fw0 is probably the card itself, fw0 is still there if the camera is 
unplugged. And has been there since 12/23/22 when I last rebooted. I 
have to plug it into the camera AND turn it on to get fw1.  Owned by 
root:video, and there is no user "video" in /etc/group or /etc/passwd. 
WT 



Do you have a second FireWire device already plugged in, or can the naming 
somehow else be explained (by slot number)?
If not, I would suggest a reboot of the machine, because I assume a jam in the 
kernel then.

But as said, no experience here.

Maybe someone else can step in?

Best regards,
Klaus.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: need kino. or a substitute that can work with a sony hi-8 metal720 by handicam.

2023-01-11 Thread Jeffrey Walton
On Wed, Jan 11, 2023 at 5:47 PM Klaus Singvogel
 wrote:
>
> gene heskett wrote:
> > Installed all that I *think* about 30 pkgs, dmesg says new device fw1, and
> > it exists now in /dev/, but VLC can't open device, see logs but other than
> > the plug in report, no connection.
>
> The advice of Jeffrey Walton to change the permission would be my first help 
> too.
>
> fw1 indicates to be a FireWire device, so I'm out; never possessed one.
>
> But I stumble about the uncommon naming: usually it's fw0, not fw1.
> Do you have a second FireWire device already plugged in, or can the naming 
> somehow else be explained (by slot number)?
> If not, I would suggest a reboot of the machine, because I assume a jam in 
> the kernel then.
>
> But as said, no experience here.
>
> Maybe someone else can step in?

It didn't occur to me fw was firewire. According to this old Ubuntu
page, there is a firewire group.[1] I can't find a similar Debian wiki
page.

If Gene is already in the firewire group, then I would look at udev
rules. udev may be setting permissions to root:root instead of
root:firewire.

[1] https://help.ubuntu.com/community/FireWire/oldPages/Firewire01

Jeff



Re: need kino. or a substitute that can work with a sony hi-8 metal720 by handicam.

2023-01-11 Thread Klaus Singvogel
gene heskett wrote:
> Installed all that I *think* about 30 pkgs, dmesg says new device fw1, and
> it exists now in /dev/, but VLC can't open device, see logs but other than
> the plug in report, no connection.

The advice of Jeffrey Walton to change the permission would be my first help 
too.

fw1 indicates to be a FireWire device, so I'm out; never possessed one.

But I stumble about the uncommon naming: usually it's fw0, not fw1.
Do you have a second FireWire device already plugged in, or can the naming 
somehow else be explained (by slot number)?
If not, I would suggest a reboot of the machine, because I assume a jam in the 
kernel then.

But as said, no experience here.

Maybe someone else can step in?

Best regards,
Klaus.


-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27



Re: quite the end of an era: Re: Bug#931659: transition: rm python2

2023-01-11 Thread Greg Wooledge
On Wed, Jan 11, 2023 at 10:42:31PM +, Tim Woodall wrote:
> On Tue, 10 Jan 2023, songbird wrote:
> 
> >  kudoes to everyone who helped with this in getting it done, finding
> > bugs, fixing problems, converting code, updating docs and testing.  :)
> > 
> 
> What does debian use for moinmoin? Is the debian wiki stuck on buster?

I was wondering exactly the same thing, a few months ago.  I asked on
the Libera #debian IRC channel, and nobody knew.  (Fair enough.)

 shows the Python version:
2.7.16 (default, Oct 10 2019, 22:02:15) [GCC 8.3.0]

This is precisely the same as mine shows, and mine is running on buster.
So my tentative conclusion is that wiki.debian.org is still hosted on
a buster machine (virtual or physical).  I'm wondering what the path
forward is for us.



Re: quite the end of an era: Re: Bug#931659: transition: rm python2

2023-01-11 Thread Tim Woodall

On Tue, 10 Jan 2023, songbird wrote:


 kudoes to everyone who helped with this in getting it done, finding
bugs, fixing problems, converting code, updating docs and testing.  :)



What does debian use for moinmoin? Is the debian wiki stuck on buster?




Re: need kino. or a substitute that can work with a sony hi-8 metal720 by handicam.

2023-01-11 Thread Jeffrey Walton
On Wed, Jan 11, 2023 at 3:08 PM gene heskett  wrote:
>
> On 1/11/23 12:17, Klaus Singvogel wrote:
> > gene heskett wrote:
> >> What happened to kino? That was an all in one package, and while kdenlive 
> >> is
> >> pretty, it can't capture from the camera...
> >
> > Thought everyone is using VLC for video stuff.
> > At least vlc is capable to do so, see screenshot.
> >
> Installed all that I *think* about 30 pkgs, dmesg says new device fw1,
> and it exists now in /dev/, but VLC can't open device, see logs but
> other than the plug in report, no connection.
>
> I'm plumb green as grass. And spoiled by my experience with kino from
> years back. Help!

I would check which group owns the new device in /dev, and then make
sure you are part of that group.

I often encounter a similar problem when trying to use a modem for
Caller Id. I forget to put myself in the dialout group, and I can't
open the modem.

Jeff



Re: PowerBook G4 OS

2023-01-11 Thread Bob Crochelt
On Wed, Jan 11, 2023 at 09:59:48AM +0100, didier gaumet wrote:
> Le mardi 10 janvier 2023 à 16:32 -0800, Bob Crochelt a écrit :
> > > 
> > Thanks to all who replied.  I appreciate the help and advice.  Think
> > I
> > will just sit tight with the system, as it works fine for what I
> > need:
> > email, a little (slow surfing) and some note writing.
> > 
> > I imagine you have saved me many hours of frustration.
> > 
> > Regards
> > Bob Crochelt
> 
> Hello,
> 
> That would leave you with unmaintained software, though, with obvious
> risks accessing the internet (web, mail, etc...)
> 
> Debian port for a Powerbook G4 is unofficial and I don't know the
> actual state of this port.
> 
> NetBSD, OpenBSD and FreeBSD all seem to have an active and official
> port for the PowerPC G4.
> 
>
Thanks for this information.  I was aware that Jessie is not maintained;
that was the reason for my inquiry.  I will look into your suggestions
Regards
Bob Crochelt



ndiswrapper (was: Re: Drivers for old Packard Bell scanner needed?)

2023-01-11 Thread rhkramer
On Wednesday, January 11, 2023 11:11:04 AM daven...@tuxfamily.org wrote:
> Isn't ndiswrapper specific to networking/wireless network drivers?
> I don't think it just works for any kind of drivers. AS far as I can
> tell, it was designed specifically for WiFi cards.

I used it for Ethernet (not WiFi) cards back in the day.

-- 
rhk 

(sig revised 20221206)

If you reply: snip, snip, and snip again; leave attributions; avoid HTML; 
avoid top posting; and keep it "on list".  (Oxford comma (and semi-colon) 
included at no charge.)  If you revise the topic, change the Subject: line.  
If you change the topic, start a new thread.

Writing is often meant for others to read and understand (legal documents 
excepted?) -- make it easier for your reader by various means, including 
liberal use of whitespace (short paragraphs, separated by whitespace / blank 
lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and 
references.

If someone has already responded to a question, decide whether any response 
you add will be helpful or not ...

A picture is worth a thousand words.  A video (or "audio"): not so much -- 
divide by 10 for each minute of video (or audio) or create a transcript and 
edit it to 10% of the original.

A speaker who uses ahhs, ums, or such may have a real physical or mental 
disability, or may be showing disrespect for his listeners by not properly 
preparing in advance and thinking before speaking.  (Remember Cicero who did 
not have enough time to write a short missive.)  (That speaker might have been 
"trained" to do this by being interrupted often if he pauses.)

A radio (or TV) station which broadcasts speakers with high pitched voices (or 
very low pitched / gravelly voices) (which older people might not be able to 
hear properly) disrespects its listeners.   Likewise if it broadcasts 
extraneous or disturbing sounds (like gunfire or crying), or broadcasts 
speakers using their native language (with or without an overdubbed 
translation).

A person who writes a sig this long probably has issues and disrespects (and 
offends) a large number of readers. ;-)
'



Re: need kino. or a substitute that can work with a sony hi-8 metal720 by handicam.

2023-01-11 Thread gene heskett

On 1/11/23 12:17, Klaus Singvogel wrote:

gene heskett wrote:

What happened to kino? That was an all in one package, and while kdenlive is
pretty, it can't capture from the camera...


Thought everyone is using VLC for video stuff.
At least vlc is capable to do so, see screenshot.

Best regards,
Klaus.
Installed all that I *think* about 30 pkgs, dmesg says new device fw1, 
and it exists now in /dev/, but VLC can't open device, see logs but 
other than the plug in report, no connection.


I'm plumb green as grass. And spoiled by my experience with kino from 
years back. Help!


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



AW: Topic: Problems with USB Sticks

2023-01-11 Thread Schwibinger Michael
Hello Cindy. Hello group.
Thank you for you email.

Sorry, I did it in a bad way describe.
I put the USB stick in, and I can see all files on the USB stick.
But I cannot destroy them.


Regards,
Sophie




Von: Cindy Sue Causey 
Gesendet: Samstag, 31. Dezember 2022 17:22
An: Debian Users 
Betreff: Re: Topic: Problems with USB Sticks

On 12/30/22, Joe  wrote:
> On Fri, 30 Dec 2022 21:16:31 +
> debian-u...@howorth.org.uk wrote:
>> >
>> > 1
>> > How can I repair USB stick which is readable but not writable?
>> >
>> > question 2
>> > What did I do wrong to create this problem?
>>
>> You didn't tell us what you actually did, and especially which bits
>> you think might be a mistake, so it's very difficult for us to answer
>> this question.
>>
>> For example, you might have hit them with a hammer, or connected them
>> to the wrong voltages, or washed them in a bath, or who knows what? Or
>> you might have plugged them in correctly but used some sequence of
>> commands that has caused a problem. But until you tell us what you
>> did, we can't know which bit was wrong!
>>
>
> I mentioned probably the simplest thing: failing to unmount before
> removal on a Windows machine. This sometimes causes problems which
> cause Linux to refuse to mount the device read/write. Windows can
> usually fix it, though I suppose there may be data loss. It's entirely
> possible that doing the same thing on Linux would sometimes cause
> similar problems.


Been there a couple times on a new secondhand hard drive this year.
Following tips regarding hiberfil.sys fixed it both times for me, but
the method comes with a harsh "this is your last ditch option" warning
about things like that data loss.

That's on a non-Linux system, by the way. Linux triggered the second
episode while while the affected partition was mounted only as a
resource for backing up images. It wasn't mounted as an operating
system.

There's a recovery partition that keeps getting mounted even though
I'm not touching it this week. I can't help wondering if that plays
some part in how that partition ended up locked down when it wasn't
used as the primary operating system..

Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *



AW: Topic: Problems with USB Sticks

2023-01-11 Thread Schwibinger Michael
Hello Joe. Hello group.
Thank you so much for your Emails.

How can I make an USB stick only readable but not writable?
How can I make an USB stick which is only readable again writable?


Thank you.


Regards,
Sophie



Von: Joe 
Gesendet: Freitag, 30. Dezember 2022 21:49
An: debian-user@lists.debian.org 
Betreff: Re: Topic: Problems with USB Sticks

On Fri, 30 Dec 2022 21:16:31 +
debian-u...@howorth.org.uk wrote:

> > Hello group. Hello Joe.
> > Thank you for your Email.
> >
> > Sorry, I did bad asking.
> > So I split the question.
> >
> > 1
> > How can I repair USB stick which is readable but not writable?
> >
> > question 2
> > What did I do wrong to create this problem?
>
> You didn't tell us what you actually did, and especially which bits
> you think might be a mistake, so it's very difficult for us to answer
> this question.
>
> For example, you might have hit them with a hammer, or connected them
> to the wrong voltages, or washed them in a bath, or who knows what? Or
> you might have plugged them in correctly but used some sequence of
> commands that has caused a problem. But until you tell us what you
> did, we can't know which bit was wrong!
>

I mentioned probably the simplest thing: failing to unmount before
removal on a Windows machine. This sometimes causes problems which
cause Linux to refuse to mount the device read/write. Windows can
usually fix it, though I suppose there may be data loss. It's entirely
possible that doing the same thing on Linux would sometimes cause
similar problems.

--
Joe



AW: Topic: Problems with USB Sticks

2023-01-11 Thread Schwibinger Michael
Hello Joe. Hello group.
Thank you for your Email.

We have about 10 or 20 USB sticks, and nearly every day everything is working 
fine.
But now we have 1 stick which is not accepted.
We could find out, you can read files, but you cannot write on the stick and 
you cannot destroy on the stick.

How can we make this stick writable again?


Thank you.


Regards,
Sophie




Von: debian-u...@howorth.org.uk 
Gesendet: Freitag, 30. Dezember 2022 21:16
An: debian-user@lists.debian.org 
Betreff: Re: Topic: Problems with USB Sticks

> Hello group. Hello Joe.
> Thank you for your Email.
>
> Sorry, I did bad asking.
> So I split the question.
>
> 1
> How can I repair USB stick which is readable but not writable?
>
> question 2
> What did I do wrong to create this problem?

You didn't tell us what you actually did, and especially which bits you
think might be a mistake, so it's very difficult for us to answer this
question.

For example, you might have hit them with a hammer, or connected them
to the wrong voltages, or washed them in a bath, or who knows what? Or
you might have plugged them in correctly but used some sequence of
commands that has caused a problem. But until you tell us what you did,
we can't know which bit was wrong!

> Thank you.
>
> Regards,
> Sophie



Re: Drivers for old Packard Bell scanner needed?

2023-01-11 Thread davenull

Hello

On 2023-01-11 15:39, David Wright wrote:

On Wed 11 Jan 2023 at 14:25:39 (+), Ottavio Caruso wrote:

Local charity shop sells a desktop scanner for next to nothing. I
could buy it and try it but it's very bulky and it's a long walk. So
I'd like to have a clue beforehand if it's supported.

The item is a Packard Bell Slimline PB 61428.

I googled it but haven't found anything relevant to Linux. The
packaging mentions Windows 98. I remember back in the day, the was a
wrapper for old Windows drivers, I can't remember its name.


Presumably you're thinking of ndiswrapper, which was also recommended
recently in https://lists.debian.org/debian-user/2023/01/msg00173.html


Isn't ndiswrapper specific to networking/wireless network drivers?
I don't think it just works for any kind of drivers. AS far as I can 
tell, it was designed specifically for WiFi cards.


But I have never used it. I'm not a huge WiFi fan/heavy user. And when 
I do use it, I've always used cards or USB dongles with native a 
GNU/Linux driver.




AFAICT this package did not make it into bullseye, and seems to have
fallen by the wayside:

https://tracker.debian.org/pkg/ndiswrapper


Or am I supposed to just plug it in and expect it to work?


That's outside my sphere of knowledge.

Cheers,
David.




Re: PowerBook G4 OS

2023-01-11 Thread Jeremy Hendricks
I second and recommend FreeBSD. I can’t guarantee it’ll just work but I had
a Sawtooth G4 years ago and it was great until the hardware died.

On Wed, Jan 11, 2023 at 1:18 PM Stefan Monnier 
wrote:

> > No, there is no release for this architecture. The architecture's state
> is
> > "unofficial" and the only branch is unstable/sid. This branch may or may
> not
> > work. If you want to use Debian unstable/sid just replace "jessie" with
> > "sid" in /etc/apt/sources.list and do:
>
> While Sven is right to point out that upgrading directly from Debian
> 8 to Sid is rather risky, and while it's important to clarify that Sid
> can indeed be broken, I believe this ends up sounding much more
> discouraging than it should: since there is still a `powerpc` ports
> being updated, you should expect that it *does* work.
>
> I think in your place, I would start  by trying to boot your current
> installation with Sid's kernel.  If that works, then I'd make a fresh
> install using `debootstrap` into a new partition (you can then try out
> the new install using `chroot` as well as using dual-boot).  Or maybe
> I'd start by cloning your current root partition, and then try my luck
> at a plain `apt full-upgrade`: in case of problem you can simply boot
> back into your original root partition.
>
>
> Stefan
>
>


Re: PowerBook G4 OS

2023-01-11 Thread Stefan Monnier
> No, there is no release for this architecture. The architecture's state is
> "unofficial" and the only branch is unstable/sid. This branch may or may not
> work. If you want to use Debian unstable/sid just replace "jessie" with
> "sid" in /etc/apt/sources.list and do:

While Sven is right to point out that upgrading directly from Debian
8 to Sid is rather risky, and while it's important to clarify that Sid
can indeed be broken, I believe this ends up sounding much more
discouraging than it should: since there is still a `powerpc` ports
being updated, you should expect that it *does* work.

I think in your place, I would start  by trying to boot your current
installation with Sid's kernel.  If that works, then I'd make a fresh
install using `debootstrap` into a new partition (you can then try out
the new install using `chroot` as well as using dual-boot).  Or maybe
I'd start by cloning your current root partition, and then try my luck
at a plain `apt full-upgrade`: in case of problem you can simply boot
back into your original root partition.


Stefan



Re: Recommended SSDs and 4-bay internal dock

2023-01-11 Thread piorunz

On 11/01/2023 14:58, Tom Browder wrote:
I plan to install a 4-bay, hot swappable SSD dock to replace the 
existing DVD in my only 5.5" externally accesible bay.  To fill it, I 
will get up to four 2.5 inch SSDs of 1 Tb: MX500 by Crucial. My plan is 
to use the SSDs for backup, but not in a RAID configuration.


I would appreciate opinions on my choice of SSD, as well as which brand 
of dock is recommended: ICY DOCK versus StarTech. On Amazon, the ICY 
DOCK mentions a lithium battery but the StarTech doesn't, and I'm not 
sure why it's needed.


I have exactly the same SSDs installed. Working in Btrfs Raid1 mode as 
/home in my desktop.


SMART data:
Device Model: CT1000MX500SSD1 (4096 bytes sector)
Power On: 1099 hours
Power Cycles: 213  (5 hours/cycle)
Temperature: 29 °C
Unused Reserve NAND Blocks: 56
Lifetime Used: 2%
Average Block-Erase Count: 33
Total Written: 71 TiB

Device Model: CT1000MX500SSD1 (4096 bytes sector)
Power On: 1095 hours
Power Cycles: 214  (5 hours/cycle)
Temperature: 29 °C
Unused Reserve NAND Blocks: 61
Lifetime Used: 2%
Average Block-Erase Count: 28
Total Written: 67 TiB

All good.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄



Re: need kino. or a substitute that can work with a sony hi-8 metal 720 by handicam.

2023-01-11 Thread Klaus Singvogel
gene heskett wrote:
> What happened to kino? That was an all in one package, and while kdenlive is
> pretty, it can't capture from the camera...

Thought everyone is using VLC for video stuff.
At least vlc is capable to do so, see screenshot.

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27


Re: Recommended SSDs and 4-bay internal dock

2023-01-11 Thread Linux-Fan

Jeremy Nicoll writes:


On Wed, 11 Jan 2023, at 14:58, Tom Browder wrote:
> I plan to install a 4-bay, hot swappable SSD dock to replace the existing
> DVD in my only 5.5" externally accesible bay.  To fill it, I will get up to
> four 2.5 inch SSDs of 1 Tb: MX500 by Crucial. My plan is to use the SSDs
> for backup, but not in a RAID configuration.

I can't advise on choice of dock etc, but I'm interested in the side issue
of how long an unpowered SSD can be assumed still to be holding
the data written to it.

Does one need (just) to mount the drive once in a while?  (How often?)

Or does one need (say) to read every file on the drive once, so that the
SSD controller can assess whether any data needs to be moved?

Or does one need to read every byte, allocated or not?


AFAIK one needs to _power_ the device every once in a while and keep power  
connected for some time. Then, the controller can dos all the necessary  
actions in the background.


A long time ago, companies claimed data retention for 10 years (that was:  
for SLC drives!). The latest figure that I am aware of was 1 year (maybe for  
TLC?). I think the trend is that manymanufacturers do not publish any data  
retention times for consumer drives (newly QLC) anymore. One can only guess  
or measurea.


For backup purposes, I believe the advantage of SSDs over HDDs is mostly  
that they are shock resistant. If this is of no concern, I'd prefer to  
backup to HDDs instead of SSDs because of the data retention issue and in  
general a higher chance of rescuing data from the drive in event of failure.


Here is an article from 2021 that shows some typical numbersas I  
remembered them. I do not know anything about this specific source's  
credibility, though:

https://www.virtium.com/knowledge-base/ssd-data-retention/

This entry seems to be rather pessimistic:
https://www.ibm.com/support/pages/potential-ssd-data-loss-after-extended-shutdown

IBM says that for enterprise drives (typically higher quality than consumer- 
grade drives) only three months of data retention are guaranteed at 40°C.  
And: This article is from 2021, too...


YMMV
Linux-Fan

öö


pgpjiKjHb2kfb.pgp
Description: PGP signature


need kino. or a substitute that can work with a sony hi-8 metal 720 by handicam.

2023-01-11 Thread gene heskett
What happened to kino? That was an all in one package, and while 
kdenlive is pretty, it can't capture from the camera...


Thanks all.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: Recommended SSDs and 4-bay internal dock

2023-01-11 Thread Tom Browder
On Wed, Jan 11, 2023 at 09:10 Dan Ritter  wrote:
…

> I have lots of MX500 1TB SSDs in service, and they are perfectly
> fine, largely unremarkable devices

…

> Thanks, Dan—good to know.
>

-Tom


Re: Drivers for old Packard Bell scanner needed?

2023-01-11 Thread David Wright
On Wed 11 Jan 2023 at 17:11:04 (+0100), daven...@tuxfamily.org wrote:
> On 2023-01-11 15:39, David Wright wrote:
> > On Wed 11 Jan 2023 at 14:25:39 (+), Ottavio Caruso wrote:
> > > Local charity shop sells a desktop scanner for next to nothing. I
> > > could buy it and try it but it's very bulky and it's a long walk. So
> > > I'd like to have a clue beforehand if it's supported.
> > > 
> > > The item is a Packard Bell Slimline PB 61428.
> > > 
> > > I googled it but haven't found anything relevant to Linux. The
> > > packaging mentions Windows 98. I remember back in the day, the was a
> > > wrapper for old Windows drivers, I can't remember its name.
> > 
> > Presumably you're thinking of ndiswrapper, which was also recommended
> > recently in https://lists.debian.org/debian-user/2023/01/msg00173.html
> 
> Isn't ndiswrapper specific to networking/wireless network drivers?
> I don't think it just works for any kind of drivers. AS far as I can
> tell, it was designed specifically for WiFi cards.
> 
> But I have never used it. I'm not a huge WiFi fan/heavy user. And when
> I do use it, I've always used cards or USB dongles with native a
> GNU/Linux driver.

You're probably right. It's probably jessie since I used it for a
WNDA3100 v2 dongle, when I had problems with one of my laptop's
wireless, and I'm so oversupplied with Cat5 ports and Netgear
Powerlines that I have no need to use it nowadays.

> > AFAICT this package did not make it into bullseye, and seems to have
> > fallen by the wayside:
> > 
> > https://tracker.debian.org/pkg/ndiswrapper
> > 
> > > Or am I supposed to just plug it in and expect it to work?
> > 
> > That's outside my sphere of knowledge.

Cheers,
David.


Re: Recommended SSDs and 4-bay internal dock

2023-01-11 Thread Jeremy Nicoll
On Wed, 11 Jan 2023, at 14:58, Tom Browder wrote:
> I plan to install a 4-bay, hot swappable SSD dock to replace the existing
> DVD in my only 5.5" externally accesible bay.  To fill it, I will get up to
> four 2.5 inch SSDs of 1 Tb: MX500 by Crucial. My plan is to use the SSDs
> for backup, but not in a RAID configuration.

I can't advise on choice of dock etc, but I'm interested in the side issue
of how long an unpowered SSD can be assumed still to be holding 
the data written to it.

Does one need (just) to mount the drive once in a while?  (How often?)

Or does one need (say) to read every file on the drive once, so that the 
SSD controller can assess whether any data needs to be moved?

Or does one need to read every byte, allocated or not?

-- 
Jeremy Nicoll - my opinions are my own.



Re: Recommended SSDs and 4-bay internal dock

2023-01-11 Thread Dan Ritter
Tom Browder wrote: 
> I plan to install a 4-bay, hot swappable SSD dock to replace the existing
> DVD in my only 5.5" externally accesible bay.  To fill it, I will get up to
> four 2.5 inch SSDs of 1 Tb: MX500 by Crucial. My plan is to use the SSDs
> for backup, but not in a RAID configuration.
> 
> I would appreciate opinions on my choice of SSD, as well as which brand of
> dock is recommended: ICY DOCK versus StarTech. On Amazon, the ICY DOCK
> mentions a lithium battery but the StarTech doesn't, and I'm not sure why
> it's needed.


I have lots of MX500 1TB SSDs in service, and they are perfectly
fine, largely unremarkable devices.

I have some ICY DOCK and Startech disk-related things; not very
many, and not the specific things you are looking for here. In
my experience, they are both perfectly fine.

-dsr-



Re: Drivers for old Packard Bell scanner needed?

2023-01-11 Thread Georgi Naplatanov

On 1/11/23 16:25, Ottavio Caruso wrote:
Local charity shop sells a desktop scanner for next to nothing. I could 
buy it and try it but it's very bulky and it's a long walk. So I'd like 
to have a clue beforehand if it's supported.


The item is a Packard Bell Slimline PB 61428.

I googled it but haven't found anything relevant to Linux. The packaging 
mentions Windows 98. I remember back in the day, the was a wrapper for 
old Windows drivers, I can't remember its name.


Or am I supposed to just plug it in and expect it to work?





Hi Ottavio,

this is a database with supported scanners by SANE - 
http://www.sane-project.org/sane-mfgs.html#Z-PACKARD-BELL


This scanner is not listed as a supported device.

Kind regards
Georgi



Recommended SSDs and 4-bay internal dock

2023-01-11 Thread Tom Browder
I plan to install a 4-bay, hot swappable SSD dock to replace the existing
DVD in my only 5.5" externally accesible bay.  To fill it, I will get up to
four 2.5 inch SSDs of 1 Tb: MX500 by Crucial. My plan is to use the SSDs
for backup, but not in a RAID configuration.

I would appreciate opinions on my choice of SSD, as well as which brand of
dock is recommended: ICY DOCK versus StarTech. On Amazon, the ICY DOCK
mentions a lithium battery but the StarTech doesn't, and I'm not sure why
it's needed.

Thanks.

-Tom


Re: Drivers for old Packard Bell scanner needed?

2023-01-11 Thread Dan Ritter
Ottavio Caruso wrote: 
> Local charity shop sells a desktop scanner for next to nothing. I could buy
> it and try it but it's very bulky and it's a long walk. So I'd like to have
> a clue beforehand if it's supported.
> 
> The item is a Packard Bell Slimline PB 61428.
> 
> I googled it but haven't found anything relevant to Linux. The packaging
> mentions Windows 98. I remember back in the day, the was a wrapper for old
> Windows drivers, I can't remember its name.

I would guess this is unlikely to work at all.

It predates any of the modern standards for scanning, and
Packard Bell was never a high-quality manufacturer, so it
probably doesn't conform to any of the older standards, either.

Honestly, a 24 year old consumer-grade scanner is not going to
be a good value even if it's free.

-dsr-



Re: Drivers for old Packard Bell scanner needed?

2023-01-11 Thread David Wright
On Wed 11 Jan 2023 at 14:25:39 (+), Ottavio Caruso wrote:
> Local charity shop sells a desktop scanner for next to nothing. I
> could buy it and try it but it's very bulky and it's a long walk. So
> I'd like to have a clue beforehand if it's supported.
> 
> The item is a Packard Bell Slimline PB 61428.
> 
> I googled it but haven't found anything relevant to Linux. The
> packaging mentions Windows 98. I remember back in the day, the was a
> wrapper for old Windows drivers, I can't remember its name.

Presumably you're thinking of ndiswrapper, which was also recommended
recently in https://lists.debian.org/debian-user/2023/01/msg00173.html

AFAICT this package did not make it into bullseye, and seems to have
fallen by the wayside:

https://tracker.debian.org/pkg/ndiswrapper

> Or am I supposed to just plug it in and expect it to work?

That's outside my sphere of knowledge.

Cheers,
David.



Re: Drivers for old Packard Bell scanner needed?

2023-01-11 Thread gene heskett

On 1/11/23 09:26, Ottavio Caruso wrote:
Local charity shop sells a desktop scanner for next to nothing. I could 
buy it and try it but it's very bulky and it's a long walk. So I'd like 
to have a clue beforehand if it's supported.


The item is a Packard Bell Slimline PB 61428.

I googled it but haven't found anything relevant to Linux. The packaging 
mentions Windows 98. I remember back in the day, the was a wrapper for 
old Windows drivers, I can't remember its name.


Or am I supposed to just plug it in and expect it to work?



Run, do not walk, to the nearest exit, taking your cash with you.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: Lien cassé sur le paquet apache2-data dist Bullseye et dépôt officiel http://ftp.debian.org

2023-01-11 Thread Erwan David

Le 11/01/2023 à 12:47, didier gaumet a écrit :
Euh, je ne connaissais pas cette couche ICAP(1) mais en gros ton 
problème me semble venir de là: elle considère (ou a considéré 
ponctuellement) le paquet Debian en question comme suspect car 
présentant trop de sous-niveaux d'archive?


(1) https://en.wikipedia.org/wiki/Internet_Content_Adaptation_Protocol




Moi je vois un "Vendor: Sophos" ça sent le proxy filtrant avec son 
antivirus.




Re: Lien cassé sur le paquet apache2-data dist Bullseye et dépôt officiel http://ftp.debian.org

2023-01-11 Thread didier gaumet
Euh, je ne connaissais pas cette couche ICAP(1) mais en gros ton 
problème me semble venir de là: elle considère (ou a considéré 
ponctuellement) le paquet Debian en question comme suspect car 
présentant trop de sous-niveaux d'archive?


(1) https://en.wikipedia.org/wiki/Internet_Content_Adaptation_Protocol



Lien cassé sur le paquet apache2-data dist Bullseye et dépôt officiel http://ftp.debian.org

2023-01-11 Thread Am I an Alien ?
Bonjour,
Je suis tombé sur un paquet dont le lien semble corrompu sur le dépôt
officiel debian http://ftp.debian.org, distribution Bullseye, paquet
apache2-data
Je m'en suis rendu compte car cela fait planter la construction d'iso avec
simple-cdd pour debian bullseye
Le lien en question est
http://ftp.debian.org/debian/pool/main/a/apache2/apache2-data_2.4.54-1~deb11u1_all.deb
La réponse est :
*"Une erreur est survenue en exécutant une opération ICAP : Maximum number
of archive layers exceeded; File: apache2-data_2.4.54-1~deb11u1_all.deb;
Sub File: ; Vendor: Sophos, Plc.; Engine version: 3.87.0; Pattern version:
5.97.79323952.0; Pattern date: 2023/01/11 01:47:31 *
* Il peut y avoir un problème réseau, le service ICAP peut être mal
configuré, ou le serveur ICAP peut avoir rapporté une erreur."*
Les autres paquets fonctionnent, et ce même paquet sur d'autres dépôts
fonctionne aussi
Cordialement
RV


Re: PowerBook G4 OS

2023-01-11 Thread didier gaumet
Le mardi 10 janvier 2023 à 16:32 -0800, Bob Crochelt a écrit :
> > 
> Thanks to all who replied.  I appreciate the help and advice.  Think
> I
> will just sit tight with the system, as it works fine for what I
> need:
> email, a little (slow surfing) and some note writing.
> 
> I imagine you have saved me many hours of frustration.
> 
> Regards
> Bob Crochelt

Hello,

That would leave you with unmaintained software, though, with obvious
risks accessing the internet (web, mail, etc...)

Debian port for a Powerbook G4 is unofficial and I don't know the
actual state of this port.

NetBSD, OpenBSD and FreeBSD all seem to have an active and official
port for the PowerPC G4.