Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #260853 > unrolled thread

Crosshairs in gimp 2.10.22 in Debian 11.7.

Back to article view | Back to linux.debian.user

Contents

  Crosshairs in gimp 2.10.22 in Debian 11.7. peter@easthope.ca - 2023-08-12 04:00 +0200
    Re: Crosshairs in gimp 2.10.22 in Debian 11.7. Dan Ritter <dsr@randomstring.org> - 2023-08-12 13:10 +0200
      Re: Crosshairs in gimp 2.10.22 in Debian 11.7. peter@easthope.ca - 2023-08-12 15:50 +0200
      Re: random number generator missing after upgrade Björn Persson <Bjorn@xn--rombobjrn-67a.se> - 2023-08-14 11:30 +0200
        Re: random number generator missing after upgrade David Wright <deblis@lionunicorn.co.uk> - 2023-08-14 15:30 +0200
          Re: random number generator missing after upgrade Björn Persson <Bjorn@xn--rombobjrn-67a.se> - 2023-08-14 21:00 +0200
            Re: random number generator missing after upgrade davidson <davidson@freevolt.org> - 2023-08-14 22:30 +0200
              Re: random number generator missing after upgrade Björn Persson <Bjorn@xn--rombobjrn-67a.se> - 2023-08-15 07:50 +0200
      Re: upgrade to bookworm broke phpmyadmin Rick Macdonald <rickmacd@shaw.ca> - 2023-08-24 05:30 +0200
        Re: upgrade to bookworm broke phpmyadmin Stefan Monnier <monnier@iro.umontreal.ca> - 2023-08-24 16:00 +0200
          Re: upgrade to bookworm broke phpmyadmin Rick Macdonald <rickmacd@shaw.ca> - 2023-08-24 23:40 +0200
      Re: Please verify Gnome and KDE wiki articles for correctness Jeffrey Walton <noloader@gmail.com> - 2023-08-26 16:30 +0200
        Re: Please verify Gnome and KDE wiki articles for correctness <tomas@tuxteam.de> - 2023-08-26 16:50 +0200
      Re: raid10 access problem gene heskett <gheskett@shentel.net> - 2023-09-07 19:10 +0200
      Re: raid10 access problem gene heskett <gheskett@shentel.net> - 2023-09-07 21:10 +0200
      Re: raid10 access problem gene heskett <gheskett@shentel.net> - 2023-09-07 21:10 +0200
      Re: Debian, Git server, Nginx, Fcgiwrap, and git push can not create  remote object directory David Mehler <dave.mehler@gmail.com> - 2023-09-10 03:30 +0200
      Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-10 18:50 +0200
        Re: usrmerge on root NFS will not be run automatically Javier Barroso <javibarroso@gmail.com> - 2023-09-11 17:30 +0200
      Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-14 16:30 +0200
        Re: usrmerge on root NFS will not be run automatically Dan Ritter <dsr@randomstring.org> - 2023-09-14 17:20 +0200
          Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-14 18:10 +0200
          Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-14 20:30 +0200
            Re: usrmerge on root NFS will not be run automatically Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-14 23:00 +0200
              Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-15 14:00 +0200
                Re: usrmerge on root NFS will not be run automatically Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-15 15:30 +0200
          Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-14 22:20 +0200
            Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-10-03 13:50 +0200
          Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-15 14:00 +0200
            Re: usrmerge on root NFS will not be run automatically Andy Smith <andy@strugglers.net> - 2023-09-15 20:00 +0200
              Re: usrmerge on root NFS will not be run automatically Marco <lists@homerow.info> - 2023-09-15 23:40 +0200
          Re: sata driver compataility Q gene heskett <gheskett@shentel.net> - 2023-09-15 23:40 +0200
            Re: sata driver compataility Q Andy Smith <andy@strugglers.net> - 2023-09-16 00:00 +0200
              Re: sata driver compataility Q gene heskett <gheskett@shentel.net> - 2023-09-16 01:30 +0200
            Re: sata driver compataility Q songbird <songbird@anthive.com> - 2023-09-16 12:10 +0200
              Re: sata driver compataility Q gene heskett <gheskett@shentel.net> - 2023-09-16 13:50 +0200
                Re: sata driver compataility Q songbird <songbird@anthive.com> - 2023-09-16 14:10 +0200
          Re: sata driver compataility Q gene heskett <gheskett@shentel.net> - 2023-09-15 23:50 +0200
          Re: sata driver compataility Q gene heskett <gheskett@shentel.net> - 2023-09-19 03:40 +0200
            Amanda (was: sata driver compataility Q) Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-19 15:00 +0200
              Re: Amanda (was: sata driver compataility Q) gene heskett <gheskett@shentel.net> - 2023-09-19 17:20 +0200
                Re: Amanda (was: sata driver compataility Q) Glenn <ve9gj@napan.com> - 2023-09-19 19:00 +0200
          Re: PATH revisited: one PATH to "rule the [Debian] World" Greg Wooledge <greg@wooledge.org> - 2023-09-24 19:30 +0200
            When a random string is not random (was Re: PATH revisited: one PATH  to "rule the [Debian] World") Max Nikulin <manikulin@gmail.com> - 2023-09-25 05:20 +0200
          Re: PATH revisited: one PATH to "rule the [Debian] World" Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-09-24 21:50 +0200
            Re: PATH revisited: one PATH to "rule the [Debian] World" Greg Wooledge <greg@wooledge.org> - 2023-09-24 22:00 +0200
              Re: PATH revisited: one PATH to "rule the [Debian] World" Tom Browder <tom.browder@gmail.com> - 2023-09-24 22:50 +0200
                Re: PATH revisited: one PATH to "rule the [Debian] World" Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-09-24 23:00 +0200
                  Re: PATH revisited: one PATH to "rule the [Debian] World" Tom Browder <tom.browder@gmail.com> - 2023-09-24 23:30 +0200
          Message IDs, was Re: PATH revisited: one PATH to "rule the [Debian]  World" David Wright <deblis@lionunicorn.co.uk> - 2023-09-25 05:20 +0200
            Re: Message IDs, was Re: PATH revisited: one PATH to "rule the  [Debian] World" Dan Ritter <dsr@randomstring.org> - 2023-09-25 13:10 +0200

