Re: Question: SSD speed

[Leslie Rhorer]

On 10/8/2020 7:10 PM, Michael Stone wrote:
Can you provide any data to back that up?  I find it often to be 
quite the opposite.  Sloppy use of language very frequently leads to 
miscommunication, sometimes of a very serious nature.


And yet correcting people in contexts where there's no real ambiguity 
simply derails the conversation and distracts from the real point.


	I will concede that can happen, but the point is divergent from mine. 
There is a difference between taking care one's own speech is precise, 
making a general request that people take care with their speech, and 
correcting someone else's speech.


Context is important. Are you confusing this mailing list with a two 
hundred million dollar science program?


	I made a general statement that holds true for both.  I am not 
confusing anything.  Whether context is important or not is beside the 
point.  Whether three hundred million dollars is at stake or not, 
precision will serve one well.



And how, exactly, does that matter?


If you don't understand how 1,000,000,000,000 bytes is different 
from 1,099,511,627,776 bytes, then I don't know what to tell you.  
They are not the same.  They are different.  Whether that difference 
is significant or not depends upon the situation.


You dodged the question of how that actually matters, in context. I'm 
just going to stop here, enjoy pedantry.


	What does "mattering" have to do with it?  Different is different.  By 
simply being consistent and precise, one needn't worry about whether 
something "matters" or not.  The situation is much like any other good 
habit.  Being habitually precise covers one whether the situation is of 
great import or not.

Re: Question: SSD speed

[Leslie Rhorer]

On 10/8/2020 5:13 PM, Stefan Monnier wrote:

a container nears being full.  If one has 1 MB of storage available
(allowing for file system overhead and block alignment), then 1 MB
of data will fit, but 1 MiB will not.


In which way is the KB-vs-KiB discrepancy different from the "file
system overhead and block alignment"?


	File system overhead is not primarily an artifact of the size of the 
blocks.  Block alignment is related to the size of the blocks, but then 
I never said it was not.



Maybe it's a higher percentage, but the end result is the same: if your
FS says you have N bytes left, it does not guarantee you that an N byte
file will fit,


	If it says you have 1.00 MB free, then it is guaranteed 1.00 MiB will 
not fit.  If it (accurately) says you have 1.00 MiB free, then 1.00 MB 
is indeed guaranteed to fit.



so you need to include some slack.


Not usually that much.  Again, it depends on the situation.


And since very few
people are able to quickly compute how many blocks are needed for
a file of size N on the specific filesystem they use, you're better off
using a "safe enough" estimate.  This notion of "safe" enough is one
learned empirically over the years, so whether it's 2% or 10% doesn't
really matter that much, as long as it's pretty much always the same.


	Well, the point is it isn't the same.  One PiB is 1,125,899,906,842,624 
bytes.  One PB is 1,000,000,000,000,000 bytes.  That is a difference of 
12.6%, vs. 2.4% difference between 1 KiB and 1 KB.




As an engineer, precision is absolutely of the essence.


When talking about the capacity of mass storage, you don't need
precision, since it just has to be large enough, rather than having to
have exactly the right size.


Indubitably, but a 12.6% shortfall would be a problem.


Engineers are very familiar with such imprecise constraint and with
the use of safety margins to account for them.


	Of course I am.  There are plenty of cases where a safety margin is 
required.  There are plenty of other cases where a tiny differential can 
mean the difference between working well and a catastrophic failure. 
Direction also matters.  A cylinder that is just 0.001 mm oversize will 
not fit in a hole that is 0.001 mm undersize.

Re: Question: SSD speed

[Michael Stone]

On Thu, Oct 08, 2020 at 06:49:56PM -0500, Leslie Rhorer wrote:



On 10/8/2020 2:17 PM, Michael Stone wrote:

On Thu, Oct 08, 2020 at 01:27:15PM -0500, Leslie Rhorer wrote:

Well, what, really, is wrong with pedantry?


It makes conversation with humans harder


	Can you provide any data to back that up?  I find it often to be 
quite the opposite.  Sloppy use of language very frequently leads to 
miscommunication, sometimes of a very serious nature.


And yet correcting people in contexts where there's no real ambiguity 
simply derails the conversation and distracts from the real point. 


with no corresponding benefit.


	There are many benefits to accuracy in communication, and many risks 
to poor accuracy in communication.  Just ask NASA.  Their $328 Million 
Mars Climate Orbiter was lost due to miscommunication between 
engineering teams.


Context is important. Are you confusing this mailing list with a two 
hundred million dollar science program?


Not only that, but the discrepancy grows exponentially with 
the order of magnitude.  The difference between 1 KB and 1 KiB is 
only 24 bytes, or 2.4%.  The difference between 1 TB and 1 TiB is 
9.9%, which is getting to be pretty significant.  That, not to 
mention the fact 93 GiB is a pretty good chunk of storage.


And how, exactly, does that matter?


	If you don't understand how 1,000,000,000,000 bytes is different from 
1,099,511,627,776 bytes, then I don't know what to tell you.  They are 
not the same.  They are different.  Whether that difference is 
significant or not depends upon the situation.


You dodged the question of how that actually matters, in context. I'm 
just going to stop here, enjoy pedantry.

Re: Question: SSD speed

[Leslie Rhorer]

On 10/8/2020 2:17 PM, Michael Stone wrote:

On Thu, Oct 08, 2020 at 01:27:15PM -0500, Leslie Rhorer wrote:

Well, what, really, is wrong with pedantry?


It makes conversation with humans harder


	Can you provide any data to back that up?  I find it often to be quite 
the opposite.  Sloppy use of language very frequently leads to 
miscommunication, sometimes of a very serious nature.


> with no corresponding benefit.

	There are many benefits to accuracy in communication, and many risks to 
poor accuracy in communication.  Just ask NASA.  Their $328 Million Mars 
Climate Orbiter was lost due to miscommunication between engineering teams.


Not only that, but the discrepancy grows exponentially with the 
order of magnitude.  The difference between 1 KB and 1 KiB is only 24 
bytes, or 2.4%.  The difference between 1 TB and 1 TiB is 9.9%, which 
is getting to be pretty significant.  That, not to mention the fact 93 
GiB is a pretty good chunk of storage.


And how, exactly, does that matter?


	If you don't understand how 1,000,000,000,000 bytes is different from 
1,099,511,627,776 bytes, then I don't know what to tell you.  They are 
not the same.  They are different.  Whether that difference is 
significant or not depends upon the situation.


If you're on your own system and 
looking at output from the same set of programs the units don't actually 
matter at all--you could look and see that you need one foosbit of space 
and have two foosbits and be fine. Units only really matter if you're 
talking to someone else or otherwise taking information out of its 
original context.


Is there some reason you feel the need to point out the obvious?

But I can't even think of a situation where I needed 
to tell someone on a mailing list that I had n TsomethingBsomething of 
space.


That is not a reasonable excuse for being sloppy.

Context is important. Within the context we're discussing, rough 
order of magnitude is more than precise enough. For humans a 5.4TB drive 
and a 4.9TiB drive both round to 5T. Relative values are generally much 
more important in this context: what percentage of the drive is used? 


	Again, that depends upon the situation.  I am certainly not going to 
