Alternative à la FAT32 ou l'exFAT

[benoit]

Bonjour à tou·te·s

Quel est le système de fichier libre d'origine (et pas libre pour échéance de 
brevet), pour remplacer la FAT32 ?
C'est pour le disque dur externe de mes photos qui viennent de la carte 
SD(formatée en FAT) de mon appareil photo, les fichiers n'ont pas de droit 
d'accès.
Pour passer d'un ordi à l'autre, quel est le système de fichier idéal ?

Merci d'avance.

--
Benoît

Envoyé avec la messagerie sécurisée [Proton Mail](https://proton.me/).

Faire venir gedit au premier plan sur ouverture d'un fichier texte

[roger . tarani]

Bonjour, 

Sous debian 11 (ou versions précédentes, d'ailleurs), comment fait-on pour 
choisir le mode de mise au premier plan d'une application lorsqu'on ouvre un 
fichier qui y est lié ? 

Par exemple, un lien vers une page web dans le shell ou une autre application 
(traitement de texte ou autre éditeur) va lancer automatiquement le navigateur 
(FF, par exemple), qui va apparaître au premier plan. 
De même pour un fichier pdf qui va ouvrir Document viewer ou autre visionneuse. 

Mais quand j'ouvre un bête fichier texte, il s'ouvre dans gedit tandis que 
gedit ne vient pas au premier plan. 

Comment configurer ce comportement pour gedit (venir au premier plan sur 
ouvertur du fichier) ? 
Y a-t-il une raison à ce comportement ? 

Merci. 

Re: Helium [was: t-bird screwing up]

[David Wright]

On Thu 03 Nov 2022 at 17:27:17 (+0100), to...@tuxteam.de wrote:

> Nice stories :) I did theoretical physics, but of course, our
> faculty was chock full of crazy and interesting folks doing stuff
> like you described above. Searching for leaks in the apparatus
> consisted of... pumping it full of helium and sniffing for it
> with a sensor :-)

… whereas we did the opposite: searching for inward leaks through
joint seals, we used the spray test, squirting a tiny jet of He
at suspect points and detecting any He being pumped out. As expected,
we never saw He entering through the stainless steel or its welds.

Cheers,
David.

Re: Will my reconstructed fstab work?

[mick.crane]

On 2022-11-03 04:52, Ken Heard wrote:

A few days ago using vim I added to my desktop fstab file a line for a
new portable storage device.  in the process I somehow managed to
screw up fstab.  Unfortunately I saved the screwed up version of fstab
before I noticed the damage done to it.




01 -e8b57fb2ac09static file system information.
02 -e8b57fb2ac09
03 -e8b57fb2ac09lkid' to print the universally unique identifier for a
04 -e8b57fb2ac09vice; this may be used with UUID= as a more robust way
to name devices
05 -e8b57fb2ac09at works even if disks are added and removed. See 
fstab(5).


It is likely unrelated but I had a thing a while ago while editing files 
with vim/nano that random text from within the file would be randomly 
inserted elsewhere in the file which was incredibly disturbing.

mick.

Re: Trying to start Xorg on a vanilla bullseye on rpi4

[Tim Woodall]

On Thu, 3 Nov 2022, Andrew M.A. Cater wrote:


On Thu, Nov 03, 2022 at 06:12:56PM +, Tim Woodall wrote:

Hi,

I have a vanilla installation of debian bullseye on a rpi4



Just going to check: this is a Debian image from gwolf and 
https://raspi.debian.net/ and not a Raspberry Pi OS image from Raspberry Pi 
foundation?


It's a home built image but only with stock debian packages installed. I
don't believe those images have X setup, but if they do then I'll try
one which might give me a clue what I've done wrong.


The image is 32 bit or 64 bit?


64 bit


[Only because there is consistent confusion - if it really is Debian, we
can likely do more].



Which doesn't really tell me a lot...

If I start with one screen connected and then plug in the other then I
get a mirrored display whan I start the second output with xandr. But
any attempt to use xrandr to move them fails.


Does anyone have any ideas of what I need to do to get this working?

Even just being able to start X without having to unplug a screen would be a
start.

Tim.



All best, as ever,

Andy Cater

Re: Fanget i DNS

[Adam Sjøgren]

Flemming writes:

> Jeg har bemærket at der er danske alternativer med gratis dns. Er der
> nogle I kan anbefale?

Der er QuickDNS: https://www.quickdns.dk/ - de har vist ikke support for
DNSSEC, hvilket var en af grundene til at jeg har en minimal virtuel
server hos hhv. Linode og Digital Ocean som jeg sammen med min
hjemmeserver bruger til at køre DNS (og mail) selv.

bind er lidt bøvlet at få sat op, men når det først kører, så kører det
bare.