Page 1 of 3  [1] 2 3  Next page →

#260853 — Crosshairs in gimp 2.10.22 in Debian 11.7.

I've retrieved 'Gregs Crosshairs.scm.zip' and unzipped to
/home/me/.config/GIMP/2.10/scripts/GregsCrosshairs.scm.

If an image is open, Image > Guides gives a menu with four options.
New guide (by Percent)...
New guide...
New Guides from Selection
Remove all Guides

"New guide" allows creation of a horizontal or vertical dashed line 
at a specified fixed location.

Can gimp have window sized crosshairs?  Ie. horizontal and vertical 
lines intersecting at the mouse pointer hotpoint.

Thanks,    ... P.



- 
mobile: +1 778 951 5147
VoIP:   +1 604 670 0140

[toc] | [next] | [standalone]

#260865

peter@easthope.ca wrote: 
> I've retrieved 'Gregs Crosshairs.scm.zip' and unzipped to
> /home/me/.config/GIMP/2.10/scripts/GregsCrosshairs.scm.
> 
> If an image is open, Image > Guides gives a menu with four options.
> New guide (by Percent)...
> New guide...
> New Guides from Selection
> Remove all Guides
> 
> "New guide" allows creation of a horizontal or vertical dashed line 
> at a specified fixed location.
> 
> Can gimp have window sized crosshairs?  Ie. horizontal and vertical 
> lines intersecting at the mouse pointer hotpoint.

Not by default. What you do get is an indicator triangle on the
left and top rulers that follows the cursor.

-dsr-

[toc] | [prev] | [next] | [standalone]

#260872

    From: Dan Ritter <dsr@randomstring.org>
    Date: Sat, 12 Aug 2023 06:44:05 -0400
> Not by default. 

If someone finds an add-on providing lines intersecting at the 
hotpoint, a link will help.  Thanks.

> What you do get is an indicator triangle on the left and top rulers 
> that follows the cursor.

OK, thanks. With a line being more than one point, the ruler points 
don't answer the requirement.

Thanks for the reply,          ... P.


- 
mobile: +1 778 951 5147
VoIP:   +1 604 670 0140

[toc] | [prev] | [next] | [standalone]

#260929 — Re: random number generator missing after upgrade