have a cow if someone accidentally says, "MB", when they mean "MiB", but 
that does not mean it is unimportant everyone should have a solid 
understanding of the difference.


At any rate here's the cold hard truth: even if you are exchanging 
information and it needs to be precise, humans being what they are it 
won't help you one bit if you're personally pedantic about MiB vs Mb 
because *you can't assume the other side means the same thing*.


	Again, you state the obvious.  The point is, attending to one's 
precision will never hurt.  Failure to do so can.  If one is precise in 
one's speech, then one needn't worry about the situations when 
imprecision can cause an issue.


You'll 
have to establish a baseline in every situation where it matters.


	Again you seem to be compelled to point out the obvious.  No 
communication can ever take place without at least implicitly agreed 
upon definitions.


But in 
a situation where it doesn't matter, doing so is just a waste of 
time


	How is it a waste of time?  Imprecision takes no less time than 
precision.  Sometimes it takes more.



--it won't change the world or human nature.


	Now that is just silly.  Nothing any of us do has more than a minuscule 
chance of changing the world, and less than that of changing human 
nature.  If we were to wait for an opportunity to do something of the 
sort, then none of use would ever do anything.

Re: Verifying checksum and signature

[leonard morin]

Thanks, Ryan. It's resolved now. When I got your email, I decided to do
something I probably should have thought of doing before. I went into my
Debian OS (which I am in the process of reinstalling) and I tried
retrieving the public keys using the signing keys from the same place (
https://www.debian.org/CD/verify ) within Debian, following the commands
you suggested. Of course, I was able to retrieve them. Then what I did was
go back to windows and try Kleopatra instead of Privacy Assistant, and it
worked! What a relief! There's some problem with Privacy Assistant. Perhaps
having it installed on the same Windows system with GPA Privacy Assistant?
I don't know. Thanks again, Leonard

On Mon, Oct 5, 2020 at 2:20 PM Ryan Nowakowski  wrote:

> On Thu, Oct 01, 2020 at 06:21:54PM -0400, leonard morin wrote:
> > Hi,
> >
> > I want to reinstall Debian but first verify the signature of the
> installer
> > checksum and the signature file. I am working with Windows and based this
> > process on this video by Crypto Dad:
> >
> > https://www.youtube.com/watch?v=N7oE0QaK540
> >
> > I was able to download the GPG4Win and verify it with the Shasum Checker,
> > also as per Crypto Dad:
> >
> > https://www.youtube.com/watch?v=QZ2GrQA_ye8
> >
> > I followed his instructions to check the signature and checksum for the
> > Debian installer in (GNU Privacy Assistant). I get the message that there
> > is no public key. When I follow his process to retrieve the public key at
> > https://www.debian.org/CD/verify
> > I get the message in GPA "No keys were found" for all the IDs and
> > fingerprints on the page. Should I be obtaining the public key elsewhere?
> > Or should I do something else differently?
> >
>
> You should be able to get the keys from the debian key
> server(keyring.debug.org).  Here's any example using gpg from the
> command-line:
>
> tubaman@potts:~$ gpg --keyserver keyring.debian.org --recv-keys
> 6BD05CFB
> gpg: key 42468F4009EA8AC3: "Debian Testing CDs Automatic Signing Key <
> debian...@lists.debian.org>" not changed
> gpg: Total number processed: 1
> gpg:  unchanged: 1
> tubaman@potts:~$ gpg --fingerprint 6BD05CFB
> pub   rsa4096 2014-04-15 [SC]
>   F41D 3034 2F35 4669 5F65  C669 4246 8F40 09EA 8AC3
> uid   [ unknown] Debian Testing CDs Automatic Signing Key <
> debian...@lists.debian.org>
> sub   rsa4096 2014-04-15 [E]
>
> Perhaps you can translate that into your Windows tools?  Here some more
> info on Debian's gpg key server: https://keyring.debian.org/
>
>

Re: Question: SSD speed

[Stefan Monnier]

>   a container nears being full.  If one has 1 MB of storage available
>   (allowing for file system overhead and block alignment), then 1 MB
>   of data will fit, but 1 MiB will not.

In which way is the KB-vs-KiB discrepancy different from the "file
system overhead and block alignment"?

Maybe it's a higher percentage, but the end result is the same: if your
FS says you have N bytes left, it does not guarantee you that an N byte
file will fit, so you need to include some slack.  And since very few
people are able to quickly compute how many blocks are needed for
a file of size N on the specific filesystem they use, you're better off
using a "safe enough" estimate.  This notion of "safe" enough is one
learned empirically over the years, so whether it's 2% or 10% doesn't
really matter that much, as long as it's pretty much always the same.

> As an engineer, precision is absolutely of the essence.

When talking about the capacity of mass storage, you don't need
precision, since it just has to be large enough, rather than having to
have exactly the right size.

Engineers are very familiar with such imprecise constraints and with
the use of safety margins to account for them.


Stefan

Re: Trimming boundary of image in GIMP.

[Tixy]

On Thu, 2020-10-08 at 12:43 -0700, pe...@easthope.ca wrote:
> From: Tixy 
> Date: Thu, 08 Oct 2020 08:37:33 +0100
> > I've attached screenshots of this...
> 
> Same behaviour here until attempting to drag top downward. 
> 
> Open GIMP in debian 10,
> open a rectangular image,
> choose the selection tool (might not be necessary),
> Select > All,
> grab top boundary and drag downward, (top; not corner)

I guess I was doing different things, I'm select an area using the
Rectangle Select tool then changing it, but you are selecting an area
with Select All then trying to drag the boundary of that area. For me
the latter doesn't work, because clicking anywhere starts just starts
using whatever tool is currently selected tool, for me, there doesn't
seem to be a way to interact with the area Select All creates.

-- 
Tixy

Re: Trimming boundary of image in GIMP.

[The Wanderer]

On 2020-10-07 at 13:49, pe...@easthope.ca wrote:

> Until recently the routine for trimming the boundary of an image was,
> (1) Select > All,
> (2) grab a boundary with pointer and drag it toward the center,
> (3) drag other boundaries in a similar way until the desired boundary
> was indicated,
> (4) Image > Crop to Selection.  
> Done.
> 
> Appears that an update since the last time I used GIMP added a new
> feature. (?) Now left and right boundaries are linked with top and
> bottom boundaries. Dragging the top boundary pulls the sides in
> simultaneously. =8~(
> 
> There must be cases where that is helpful but what if the objective
> is to change only one boundary?  The top for example.  I've tried
> unlinking Width and Height in Layer > Layer to Boundary Size. No
> dice.
> 
> I've tried holding ,  or  while dragging a
> boundary. No dice.
> 
> How is the new feature overridden?

This sounds as if the rectangle selection tool's "Fixed" option has been
selected, and set to "Aspect Ratio". (The other options are "Width",
"Height", and "Size".)

Look in the toolbox (for me it appears at the side, but you may have it
set up otherwise), and see what you find for this setting.

The relevant toolbox and area are shown (highlighted by red border) in a
screenshot on this question:

https://superuser.com/questions/463585/how-to-set-a-custom-sized-rectangle-select-area-in-gimp

That

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Trimming boundary of image in GIMP.

[peter]

From: Tixy 
Date: Thu, 08 Oct 2020 08:37:33 +0100
> I've attached screenshots of this...

Same behaviour here until attempting to drag top downward. 

Open GIMP in debian 10,
open a rectangular image,
choose the selection tool (might not be necessary),
Select > All,
grab top boundary and drag downward, (top; not corner)
left and right side boundaries immediately contract inward to make the boundary 
square.

Result visible here.  http://easthope.ca/GIMP.png

Thanks for the replies,... P.


-- 
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: desinscription

[4q9fusc262]

Merci beaucoup.  

  

Bonne continuation à tous sur notre merveilleux outils debian et linux en
général et un gros big up a toute l'equipe derrière ;)  

  

On Thursday, October 8, 2020 8:26 PM, "Th.A.C" rai...@free.fr wrote:  

>

> Le 08/10/2020 à 19:55, 4q9fusc...@use.startmail.com a écrit :

>  >

>  >

>  > Comment fait-on pour se desinscrire à cette liste de diffusion, je

> n'en peux plus

>  >de recevoir 50 mails par cette liste.

>  >

>  
> Hello,

>  
>  
> c'est marqué dans les en-têtes des messages:

>  
>  
> il faut envoyez un message à

>  debian-user-french-requ...@lists.debian.org

>  
> avec

>  unsubscribe

> dans le sujet

>  
>  
> List-Id: 

> List-URL: 

> List-Post: 

> List-Help: 

> List-Subscribe:

> 

> List-Unsubscribe:

> 

>  
> Thierry

>  
>  
>  
>  

  

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[Marc Chantreux]

Bonjour Charles,

> > et il me semble que meme sous debian (ou ubuntu?) il avait été évoqué de
> > virer bash pour dash. ce serait logique!
> c'est fait depuis Squeeze

ah ben voilà :)

cordialement,
marc

KopiaUI backups

[Peter Ehlert]

I am a long time user of LuckyBackup, and am very satisfied.

experimenting with Clear Linux OS system, I have been looking for a 
backup solution LuckyBackup is not readily available.
Clear OS provides KopiaUI ...reading the Kopia webpage and YouTube 
tutorial the KopiaUI app seems to be worthwhile.
I am now making a massive backup on Clear OS, and it occurs to me that 
KopiaUI would be good for using in Debian also.


Issue: KopiaUI is not in the Debian Stable repos.

Q: is there a reason to avoid KopiaUI?

Re: KopiaUI

[Andreas Rönnquist]

Den Thu, 8 Oct 2020 12:03:55 -0700
skrev KopiaUI:

> I am a long time user of LuckyBackup, and am very satisfied.
> 
> experimenting with Clear Linux OS system, I have been looking for a 
> backup solution LuckyBackup is not readily available.
> reading the Kopia webpage and YouTube tutorial the KopiaUI app seems
> to be worthwhile.
> I am now making a massive backup on Clear OS, and it occurs to me that
> 
> Issue: KopiaUI is not in the Debian Stable repos.
> 
> Q: is there a reason to avoid it?

The Github page of kopia mentions kopiaUI as an _experimental_ user
interface - This might be a reason for people to avoid packaging it.

/Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

Re: KopiaUI

[Reco]

Hi.

On Thu, Oct 08, 2020 at 12:03:55PM -0700, Peter Ehlert wrote:
> Q: is there a reason to avoid it?

That "Electron" word might have something to do with it - [1]:

KopiaUI is built using Electron and packaged as native binary using
Electron Builder.

Reco

[1] https://github.com/kopia/kopia/blob/master/BUILD.md

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[Charles Plessy]

Le Thu, Oct 08, 2020 at 06:04:24PM +0200, Marc Chantreux a écrit :
> 
> et il me semble que meme sous debian (ou ubuntu?) il avait été évoqué de
> virer bash pour dash. ce serait logique!

Bonjour Marc,

c'est fait depuis Squeeze:

$ ls -lh /bin/sh
lrwxrwxrwx 1 root root 4 janv. 18  2019 /bin/sh -> dash

Cordialement,

-- 
Charles Plessy
Akano, Uruma, Okinawa, Japan

KopiaUI

[Peter Ehlert]

I am a long time user of LuckyBackup, and am very satisfied.

experimenting with Clear Linux OS system, I have been looking for a 
backup solution LuckyBackup is not readily available.
reading the Kopia webpage and YouTube tutorial the KopiaUI app seems to 
be worthwhile.

I am now making a massive backup on Clear OS, and it occurs to me that

Issue: KopiaUI is not in the Debian Stable repos.

Q: is there a reason to avoid it?

Re: Question: SSD speed

[Michael Stone]

On Thu, Oct 08, 2020 at 01:27:15PM -0500, Leslie Rhorer wrote:

Well, what, really, is wrong with pedantry?


It makes conversation with humans harder with no corresponding benefit.

	Not only that, but the discrepancy grows exponentially with the order 
of magnitude.  The difference between 1 KB and 1 KiB is only 24 bytes, 
or 2.4%.  The difference between 1 TB and 1 TiB is 9.9%, which is 
getting to be pretty significant.  That, not to mention the fact 93 
GiB is a pretty good chunk of storage.


And how, exactly, does that matter? If you're on your own system and 
looking at output from the same set of programs the units don't actually 
matter at all--you could look and see that you need one foosbit of space 
and have two foosbits and be fine. Units only really matter if you're 
talking to someone else or otherwise taking information out of its 
original context. But I can't even think of a situation where I needed 
to tell someone on a mailing list that I had n TsomethingBsomething of 
space. Context is important. Within the context we're discussing, rough 
order of magnitude is more than precise enough. For humans a 5.4TB drive 
and a 4.9TiB drive both round to 5T. Relative values are generally much 
more important in this context: what percentage of the drive is used? 
what's the rate of consumption? Can debian 11 fit on a 5T drive? If 
you operate in some domain where you need much more precision then go 
ahead and do you, but it pretty much certainly isn't going to be on 
debian-user. 

At any rate here's the cold hard truth: even if you are exchanging 
information and it needs to be precise, humans being what they are it 
won't help you one bit if you're personally pedantic about MiB vs Mb 
because *you can't assume the other side means the same thing*. You'll 
have to establish a baseline in every situation where it matters. But in 
a situation where it doesn't matter, doing so is just a waste of 
time--it won't change the world or human nature.

Re: Quick help on

[Nicholas Geovanis]

On Thu, Oct 8, 2020, 9:35 AM  wrote:

>
> I've recently found that if I leave the machines with the KVM set to the
> Jessie machine, when I come back, the power light on the monitor is red,
> but
> does not come back to life when I move the mouse or press a key.
>

I had a similar problem with Jessie on laptops a couple years back. What I
found was that X seemed to be dialing down the brightness on the monitor
all the way to black.

>

Re: Question: SSD speed

[Dan Ritter]

Leslie Rhorer wrote: 
> On 10/8/2020 8:09 AM, Michael Stone wrote:
> > On Thu, Oct 08, 2020 at 11:53:16AM +0200, Thomas Schmitt wrote:
> > > Michael Stone wrote:
> > > > > I'd assume it's confusion between bits and bytes. [...]
> > > > > just write out bit or byte
> > > 
> > > Andrei POPESCU wrote:
> > > > SI prefixes can also help... if you use them consistently.
> > > 
> > This is basically never an issue in conversational usage as the
> > difference is less than the margin of error or real-world precision. If
> 
>   I rather beg to differ.  Many daily operations involve precision better
> than the 2.4% variance between 1000 and 1024.  Certainly my bank account
> balance is maintained to within $.01 of more than $10,000, or 0.0001%. I
> would be fairly distressed if $240 were missing from my account.
> 
>   Much of the work I do involves tolerances of less than 1%.


That's great, that's awesome; software is actually very good at
dealing with precision and accuracy. 

However, we're talking about people, not software. The people keep being
imprecise. There's nothing that Debian can do about that.

-dsr-

Re: Question: SSD speed

[Leslie Rhorer]

On 10/8/2020 8:09 AM, Michael Stone wrote:

On Thu, Oct 08, 2020 at 11:53:16AM +0200, Thomas Schmitt wrote:

Michael Stone wrote:

> I'd assume it's confusion between bits and bytes. [...]
> just write out bit or byte


Andrei POPESCU wrote:

SI prefixes can also help... if you use them consistently.


It is a classic that programs talk mixed about GB and GiB while not 
clearly
distinguishing them. In general, users must keep the difference in 
mind when

they compare "GB" values from different programs.
See
 https://en.wikipedia.org/wiki/Mebibyte


This is basically never an issue in conversational usage as the 
difference is less than the margin of error or real-world precision. If 


	I rather beg to differ.  Many daily operations involve precision better 
than the 2.4% variance between 1000 and 1024.  Certainly my bank account 
balance is maintained to within $.01 of more than $10,000, or 0.0001%. 
I would be fairly distressed if $240 were missing from my account.


Much of the work I do involves tolerances of less than 1%.

you're planning for a million dollars worth of storage, yeah, make sure 
you're clear on what you're buying. But when discussing a 10Gbit/s 
network or a 4TByte drive, there isn't ambiguity. (Only, potentially, 
pedantry.)


	Well, what, really, is wrong with pedantry?  As an engineer, precision 