Mht. reverse DNS og udbydere sætter Kviknet det op hvis man henvender
sig til kundeservice.

(Før Fullrate blev købt af YouSee kunne man selv konfigurere det i deres
brugerinterface, det forsvandt naturligvis efter sammenlægningen.)

For VPS'er har både Linode og Digital Ocean rDNS sat til hostnavnet for
både IPv4 og IPv6 for mine to.


  Best regards,

Adam

-- 
 "Many activities in life are either so difficult   Adam Sjøgren
  or so boring and repetitive that we would like   a...@koldfront.dk
  to delegate them to other people or to machines"

Re: Trying to start Xorg on a vanilla bullseye on rpi4

[Andrew M.A. Cater]

On Thu, Nov 03, 2022 at 06:12:56PM +, Tim Woodall wrote:
> Hi,
> 
> I have a vanilla installation of debian bullseye on a rpi4
> 

Just going to check: this is a Debian image from gwolf and 
https://raspi.debian.net/ and not a Raspberry Pi OS image from Raspberry Pi 
foundation?

The image is 32 bit or 64 bit?

[Only because there is consistent confusion - if it really is Debian, we
can likely do more].

> 
> Which doesn't really tell me a lot...
> 
> If I start with one screen connected and then plug in the other then I
> get a mirrored display whan I start the second output with xandr. But
> any attempt to use xrandr to move them fails.
> 
> 
> Does anyone have any ideas of what I need to do to get this working?
> 
> Even just being able to start X without having to unplug a screen would be a
> start.
> 
> Tim.
>

All best, as ever,

Andy Cater 

Trying to start Xorg on a vanilla bullseye on rpi4

[Tim Woodall]

Hi,

I have a vanilla installation of debian bullseye on a rpi4

But I cannot get X to start with two 4K screens attached.


The error (entire log below) is
[   707.980] (II) modeset(0): Output HDMI-1 connected
[   707.980] (II) modeset(0): Output HDMI-2 connected
[   707.980] (II) modeset(0): Using spanning desktop for initial modes
[   707.980] (II) modeset(0): Output HDMI-1 using initial mode 3840x2160 +0+0
[   707.980] (II) modeset(0): Output HDMI-2 using initial mode 3840x2160 +3840+0
[   707.980] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[   707.980] (==) modeset(0): DPI set to (96, 96)
[   707.980] (II) Loading sub module "fb"
[   707.981] (II) LoadModule: "fb"
[   707.981] (II) Loading /usr/lib/xorg/modules/libfb.so
[   707.982] (II) Module fb: vendor="X.Org Foundation"
[   707.982]compiled for 1.20.11, module version = 1.0.0
[   707.982]ABI class: X.Org ANSI C Emulation, version 0.4
[   707.983] (II) UnloadModule: "fbdev"
[   707.983] (II) Unloading fbdev
[   707.983] (II) UnloadSubModule: "fbdevhw"
[   707.983] (II) Unloading fbdevhw
[   707.999] (EE) 
Fatal server error:

[   707.999] (EE) AddScreen/ScreenInit failed for driver 0
[   707.999] (EE) 
[   707.999] (EE)


Which doesn't really tell me a lot...

If I start with one screen connected and then plug in the other then I
get a mirrored display whan I start the second output with xandr. But
any attempt to use xrandr to move them fails.



root@test17:~# xrandr --output HDMI-2 --mode 3840x2160 --panning 3840x2160+0+0
root@test17:~# xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 7680 x 7680
HDMI-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y 
axis) 600mm x 340mm
   3840x2160 27.26*+  30.0025.0024.0029.9723.98
   2560x1440 59.95
   1920x1080 60.0059.9430.0029.97
   1920x1080i60.0059.94
   1600x900  60.00
   1280x1024 60.02
   1280x800  59.91
   1280x720  60.0059.94
   1024x768  60.00
   800x600   60.32
   720x480   60.0059.94
   640x480   60.0059.94 
HDMI-2 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm

   3840x2160 27.26*+  30.0030.0025.0024.0029.9723.98
   2560x1440 59.95
   1920x1080 60.0060.0059.9430.0024.0029.9723.98
   1920x1080i60.0059.94
   1600x900  60.00
   1280x1024 60.02
   1280x800  59.91
   1280x720  60.0059.94
   1024x768  60.00
   800x600   60.32
   720x480   60.0059.94
   640x480   60.0059.94


root@test17:~# xrandr --output HDMI-2 --mode 3840x2160 --panning 
3840x2160+3840+0
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  7 (RRSetScreenSize)
  Serial number of failed request:  35
  Current serial number in output stream:  36
root@test17:~#


Does anyone have any ideas of what I need to do to get this working?

Even just being able to start X without having to unplug a screen would be a
start.

Tim.

Re: Helium [was: t-bird screwing up]