[Multipart message — attachments visible in raw view] — view raw

Dan Ritter wrote:
> OK, either boot to the old kernel and look for an rng kernel
> module,

The only loaded module with "rng" in its name is "rng_core". That one
is present in both kernels, but four TPM-related modules are absent
from Linux 6.1:

# uname -v
#1 SMP Debian 5.10.179-3 (2023-07-27)
# lsmod | egrep -i 'rng|tpm'
tpm_crb                20480  0
tpm_tis                16384  0
tpm_tis_core           28672  1 tpm_tis
tpm                    73728  3 tpm_tis,tpm_crb,tpm_tis_core
rng_core               16384  3 ccp,tpm

# uname -v
#1 SMP PREEMPT_DYNAMIC Debian 6.1.38-3 (2023-08-07)
# lsmod | egrep -i 'rng|tpm'
rng_core               20480  1 ccp

And yet /dev/tpm0 exists in both kernels, but disappears when I
physically remove the TPM, so the TPM is recognized to some degree even
without those modules.

Those four TPM-related modules are also present as files under
/lib/modules in Linux 5.10, but absent in Linux 6.1. The corresponding
source files still exist in the source tree. Have they been disabled in
Debian 12? Have they been moved to some "extra modules" package that I
haven't found? Or are they just not modules because they're statically
built-in?

> or identify the rng hardware a little better

As I wrote in my first email, it seems to be an Infineon SLB 9665TT2.0.
It says "SLB9665TT20" on the chip package.