is absolutely of the essence.  What's more, variations become far 
tighter in certain circumstances.  This especially as a container nears 
being full.  If one has 1 MB of storage available (allowing for file 
system overhead and block alignment), then 1 MB of data will fit, but 1 
MiB will not.


	Not only that, but the discrepancy grows exponentially with the order 
of magnitude.  The difference between 1 KB and 1 KiB is only 24 bytes, 
or 2.4%.  The difference between 1 TB and 1 TiB is 9.9%, which is 
getting to be pretty significant.  That, not to mention the fact 93 GiB 
is a pretty good chunk of storage.

Re: desinscription

[Th.A.C]

Le 08/10/2020 à 19:55, 4q9fusc...@use.startmail.com a écrit :
>
>
> Comment fait-on pour se desinscrire à cette liste de diffusion, je 
n'en peux plus

>de recevoir 50 mails par cette liste.
>

Hello,


c'est marqué dans les en-têtes des messages:


il faut envoyez un message à
debian-user-french-requ...@lists.debian.org

avec
unsubscribe
dans le sujet


List-Id: 
List-URL: 
List-Post: 
List-Help: 
List-Subscribe: 

List-Unsubscribe: 



Thierry

Re: desinscription

[Olivier Humbert]

Le 2020-10-08 19:55, 4q9fusc262 a écrit :