[gene heskett]

On 11/3/22 10:39, David Wright wrote:
[...]

Do you think they cared?


Of course not, our taxes were footing the bill and they can always
feel that last penny and be upset they did not get it.

  Forget John Glenn: his ride was just the
consolation prize. You have the US Government in a panic to produce
an ICBM worthy of the name, and they have a virtual monopoly on the
world production of He. Feel free to mark the waste down as another
of the project's failures if you like.
I did that even before the Trieste went down. The waste was just a CODB 
for those folks.

The operative word is seal, not the thickness of the monel walls.
Seal—and no cracks.

You still don't get it, the helium molecule is so small it wiggles
thru a steel walls  huge molecules
like they were a layer of felt. Monel alloy is denser but it still leaks.

I haven't done the experiments, but others, like this pair, have.

https://www.sciencedirect.com/science/article/abs/pii/0042207X61900185

I haven't paid for the full PDF, but a year earlier, the same pair
"investigated the permeation of helium and hydrogen through 0.25 mm
thick tubes at 1023 K. Hydrogen permeation was detected through Monel,
304 stainless steel, Kovar, Inconel, nickel, and 52 Alloy (Fe50 Ni50)
even at temperatures approaching room temperature. The same metals
were not permeated by helium at temperatures as high as 1123 K."
   R. Collins and J. Turnbull. Degassing and permeation of gases
   in tube materials. In D. Slater, editor, Advances in Electron
   Tube Techniques, Proceedings of the Fifth National Conference,
   pages 186–190. 1960.
(reported in a dissertation by Daniel Schultheiß, Augsburg, 2007)

I don't know how it was leaking but it went someplace.

We bought a small bottle, probably 25+ years ago now, one of the
news girls was getting married, and the tv station threw a party for her.

When we were done blowing up balloons I personally closed the tank valve 
while
the regulator was showing around 1500 lbs.  This was in late September. 
Come time
for the annual roast turkey in November, I cracked the valve and the 
needle just
barely moved, maybe 50 lbs left. By then we were being billed for the 
demurrage

at about $50/mo so it went home the next business day.

Cheers,
David.

.



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

Re: Helium

[Thomas Schmitt]

Hi,

i looked up some data points about helium.

This table gives floating times for helium balloons and the pressure in
usual helium cylinders (200 bar).
  https://de.wikipedia.org/wiki/Luftballon#Ma%C3%9Fe

The numbers of fillings per ballon diameter in the "10 liter" column
indicate that the carnies fill them sparsely and that there is not much
pressure in them. A german trumpet player player forum mentions that the
maximum pressure by human lungs is about 1.15 bar (versus 1.0 bar of
environmental air pressure). So i guess a freshly filled toy ballon has
1.1 bar.
Such a rubber ballon loses most of its helium within 12 hours. I still
remember how disappointingly wrinkled they get.

Physical theory says that diffusion is proportional to partial pressure.
Gene mentions 7200 psi which is about 500 bar. That's about 450 times the
pressure in a toy balloon and 2.5 times the pressure in a commercial helium
cylinder, which surely does not have 2 inches of wall thickness.

  https://en.wikipedia.org/wiki/Helium#Gas_and_plasma_phases
states
  "[...] helium diffuses through solids at a rate three times that of air
   and around 65% that of hydrogen"
referring to
  Hampel, Clifford A. (1968). The Encyclopedia of the Chemical Elements.


All in all i riddle what physical (or criminal ?) effect caused the loss
of 20 percent (5800 / 7200 = 0.805) of the stored helium's pressure within
12 hours.

The only idea i have would be loss of temperature and not loss of substance.
The equation for ideal gases is:
  P * V = n * R * T
Volume V and R are constants. Pressure P decreases. So number of moles n or
temperature T must have decreased.


Have a nice day :)

Thomas

Re: Helium [was: t-bird screwing up]

[tomas]

On Thu, Nov 03, 2022 at 03:34:54PM +, mick.crane wrote:

[...]

> I know next to nothing about this stuff but it helps me to think that rather
> than everything made of little things that it's clouds of god knows what
> swirling about.

Yes, the depth of the "technological stack" is sometimes scary. Makes one
aware of how fragile this whole pudding is.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Helium [was: t-bird screwing up]

[tomas]

On Thu, Nov 03, 2022 at 09:38:20AM -0500, David Wright wrote:
> On Wed 02 Nov 2022 at 06:44:22 (+0100), to...@tuxteam.de wrote:

[...]

> > Of course, if you've got 200 or 500 bar, something might leak.
> 
> Yes, that referred only to the gas cylinders (snipped from the above).

I understood that. My point was that a helium filled HD most probably
hasn't that pressure, so the leak rate is bound to be lower. Besides,
if it's just He one can't make tight containers for, it'd be that
leaking out, but air staying out, so...