These characters are also written on the package. They mean nothing to
me, but maybe they can be used to identify the hardware better:
G1946KIV
51ZA947148IA1
(It's extremely difficult to tell I from 1 though.)

> and look
> for it in the kernel sources at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/hw_random

In that directory I don't see anything that looks relevant.

The identifier "tpm-rng-0" comes from tpm_add_hwrng in
drivers/char/tpm/tpm-chip.c, which is still there:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/char/tpm/tpm-chip.c?h=v6.1&id=830b3c68c1fb1e9176028d02ef86f3cf76aa2476#n517

Other functions in the same source file create /dev/tpm0, and it looks
like the random number generator should get registered together with
the TPM. It's conditional on CONFIG_HW_RANDOM_TPM. Where can I check
the value of that option?

Björn Persson

[toc] | [prev] | [next] | [standalone]

#260931 — Re: random number generator missing after upgrade

On Mon 14 Aug 2023 at 11:26:13 (+0200), Björn Persson wrote:

> Other functions in the same source file create /dev/tpm0, and it looks
> like the random number generator should get registered together with
> the TPM. It's conditional on CONFIG_HW_RANDOM_TPM. Where can I check
> the value of that option?

$ grep CONFIG_HW_RANDOM_TPM /boot/config-5.10.0-2*
/boot/config-5.10.0-23-amd64:CONFIG_HW_RANDOM_TPM=y
/boot/config-5.10.0-24-amd64:CONFIG_HW_RANDOM_TPM=y
$ 

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#260937 — Re: random number generator missing after upgrade

[Multipart message — attachments visible in raw view] — view raw

David Wright wrote:
> On Mon 14 Aug 2023 at 11:26:13 (+0200), Björn Persson wrote:
> > Other functions in the same source file create /dev/tpm0, and it looks
> > like the random number generator should get registered together with
> > the TPM. It's conditional on CONFIG_HW_RANDOM_TPM. Where can I check
> > the value of that option?  
> 
> $ grep CONFIG_HW_RANDOM_TPM /boot/config-5.10.0-2*
> /boot/config-5.10.0-23-amd64:CONFIG_HW_RANDOM_TPM=y
> /boot/config-5.10.0-24-amd64:CONFIG_HW_RANDOM_TPM=y
> $ 

Thanks. And look at that:

# grep CONFIG_HW_RANDOM_TPM /boot/config-*
/boot/config-5.10.0-23-amd64:CONFIG_HW_RANDOM_TPM=y
# grep CONFIG_HW_RANDOM_TPM /boot/config-6.1.0-11-amd64 ; echo $?
1

So apparently randomness from a TPM is completely disabled in Debian 12
regardless of manufacturer. Next question: Why?

Björn Persson

[toc] | [prev] | [next] | [standalone]

#260941 — Re: random number generator missing after upgrade

[Multipart message — attachments visible in raw view] — view raw

On Mon, 14 Aug 2023 Björn Persson wrote:
> David Wright wrote:
>> On Mon 14 Aug 2023 at 11:26:13 (+0200), Björn Persson wrote:
>>> Other functions in the same source file create /dev/tpm0, and it looks
>>> like the random number generator should get registered together with
>>> the TPM. It's conditional on CONFIG_HW_RANDOM_TPM. Where can I check
>>> the value of that option?
>>
>> $ grep CONFIG_HW_RANDOM_TPM /boot/config-5.10.0-2*
>> /boot/config-5.10.0-23-amd64:CONFIG_HW_RANDOM_TPM=y
>> /boot/config-5.10.0-24-amd64:CONFIG_HW_RANDOM_TPM=y
>> $
>
> Thanks. And look at that:
>
> # grep CONFIG_HW_RANDOM_TPM /boot/config-*
> /boot/config-5.10.0-23-amd64:CONFIG_HW_RANDOM_TPM=y
> # grep CONFIG_HW_RANDOM_TPM /boot/config-6.1.0-11-amd64 ; echo $?
> 1
>
> So apparently randomness from a TPM is completely disabled in Debian 12
> regardless of manufacturer. Next question: Why?

 Debian Bug #1041007
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041007#10

  Message #10
  From: Vincent Blut
  [...]
  Subject: linux-image-6.1.0-0.deb11.7-amd64: Please enable TPM hardware RNG support (CONFIG_HW_RANDOM_TPM)
  Date: Sat, 29 Jul 2023 00:33:35 +0200

  [...]
  Indeed, this regression compared to the kernel provided in bullseye
  is due to a configuration issue.
  For HW_RANDOM_TPM to be enabled, the TCG_TPM and HW_RANDOM config
  symbols are required but there is a subtlety in the way they have to
  be built. If TCG_TPM is built-in then HW_RANDOM must not be loadable
  (built as a module).

  If we take a look at the kernel configuration files prior being
  constructed, we can see that both TCG_TPM and HW_RANDOM config
  symbols should be built as modules:

  $ grep -Er "TCG_TPM|HW_RANDOM="
  arm64/config:CONFIG_TCG_TPM=m
  kernelarch-x86/config:CONFIG_TCG_TPM=m
  config:CONFIG_HW_RANDOM=m
  config.cloud:CONFIG_TCG_TPM=m

  However after these files have been constructed, the TCG_TPM config
  symbol is no longer provided as module but built-in:

  $ grep TCG_TPM /boot/config-6.3.0-1-amd64
  CONFIG_TCG_TPM=y

  This change is what causes HW_RANDOM_TPM to be disabled and is
  probably due to

   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=644f17412f5acf01a19af9d04a92193
  [...]

-- 
Hackers are free people. They are like artists. If they are in a good
mood, they get up in the morning and begin painting their pictures.
-- Vladimir Putin

[toc] | [prev] | [next] | [standalone]

#260951 — Re: random number generator missing after upgrade

[Multipart message — attachments visible in raw view] — view raw

davidson wrote:
>  Debian Bug #1041007
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041007#10

Yes, that seems to be exactly my problem. So it's not intentionally
disabled. Then I can hope that it may be fixed some day. Thanks for
your help.

Björn Persson

[toc] | [prev] | [next] | [standalone]

#261126 — Re: upgrade to bookworm broke phpmyadmin

On 8/23/23 18:14, Dan Ritter wrote:
> Rick Macdonald wrote:
>> Silly me though, I see I didn't actually describe the failure when I try to
>> connect to localhost/phpmyadmin. The browser just opens and shows the text
>> of the file /usr/share/phpmyadmin/index.php. Is this a clue?
> That generally means that the web server -- apache2? nginx? --
> does not know how to hand the .php file off to a php processor.
>
> For apache2, you would need to install libapache2-mod-php8.2 and
> then run
>
> a2enmod php8.2
>
> and
>
> service apache2 restart

Bingo! That's it! Thank-you so much, Dan!

libapache2-mod-php8.2 was already installed, so I just ran a2enmod and restarted.


So, given that I purged everything and re-installed and it still didn't 
work, is this indeed a packaging error? I've been running Debian for 
well over 25 years (I started with a pre-release before buzz was 
released) and I don't remember anything that didn't work after installing.

Rick

[toc] | [prev] | [next] | [standalone]

#261139 — Re: upgrade to bookworm broke phpmyadmin

> So, given that I purged everything and re-installed and it still didn't
> work, is this indeed a packaging error? I've been running Debian for well
> over 25 years (I started with a pre-release before buzz was released) and
> I don't remember anything that didn't work after installing.

I don't know the history of this precise thingy, but there can be valid
reasons to install both PHP and Apache, yet not to intend to run PHP
from Apache or not in the way that `a2enmod php8.2` does (especially
given the security risks it entails).

I have a vague recollection of having to explicitly enable/activate PHP
support in Apache's config many years ago, so I believe this is not
a new requirement.


        Stefan

[toc] | [prev] | [next] | [standalone]

#261144 — Re: upgrade to bookworm broke phpmyadmin

On 8/24/23 07:53, Stefan Monnier wrote:
>> So, given that I purged everything and re-installed and it still didn't
>> work, is this indeed a packaging error? I've been running Debian for well
>> over 25 years (I started with a pre-release before buzz was released) and
>> I don't remember anything that didn't work after installing.
> I don't know the history of this precise thingy, but there can be valid
> reasons to install both PHP and Apache, yet not to intend to run PHP
> from Apache or not in the way that `a2enmod php8.2` does (especially
> given the security risks it entails).
>
> I have a vague recollection of having to explicitly enable/activate PHP
> support in Apache's config many years ago, so I believe this is not
> a new requirement.

Fair enough, but if somebody installs the phpmyadmin package, which 
requires both PHP and Apache, clearly the intention is to "run PHP from 
Apache in the way that `a2enmod php8.2` does".

So, I finally found the following in 
/usr/share/doc/phpmyadmin/README.Debian:

> phpmyadmin for Debian
> ---------------------
>
>
> USAGE
>
>   The application will be available at http://localhost/phpmyadmin/
>   after install if you use one of supported web servers (Apache and 
> Lighttpd
>   at time of writing this). Please note that you need to have enabled PHP
>   support in your webserver (for Apache you can do this by a2enmod 
> php8.2, for
>   Lighttpd by lighty-enable-mod fastcgi).

I've been running phpmyadmin for years, so I can't swear I didn't 
manually enable this back in the day. I've done other Debian releases 
along the way but it never broke before.

However, I'm perfectly happy to say it's "my bad": for not scouring 
through these doc files.

Thanks again to all, I REALLY do appreciate the help!

Rick

[toc] | [prev] | [next] | [standalone]

#261198 — Re: Please verify Gnome and KDE wiki articles for correctness

On Sat, Aug 26, 2023 at 10:15 AM Dan Ritter <dsr@randomstring.org> wrote:
>
> Jeffrey Walton wrote:
> > Popularity Contest (https://popcon.debian.org/) would be good to
> > consult. But it looks like something is sideways. It does not provide
> > usage statistics for packages like kde-full and gnome. I'm getting the
> > message, "No Popularity contest entry for kde-full" (and friends). I
> > use kde-full and I have popularity contest enabled, so there should be
> > at least one entry.
>
> The basic problem with popcon is that it is opt-in, and nobody
> who is at all privacy conscious opts-in.
>
> (I fully support this decision. It is absolutely correct.)

A quick note with an opposing view... learning that I run libc or kde
on my Debian machine reveals information with little to no value.
Speaking for myself, I am not concerned about a privacy leak in this
particular case.

Telling the Debian maintainers I run libc and kde benefits me and the
community. Maintainers and developers learn where to allocate
resources. I think it's worth the leak since it benefits the distro
and the community.

> The result is that when a popcon entry exists, it represents the
> people who have opted-in to popcon, who are (in my opinion):
>
> - new users
> - individual users (not organization)
> - laptop users
> - desktop users
>
> If you are looking at a package and wondering about large
> organizations or servers, it's probably a bad source of data.

If an organization does not wish to share, then that's their business.
It's not the first time a company takes but does not give back. It
won't be the last time.

> For this particular purpose, it's actually useful:
>
> #rank name                            inst  vote   old recent no-files (maintainer)
> 1     perl-base                      219693 203274    17 16365    37 (Niko Tyni)
> 2     libc6                          219636 201427   609 17581    19 (Gnu Libc Maintainers)
>
> gnome-shell is the default window manager for GNOME:
>
> 738   gnome-shell                    53530 40495  4216  8804    15 (Debian Gnome Maintainers)
>
> kwin is the KDE window manager, so it's more or less as popular as KDE.
>
> 1402  kwin-common                    22176 15401  3453  3315     7 (Debian Qt/kde Maintainers)

Jeff

[toc] | [prev] | [next] | [standalone]

#261200 — Re: Please verify Gnome and KDE wiki articles for correctness

[Multipart message — attachments visible in raw view] — view raw

On Sat, Aug 26, 2023 at 10:29:02AM -0400, Jeffrey Walton wrote:
> On Sat, Aug 26, 2023 at 10:15 AM Dan Ritter <dsr@randomstring.org> wrote:

[...]

> > The basic problem with popcon is that it is opt-in, and nobody
> > who is at all privacy conscious opts-in.
> >
> > (I fully support this decision. It is absolutely correct.)
> 
> A quick note with an opposing view... learning that I run libc or kde
> on my Debian machine reveals information with little to no value.

[...]

> Telling the Debian maintainers I run libc and kde benefits me and the
> community. Maintainers and developers learn where to allocate
> resources [...]

I think this is the wrong angle. Opt-in is a sign of respect 
towards the users -- whatever reasons the user has is actually
totally irrelevant. It might be privacy, it might be something
else.

This attitude is one of the things why I love Debian.

Cheers
-- 
t

[toc] | [prev] | [next] | [standalone]

#261553 — Re: raid10 access problem

On 9/7/23 10:34, Dan Ritter wrote:
> gene heskett wrote:
>> I thought, when I installed bullseye on this box, that a raid is what I
>> needed for a /home partition, and indeed under bullseye it worked
>> flawlessly.  Since my surprise install of bookworm, cause by an update to
>> bullseye wiping out my user pw, so I went to another machine and downloaded
>> the netinstall.
>>
>> This raid is 4, 1T samsung SSD's, software raid.
> 
> I'm going to assume you're using the kernel's md system. What
> does
> 
> cat /proc/mdstat
> 
> say?
> 
> -dsr-
> .
gene@coyote:/home/nut$ cat /proc/mdstat
Personalities : [raid10] [linear] [multipath] [raid0] [raid1] [raid6] 
[raid5] [raid4]
md0 : active raid10 sdg1[1] sdf1[0] sdi1[3] sdh1[2]
       1842937856 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
       bitmap: 6/14 pages [24KB], 65536KB chunk

md1 : active (auto-read-only) raid10 sdi2[3] sdg2[1] sdf2[0] sdh2[2]
       62879744 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
         resync=PENDING

md2 : active (auto-read-only) raid10 sdf3[0] sdi3[3] sdg3[1] sdh3[2]
       3166208 blocks super 1.2 512K chunks 2 offset-copies [4/4] [UUUU]

unused devices: <none>
neither md1, nor md2 is actually mounted.

Thank you DSR.

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 <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#261554 — Re: raid10 access problem

On 9/7/23 13:28, Dan Ritter wrote:
> module(load="imuxsock" SysSock.Name="/run/systemd/journal/syslog" ) # provides support for local system logging
There was a simpler line there, I commented it out.

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 <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#261555 — Re: raid10 access problem

On 9/7/23 13:28, Dan Ritter wrote:
> gene heskett wrote:
>> On 9/7/23 10:34, Dan Ritter wrote:
>>> gene heskett wrote:
>>>> I thought, when I installed bullseye on this box, that a raid is what I
>>>> needed for a /home partition, and indeed under bullseye it worked
>>>> flawlessly.  Since my surprise install of bookworm, cause by an update to
>>>> bullseye wiping out my user pw, so I went to another machine and downloaded
>>>> the netinstall.
>>>>
>>>> This raid is 4, 1T samsung SSD's, software raid.
>>>
>>> I'm going to assume you're using the kernel's md system. What
>>> does
>>>
>>> cat /proc/mdstat
>>>
>>> say?
>>>
>>> -dsr-
>>> .
>> gene@coyote:/home/nut$ cat /proc/mdstat
>> Personalities : [raid10] [linear] [multipath] [raid0] [raid1] [raid6]
>> [raid5] [raid4]
>> md0 : active raid10 sdg1[1] sdf1[0] sdi1[3] sdh1[2]
>>        1842937856 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
>>        bitmap: 6/14 pages [24KB], 65536KB chunk
>>
>> md1 : active (auto-read-only) raid10 sdi2[3] sdg2[1] sdf2[0] sdh2[2]
>>        62879744 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]
>>          resync=PENDING
>>
>> md2 : active (auto-read-only) raid10 sdf3[0] sdi3[3] sdg3[1] sdh3[2]
>>        3166208 blocks super 1.2 512K chunks 2 offset-copies [4/4] [UUUU]
>>
>> unused devices: <none>
>> neither md1, nor md2 is actually mounted.
> 
> 
> That looks fine.
> 
> Let's get you logging things again.
> 
> apt install rsyslog
> 
> Then, in  /etc/systemd/system/syslog.service  add
> 
> Requires=syslog.socket
> 
under which [heading]?
> and in  /etc/rsyslog.conf  add
> 
> module(load="imuxsock" SysSock.Name="/run/systemd/journal/syslog" ) # provides support for local system logging
> 
> and now systemd will copy logs to rsyslogd, where they can be
> sent to disk in the old familiar way.
> 
> -dsr-
> .

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 <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#261572 — Re: Debian, Git server, Nginx, Fcgiwrap, and git push can not create remote object directory

Hello,

"I'm assuming that you replaced 'git.domain.com' and 'domain.com'
in this config with real domain names, and that they are
functional and tested."

Yes, the real domains are functional and tested.

"All this is to set up a fastCGI-compliant server protected with
HTTP basic auth and accessed via a socket at
/var/run/fcgiwrap.socket.

Is it running? Is it configured for a socket there?

are username and password properly set up in .gitpasswd?"

Yes, the fcgiwrap is running and the socket is there. Yes, usernames
and passwords are also set up in .gitpasswd.

"And here's a different one to run PHP scripts. Is php8.2
installed, is the fpm module installed and running, is
/run/php/php8.2-fpm.sock actually present?"

Yes, PHP 8.2 is installed and running, again that socket is also working.

Thanks.
Dave..


On 9/9/23, Dan Ritter <dsr@randomstring.org> wrote:
> David Mehler wrote:
>> I'm trying to set up a git server on Debian 12, served by Nginx via
>> https. I used this as a debian-specific starter though I have done
>> this in the past using a FreeBSD and Apache type setup:
>>
>> https://esc.sh/blog/setting-up-a-git-http-server-with-nginx/
>
> ...
>
>> nginx configuration file:
>>
>> server {
>> listen       443 ssl http2;
>>
>> server_name git.domain.com;
>>
>> # ECC/ECDSA certificates (dual config)
>> ssl_certificate /etc/ssl/domain.com/domain.com.fullchain.crt.ecc;
>> ssl_certificate_key /etc/ssl/domain.com/domain.com.key.ecc;
>> ssl_session_cache shared:domainSSL:50m;
>> ssl_dhparam /etc/ssl/domain.com/dhparams.pem;
>
> I'm assuming that you replaced 'git.domain.com' and 'domain.com'
> in this config with real domain names, and that they are
> functional and tested.
>
>
>> location / {
>> # First attempt to serve request as file, then
>> # as directory, then fall back to displaying a 404.
>> try_files $uri $uri/ =404;
>> }
>
>> location ~ (/.*) {
>> client_max_body_size 0;
>> auth_basic "Git Login";
>> auth_basic_user_file /etc/nginx/.gitpasswd;
>> fastcgi_pass  unix:/var/run/fcgiwrap.socket;
>> include       fastcgi_params;
>> fastcgi_param SCRIPT_FILENAME     /usr/lib/git-core/git-http-backend;
>> # export all repositories under GIT_PROJECT_ROOT
>> fastcgi_param GIT_HTTP_EXPORT_ALL "";
>> fastcgi_param GIT_PROJECT_ROOT    /srv/git;
>> fastcgi_param REMOTE_USER $remote_user;
>> fastcgi_param PATH_INFO           $1;
>> }
>
> All this is to set up a fastCGI-compliant server protected with
> HTTP basic auth and accessed via a socket at
> /var/run/fcgiwrap.socket.
>
> Is it running? Is it configured for a socket there?
>
> are username and password properly set up in .gitpasswd?
>
>> # Pass PHP Scripts To FastCGI Server
>> location ~ \.php$ {
>> fastcgi_split_path_info ^(.+\.php)(/.+)$;
>> fastcgi_pass unix:/run/php/php8.2-fpm.sock; #depends on PHP versions
>> fastcgi_index index.php;
>> fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
>> include fastcgi_params;
>> }
>> }
>
> And here's a different one to run PHP scripts. Is php8.2
> installed, is the fpm module installed and running, is
> /run/php/php8.2-fpm.sock actually present?
>
>
> This all smacks of following directions without understanding
> quite what they do. Everyone has to start somewhere.
>
> -dsr-
>

[toc] | [prev] | [next] | [standalone]

#261576 — Re: usrmerge on root NFS will not be run automatically

On Fri, 8 Sep 2023 12:26:38 -0400
Dan Ritter <dsr@randomstring.org> wrote:

> > That is quite an involved task. I didn't expect such fiddling for a
> > simple OS update. I'm a bit worried that the permissions and owners
> > go haywire when I copy stuff directly off the server onto a VM and
> > back onto the server. Is there a recommended procedure or
> > documentation available?  
> 
> Can you start a temporary VM directly on the server?

I might actually. I'll have to check the following days.

> If so, you can
> * stop your remote Debian machine
> * run a Debian rescue image in the VM on the NFS server
> * have the VM mount the filesystem directly
> * chroot, run usrmerge
> * unmount

Ok, that's also quite a task, but it seems less error-prone than
copying a bunch of system files across the network and hope for the
best. I'll try.

Marco

[toc] | [prev] | [next] | [standalone]

#261590 — Re: usrmerge on root NFS will not be run automatically

[Multipart message — attachments visible in raw view] — view raw

Hello,

El dom., 10 sept. 2023 21:55, Marco <lists@homerow.info> escribió:

> On Fri, 8 Sep 2023 12:26:38 -0400
> Dan Ritter <dsr@randomstring.org> wrote:
>
> > > That is quite an involved task. I didn't expect such fiddling for a
> > > simple OS update. I'm a bit worried that the permissions and owners
> > > go haywire when I copy stuff directly off the server onto a VM and
> > > back onto the server. Is there a recommended procedure or
> > > documentation available?
> >
> > Can you start a temporary VM directly on the server?
>
> I might actually. I'll have to check the following days.
>
> > If so, you can
> > * stop your remote Debian machine
> > * run a Debian rescue image in the VM on the NFS server
> > * have the VM mount the filesystem directly
> > * chroot, run usrmerge
> > * unmount
>
> Ok, that's also quite a task, but it seems less error-prone than
> copying a bunch of system files across the network and hope for the
> best. I'll try.
>
> Marco
>

Maybe you can open a new bug asking for a better documentation or what
should be done in this case.

Maybe dpkg -L with both files can help to clarify what should be done

Regards

>

[toc] | [prev] | [next] | [standalone]

#261663 — Re: usrmerge on root NFS will not be run automatically

On Fri, 8 Sep 2023 12:26:38 -0400
Dan Ritter <dsr@randomstring.org> wrote:

> Can you start a temporary VM directly on the server?

I just checked. I can, yes.

> If so, you can
> * stop your remote Debian machine

Ok, no problem.

> * run a Debian rescue image in the VM on the NFS server

No problem.

> * have the VM mount the filesystem directly

How? I can only attach devices (=whole disks) to the VM or mount the
FS via NFS. I can't attach it as a device because it's not a device,
rather than a directory with the root file systems of several hosts
directly on the server. So that doesn't work.

This leaves me with an NFS mount in the VM. But NFS mounts are not
supported by usrmerge, that's the whole issue I'm facing here.

So this VM-on-the-server idea doesn't work in my case or am I
missing something here?

Another question: if usrmerge complains that the file is present in
/lib as well as /usr/lib, what's the correct thing to do if

i)  the files are identical
ii) the files are different ?

Regards
Marco

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web