Comment fait-on pour se desinscrire à cette liste de diffusion, je
n'en peux plus de recevoir 50 mails par cette liste.


Bonsoir.

Vous devez pouvoir vous désinscrire à partir de cette page : 
https://lists.debian.org/debian-user-french/


Cordialement,
Olivier

desinscription

[4q9fusc262]

Bonjour,  

  

Comment fait-on pour se desinscrire à cette liste de diffusion, je n'en peux
plus de recevoir 50 mails par cette liste.  

  

Merci d'avance  

  

Cordialement  

Re: Quick help on

[Bob Weber]

On 10/8/20 1:30 PM, Charles Curley wrote:

On Thu, 8 Oct 2020 10:34:33 -0400
rhkra...@gmail.com wrote:


I've recently found that if I leave the machines with the KVM set to
the Jessie machine, when I come back, the power light on the monitor
is red, but does not come back to life when I move the mouse or press
a key.

My work-around for a similar situation is CTL-ALT-F1, then release all
keys, then CTL-ALT-F7. Which I believe forces X to re-initialize itself.

I have the same problem in qemu VMs.  I do the equivalent of CTL-ALT-F1 then 
CTL-ALT-F7 to get the GUI back.  It started in the last year so it is something 
in the system is doing it.  Googling wasn't much help.  I have put all the 
settings (in KDE) to not sleep or turn off the monitor to no avail.


--


*...Bob*

Re: Quick help on

[Charles Curley]

On Thu, 8 Oct 2020 10:34:33 -0400
rhkra...@gmail.com wrote:

> I've recently found that if I leave the machines with the KVM set to
> the Jessie machine, when I come back, the power light on the monitor
> is red, but does not come back to life when I move the mouse or press
> a key.

My work-around for a similar situation is CTL-ALT-F1, then release all
keys, then CTL-ALT-F7. Which I believe forces X to re-initialize itself.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Boot warnings: "No irq handler for vector …"

[nito]

Hi,

after updating the BIOS, I'm now met with warning/error messages every boot, 
however it continues to boot normally.
There has since been one crash related to PCIe errors, but I'm not sure if 
this was related to the BIOS update or "just" a driver bug.

Downgrading the BIOS to the previous version is - as I found out - not 
officially supported.

I'm not sure how bad these warnings/errors are and if I should be concerned 
about it and if this should be reported to the manufacturer or kernel devs.
I'd appreciate if someone more knowledgeable with this could give me an 
opinion on it.

Relevant dmesg excerpt:

[0.364305] rcu: Hierarchical SRCU implementation.
[0.364572] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[0.364641] smp: Bringing up secondary CPUs ...
[0.364641] x86: Booting SMP configuration:
[0.364641]  node  #0, CPUs:#1
[0.068359] __common_interrupt: 1.55 No irq handler for vector
[0.364641]   #2
[0.068359] __common_interrupt: 2.55 No irq handler for vector
[0.364705]   #3
[0.068359] __common_interrupt: 3.55 No irq handler for vector
[0.366814]   #4
[0.068359] __common_interrupt: 4.55 No irq handler for vector
[0.368708]   #5
[0.068359] __common_interrupt: 5.55 No irq handler for vector
[0.372703]   #6
[0.068359] __common_interrupt: 6.55 No irq handler for vector
[0.374847]   #7
[0.068359] __common_interrupt: 7.55 No irq handler for vector
[0.376706]   #8
[0.068359] __common_interrupt: 8.55 No irq handler for vector
[0.378863]   #9
[0.068359] __common_interrupt: 9.55 No irq handler for vector
[0.380706]  #10
[0.068359] __common_interrupt: 10.55 No irq handler for vector
[0.382816]  #11 #12 #13 #14 #15
[0.394846] smp: Brought up 1 node, 16 CPUs
[0.394846] smpboot: Max logical packages: 2
[0.394846] smpboot: Total of 16 processors activated (102210.65 BogoMIPS)
[0.397401] devtmpfs: initialized