> Yes, I've read anecdotes of walls collapsing from He's diffusive
> escape, but IIRC they've involved semi-permeable materials.

...this is what ultimately would happen. The HD would fail earlier,
but then from heads flying too low, for lack of pressure.

> One symptom of an decreasing vacuum would probably be overheating,
> but by the time that happens, the heads might have crashed anyway.

Yep. It took me a while to interpret that "decreasing vacuum" in
the right direction :)

BTW, the Wikipedia says the driving factors for helium are less
turbulence and lower friction; of course that is boud to correlate
with lower flight height.

[...]

> We baked our mass spectrometers in removeable oven enclosures.

[...]

Nice stories :) I did theoretical physics, but of course, our
faculty was chock full of crazy and interesting folks doing stuff
like you described above. Searching for leaks in the apparatus
consisted of... pumping it full of helium and sniffing for it
with a sensor :-)

> I haven't done the experiments, but others, like this pair, have.
>
> https://www.sciencedirect.com/science/article/abs/pii/0042207X61900185
>
> I haven't paid for the full PDF, but a year earlier, the same pair
> "investigated the permeation of helium and hydrogen through 0.25 mm
> thick tubes at 1023 K. Hydrogen permeation was detected through Monel,
> 304 stainless steel, Kovar, Inconel, nickel, and 52 Alloy (Fe50 Ni50)
> even at temperatures approaching room temperature"

I didn't know, but I had the hunch that hydrogen is even nastier than
helium to contain. Hydrogen readily makes hydrides with metals, i.e.
whithin the metal matrix it's a proton in a sea of electros. An atom
doesn't get much smaller as that. Helium, OTOH, holds pretty tight
onto the two electrons it has (snobby noble gases, they are).

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Helium [was: t-bird screwing up]

[mick.crane]

On 2022-11-03 14:38, David Wright wrote:


You still don't get it, the helium molecule is so small it wiggles
thru a steel walls  huge molecules
like they were a layer of felt. Monel alloy is denser but it still 
leaks.


I haven't done the experiments, but others, like this pair, have.

https://www.sciencedirect.com/science/article/abs/pii/0042207X61900185


I know next to nothing about this stuff but it helps me to think that 
rather than everything made of little things that it's clouds of god 
knows what swirling about.

mick

Re: Helium [was: t-bird screwing up]

[David Wright]

On Wed 02 Nov 2022 at 06:44:22 (+0100), to...@tuxteam.de wrote:
> On Wed, Nov 02, 2022 at 12:06:16AM -0500, David Wright wrote:
> > On Tue 01 Nov 2022 at 06:49:09 (+0100), to...@tuxteam.de wrote:
> 
> [...]
> 
> > > This is only a half-truth. You know what goes out faster than helium?
> > > Vacuum. And there was a whole glorious epoch in electronics which did
> > > rely on keeping vacuum "in". You should have some fond memories of
> > > that.
> > 
> > To be fair, most vacuum tubes aren't bathed in helium, but air, and
> > then only at a one atmosphere differential pressure. A gas cylinder
> > might be as high as 500 atmospheres.
> 
> But not a harddisk. My point was somewhat tongue-in-cheek: even assuming
> He diffuses out of the harddisk, we've got very good at keeping air out
> (cf. vacuum tubes), so you'll be left with... vacuum. Heads would fly
> lower, not higher. Actually heads would roll on the tarmac :-)
> 
> Of course, if you've got 200 or 500 bar, something might leak.

Yes, that referred only to the gas cylinders (snipped from the above).

> > And vacuum tubes do contain a getter to deal with outgassing, which
> > will help mitigate slight leaks.
> 
> Oxygen. Not nitrogen, AFAIK. Talk nerds getting off-topic :-)

Gettering nitrogen is tough.

On Wed 02 Nov 2022 at 07:51:35 (+), Tim Woodall wrote:
> On Wed, 2 Nov 2022, David Wright wrote:
> 
> > > > Whatever, even I with an 8th grade diploma, knows you cannot keep helium
> > > > anyplace for very long. Put it in a monel metal
> > > > bottle with walls an inch thick and its molecules's are so small that 
> > > > 10% of
> > > > it is gone in 6 or 7 hours.?
> > 
> > So the He cylinders that we used after a few months in storage
> > really contained nothing at all!
> 
> I assume this is down to the type of metal. Similar to the fact that you
> cannot inflate tyres using CO2 other than as an emergency measure as CO2
> escapes remarkably quickly. N2, a smaller molecule, has no such
> problems.

Gene said Monel, and it's generally selected for properties like
remaining ductile at very low temperatures, strength, corrosion
resistance, low permeability etc.

