Resending this to everyone (sorry for the double send Richard).
On 14/04/2023 09:15, Andre Vieira (lists) wrote:
>
>
> On 14/04/2023 07:55, Richard Biener wrote:
>> On Thu, Apr 13, 2023 at 4:25 PM Andre Vieira (lists)
>> wrote:
>>>
>>>
>>&g
On 13/04/2023 15:00, Richard Biener wrote:
On Thu, Apr 13, 2023 at 3:00 PM Andre Vieira (lists) via Gcc-patches
wrote:
On 13/04/2023 11:01, Andrew Stubbs wrote:
Hi Andre,
I don't have a cascadelake device to test on, nor any knowledge about
what makes it different from regular x86_64
On 13/04/2023 11:01, Andrew Stubbs wrote:
Hi Andre,
I don't have a cascadelake device to test on, nor any knowledge about
what makes it different from regular x86_64.
Not sure you need one, but yeah I don't know either, it looks like it
fails because:
in-branch vector clones are not yet
install --allow-downgrades -y \
'xen-utils-common=4.14*' \
'libxenstore3.0=4.14*' \
'xenstore-utils=4.14*'
fails because I did run
'apt upgrade; apt dist-upgrade'
already:
Reading package lists... Done
Building dependency tree... Done
Reading state information
Hello!
a while ago when migrating Qubes 4.0 to Qubes 4.1
I restored a standalone debian VM (created on r4.0) on a fresh r4.1 system and
did not
notice that I also should replace the r4.0 repos _in_ the VM to r4.1 repos
but it still worked fine.
Today I replaced this line:
deb [arch=amd64]
On Mittwoch, 12. April 2023 17:14:46 CEST Linux-Hus Oni via tor-relays wrote:
> hi again, actulay i have made my exit to a bridge, so my bandwith is not so
> big for an exit. it is automatically removed from the metrics ?
Get a new IP, you put users at risk!
It doesn't matter, even if your relay
On Mittwoch, 12. April 2023 18:28:09 CEST tor-opera...@urdn.com.ua wrote:
> Finn wrote:
> > The weird thing is, that the relay in question is only a relay and
> > not an exit node since its creation (185.241.208.179)
> > (https://nusenu.github.io/OrNetStats/w/relay/B67C7039B04487854129A66B16F5E
>
On 4/12/23 07:54, Ralf Mardorf wrote:
I don't understand it. If it should be a signing issue, then it does
matter when using one mobo and doesn't matter, if the same SSD holding
the Arch Linux install is connected to another mobo? It only matters
when UEFI booting (with secure boot disabled),
On 4/12/23 03:55, Ralf Mardorf wrote:
Hi,
Bit hard to say from above - clearly these need 2 different keys
(right?) also you dont say what CONFIG_MODULE_COMPRESS_xx are set to
either since you have 2 different module compressions as well as keys
being different.
Maybe post the actual
On Dienstag, 11. April 2023 14:09:15 CEST Finn wrote:
> Hello everyone,
>
> We are hosting multiple relays under our AS 210558 and received an email
> from a local police station in Germany requesting user data, nothing
> unusual.
Nothing unusual? I had a house search because of exits but never a
On Thu, Apr 06, 2023 at 04:17:26PM +0200, Martin Schröder wrote:
> > I'd like to create a "bridge" between two IP networks which will pass
> > only multicast info. / traffic.
>
> So it should only route FF00::/8?
I'm not exactly sure of the siginificance of that address range, but in
the
Stimmengemenge verstärkt.
Nur falls es jemand wissen muss.
LG
Wiebke
Am 05.04.2023 11:49 schrieb Antonin Delpeuch (lists):
Hallo alle,
das Volkshaus klingt perfekt, wenn die Moritzbastei schon
Veranstaltungen hat. Ist es Nichtraucher?
Bis bald,
Antonin
On 05/04/2023 11:18, wiebkerein...@posteo.de wrote
On 4/7/23 09:27, Genes Lists wrote:
Closing the loop - this is now been fixed by mesa 23.0.2 in testing repo.
Big thanks to heftig for sorting it out so quickly!
gene
On 4/7/23 09:31, Petr Mánek wrote:
See also: https://bugs.archlinux.org/task/78137
Best I can tell there are 2 (possibly related) issues - (a) firefox
crashes on start and (b) firefox crashes on exit.
Course to get to (b) you have to not experience (a) :)
gene
On 4/7/23 09:22, Genes Lists wrote:
Running on gnome
This may have to do with updated updated wayland package (1.22.0-1) -
I confirm the problem goes away if I roll wayland back to prev version
(1.21.0-2)
So indeed the problem package is wayland.
Running on gnome
This may have to do with updated updated wayland package (1.22.0-1) -
didn't see much else that may be related.
I tried rolling back firefox and makes no difference - I also tried with
and without MOZ_ENABLE_WAYLAND - always get instant crash with:
Hi All,
I'd like to create a "bridge" between two IP networks which will pass
only multicast info. / traffic.
Is that something that I could do using OpenBSD and pf? I don't see
anything specific to multicasting in the pf.conf man page but I suppose
it should be possible to define a set of
ah non, pour une fois qu'un commercial se plante en public, laissons nous lui
proposer un RDV !
Fabien VINCENT
@beufanet
--- Original Message ---
Le mercredi 5 avril 2023 à 12:44, Jeremy a écrit :
> On peu ban ce mec qui n'a rien à faire sur cette liste et qui est en
> infraction
hat denn Zeit, z.B. am:
https://dud-poll.inf.tu-dresden.de/x7yQ-4h_xw/ ?
Laut Wiki waren die letzten Stammtische 18:30.
Gruß, Fabian.
Am 26.03.23 schrieb Antonin Delpeuch (lists):
Hallo die Runde,
ich bin neu in Leipzig und hätte Lust, die lokale OSM-Gemeinschaft
kennen
zu lernen
Hi,
The original patch to fix this PR broke the if-conversion of calls into
IFN_MASK_CALL. This patch restores that original behaviour and makes
sure the tests added earlier specifically test inbranch SIMD clones.
Bootstrapped and regression tested on aarch64-none-linux-gnu and
Hi,
If you are only fetching data via the API, then you should only be
making GET requests, right? In that case, did you try setting the
"origin=*" GET parameter? That should be enough to set the appropriate
CORS headers on the response.
See:
On 4/2/23 12:07, Matthew Blankenbeheler wrote:
Does this method 2 mean making 3 partitions?
The UEFI spec requires that the Extended Boot Loader be its own
partition of type XBOOTLDR (gpt EA00) - so yes thats correct.
1 partition for (/efi), 1 for extended boot loader (/boot) and
On 4/2/23 07:44, Genes Lists wrote:
[1] XBOOTLDR
https://uapi-group.org/specifications/specs/discoverable_partitions_specification/
Oops, Forgot to provide this link as well:
https://uapi-group.org/specifications/specs/boot_loader_specification/
On 4/2/23 04:04, Ralf Mardorf wrote:
Assuming I would do without the museum, then the modern kernels would
have to be in the ESP, a FAT partition without file permissions. Or do I
misunderstand something?
Ralf
Here's a brief overview. There are 2 methods available for UEFI
booting
On Freitag, 31. März 2023 16:56:16 CEST denny.obre...@a-n-o-n-y-m-e.net wrote:
> The second IP is still in "Exit Addresses" with the new configuration ...
> https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B
> 5881B7D4C97C
I don't understand that now either. I have at
Hi denny,
> Hi,
>
> I just activated my first exit relay. (
> https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B
> 5881B7D4C97C ) I had the following in my torrc (plus some other things):
I've answered the rest to the list.
If you want to enable IPv6 at Frantech/BuyVM:
On Freitag, 31. März 2023 01:26:42 CEST denny.obre...@a-n-o-n-y-m-e.net wrote:
> Hi,
>
> I just activated my first exit relay. (
> https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B
> 5881B7D4C97C ) I had the following in my torrc (plus some other things):
Don't forget
/ ?
Laut Wiki waren die letzten Stammtische 18:30.
Gruß, Fabian.
Am 26.03.23 schrieb Antonin Delpeuch (lists):
Hallo die Runde,
ich bin neu in Leipzig und hätte Lust, die lokale OSM-Gemeinschaft
kennen zu lernen. Anscheinend ist der Stammtisch nicht mehr regelmäßig
aktiv, aber ich frage mich
:-)
Jeff Broadwick
CTIconnect
312-205-2519 Office
574-220-7826 Cell
jbroadw...@cticonnect.com
> On Mar 27, 2023, at 1:15 PM, Jaime Solorza wrote:
>
>
> Here you go Jeff..
> <20230311_172607.jpg>
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
On 27/03/2023 01:18, Dale wrote:
Thanks for any light you can shed on this. Googling just leads to a ton
of confusion. What's true 6 months ago is wrong today. :/ It's hard
to tell what still applies.
Well, back in the days of the megahurtz wars, a higher clock speed
allegedly meant a
Hallo die Runde,
ich bin neu in Leipzig und hätte Lust, die lokale OSM-Gemeinschaft
kennen zu lernen. Anscheinend ist der Stammtisch nicht mehr regelmäßig
aktiv, aber ich frage mich, ob irgendwelche Leute doch Interesse hätten,
uns zu treffen.
Vielen Dank an allen für den wunderbaren
On 3/26/23 01:02, rino mardo wrote:
if i stop the iwd, my wireless connections goes away. wlan0 also
Try tell network manager to use iwd - create this file:
/etc/NetworkManager/conf.d/wifi_backend.conf
with these 2 lines
[device]
wifi.backend=iwd
Stop it please. I enjoy this list for tidbits of industry info and it’s friendly banter. I’m even interested in Jaime’s breakfast and weather girls.If the politics was light and friendly, I’d be all in…this is anything but.Jeff BroadwickCTIconnect312-205-2519 Office574-220-7826
From: Alexis Lothoré
Regression reports are not generated on some integration branches because
yocto_testresults_query.py truncates branches names with slashes when it passes
it to resulttool. For example, "abelloni/master-next" is truncated to "abelloni"
Fix this unwanted branch truncation by
On 3/23/23 13:44, Rémy Oudompheng wrote:
Hello
Texlive packages have been updated to 2023 version in [testing].
...
Thank you Rémy.
I don't use luaxxx. On the docs I've tested so far, pdflatex is
working well.
gene
From: Alexis Lothoré
Regression reports are currently stored alongside test reports and other
artifacts on the autobuilder artifacts web page. This small update propose to
add a link to the regression report (when available) on main non-release page
([1]) instead of having to manually navigate
From: Alexis Lothoré
When available, expose tesresult-regressions-report.txt on non-release web page,
as it is done for many other artifacts currently
Signed-off-by: Alexis Lothoré
---
scripts/generate-testresult-index.py | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/generate-testresult-index.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/generate-testresult-index.py
b/scripts/generate-testresult-index.py
index 1fc9f41..09d2edb 100755
---
Hi Richard,
On 3/24/23 10:55, Richard Purdie wrote:
> On Fri, 2023-03-24 at 10:00 +0100, Alexis Lothoré via
> lists.yoctoproject.org wrote:
>> From: Alexis Lothoré
>> -entries.append((build, reldir, btype, testreport, branch, buildhistory,
>> perfreports, ptestlogs, hd))
>> +
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/generate-testresult-index.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/generate-testresult-index.py
b/scripts/generate-testresult-index.py
index 1fc9f41..09d2edb 100755
---
From: Alexis Lothoré
Regression reports are currently stored alongside test reports and other
artifacts on the autobuilder artifacts web page. This small update propose to
add a link to the regression report (when available) on main non-release page
([1]) instead of having to manually navigate
From: Alexis Lothoré
When available, expose tesresult-regressions-report.txt on non-release web page,
as it is done for many other artifacts currently
Signed-off-by: Alexis Lothoré
---
scripts/generate-testresult-index.py | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff
From: Alexis Lothoré
Some nightly builders are configured in yocto-autobuilder2 to run master builds.
Those build parameters currently skip all branches of
get_regression_base_and_target, which then return None, while the caller
expects a base and target tuple
Set default behaviour to return
From: Alexis Lothoré
It has been observed that regression reporting is currently failing on nightly
builds ([1]). Those builds parameters are currently not properly managed by the
base and target computation for regression reports. Add default behaviour to
generate report against last tag
[1]
From: Alexis Lothoré
When the test assert is about a tag in Poky, the result will not be the same
depending on existing tags at the time of running tests.
Add a LAST_TAG marker to loosen constraints but still allow to tests for general
cases (e.g. : test that tag-depending tests does not return
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/test_utils.py | 10 ++
1 file changed, 10 insertions(+)
diff --git a/scripts/test_utils.py b/scripts/test_utils.py
index ab91e3b..d02e9b2 100755
--- a/scripts/test_utils.py
+++ b/scripts/test_utils.py
@@ -99,6 +99,16 @@
Hi Richard,
On 3/22/23 10:41, Richard Purdie wrote:
> On Mon, 2023-03-13 at 15:51 +0100, Alexis Lothoré via
> lists.yoctoproject.org wrote:
>> From: Alexis Lothoré
>>
>> This series fixes regression report generation on "next" branches, as raised
>> in
>> [1].
>>
>> The first five patches are
On 3/21/23 04:26, lacsaP Patatetom wrote:
hi everybody,
my development workstation is running 6.1.20-1-lts and I made
linux-lts-ro-6.1.15-1-x86_64.pkg.tar.zst and
linux-lts-ro-headers-6.1.15-1-x86_64.pkg.tar.zst packages on it : if now
I want to compile on this development workstation
From: Alexis Lothoré
There is a typo in BUILD_HISTORY_FORKPUSH, leading to failures on Autobuilder
when trying to generate regression reports:
Traceback (most recent call last):
File
"/home/pokybuild/yocto-worker/a-full/yocto-autobuilder-helper/scripts/send-qa-email",
line 213, in
if I understand correctly, I can install my package
linux-lts-perso-6.1.15-2-x86_64.pkg.tar.zst, boot on it (eg. "my"
kernel) and continue to use the binaries present on my system while they
have not been compiled with its (new) headers and especially for the
binaries that call the
On 3/20/23 06:44, lacsaP Patatetom wrote:
Please don't top post on mailing lists.
I don't understand what 'problem' you are speaking of. All you've asked
is if you can install a kernel headers from a different build - the
general answer is "no" - don't ever do that.
I already
On 3/20/23 05:27, lacsaP Patatetom wrote:
hi,
- When you change the source you must also bump pkgrel as the package
is now different.
- If you want to build your own version of an Arch package, you should
not use same package name as the official Arch package - this will only
lead to
On Freitag, 17. März 2023 17:25:10 CET Bauruine wrote:
> ... but I'll
> just keep "mining" consensus weight. Because you don't need a modified
> version of Tor and you don't need the blockchain for that. Just download
> the consensus and look at the consensus weight and you have your proof
> of
On 3/14/23 12:50, Tobias Powalowski wrote:
Hi guys,
early spring cleanup on my adopted packages:
..
- mdadm
Thanks for all the work you've put into Arch Tobias - it is very much
appreciated.
Of the packages you listed, I sure hope mdadm will be picked up - this
quite obviously is a very
Hi Richard,
I'm only picking this up now. Just going through your earlier comments
and stuff and I noticed we didn't address the situation with the
gimple::build. Do you want me to add overloaded static member functions
to cover all gimple_build_* functions, or just create one to replace
> On 14 Mar 2023, at 02:50, Rick Womer wrote:
>
> I took my camera for a walk on a lovely afternoon a week ago. These
> were my favorites.
>
> https://rickwomer.smugmug.com/2023/March-2023/Woodland-Cemetery-3-6-23/
>
Nice and pleasing images Rick!
It sure seems like lovely weather ;-)
This patch fixes the condition check for eligilibity of lowering bitfields,
where before we would check for non-BLKmode types, in the hope of excluding
unsuitable aggregate types, we now check directly the representative is
not an
aggregate type, i.e. suitable for a scalar register.
I tried
From: Alexis Lothoré
Add "abelloni/master-next" branch from poky-contrib in configuration so that
regression reports are generated when testing for patches
Signed-off-by: Alexis Lothoré
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.json
From: Alexis Lothoré
d6018b891a3b7c62c7a2883c7fb9ae55e66f1363 broke regression reporting for testing
branches (e.g: master-next in poky, ross/mut in poky-contrib) by ignoring the
comparebranch returned by
utils.getcomparison branch
Fix regression reporting for those branches by using
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/test_send_qa_email.py | 21 +
1 file changed, 21 insertions(+)
diff --git a/scripts/test_send_qa_email.py b/scripts/test_send_qa_email.py
index 48bca98..ccdcba6 100755
--- a/scripts/test_send_qa_email.py
+++
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/test_send_qa_email.py | 10 ++
1 file changed, 10 insertions(+)
diff --git a/scripts/test_send_qa_email.py b/scripts/test_send_qa_email.py
index c1347fb..48bca98 100755
--- a/scripts/test_send_qa_email.py
+++
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/send_qa_email.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/send_qa_email.py b/scripts/send_qa_email.py
index 320ff24..540eb94 100755
--- a/scripts/send_qa_email.py
+++ b/scripts/send_qa_email.py
@@
From: Alexis Lothoré
This series fixes regression report generation on "next" branches, as raised in
[1].
The first five patches are preparatory updates for the real fix, being either
refactoring, cleanup or unit tests addition to better understand how integration
branches are used in
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/send_qa_email.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/send_qa_email.py b/scripts/send_qa_email.py
index 7999c1b..96225a8 100755
--- a/scripts/send_qa_email.py
+++ b/scripts/send_qa_email.py
@@ -83,7 +83,6 @@
From: Alexis Lothoré
Signed-off-by: Alexis Lothoré
---
scripts/test_utils.py | 104 ++
1 file changed, 104 insertions(+)
create mode 100755 scripts/test_utils.py
diff --git a/scripts/test_utils.py b/scripts/test_utils.py
new file mode 100755
index
From: Alexis Lothoré
is_non_release_version has an inverted logic which makes its reuse quite
confusing
Transform it as is_release_version and let caller do the negation if needed
Signed-off-by: Alexis Lothoré
---
scripts/send_qa_email.py | 6 +++---
1 file changed, 3 insertions(+), 3
On 3/13/23 05:56, Genes Lists wrote:
On 3/13/23 03:00, David Bohman wrote:
There is a fairly serious regression in linux-6.2.3 that kills wifi:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79d1ed5ca7db67d48e870c979f0e0f6b0947944a
Hi David:
I am sure
On 3/13/23 03:00, David Bohman wrote:
There is a fairly serious regression in linux-6.2.3 that kills wifi:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79d1ed5ca7db67d48e870c979f0e0f6b0947944a
Hi David:
I am sure this commit is in 6.2.3 and all later stable
On Sonntag, 12. März 2023 04:45:21 CET Keifer Bly wrote:
> I do not use any scripts to start tor, I just type tor to start the process
> on debian.
That's where your problems begin. You start a 2nd tor process as root that
doesn't take the default configs from:
On Dienstag, 7. März 2023 13:31:13 CET mail--- via tor-relays wrote:
> Running a few relays on 1-2 CPU cores with limited RAM is
> fine, but just keep an eye on it and don't run other memory intensive stuff
> on the server (like DNS query caching, which can take quite some RAM as
> well).
A
On Mittwoch, 8. März 2023 18:13:01 CET Keifer Bly wrote:
> Strangely, nothing whatsoever is being written to the notices.log file,
> upon checking it it is completely empty, nothing there.
That can't be, please post:
~# ls -A /var/log/tor
In general, everything is always written to
On Dienstag, 7. März 2023 03:00:49 CET Sydney wrote:
> Newbie here. No network experience but already running 2 TOR instances: 1
> TOR service + 1 bridge.
Never mix different relay types under one IP.
> I would like to "upgrade" to TOR relays but have a few questions relating to
> hardware needs.
Curious - Are you able to ping the WKD webserver from failing machine?
ping openpgpkey.archlinux.org
On 3/10/23 05:39, Łukasz Michalski wrote:
A and B. Both updated at the same time. On A service works, on B it fails.
I have similar situation. On a machine that had fails running manually
worked fine.
What happens if you run manually?
/usr/bin//archlinux-keyring-wkd-sync
best
gene
From: Alexis Lothoré
The script currently only works if base and target can be found on default
branches. It breaks if we try to generate a regression report between revisions
that live on different branches (as needed on integration and testing branches).
For example, the following command:
Hi,
This RFC is to propose relaxing the flag needed to allow the creation of
simd clones from omp declare variants, such that we can use
-fopenmp-simd rather than -fopenmp.
This should only change the behaviour of omp simd clones and should not
enable any other openmp functionality, though I
Hi,
This RFC extends the omp-simd-clone pass to create simd clones for
functions with 'omp declare variant' pragmas that contain simd
constructs. This patch also implements AArch64's use for this functionality.
This requires two extra pieces of information be kept for each
simd-clone, a
Hi,
This patch adds SVE support for simd clone generation when using 'omp
declare simd'. The design is based on what was discussed in PR 96342,
but I did not look at YangYang's patch as I wasn't sure of whether that
code's copyright had been assigned to FSF.
This patch also is not in
Hi,
This patch modifies this function in parloops to allow it to handle
loops with poly iteration counts.
gcc/ChangeLog:
* tree-parloops.cc (try_transform_to_exit_first_loop_alt):
Handle poly nits.
Is this OK for Stage 1?diff --git a/gcc/tree-parloops.cc b/gcc/tree-parloops.cc
Hi,
This patch makes sure we copy over
DECL_FUNCTION_SPECIFIC_{TARGET,OPTIMIZATION} in parloops when creating
function clones. This is required for SVE clones as we will need to
enable +sve for them, regardless of the current target options.
I don't actually need the 'OPTIMIZATION' for this
Hi,
This patch replaces the uses of simd_clone_subparts with
TYPE_VECTOR_SUBPARTS and removes the definition of the first.
gcc/ChangeLog:
* omp-sind-clone.cc (simd_clone_subparts): Remove.
(simd_clone_init_simd_arrays): Replace simd_clone_subparts with
TYPE_VECTOR_SUBPARTS.
Hi all,
This is a series of patches/RFCs to implement support in GCC to be able
to target AArch64's libmvec functions that will be/are being added to glibc.
We have chosen to use the omp pragma '#pragma omp declare variant ...'
with a simd construct as the way for glibc to inform GCC what
> On 5 Mar 2023, at 14:12, Alan C wrote:
>
> We were graced by the appearance of Guinea Fowl with chicks.
Nice one Alan!
Saw lots of those, sometimes in flocks of hundreds, last year in the Kalahari
Desert (Deception Valley, Botswana).
> They have a hard time around here with all the
All
I gave updated the code and now provide an inotify based daemon to sync
alternate s - and a systemd service unit to run it.
I would very much appreciate if others ran this - by using the test
option it does nothing but prints what would happen. And can be run as
non-root user.
It is
On 3/7/23 03:50, Óscar García Amor wrote:
El lun, 06-03-2023 a las 21:30 -0500, Jonathan Whitlock escribió:
This is about having a computer that is resilient to root drive failure.
This is in addition to doing backups, certainly not a replacement :)
gene
On 3/4/23 12:56, Genes Lists wrote:
I know there's lots of info available about dual boot - but not much I
could find on Dual Root.
What is Dual Root?
This is a machine with 2 "root" disks where the second one is a hot
standby - in event of root disk failure the secon
On 3/6/23 02:50, Óscar García Amor wrote:
Interesting, I'll take a look at it when you upload the code.
I'd appreciate wider testing on the code - we all know that just because
it works for me, doesn't mean it will work everywhere with certainty.
It would be super helpful if others can
On 06/03/2023 11:08, Peter Humphrey wrote:
On Monday, 6 March 2023 10:56:37 GMT Wols Lists wrote:
On 06/03/2023 10:06, Michael wrote:
I suspect the behaviour you noticed is related to FF functionality like
TRR
(Trusted Recursive Resolver) farming all your DNS queries over to the
cloudfarce
On 06/03/2023 10:06, Michael wrote:
On Monday, 6 March 2023 08:24:35 GMT Wols Lists wrote:
On 06/03/2023 08:08, Neil Bothwick wrote:
On Mon, 6 Mar 2023 07:54:51 +, Wols Lists wrote:
There's another file - can't remember its name - that tells your
resolver what to try in what order
On 06/03/2023 08:08, Neil Bothwick wrote:
On Mon, 6 Mar 2023 07:54:51 +, Wols Lists wrote:
There's another file - can't remember its name - that tells your
resolver what to try in what order - the hosts file, dns, what dhcp
told you, etc etc, so your resolver might not be using dns the way
On 05/03/2023 18:41, Dale wrote:
I edited the file they say with kwrite. Even after I restart openvpn,
the IP they want is there but it doesn't use it according to the site
they sent for me to check it with. It shows other IP addresses. I'm
sure I'm missing something, likely something simple,
I have updated the notes which now shows the original way but also the
approach suggested by Oscar (thank you) - this is a superior method but
bit more painful for existing installs.
This way has on each disk along with btrfs raid1 for the rest
basically.
I have a working example doing
This is _not_ my relay:
https://metrics.torproject.org/rs.html#details/D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11
https://nusenu.github.io/OrNetStats/w/relay/D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11.html
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
On 3/5/23 07:11, Óscar García Amor wrote:
In fact at hook level you can put one like in the example of the manual
ml
Yes I agree that Hooks are useful, but they do only catch things on
package updates as far as I know. If you want to catch manual changes,
like an edit to a loader file, then
On 3/5/23 07:11, Óscar García Amor wrote:
Thanks Oscar - I edited my notes to show this as the preferred approach.
Still needs more write up but I thought it best to get it up sooner than
later.
Do you know if it would work to use separate /boot partitions, as I
mention above, (each
On 3/5/23 05:13, Óscar García Amor wrote:
...
The method is simple as you simply need two partitions on the two
disks. The first one on each disk is the ESP and the second one is the
one you are going to use for the btrfs raid. Then you simply mount the
raid1 between both partitions btrfs[1] and
On Samstag, 4. März 2023 02:09:19 CET Keifer Bly wrote:
> Wheres the pastebin page? Thanks.
$websearch pastebin
https://paste.debian.net/
https://paste.systemli.org/
https://pastebin.mozilla.org/
...
--
╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!
On 3/4/23 18:22, Genes Lists wrote:
But your cautionary comment is definitely something to keep an eye on.
I already have these concerns noted at the bottom of the notes - since
you pointed it out, It would be better for me to highlight them and
move them earlier in the notes.
thanks
On 3/4/23 18:08, Łukasz Michalski wrote:
I have this setup on all servers that do not have battery backed HW raid
cards and use mdadm there. I use systemd-boot as bootloader. Works well
and can be done on existing system with just a single reboot. It is not
easy - you have to create degraded
On 3/4/23 13:21, Uwe Sauter wrote:
The usual Linux MD-RAID can have its metadata placed on different
positions in the partition (see man (8) mdadm, option "-e, --metadata").
This is intriguing for sure but to be honest it has a bit of a brittle,
hacky feel to it.
My own preference is
801 - 900 of 37080 matches
Mail list logo