Full dmesg logs from before and after the BIOS update are attached.

Those irq errors happen with all tested kernel versions.
( Buster's 4.19.0-11-amd64, backport's 5.7.0-0.bpo.2-amd64
  and local 5.8.12 and 5.8.14 kernels )

As for why I was updating the BIOS:
With the previous BIOS version I wasn't able to run the RAM at the 
advertised speeds. Now I can, but I get these warnings/errors instead — 
regardless of memory speed.


Nito


before.log.xz
Description: application/xz


after.log.xz
Description: application/xz

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[Marc Chantreux]

salut,

> Quel serait l'intérêt d'écrire ou de transcrire un script en ZSH ? En
> sachant que l'inconvénient serait la perte de portabilité ?

* c'est facile de porter de bash vers zsh
* ensuite tu te retrouves avec tous les avantages de zsh (ils sont
  legion)
* la portabilité avec quoi?

alpine, openwrt: dash (busybox), openbsd: ksh, kali et macos: bientot zsh

et il me semble que meme sous debian (ou ubuntu?) il avait été évoqué de
virer bash pour dash. ce serait logique!

cordialement,
marc

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[Marc Chantreux]

salut,

> ZSH est un shell sympa et très modifiable avec plein de
> fonctionnalités intégrées.

c'est surtout un super outils de scripting.

> Par contre tu ne le retrouves de base installé dans les environnements
> systèmes.

ajoute "linux" pour ce que soit vrai:

* le shell par defaut sous openbsd est ksh et je crois que c'est aussi
  le cas sous les autres bsd.
* les prochains macos auront zsh comme shell par defaut
* et meme sous linux, dash et zsh commencent a faire leur chemin.
  le choix de dash comme shell par defaut me parrait tres pertinent:
  dans le sens ou plein d'utilisateurs n'utilisent plus le terminal,
  pourquoi se trainer un veau comme bash?

> Quand tu fais de la maintenance de serveurs, tu aimes avoir un système
> identique et stable.

apt install zsh dans ta regle ansible/flex/puppet/chef/airborne

> Cela fait des dizaines d'années que c'est BASH comme
> interpréteur sur les systèmes GNU/Linux et avant c'est Bourne shell
> (SH).

parce que c'était l'implémentation shell du GNU et que tout le monde.
a l'époque ou perl, python ou ruby sont arrivés, il y a eu des levées de
boucliers de ceux qui pensaient que awk et sh suffisaient.

un existant n'est pas une excuse pour ne pas évoluer.

> BASH est retro-compatible avec les scripts SH.

zsh l'est avec sh, ksh et même une partie de rc.
je n'ai pas verifié mais il me semble qu'il y a aussi un mode de
compatibilité avec ... bash.


> raisons de compatibilité futur, un script ce fait souvent avec BASH et
> suivant le type de machine qui l'accueil il faudrait préférer la
> syntaxe du Bourne Shell.

c'est quoi la "compatibilité future"??? si tu veux un standard il y en a
deja un et il s'appelle POSIX: bonne chance :)

Si tu pars de l'idée qu'il faut s'appuyer sur un set d'outils homogène
qui est controlé par un seul groupe: c'est une approche qui peut se
discuter mais GNU coreutils ne serait pas mon premier choix! pourquoi
pas heiloom ou 9base ?

Ensuite je reprendrais une phrase celebre de larry wall:

https://news.ycombinator.com/item?id=10104203

“It's easier to port a shell than a shell script” (1998)

Si tu veux un truc qui est:

* très implanté dans presque tous les unices
* dont la syntaxe hérite de cette culture
* qui est très portable
* qui peut s'enorgueuillir de 25 ans de rétrocompatibilité
  (sauf problèmes de secu) tout en ayant des features que j'attend
  toujours de voir dans les autres langages

alors écris tes scripts en perl.

> Après si tu veux t'amuser à récrire tes scripts, tu peux! Mais je ne
> sais pas si il y a un outil pour la conversion de script.

nope et ca n'aurait pas de sens je crois :)

a+
marc

Re: Question: SSD speed

[Stefan Monnier]

Michael Stone [2020-10-08 11:44:17] wrote:

> On Thu, Oct 08, 2020 at 11:35:19AM -0400, Stefan Monnier wrote:
>>> In 2020 assume you'll need more than one and let the computer figure
>>> out how to split it.
>>
>>I'm not sure what you're referring to here.  OT1H, from the context
>>I get the impression you're talking about DVD-R, but OTOH in 2020 the
>>assumption should rather be not to bother with DVDs any more.
>
> I thought it was pretty clear, someone asked about fitting stuff on
> a DVD. The answer is that you'll probably need to deal with more than one
> DVD. There is a place for offline backups; DVDs lack in capacity, but
> they're still compelling for that role from a cost standpoint if the data
> volume isn't too high. At any rate, I don't see a point in arguing about
> whether the person I was replying to is doing it wrong because they choose
> to use a DVD.

Looks like I should have included the smiley after all,


Stefan

Re: Question: SSD speed

[Michael Stone]

On Thu, Oct 08, 2020 at 11:35:19AM -0400, Stefan Monnier wrote:

In 2020 assume you'll need more than one and let the computer figure
out how to split it.


I'm not sure what you're referring to here.  OT1H, from the context
I get the impression you're talking about DVD-R, but OTOH in 2020 the
assumption should rather be not to bother with DVDs any more.


I thought it was pretty clear, someone asked about fitting stuff on a 
DVD. The answer is that you'll probably need to deal with more than one 
DVD. There is a place for offline backups; DVDs lack in capacity, but 
they're still compelling for that role from a cost standpoint if the 
data volume isn't too high. At any rate, I don't see a point in arguing 
about whether the person I was replying to is doing it wrong because 
they choose to use a DVD.

Re: Question: SSD speed

[Stefan Monnier]

> In 2020 assume you'll need more than one and let the computer figure
> out how to split it.

I'm not sure what you're referring to here.  OT1H, from the context
I get the impression you're talking about DVD-R, but OTOH in 2020 the
assumption should rather be not to bother with DVDs any more.


Stefan

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[Marc Chantreux]

salut Steve,

On Thu, Oct 08, 2020 at 11:35:44AM +0200, steve wrote:
> J'ai des dizaine de script écrits en Bash. Existe-t-il un moyen
> automatique de les porter sous Zsh?