> I don't recall ever talking about this in my student days and I cannot
> begin to guess how to calculate it now, but I'd expect a porous to He
> enclosure but otherwise sealed would only lose He to the point that
> there was a partial vacuum. Beyond that point, any He that entered the
> walls would return to the enclosure with very high probability.

Yes, I've read anecdotes of walls collapsing from He's diffusive
escape, but IIRC they've involved semi-permeable materials.

One symptom of an decreasing vacuum would probably be overheating,
but by the time that happens, the heads might have crashed anyway.

> I did do some vacuum stuff at college, although not about vacuum tubes
> specifically, and I'd assume the getter is just there to catch the
> outgassing you cannot bake out and even a small leak would quickly
> render the tube useless.
> 
> I've wondered how CERN deals with outgassing - perhaps the magnets act
> as a cold trap.

We baked our mass spectrometers in removeable oven enclosures.
Obviously we'd slide the magnet out of the way on compressed air,
as they weigh about a ton. After removing the ovens, the flight tube
(which would otherwise cool quickly) would be kept hot with one of
those tapes like people use to keep pipes in the roof from freezing
(but hotter).

During and after that, it's down to pumps of various sorts, oil- or
Hg- diffusion (yuk, never used those), Ti-sublimation, turbos, sputter
ion, plus a cold finger trap using liquid nitrogen. Whenever the
source was opened, an isolation valve maintained the vacuum in the
flight tube and detectors, while dry nitrogen was fed into the source
to prevent laboratory air from entering.

All that was just for ~10-7 mbar vacuum or so. (Any better was
pointless, as the sample itself, being incandescently evaporated,
would ruin it.) I'm sure the vacuums at CERN are far, far higher.

On Wed 02 Nov 2022 at 10:25:39 (-), Curt wrote:
> On 2022-11-02, David Wright  wrote:
> >
> > To be fair, most vacuum tubes aren't bathed in helium, but air, and
> > then only at a one atmosphere differential pressure. A gas cylinder
> > might be as high as 500 atmospheres.
> 
> I always thought vacuum tubes weren't filled with anything but a "high
> vacuum" and electrodes.

Yes, so the electrodes are surrounded by a vacuum; it's the vacuum
/tubes/ that are bathed in air. That's easier for the seals to cope
with than He would be.

> Gas-filled tubes, on the other hand, are filled with a gas.

How interesting :)

On Wed 02 Nov 2022 at 07:56:02 (-0400), gene heskett wrote:
> On 11/2/22 01:07, David Wright wrote:
> > On Tue 01 Nov 2022 at 06:49:09 (+0100), to...@tuxteam.de wrote:
> > > On Mon, Oct 31, 2022 at 06:32:17PM -0400, gene heskett wrote:
> > > 
> > > [...]
> > > 
> > > > Whatever, even I with an 8th grade diploma, knows you cannot keep helium
> > 

Re: Fwd: [SECURITY] [DLA 3173-1] linux-5.10 security update

[David Wright]

On Wed 02 Nov 2022 at 13:53:24 (-0400), Greg Wooledge wrote:
> On Wed, Nov 02, 2022 at 12:45:57PM -0500, Nicholas Geovanis wrote:
> > > > On 2022-11-02 03:40, Anssi Saari wrote:
> > > >> Looks like a linux-5.10 source package was indeed added to Buster in
> > > >> August and as you noted, it's getting security updates too.
> 
> > I'm just curious if this is the first time that a kernel _version_ bump
> > took place within the trajectory of a single Debian version? Or have kernel
> > _version_ changes always taken place at debian release boundaries before?
> 
> It's important to note that this is an optional, newer kernel image.
> Users who've just been running buster from the beginning may not even
> know about it, and it will have no effect on them.
> 
> It's very much UNlike the version bumps on, say, samba that have happened
> mid-stable-release in the past.
> 
> I'm fairly certain other releases have had optional kernel packages
> added to them, but I can't name any other than "etch-and-a-half" off
> the top of my head.
> 
> https://wiki.debian.org/EtchAndAHalf

>From my notes,

slink was 2.0.3n, but 2.2 was runnable, and I built a 2.2.10. It was
kernel-image back then, presumably as there was no hurd.

potato was 2.2.19, but it appears there were 2.4 ones around too. I'm
not sure where the latter originated, but perhaps the name of one of
the sources, kernel-source-2.4.9-0.bunk, might be a clue.

sarge had 2.4.27 and 2.6.8 kernels, but the latter might not have been
all archs.

etch was all 2.6.

AFAICT lenny was still 2.6 when I built my last kernel, 2.6.26lucy.

While these are all version 2.x, AIUI everything changed after that.
So the x in 2.x is really equivalent to the first digit nowadays,
except of course that x had to increment by 2 each time.

Cheers,
David.

Re: Fanget i DNS

[Kim Bak]

Den 03.11.2022 kl. 13.30 skrev Povl Ole Haarlev Olsen:

On Thu, 3 Nov 2022, Flemming Bjerke wrote:

Den 03.11.2022 kl. 11.29 skrev Povl Ole Haarlev Olsen:

On Thu, 3 Nov 2022, Flemming Bjerke wrote:

Er der nogen af Jer der har nogle løsninger?
Behold dit .dk domain hvor det er og nøjes med at lade hostwinds stå 
for rDNS for IP adressen.

Nåeh ja, selvfølgelig. Tak, for hjælpen!!!


No problem...

Før havde jeg mine domæner hos gratisdns. Nu er de flyttet til 
one.com. Men one.com er lidt trættende. Man skal hele sno sig uden om 
forskellige tilbud, og så er deres dns lidt begrænset.


Jeg har det på samme måde.






Sådan var det også for mig. Jeg løste problemet ved at få mine egne 
maskine godkendt hos DK Hostmaster og derefter flytte DNS for mine 
domains til min egne DNS servere. Måske ikke en løsning, der er god 
for alle, men den virker fint for mig.


Jeg har også gjort dette med nogle domæner, som alternativ kan man 
oprette dem hos cloudflare.com, de kan køre navneservere på deres gratis 
web cache selvom det nok ikke er meningen at man kun bruger dem til DNS :)





smime.p7s
Description: S/MIME-signeret meddelelse

Re: Fanget i DNS

[Povl Ole Haarlev Olsen]

On Thu, 3 Nov 2022, Flemming Bjerke wrote:

Den 03.11.2022 kl. 11.29 skrev Povl Ole Haarlev Olsen:

On Thu, 3 Nov 2022, Flemming Bjerke wrote:

Er der nogen af Jer der har nogle løsninger?
Behold dit .dk domain hvor det er og nøjes med at lade hostwinds stå for 
rDNS for IP adressen.

Nåeh ja, selvfølgelig. Tak, for hjælpen!!!


No problem...

Før havde jeg mine domæner hos gratisdns. Nu er de flyttet til one.com. Men 
one.com er lidt trættende. Man skal hele sno sig uden om forskellige tilbud, 
og så er deres dns lidt begrænset.


Sådan var det også for mig. Jeg løste problemet ved at få mine egne 
maskine godkendt hos DK Hostmaster og derefter flytte DNS for mine domains 
til min egne DNS servere. Måske ikke en løsning, der er god for alle, men 
den virker fint for mig.


--
Povl Ole

Re: Will my reconstructed fstab work?

[songbird]

Ken Heard wrote:
> A few days ago using vim I added to my desktop fstab file a line for a 
> new portable storage device.  in the process I somehow managed to screw 
> up fstab.  Unfortunately I saved the screwed up version of fstab before 
> I noticed the damage done to it.

...

  the package etckeeper is nice to have.


  songbird

Re: Fanget i DNS

[Flemming Bjerke]

Den 03.11.2022 kl. 11.29 skrev Povl Ole Haarlev Olsen:

On Thu, 3 Nov 2022, Flemming Bjerke wrote:

Hvordan løser I problemer med reverse DNS?


Jeg ved, at DanskNet, Telenor og YouSee alle tre understøtter rDNS.

Og med et tryk på maven og en henvisning til RFC2317/BCP20 kan man 
endda få dem til at redelegere rDNS for en enkelt IP-adresse til nogle 
andre DNS servere end deres egne.



Navneserveren er ikke registreret hos DK Hostmaster


Du behøver ikke bruge samme DNS servere for forward og reverse DNS.

Dit .dk domain skal ganske rigtigt være på nogle servere DK Hostmaster 
kender, men rDNS (dvs. PTR-recorden for .in-addr.arpa) 
bør være på mdns3.hostwindsdns.com, hvis det er den, der er auth DNS 
for rDNS domænet (mailserverens IP adresse skrevet baglæns og med 
".in-addr.arpa" bagefter).



Er der nogen af Jer der har nogle løsninger?


Behold dit .dk domain hvor det er og nøjes med at lade hostwinds stå 
for rDNS for IP adressen.




Nåeh ja, selvfølgelig. Tak, for hjælpen!!!

Før havde jeg mine domæner hos gratisdns. Nu er de flyttet til one.com. 
Men one.com er lidt trættende. Man skal hele sno sig uden om forskellige 
tilbud, og så er deres dns lidt begrænset.


Jeg har bemærket at der er danske alternativer med gratis dns. Er der 
nogle I kan anbefale?


Forøvrigt havde virkelig problemer med at genopsætte min mailserver op 
på debian 11 i foråret. Det lykkedes først da jeg fulgte linuxbabe.com:

https://www.linuxbabe.com/mail-server/build-email-server-from-scratch-debian-postfix-smtp