il n'y a pas de de tanspiler bash vers zsh. par contre zsh et
bash ont un gros tronc commun qui est la syntaxe ksh (et il me semble
qu'il y a des options de compatibilité bash dans zsh) et ksh n'est
qu'une évolution du bourne shell (sh) dont dash est l'implémentation
qui fait consensus aujourd'hui.

Donc a priori, j'aimerais te dire qu'il suffit de prendre ton script
bash, de modifier le shebang et de voir ce qui casse...sauf que si t'as
un rm (ou autre commande avec de possibles forts effets de bord), tu
risques de faire des degats avec des incompatibilités qui amènent
eventuellement a avoir un comportement très loin de ce qui est attendu.

Voici donc des idées de filets pour sécuriser un peu ta démarche:

0. se renseigner sur les bashisms et voir ce que zsh propose à la place

eventuellement identifier les bashisms automatiquement ?

http://manpages.ubuntu.com/manpages/bionic/man1/checkbashisms.1.html

1. fais tout ca depuis un container

debootstrap + ( chroot | lxroot ) , docker, ... il a plétore de solutions.

j'aurais tendance a faire une copie du container apres installation
histoire de pouvoir d'un container preinstallé si besoin.

2. change le shebang

sed -i.bak 1s,$(which bash),$(which zsh), la liste de tes scripts

3. relance tes tests pour voir si tout se passe bien

si tout se passe bien: c'est fini :) tu peux changer les shebangs
partout

4. si tu as/veux plus erreurs

ben il faut lire et corriger. je dis "tu veux plus d'erreur" parce que
il faut savoir que les pires erreurs sont celles qui arrivent
tardivement. aussi je te conseille d'ajouter ces lignes dans ton
~/.zshenv:

setopt warncreateglobal nounset pipefail

5. corriger

tu as 2 stratégies possibles:

* virer les bashims et te rapprocher de la norme POSIX (du coup tu
  pourrais meme tenter de rendre ton script compatible avec mksh ou dash)

* remplacer les bashisms par des zshisms ... c'est vraiment très
  plaisant et puissant mais ca nécessite zsh (et des collègues qui
  adhèrent à l'idée). tu vas te retrouver dans la meme situation que
  perl vs python: d'un coté un truc puissant que "personne ne peut lire"
  (en gros: pas le temps de lire la doc) et d'un autre survendu comme
  "la référence" et "super lisible".

  exemple:

  en zsh tu peux écrire
  dpkg -S $( readlink -f $(which vi) )

  avec l'habitude tu vas plutôt écrire
  dpkg -S =vi(:A)

  mais tu risques de te faire pourrir par les collègues

  Aussi: apres 25 ans de shell scripting, je me rend compte que la puissance
  de zsh m'a fait passé à coté de l'élégance de commandes comme bc, mkfifo, 
xargs, ...
  aussi j'ai tendance maintenant à écrire des scripts avec des shells
  beaucoup plus légers (rc a ma préférence mais il y a aussi dash et
  mksh).


cordialement,
marc

Nieuwe Thunderbird en PGP

[Paul van der Vlis]

Hallo,

Vandaag is de nieuwe Thunderbird uitgerold via security met daarin een 
eigen PGP implementatie.  Deze gebruikt geen PGP van het systeem, maar 
een eigen PGP die minder kan.


Met moeite heb ik mijn private keys weten te importeren uit 
~/.gnupg/secring.pgp. Hierin stonden verschillende keys, en als je opgaf 
dat je niet al die keys wou, dan wou hij ze toch. Maar goed, gelukt, 
maar het lijkt me lastig voor iemand die het paswoord van een oude key 
kwijt is, want het wil wel de paswoorden.


De public keys importeren uit ~/.gnupg/pubring.pgp wil nog niet erg 
lukken. Thunderbird zegt dat het bestand te groot is. Iemand hier 
ervaring hoe je pubring.pgp opsplitst?


De melding in het Engels is:
This file is too big. Please don't import a large set of keys at once.
Mijn pubring is overigens 23 MB, dat noem ik niet groot.


Groet,
Paul



--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Quick help on

[rhkramer]

What I'm looking for: I didn't do much research on this problem, I checked the 
settings I could quickly find in Jessie, and did a google search or two on [].

I'm not looking for in depth help at this point, I have a workaround, I'm 
looking for someone who might have had the same problem and can say "aha, I 
had the same problem, here's what you need to do".

If no one comes forth with such a response, I will dig deeper (in my own time) 
including more googling and such, and, if no luck, will write a more detailed 
request to this list for help.

Background to the problem: I run several computers with one monitor, keyboard, 
and mouse via a Belkin SOHO KVM switch.  

One runs Wheezy (my daily driver), one runs Jessie (I was going to migrate 
there), one runs Buster (maybe I'll migrate there, in any case, I plan to use 
it to try to write a new lexer for Scintilla, which now uses C++17, so (to me) 
the easiest approach was to put Buster on my (rarely used) laptop.

I often / usually leave the computers on when I leave them to do something 
else.  

The problem: Until recently, I used the Wheezy machine almost all the time, 
and when I left the machines, the KVM was set to the Wheezy machine, and when 
I came back I could do things like move the mouse or press a key and the 
monitor would come back to life (the little power light on the monitor will 
have switched to red while I was gone, and when I move the mouse or press a 
key, it turns green and comes back to life.

I've recently found that if I leave the machines with the KVM set to the 
Jessie machine, when I come back, the power light on the monitor is red, but 
does not come back to life when I move the mouse or press a key.

In fact, I've found that in this condition, so far the only way I've been able 
to get the monitor to come back to life is to unplug and replug it to the 
power source.  (As a practice, I try to do that for some "reasonable" time, 
maybe 15 seconds or so.)

The other thing that doesn't work is switching the KVM to the Wheezy or Buster 
machines and then moving the mouse, etc.

(I presume that I could reboot one of the machines to get the monitor to "wake 
up", but I have no desire to do that.)

Aside: The three machines are not set to go into suspend or hibernate while 
I'm away.  The Wheezy and Jessie machines are set to turn the monitor off (or 
suspend?) after 10 minutes (the power light stays lit, but is red instead of 
green).

I did find (via google) one webpage that said I should look for a setting for 
the keyboard and mouse that was something like "wake on activity".

BTW, the workaround I currently (try to remember) to use is to switch to the 
Wheezy machine before stepping away.  (Aside: the power cord for the monitor 
is buried behind my desk, in a power strip with several other devices that I 
don't particularly want to turn off and back on -- things like my ObiHai VOIP 
device which has to go through a reboot process when it powers up.)





 

Re: Question: SSD speed

[Michael Stone]

On Thu, Oct 08, 2020 at 03:51:53PM +0200, Thomas Schmitt wrote:

i wrote:

> It is a classic that programs talk mixed about GB and GiB while not
> clearly distinguishing them.


Michael Stone wrote:

This is basically never an issue in conversational usage as the difference
is less than the margin of error or real-world precision. If you're planning
for a million dollars worth of storage, yeah,


But what about a 25 cent DVD-R which is labeled "4.7 GB" and only can take
4.377 GiB (4482.625 MiB, 4,700,372,992 bytes) ?


If the difference matters you want the exact size in bytes. If you're 
willing to round off that many significant digits you weren't that 
worried about the exact size anyway. In 2020 assume you'll need more 
than one and let the computer figure out how to split it.



Since we know that 1.5Gbyte/s SATA
doesn't exist we've clearly identified that there was confusion when reading
the original spec


There could also have been confusion about SATA and NVMe, at least.


Occam's razor suggests not. No need to look for additional remote 
possibilities until the most likely explanation has been ruled out.

Re: Question: SSD speed

[Thomas Schmitt]

Hi,

i wrote:
> > It is a classic that programs talk mixed about GB and GiB while not
> > clearly distinguishing them.

Michael Stone wrote:
> This is basically never an issue in conversational usage as the difference
> is less than the margin of error or real-world precision. If you're planning
> for a million dollars worth of storage, yeah,

But what about a 25 cent DVD-R which is labeled "4.7 GB" and only can take
4.377 GiB (4482.625 MiB, 4,700,372,992 bytes) ?

I see such complaints in the web every few months. (With interesting
theories about what might be wrong.)


> Since we know that 1.5Gbyte/s SATA
> doesn't exist we've clearly identified that there was confusion when reading
> the original spec

There could also have been confusion about SATA and NVMe, at least.


Have a nice day :)

Thomas

Gnome software and policykit question

[Paul van der Vlis]

Hello,

I try to use "Gnome software", it seems to be a very nice program for
end users to install software.

On one machine, often upgraded, it runs fine. It starts with normal user
rights, and if you want to install or remove a package it asks for a
root password and the package is installed or removed.

On the second machine, fresh installed, it does not run fine. When you
want to install or remove a package, I get a message that I don't have
enough rights to do so. I do not get the question for the root password.

On both machines /etc/polkit-1 are identical, checked with diff.

I've tested this with XFCE and Cinnamon. Both desktops are using the
policykit-1-gnome authentication agent what's installed.

Anyone an idea what will be wrong on the second machine?
Maybe I need an extra package?

With regards,
Paul


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: Question: SSD speed

[Michael Stone]

On Thu, Oct 08, 2020 at 11:53:16AM +0200, Thomas Schmitt wrote:

Michael Stone wrote:

> I'd assume it's confusion between bits and bytes. [...]
> just write out bit or byte


Andrei POPESCU wrote:

SI prefixes can also help... if you use them consistently.


It is a classic that programs talk mixed about GB and GiB while not clearly
distinguishing them. In general, users must keep the difference in mind when
they compare "GB" values from different programs.
See
 https://en.wikipedia.org/wiki/Mebibyte


This is basically never an issue in conversational usage as the 
difference is less than the margin of error or real-world precision. If 
you're planning for a million dollars worth of storage, yeah, make sure 
you're clear on what you're buying. But when discussing a 10Gbit/s 
network or a 4TByte drive, there isn't ambiguity. (Only, potentially, 
pedantry.) 


Hans wrote:

> And second: If the real transferrate is only 1,5Gbyte/sec, does this mean,
> that the sata controller is not capable to higher transferrates


No existing SATA can deliver 1.5 gigabytes (+/- 7.4 percent).
So something is wrong in this statement and only original output from
exactly quoted program runs could tell what.


Again, there's no real ambiguity here. Since we know that 1.5Gbyte/s 
SATA doesn't exist we've clearly identified that there was confusion 
when reading the original spec (caused by the stupid B/b convention) and 
that 1.5Gbit/s is correct--with enough certainty to simply point out and 
explain the issue and move on.

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[benoit]

Bonjour à toutes et tous

J'utilise ZSH, mes scripts sont en Bash, mais quand je les appelles, depuis un 
terminale en ZSH, le shebang :
#!/bin/bash

fait qu'ils s'exécutent dans une instance de  bash, bien qu'appelé depuis un 
terminal en ZSH.

Le fait de passer à ZSH ne supprime pas BASH à moins de l'avoir volontairement 
désinstallé.

Même en utilisant ZSH, BASH par défaut sur les OS reste une référence de 
portabilité.

Quel serait l'intérêt d'écrire ou de transcrire un script en ZSH ? En sachant 
que l'inconvénient serait la perte de portabilité ?

--
Benoit



Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
Le jeudi 8 octobre 2020 11:35, steve  a écrit :

> J'ai des dizaine de script écrits en Bash. Existe-t-il un moyen
> automatique de les porter sous Zsh ?

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[Rom1]

La réponse est pourquoi faire en ZSH?



ZSH est un shell sympa et très modifiable avec plein de fonctionnalités 
intégrées. Par contre tu ne le retrouves de base installé dans les 
environnements systèmes. Quand tu fais de la maintenance de serveurs, tu aimes 
avoir un système identique et stable. Cela fait des dizaines d'années que c'est 
BASH comme interpréteur sur les systèmes GNU/Linux et avant c'est Bourne shell 
(SH). BASH est retro-compatible avec les scripts SH. Donc pour des raisons de 
compatibilité futur, un script ce fait souvent avec BASH et suivant le type de 
machine qui l'accueil il faudrait préférer la syntaxe du Bourne Shell.



Après si tu veux t'amuser à récrire tes scripts, tu peux! Mais je ne sais pas 
si il y a un outil pour la conversion de script.

Le 08.10.20 à 12:15, steve a écrit :

Le jeudi 08 octobre 2020, Rom1 a écrit :


J'utilise ZSH au quotidien sur mon ordi de travail et j'utilise BASH
pour les serveurs. Dès que je dois écrire un script, je le fais le plus
souvent en BASH même si je suis sur un shell ZSH.


La question est pourquoi ?

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[steve]

Le jeudi 08 octobre 2020, Rom1 a écrit :


J'utilise ZSH au quotidien sur mon ordi de travail et j'utilise BASH
pour les serveurs. Dès que je dois écrire un script, je le fais le plus
souvent en BASH même si je suis sur un shell ZSH.


La question est pourquoi ? 

[SOLVED] Re: Question: SSD speed

[Hans]

Hi folks,

I would like to inform you, that due to your responses to my question I got a 
good solution. Although I got the newest BIOS from the vendor, I only got 1,5 
Gb/s for my ssd.

Now I found a hacked BIOS for my notebook with a lot of more settings, flashed 
my notebook, crossed fingers - and it worked!

With the new BIOS I got settings for sata clock (former 133MHz now 200MHz) and 
a clock factor setting from 1-31 (now 16). 

With these settings I got now 3Gb/s , which is doubling the speed. Also other 
settings in this new BIOS like CPU Spread Spectrum and let me well fine tune 
my system. 

Everything is working well with the new BIOS and I am happy with it.

FYI: The notebook is an Acer 7520G with a Phoenix BIOS (which originally is 
really poor with settings). If you have a mainboard with an Award or AMI BIOS, 
you are the lucky guys.

So, thanks to your hints I got the best solution.

Thanks again! 

Cheers and best regards

Hans


signature.asc
Description: This is a digitally signed message part.

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[Rom1]

J'utilise ZSH au quotidien sur mon ordi de travail et j'utilise BASH pour les 
serveurs. Dès que je dois écrire un script, je le fais le plus souvent en BASH 
même si je suis sur un shell ZSH. Le plus important c'est d'utiliser le bon 
shebang (https://fr.wikipedia.org/wiki/Shebang) pour que le système exécute le 
bon interpréteur.

Shebang:
  #!/usr/bin/env bash

Le 08.10.20 à 11:35, steve a écrit :

J'ai des dizaine de script écrits en Bash. Existe-t-il un moyen
automatique de les porter sous Zsh ?

Re: Question: SSD speed

[Thomas Schmitt]

Hi,

Hans wrote:
> > > Smartctl is telling me, that my ssd drive is 6Gb/sec
> > > capable, but the actual speed is only 1,5GB/sec.
> > > [...]
> > > The notebook is a little bit older, [...]

Andrei POPESCU wrote:
> You would have gotten much better answers by just specifying the exact
> notebook make and model.

... plus the original report lines from smartctl which tell you the speed
value.


Michael Stone wrote:
> > I'd assume it's confusion between bits and bytes. [...]
> > just write out bit or byte

Andrei POPESCU wrote:
> SI prefixes can also help... if you use them consistently.

It is a classic that programs talk mixed about GB and GiB while not clearly
distinguishing them. In general, users must keep the difference in mind when
they compare "GB" values from different programs.
See
  https://en.wikipedia.org/wiki/Mebibyte

Normally i use programmer's units: KiB, MiB, GiB, TiB. Meanwhile this habit
becomes questionable. What was a nice extra of 2.4 percent in the "kilobytes"
era became 4.9 percent with "mega", 7.4 with "giga", and 10 with "tera".
The merchants begin to cheat in the other direction. A 128 "GB" USB stick
might offer only 126 billion bytes a storage capacity.


But in this thread about SSD speed it was most confusing for me to read this:

Hans wrote:
> > And second: If the real transferrate is only 1,5Gbyte/sec, does this mean,
> > that the sata controller is not capable to higher transferrates

No existing SATA can deliver 1.5 gigabytes (+/- 7.4 percent).
So something is wrong in this statement and only original output from
exactly quoted program runs could tell what.


Have a nice day :)

Thomas

Re: (bash vs *sh) Re: exécuter automatiquement un programme dépendant du suffixe

[steve]

J'ai des dizaine de script écrits en Bash. Existe-t-il un moyen
automatique de les porter sous Zsh ?

Re: Question: SSD speed

[Andrei POPESCU]

On Mi, 07 oct 20, 09:06:51, Michael Stone wrote:
> 
> I'd assume it's confusion between bits and bytes. For clarity, *never* use B
> or b, just write out bit or byte because some people put attach much more
> significance to the case of that letter than others--making it basically
> useless for communication. 

SI prefixes can also help... if you use them consistently.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Question: SSD speed

[Andrei POPESCU]

On Mi, 07 oct 20, 10:39:44, Hans wrote:
> Hi folks, 
> 
> I have a little question. Smartctl is telling me, that my ssd drive is 
> 6Gb/sec 
> capable, but the actual speed is only 1,5GB/sec.
> 
> The notebook is a little bit older, AMD CPU with 2x2,4 GHz, 4GB RAM, debian/
> testing.

You would have gotten much better answers by just specifying the exact 
notebook make and model.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Question: SSD speed

[Andrei POPESCU]

On Mi, 07 oct 20, 13:31:49, Jeremy Nicoll wrote:
> On Wed, 7 Oct 2020, at 12:14, Alberto Sentieri wrote:
> > Just a small correction: it I believe SATA uses 8B/10B protocol, which 
> > means each byte uses 10 bits on the serial channel.
> 
> I didn't know that.  Divide bps by ten to get Bps is the rule of thumb I
> use for things like broadband connections, to allow for protocol
> overhead.

In the times of 56k modems I've seen 9 suggested as a divider, to allow 
for protocol overhead and some compression (assuming the data itself is 
not compressible).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Trimming boundary of image in GIMP.

[tomas]

On Wed, Oct 07, 2020 at 10:49:32AM -0700, pe...@easthope.ca wrote:
> Until recently the routine for trimming the boundary of an image was,

Doesn't happen here (Gimp 2.10.8 -- Debian package 2.10.8-2). Rectangle
selection also behaves "normal" (i.e. it doesn't force a square).

This assuming that I did understand what you're talking about: this what
you call "borders" are what Gimp calls "guides", right?

Cheers
 - t


signature.asc
Description: Digital signature

Re: Trimming boundary of image in GIMP.

[Tixy]

On Thu, 2020-10-08 at 08:37 +0100, Tixy wrote:
> I've attached screenshots of this...

Ah, I just noticed that the screenshot program didn't include the
modified mouse pointer I see, it just added a generic pointer. But they
do show the selection area I describe.

-- 
Tixy

Re: Trimming boundary of image in GIMP.

[Tixy]

On Thu, 2020-10-08 at 08:32 +0100, Tixy wrote:
> Not that I know. For me, with up-to-date Buster install, the Rectangle
> Select is only 'square select' if you click inside the corners of the
> selection box. In fact, hovering the mouse inside the selection box
> shows an area to grab, which is either a square (if it's in the
> corner), or a rectangle along a side where you can drag just that side.
> The mouse pointer also changes to indicate the selection type.

I've attached screenshots of this...

Re: Trimming boundary of image in GIMP.

[Tixy]

On Wed, 2020-10-07 at 20:31 -0700, pe...@easthope.ca wrote:
> From: Tixy 
> Date: Wed, 07 Oct 2020 20:24:01 +0100
> > I've always used the Rectangle Select tool by press the 'R' key .
> 
> Yes, I've used rectangle select for years.  Unfortunately it is now square 
> select.
> In this GIMP at least.  Is there an aspect ratio setting somewhere?

Not that I know. For me, with up-to-date Buster install, the Rectangle
Select is only 'square select' if you click inside the corners of the
selection box. In fact, hovering the mouse inside the selection box
shows an area to grab, which is either a square (if it's in the
corner), or a rectangle along a side where you can drag just that side.
The mouse pointer also changes to indicate the selection type.

-- 
Tixy 

[SOLVED] Re: Question: SSD speed

[Hans]

Hi folks,

I would like to inform you, that due to your responses to my question I got a 
good solution. Although I got the newest BIOS from the vendor, I only got 1,5 
Gb/s for my ssd.

Now I found a hacked BIOS for my notebook with a lot of more settings, flashed 
my notebook, crossed fingers - and it worked!

With the new BIOS I got settings for sata clock (former 133MHz now 200MHz) and 
a clock factor setting from 1-31 (now 16). 

With these settings I got now 3Gb/s , which is doubling the speed. Also other 
settings in this new BIOS like CPU Spread Spectrum and let me well fine tune 
my system. 

Everything is working well with the new BIOS and I am happy with it.

FYI: The notebook is an Acer 7520G with a Phoenix BIOS (which originally is 
really poor with settings). If you have a mainboard with an Award or AMI BIOS, 
you are the lucky guys.

So, thanks to your hints I got the best solution.

Thanks again! 

Cheers and best regards

Hans



 

signature.asc
Description: This is a digitally signed message part.