Flemming

Re: Fanget i DNS

[Povl Ole Haarlev Olsen]

On Thu, 3 Nov 2022, Flemming Bjerke wrote:

Hvordan løser I problemer med reverse DNS?


Jeg ved, at DanskNet, Telenor og YouSee alle tre understøtter rDNS.

Og med et tryk på maven og en henvisning til RFC2317/BCP20 kan man endda 
få dem til at redelegere rDNS for en enkelt IP-adresse til nogle andre DNS 
servere end deres egne.



Navneserveren er ikke registreret hos DK Hostmaster


Du behøver ikke bruge samme DNS servere for forward og reverse DNS.

Dit .dk domain skal ganske rigtigt være på nogle servere DK Hostmaster 
kender, men rDNS (dvs. PTR-recorden for .in-addr.arpa) bør 
være på mdns3.hostwindsdns.com, hvis det er den, der er auth DNS for rDNS 
domænet (mailserverens IP adresse skrevet baglæns og med ".in-addr.arpa" 
bagefter).



Er der nogen af Jer der har nogle løsninger?


Behold dit .dk domain hvor det er og nøjes med at lade hostwinds stå for 
rDNS for IP adressen.


--
Povl Ole

Fanget i DNS

[Flemming Bjerke]

Hej alle

Hvordan løser I problemer med reverse DNS?

Jeg har min debian mailserver på min fibia-internet-opkobling. De vil så 
have 49 kr/md for fast ip, hvilket jeg synes er uacceptabelt dyrt. (Og 
jeg tvivler på at de alligevel gider give mig reverse dns.) Jeg har 
derfor ikke reverse dns på min server, hvilket har givet problemer når 
jeg sender til gmail-konti.


Jeg har bl.a. af denne grund prøvet at flytte min mailserver til en VPS, 
men det har vist ikke at være let så endda. Mange VPS-udbydere har enten 
lukket for port 25 eller for reverse dns, og når man beder om åbning, 
får man tågede svar om at det vil de måske nok hvis ... bla bla. (F.eks. 
Hetzner og Kamatera). Og det kan jeg jo ikke rigtig bruge til noget. 
(Jeg ved selvfølgelig godt at de prøver at beskytte sig mod spammere og 
andre skumle typer.)


Så fandt jeg en liste over servere med åben port 25 
(https://j-insights.com/list-of-vps-providers-with-port-25-open/). Og 
mit valg blev hostwinds.com. Og ganske rigtigt, der er åben port 25, og 
man kan opsætte PTR. MEN ... da jeg skulle skifte DNS server via 
dk-hostmaster, fik jeg beskeden:


Navneserveren er ikke registreret hos DK Hostmaster

Skal jeg nu til at gå alle 25 servere igennem for at finde ud af hvilke 
Dk-Hostmaster har registreret hvis overhovedet nogen af dem?


Er der nogen af Jer der har nogle løsninger?

Bedste hilsener

Flemming

PS: I et anfald af optimisme skrev jeg lige til dk-hostmaster:

"Jeg har en VPS hos hostwinds.com. De har primær navnerserver:

mdns3.hostwindsdns.com

Men når jeg forsøger at skifte navneserver for rødblog.dk til at skifte 
til hostwinds ser, meddeler I: Navneserveren er ikke registreret hos DK 
Hostmaster.


Kan der ikke blive lavet om på det selvom det er em amerikansk server? 
Problemet eksisterer ikke når der er tale om det tyske firma hetzner.com."

Re: Will my reconstructed fstab work?

[Anssi Saari]

"Rick Thomas"  writes:

> Sorry to hear of your mishap, Ken ...
> In regards to possibly making your system un-bootable, I have two suggestions:
> 1) First make a backup of everything ASAP! (and make plans for frequent 
> regular backups into the future)

And for now, as the mounts are mounted and system is running, then make
a backup /etc/mtab on something easy to access before booting since that
file lists current mounts. /etc/mtab is usually a symlink to
/proc/self/mounts so it wouldn't normally go into a backup.

Re: Will my reconstructed fstab work?

[Rick Thomas]

Sorry to hear of your mishap, Ken ...
In regards to possibly making your system un-bootable, I have two suggestions:
1) First make a backup of everything ASAP! (and make plans for frequent regular 
backups into the future)
2) Always remember that you can boot from the Bullseye install DVD (or USB 
stick, or whatever) and go into "rescue mode".  From there you can chroot (it's 
one of the menu options) into the root partition and fix whatever problems you 
encounter with the fstab.

If you run into problems with either of those, you can always come back to the 
list with questions.

Good luck! and I hope that helps!
Rick

On Wed, Nov 2, 2022, at 9:52 PM, Ken Heard wrote:
> A few days ago using vim I added to my desktop fstab file a line for a 
> new portable storage device.  in the process I somehow managed to screw 
> up fstab.  Unfortunately I saved the screwed up version of fstab before 
> I noticed the damage done to it.
>
> As I had no fstab backup  -- to correct later -- I had to reconstruct 
> fstab using the information produced by blkid for the missing UUIDs.   I 
> think the reconstruction is correct, but I have since been afraid to 
> close the computer if because of a faulty fstab I would be unable to 
> reopen it
>
> I would consequently appreciate help in verifying  the essential fstab 
> lines, numbered 11-20 in the reconstructed fstab quoted below and 
> thereby assuage my reopening fears.  (Lines 26-40 relating to portable 
> storage devices I checked myself; they all work.)
>
> Basic Information:  two internal hard drives, /dev/sda and /dev/sdb, 
> each divided into two small partitions of equal size.  Sda1 is used for 
> /boot/efi, lines 13 and 15. Partition sdb1, line 17, is currently 
> unused; in time I will copy to it what is in sda1.  Partitions sda2 and 
> sdb2 form a RAID1, with the five LVM partitions listed in lines 11, 18, 
> 19 and 20.  Operating system is Debian Bullseye.
>
> If anybody in interested, following the reconstructed fstab  quoted 
> below is quoted further below how the fsab looked right after the screw 
> up.
>
> 01 # /etc/fstab: static file system information.
> 02 #
> 03 # Use 'blkid' to print the universally unique identifier for a
> 04 # device; this may be used with UUID= as a more robust way to name 
> devices
> 05 # that works even if disks are added and removed. See fstab(5).
> 06 #
> 07 # Systemd generates mount units based on this file, see systemd.mount(5).
> 08 # Please run 'systemctl daemon-reload' after making changes here.
> 09 #
> 10 #
> 11 /dev/mapper/Morcom-ROOT /   ext4errors=remount-ro 0 1
> 12 # /boot/efi was on /dev/sda1 during installation
> 13 UUID=3020-1029  /boot/efi   vfatumask=0077  0   1
> 14 # /dos was on /dev/sda1 during installation
> 15 UUID=3020-1029  /dosvfatutf80   0
> 16 # /dos2 was on /dev/sdb1 during installation
> 17 UUID=2AF2-0A16  /dos2   vfatutf80   0
> 18 /dev/mapper/Morcom-HOME_crypt /home   ext4defaults 0   2
> 19 /dev/mapper/Morcom-VAR /varext4defaults0   2
> 20 /dev/mapper/Morcom-SWAP_crypt noneswapswap  0   0
> 21 /dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
> 22 tmpfs  /tmptmpfs   nodev,nosuid,size=20%   0   0
> 23 UUID=c577-7f18-4443-a77b-c5827f977449 /media/fdr ext2 
> user,noauto,noatime 0  0
> 24 UUID=33cebfb3-b568-493f-853b-e1b7ca5cc3a2 /media/fde ext2 
> user,noauto,noatime  0 0
> 25 # -e8b57fb2ac09/media/ssda ext4user,npauto,noatime 0   > 0
> 26 UUID=la449167-8497-4471-ae0c-e8b57fb2ac09 /media/phda ext4 
> user,noauto,noatime 0 0
> 27 UUID=0fee2d01-2441-4699-a4ae-bb45c417b8ee /media/ssda ext4 
> user,noauto,noatime 0 0
> 28 UUID=e26255ab-e6c5-4bcd-941c-7378b7cf4083 /media/ssdb ext4 
> user,noauto,noatime 0 0
> 29 UUID=3DB1-1700 /media/fdg  vfatuser,noauto,noatime 
> 0   0
> 30 UUID=5966-5502 /media/fdp  vfatuser,noauto,noatime 
> 0   0
> 31 UUID=1170-1657 /media/hca  vfatuser,noauto,noatime 
> 0   0
> 32 UUID=0E0A-0F26 /media/hcb  vfatuser,noauto,noatime 
> 0   0
> 33 UUID=1E82-122E /media/hcc  vfatuser,noauto,noatime 
> 0   0
> 34 UUID=1D1F-1032  /media/xca exfat   user,noauto,noatime 
> 0   0
> 35 UUID=1909-1458 /media.xcb  exfat   user,noauto,noatime 
> 0   0
> 36 UUID=6238-3434 /media/xcc  exfat   user,noauto,noatime 
> 0   0
> 37 UUID=206F-163F /media/xcd  exfat   user,noauto,noatime 
> 0   0
> 38 UUID=3630-6530 /media/xce  exfat   user,noauto,noatime 
> 0   0
> 39 UUID=3065-6630 /media/xcf  exfat   user,noauto,noatime 
> 0   0
> 40 LABEL=ostree   /media/phdc ext4