Start by saying you're on Debian unstable. Then give the
> installed package version (as printed by "dpkg -l openssh-client")
> and the output of "ssh -V".
As I've said in my message: I've upgraded to openssh-client 1:9.5p1-2.
The versions up to 9.4 were f
rsion of "ssh" in your PATH
before /usr/bin/ssh, or... anything. Anything at all.
When asking for help, it's best to give all of the relevant details up
front. Start by saying you're on Debian unstable. Then give the
installed package version (as printed by "dpkg -l openssh
Vincent Lefevre wrote:
> I have the latest version!!! I recall that this is a Debian/unstable
> machine, which I upgrade regularly. So, everytime I get such an error,
> I have the latest client.
>
> Note also that this is an error that occurs randomly.
Then I'm sorry, that I can't help you more o
On 2023-12-14 17:03:10 +0100, Klaus Singvogel wrote:
> Vincent Lefevre wrote:
> > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent
> > errors like
> >
> > kex_exchange_identification: read: Connection reset by peer
> > Connection reset by x.x.x.x port 22
>
> This sounds most like
Vincent Lefevre wrote:
> Since 2 years (from early 2022 to 2023-11-26), I've got recurrent
> errors like
>
> kex_exchange_identification: read: Connection reset by peer
> Connection reset by x.x.x.x port 22
This sounds most likely that your SSH client (program at your local machine)
has an outda
, the errors just became
Connection closed by x.x.x.x port 22
though I suspect that this is exactly the same issue.
The sshd server and its config have not changed. Only the client has
changed: I upgraded to openssh-client 1:9.5p1-2 on 2023-11-27 (this
is a Debian/unstable machine).
Is ther
On Thu, Feb 16, 2023 at 01:56:05PM +0530, jadhav vishwanath wrote:
> The ssh timeout functionality was removed in the OpenSSH-server-8.4, Now
> this functionality has been fixed(restored) in OpenSSH-server-9.2 (refer
> <https://bugzilla.mindrot.org/show_bug.cgi?id=3182#c5>) rel
Hi All,
The ssh timeout functionality was removed in the OpenSSH-server-8.4, Now
this functionality has been fixed(restored) in OpenSSH-server-9.2 (refer
<https://bugzilla.mindrot.org/show_bug.cgi?id=3182#c5>) released in Debian
bookworm. The functionality was working properly in Buster
On 2022-08-22 at 08:42 -0400, Roberto C. Sánchez wrote:
> On Mon, Aug 22, 2022 at 12:33:42PM +0200, Radwan Daoud wrote:
> >I want to install an old version of openssh server on my Debian 11.
> >I want to install Debian 9 ssh version on Debian 11 , is that possible:
On Mon, Aug 22, 2022 at 12:33:42PM +0200, Radwan Daoud wrote:
>I want to install an old version of openssh server on my Debian 11.
>I want to install Debian 9 ssh version on Debian 11 , is that possible:
>[1]https://packages.debian.org/stretch/openssh-server
>Please
On 2022-06-15 15:10:17 +0200, Vincent Lefevre wrote:
> They set LogLevel to DEBUG, which explains that the debug3() message
> doesn't appear. They can see debug lines when my connection succeeds,
> but nothing in case of immediate failure. So this would mean that it
> is the pipe() from server_acce
On 2022-06-15 03:48:38 +0200, Vincent Lefevre wrote:
> The source from misc.c is
>
> int
> unset_nonblock(int fd)
> {
> int val;
>
> val = fcntl(fd, F_GETFL);
> if (val < 0) {
> error("fcntl(%d, F_GETFL): %s", fd, strerror(errno));
> return
On 2022-06-14 19:17:01 +0100, Tim Woodall wrote:
[MaxStartups limit]
> In the case where I hit it it was a cron job starting an ssh connection
> from multiple machines - 'out of hours' where 'convenience' was more
> valuable than 'performance'.
Note that I get the errors at random times of the day
On Tue, 14 Jun 2022, Vincent Lefevre wrote:
On 2022-06-07 17:19:12 +0100, Tim Woodall wrote:
On Tue, 7 Jun 2022, Vincent Lefevre wrote:
I eventually did a packet capture on the client side as I was able to
reproduce the problem. When it occurs, I get the following sequence:
Client ? Server: [
On 2022-06-07 17:19:12 +0100, Tim Woodall wrote:
> On Tue, 7 Jun 2022, Vincent Lefevre wrote:
> > I eventually did a packet capture on the client side as I was able to
> > reproduce the problem. When it occurs, I get the following sequence:
> >
> > Client ? Server: [SYN] Seq=0
> > Server ? Client:
On Tue, 7 Jun 2022, Vincent Lefevre wrote:
On 2022-02-05 18:39:27 -0300, Henrique de Moraes Holschuh wrote:
If it is sshd, ensure it is actually logging all you need, and carefully
study the logs.
Nothing interesting in the logs, according to the admins of the server.
If nothing helps, pack
On 2022-02-05 18:39:27 -0300, Henrique de Moraes Holschuh wrote:
> If it is sshd, ensure it is actually logging all you need, and carefully
> study the logs.
Nothing interesting in the logs, according to the admins of the server.
> If nothing helps, packet-dump both sides (client and server) and
On 2022-02-05 18:39:27 -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 02 Feb 2022, Vincent Lefevre wrote:
> > When I want to connect with SSH (ssh/scp) to some machine, I sometimes
> > get errors, either
> >
> > kex_exchange_identification: Connection closed by remote host
> >
> > or
> >
>
On Wed, 02 Feb 2022, Vincent Lefevre wrote:
> When I want to connect with SSH (ssh/scp) to some machine, I sometimes
> get errors, either
>
> kex_exchange_identification: Connection closed by remote host
>
> or
>
> kex_exchange_identification: read: Connection reset by peer
That's a very early
On 2022-02-02 14:21:08 -0500, gene heskett wrote:
> When I change something, like rebooting the rpi4 running my big Sheldon
> lathe, from debian buster to debian bullseye, the keyfile changes, and I
> get an explicit error telling me to run ssh-keygen to remove the
> offending key, which I do, a
On Wed 02 Feb 2022 at 14:28:40 (-0500), Greg Wooledge wrote:
> On Wed, Feb 02, 2022 at 02:21:08PM -0500, gene heskett wrote:
> > When I change something, like rebooting the rpi4 running my big Sheldon
> > lathe, from debian buster to debian bullseye, the keyfile changes, and I
> > get an explicit
On Wed, Feb 02, 2022 at 02:21:08PM -0500, gene heskett wrote:
> When I change something, like rebooting the rpi4 running my big Sheldon
> lathe, from debian buster to debian bullseye, the keyfile changes, and I
> get an explicit error telling me to run ssh-keygen to remove the
> offending key, w
On Wednesday, February 2, 2022 9:44:32 AM EST Vincent Lefevre wrote:
> When I want to connect with SSH (ssh/scp) to some machine, I sometimes
> get errors, either
>
> kex_exchange_identification: Connection closed by remote host
>
> or
>
> kex_exchange_identification: read: Connection reset by p
On Wed 02 Feb 2022 at 15:44:32 (+0100), Vincent Lefevre wrote:
> When I want to connect with SSH (ssh/scp) to some machine, I sometimes
> get errors, either
>
> kex_exchange_identification: Connection closed by remote host
>
> or
>
> kex_exchange_identification: read: Connection reset by peer
>
On 2022-02-02 09:44, Vincent Lefevre wrote:
In the source, this corresponds to function kex_exchange_identification
in kex.c:
len = atomicio(read, ssh_packet_get_connection_in(ssh),
&c, 1);
if (len != 1 && errno == EPIPE) {
error_f("Connection closed by remote hos
nge_" expected.
No, that's really kex_ in the OpenSSH source, and I think that it just
means "key exchange" (the "exchange" in kex_exchange_identification is
about identification, as part of the key exchange, if I understand
correctly).
[...]
> Other reasons m
Am Mittwoch, 2. Februar 2022, 15:44:32 CET schrieb Vincent Lefevre:
Sounds weired. I wonder, if there is a typo. Your message beginning with
kex_exchange_identif
looks for me like a typo. I would have "key_exchange_" expected.
However, I did not check this, and mybe this is correct.
On
On 2022-02-02 14:44, Vincent Lefevre wrote:
When I want to connect with SSH (ssh/scp) to some machine, I sometimes
get errors, either
kex_exchange_identification: Connection closed by remote host
or
kex_exchange_identification: read: Connection reset by peer
immediately after the connection a
When I want to connect with SSH (ssh/scp) to some machine, I sometimes
get errors, either
kex_exchange_identification: Connection closed by remote host
or
kex_exchange_identification: read: Connection reset by peer
immediately after the connection attempt. This happens randomly,
and there are s
On Thu, 21 Oct 2021 15:26:21 -0700
dmacdoug wrote:
>
> Assuming your sshd server is on a computer attached
> to a router which is your gateway to the internet, and
> the router is set to forward port 22 to that computer
> some ISP's don't route port 22 traffic. I know that
> AT&T blocks por
On Sb, 23 oct 21, 09:33:44, Joe wrote:
>
> The ssh protocol by default works on TCP port 22, but the sshd (server)
> configuration file allows different ports to be specified. If you have
> port 22 open to the Internet, you will get many firewall logs for
> people trying brute-force password attac
On Sat, 23 Oct 2021 08:42:09 +0300
Semih Ozlem wrote:
> Are there specific tutorials websites that you can recommend, how
> about port forwarding. From where which sites in particular can I
> learn about these topics?
Here's a good practical guide:
https://www.digitalocean.com/community/tutoria
Are there specific tutorials websites that you can recommend, how about
port forwarding. From where which sites in particular can I learn about
these topics?
Joe , 22 Eki 2021 Cum, 00:08 tarihinde şunu yazdı:
> On Thu, 21 Oct 2021 23:48:38 +0300
> Semih Ozlem wrote:
>
> > I think it was somethin
On Friday, 22 Oct 2021 at 09:46, David Wright wrote:
> I'm guessing it was a BT Home Hub.
EE *before* bought by BT but maybe same supplier even then.
> One might suspect that 100 lies at the lower boundary of its DHCP
> range, leaving 99 static addresses free. But no guess at a product.
I canno
On Fri 22 Oct 2021 at 11:59:40 (+0100), Eric S Fraga wrote:
> On Friday, 22 Oct 2021 at 13:40, Andrei POPESCU wrote:
> > Typically modems and home routers use the .1 address for themselves.
>
> Interesting. My last 2 routers have had *.254 (!)
I'm guessing it was a BT Home Hub. It's idiosyncrati
On Friday, 22 Oct 2021 at 13:40, Andrei POPESCU wrote:
> Typically modems and home routers use the .1 address for themselves.
Interesting. My last 2 routers have had *.254 (!) and *.100 as their
address.
--
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.1
On Jo, 21 oct 21, 22:52:37, Semih Ozlem wrote:
> I am unable to access my modem settings page when writing 192.168.1.100 to
> check if there is a firewall.
Are you sure this is the correct address? How did you establish that?
Typically modems and home routers use the .1 address for themselves.
E
That's 'systemctl status ssh' without the 1) of course.I meant to put more
steps but decided not to
--
James B
portoteache...@fastmail.com
Em Sex, 22 Out ʼ21, às 00:18, James B escreveu:
> Hi Semih,
>
> In my opinion, I would go back to basics first.You may have ins
Hi Semih,
In my opinion, I would go back to basics first.You may have installed openssh
but it doesn't necessarily run by default (for reasons that will make sense
when you look at it further).Do you know how to start systemd services? It
looks to me like your ssh server isnt' runni
On Fri, 22 Oct 2021 at 09:53, Semih Ozlem wrote:
> From:Semih Ozlem
> To:Debian Users , ubuntu-us...@lists.ubuntu.com
Please, do not send individual messages to more than one
mailing list.
It is rather unfriendly to everyone else that reads each list, because
we do not see any conversation tha
I am unable to access my modem settings page when writing 192.168.1.100 to
check if there is a firewall.
Below is the web page that I get
Unable to connect
Firefox can’t establish a connection to the server at 192.168.1.100.
The site could be temporarily unavailable or too busy. Try again
On Thu, Oct 21, 2021 at 11:41:43PM +0300, Semih Ozlem wrote:
> Hi everyone,
>
> I set up an openssh server and I am trying to access that machine remotely
> (not from the local network. but from another ip address). I get an error
> (something about port 22). What setting needs to
On Thu, Oct 21, 2021 at 09:07:02PM +, Semih Ozlem wrote:
> Yes the error message is
>
> ssh: connect to host (ip address of remote host) port 22: Connection refused
This message means one of these things:
1) The sshd process is not running, or is not listening on the default port.
2) A fire
On Thu, 21 Oct 2021 23:48:38 +0300
Semih Ozlem wrote:
> I think it was something like "ssh: connect to host port 22:
> Connection refused" It will take me a little while to get the same
> error message again.
>
>
Ideally you need to do more than open the ssh port, particularly if you
inten
es B
>> portoteache...@fastmail.com
>>
>>
>>
>> Em Qui, 21 Out ʼ21, às 21:41, Semih Ozlem escreveu:
>>
>> Hi everyone,
>>
>> I set up an openssh server and I am trying to access that machine
>> remotely (not from the local network. but f
ge please?
>
> Best
>
> JB
>
> --
> James B
> portoteache...@fastmail.com
>
>
>
> Em Qui, 21 Out ʼ21, às 21:41, Semih Ozlem escreveu:
>
> Hi everyone,
>
> I set up an openssh server and I am trying to access that machine remotely
> (no
Hi Semih,
Could you post the exact wording of the error message please?
Best
JB
--
James B
portoteache...@fastmail.com
Em Qui, 21 Out ʼ21, às 21:41, Semih Ozlem escreveu:
> Hi everyone,
>
> I set up an openssh server and I am trying to access that machine remotely
> (
Hi everyone,
I set up an openssh server and I am trying to access that machine remotely
(not from the local network. but from another ip address). I get an error
(something about port 22). What setting needs to be checked and what needs
to be done on the machine that openssh server is running and
On Sat 11 Sep 2021 at 16:02:30 (-0400), Greg Wooledge wrote:
> On Sat, Sep 11, 2021 at 02:44:13PM -0500, David Wright wrote:
> > As I understood the OP's first reply (to yourself), there are
> > remote logs available, not logged locally but sent by email:
> >
> > "/usr/sbin/logwatch --detail low
On Sat, Sep 11, 2021 at 02:44:13PM -0500, David Wright wrote:
> As I understood the OP's first reply (to yourself), there are
> remote logs available, not logged locally but sent by email:
>
> "/usr/sbin/logwatch --detail low --mailto x...@domain.com"
I don't know anything about logwatch. But
On Fri 10 Sep 2021 at 17:55:59 (-0400), rhkra...@gmail.com wrote:
> On Friday, September 10, 2021 02:52:42 PM Dan Ritter wrote:
> > David Wright wrote:
> > > If you make a telephone call on speaker, and you have a tape recorder
> > > in the room recording the conversation, the speaker at the other
On Fri 10 Sep 2021 at 13:17:39 (-0400), Greg Wooledge wrote:
> On Fri, Sep 10, 2021 at 11:51:07AM -0500, David Wright wrote:
> > On Fri 10 Sep 2021 at 16:05:26 (+0100), Adam Weremczuk wrote:
> >
> > > Would it be possible for another host to log to syslog without a prior
> > > explicit manual conf
On Friday, September 10, 2021 02:52:42 PM Dan Ritter wrote:
> David Wright wrote:
> > If you make a telephone call on speaker, and you have a tape recorder
> > in the room recording the conversation, the speaker at the other end
> > of the call doesn't need to have permission for their words to be
David Wright wrote:
> On Fri 10 Sep 2021 at 16:05:26 (+0100), Adam Weremczuk wrote:
>
> > Would it be possible for another host to log to syslog without a prior
> > explicit manual configuration allowing that?
>
> If you make a telephone call on speaker, and you have a tape recorder
> in the roo
On Fri, Sep 10, 2021 at 06:10:59PM +0100, Adam Weremczuk wrote:
> On 10/09/2021 17:46, Greg Wooledge wrote:
>
> > Depends on which syslog daemon implementation you're using, I think.
>
> My environment: Linux deb10 5.4.44-1-pve #1 SMP PVE 5.4.44-1 (Fri, 12 Jun
> 2020 08:18:46 +0200) x86_64 GNU/Li
On 10/09/2021 17:46, Greg Wooledge wrote:
Depends on which syslog daemon implementation you're using, I think.
My environment: Linux deb10 5.4.44-1-pve #1 SMP PVE 5.4.44-1 (Fri, 12
Jun 2020 08:18:46 +0200) x86_64 GNU/Linux
Pretty minimalistic set up.
Rsyslog 8.1901.0-1 out of the box, no c
On 10/09/2021 17:51, David Wright wrote:
When you commence your call, both you and the person at the other end
probably exchange some pleasantries, which confirm that you're both
who you say you are. These all get recorded too.
Ssh is no different.
Are you saying these entries could belong to a
On Fri, Sep 10, 2021 at 01:17:39PM -0400, Greg Wooledge wrote:
> It's not clear which syslogd the OP is using. It's not even clear to me
> what *operating system* they're using, since their systemctl status output
> has at least one line that mine (bullseye) does not have.
I just checked on a bus
On Fri, Sep 10, 2021 at 11:51:07AM -0500, David Wright wrote:
> On Fri 10 Sep 2021 at 16:05:26 (+0100), Adam Weremczuk wrote:
>
> > Would it be possible for another host to log to syslog without a prior
> > explicit manual configuration allowing that?
>
> If you make a telephone call on speaker,
On Fri 10 Sep 2021 at 16:05:26 (+0100), Adam Weremczuk wrote:
> Would it be possible for another host to log to syslog without a prior
> explicit manual configuration allowing that?
If you make a telephone call on speaker, and you have a tape recorder
in the room recording the conversation, the s
On Fri, Sep 10, 2021 at 04:05:26PM +0100, Adam Weremczuk wrote:
> Would it be possible for another host to log to syslog without a prior
> explicit manual configuration allowing that?
Depends on which syslog daemon implementation you're using, I think.
you omitted most of the systemctl output. It would
have been nice to see whether PID 145 is actually sshd on this host. You
could also check by hand, of course: ps -fp 145 and ps -ef | grep sshd
PID 145 doesn't match anything that I could identify.
This container:
openssh-server
these lines are being remotely syslogged to you from
> another host?
… as I suggested Aug 16¹, and I haven't changed my view. In fact, the
OP stated that they were running openssh 7.9p1-10+deb10u2 on Debian 10.10,
but the objectionable configuration options as defaults wer
On Fri, Sep 10, 2021 at 10:33:47AM +0100, Adam Weremczuk wrote:
> Weeks later it happened again and I'm not any less puzzled:
What's "it"?
> /var/log/syslog
>
> Aug 28 10:12:30 deb10 sshd[145]: /etc/ssh/sshd_config line 25: Deprecated
> option UsePrivilegeSeparation
Fine, just comment out the o
Hi all,
Weeks later it happened again and I'm not any less puzzled:
/var/log/syslog
Aug 28 10:12:30 deb10 sshd[145]: /etc/ssh/sshd_config line 25:
Deprecated option UsePrivilegeSeparation
Aug 28 10:12:30 deb10 sshd[145]: /etc/ssh/sshd_config line 28:
Deprecated option KeyRegenerationInterval
Adam Weremczuk writes:
> Installation and configuration was straightforward:
>
> sudo apt install logwatch
>
> /etc/cron.daily/00logwatch
> #execute
> /usr/sbin/logwatch --detail low --mailto x...@domain.com
Maybe run logwatch manually and with different options? Like with
--detail high or somet
On Mon 16 Aug 2021 at 16:49:16 (+0100), Adam Weremczuk wrote:
> Installation and configuration was straightforward:
>
> sudo apt install logwatch
>
> /etc/cron.daily/00logwatch
> #execute
> /usr/sbin/logwatch --detail low --mailto x...@domain.com
>
> The master config file /usr/share/logwatch/de
f -exec grep -l UsePrivilegeSeparation {} \;
Still puzzled...
On 16/08/2021 15:34, Greg Wooledge wrote:
On Mon, Aug 16, 2021 at 03:06:30PM +0100, Adam Weremczuk wrote:
I run openssh 7.9p1-10+deb10u2 on Debian 10.10.
Logwatch, which runs daily, occasionally (maybe 2-3 times per month) reports
the following:
So
On Mon, Aug 16, 2021 at 03:06:30PM +0100, Adam Weremczuk wrote:
> I run openssh 7.9p1-10+deb10u2 on Debian 10.10.
>
> Logwatch, which runs daily, occasionally (maybe 2-3 times per month) reports
> the following:
Sometimes you get warnings, and sometimes you don't? That'
Hi all,
I run openssh 7.9p1-10+deb10u2 on Debian 10.10.
Logwatch, which runs daily, occasionally (maybe 2-3 times per month)
reports the following:
- SSHD Begin
Deprecated options in SSH config:
KeyRegenerationInterval - line 28
On Mon, Aug 17, 2020 at 09:31:20PM +0300, Semih Ozlem wrote:
> Hi Greg,
> Sorry for lack of details in my response, it was just a tiring day because
> almost the whole day passed and finally the issue is at least temporarily
> resolved, and one gets somewhat forgetful. the firewall was enabled on t
Hi Greg,
Sorry for lack of details in my response, it was just a tiring day because
almost the whole day passed and finally the issue is at least temporarily
resolved, and one gets somewhat forgetful. the firewall was enabled on the
debian machine, and I am trying to connect to the debian machine f
On 8/17/2020 8:15 PM, Semih Ozlem wrote:
Sorry for the maybe too simple question, but how does one open and close
ports, and how can ufw firewall be configured so as to allow ssh
connections
Have a look at (1).
In the linux world, it is wise to answer at the bottom of an e-mail as
opposed to
On Mon, Aug 17, 2020 at 08:12:32PM +0200, john doe wrote:
> On 8/17/2020 8:04 PM, Semih Ozlem wrote:
> > And thanks to Greg for the quick response.
> >
> > Semih Ozlem , 17 Ağu 2020 Pzt, 21:03
> > tarihinde şunu yazdı:
> >
> > > Sorry for the trailing list of emails, I just realized the firewall
On 8/17/2020 8:04 PM, Semih Ozlem wrote:
And thanks to Greg for the quick response.
Semih Ozlem , 17 Ağu 2020 Pzt, 21:03
tarihinde şunu yazdı:
Sorry for the trailing list of emails, I just realized the firewall was
preventing the connection. After disabling ssh connection works. However I
woul
Regarding previous question on ssh server
>>> Both machines are in the same home network, connected to the internet
>>> through modem.
>>> One machine is running on windows the other on debian. (I tried running
>>> the windows machine from debian as well a
hine is running on windows the other on debian. (I tried running
>> the windows machine from debian as well and that did not work either.)
>> When I run localhost on the debian machine, the openssh-server is
>> running, and can connect to it from the same machine.
>> When I run
unning
> the windows machine from debian as well and that did not work either.)
> When I run localhost on the debian machine, the openssh-server is running,
> and can connect to it from the same machine.
> When I run openssh-server on the windows machine, I am able to connect to
> it from d
debian machine, the openssh-server is running,
and can connect to it from the same machine.
When I run openssh-server on the windows machine, I am able to connect to
it from debian.
When I run openssh-server from debian, I am not able to connect to it from
the other machine regardless of it working
On Mon, Aug 17, 2020 at 08:49:11PM +0300, Semih Ozlem wrote:
> I am trying to connect to a debian machine with openssh-server installed.
> When I try to connect, I get the message "connection timed out". I am not
> sure if this group is the right place to address this is
Hi,
I am trying to connect to a debian machine with openssh-server installed.
When I try to connect, I get the message "connection timed out". I am not
sure if this group is the right place to address this issue, but is there a
configuration file that needs to be adjusted to fix the i
On Fri, Jul 24, 2020 at 09:49:04PM +0300, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 17:53:53, to...@tuxteam.de wrote:
[...]
> Aren't those files an internal implementation detail? Most users won't
> ever need to interact with those files or even be aware of their
> existence.
Strictly speaking
On Fri, Jul 24, 2020 at 09:49:04PM +0300, Andrei POPESCU wrote:
> Aren't those files an internal implementation detail? Most users won't
> ever need to interact with those files or even be aware of their
> existence.
The whole design is built around "you can do this with systemctl commands,
or b
On Vi, 24 iul 20, 17:53:53, to...@tuxteam.de wrote:
> On Fri, Jul 24, 2020 at 05:18:24PM +0300, Andrei POPESCU wrote:
> > On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> > > On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > > > Seriously?
> > >
> > > Yes seriously. This is
On Fri, Jul 24, 2020 at 05:18:24PM +0300, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> > On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > > Seriously?
> >
> > Yes seriously. This is a pain point that could be avoided. I'm not a
> > systemd hater.
On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > Seriously?
>
> Yes seriously. This is a pain point that could be avoided. I'm not a
> systemd hater. I do some quite advanced things with it. But I don't
> think it's above cri
On Fri, Jul 24, 2020 at 09:52:29AM -0400, Greg Wooledge wrote:
[...]
> I don't know of any specific term for a directory's physical
> manifestation, other than "directory".
>
> In the olden days, a directory was basically a series of 16-byte
> records (14 bytes for the filename, 2 bytes for the
On Fri, Jul 24, 2020 at 09:56:27AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
[...]
> Since writing that, I've had occasion to remember the term 'dirent',
> which I think is more the in-memory representation of a directory than
> the on-disk representation, but m
On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
Seriously?
Yes seriously. This is a pain point that could be avoided. I'm not a
systemd hater. I do some quite advanced things with it. But I don't
think it's above criticism, and this is an area I feel is worthy of
criticism.
Co
On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
>
> On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
>
>> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>>> Nitpick: the directory entry is the one carrying the name.
>>
>> I had the impression that even a directory is stored in/as
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
Sounds like a case where directly editing the underlying
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
> On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
>
>> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
>>
>>> Sounds like a case where directly editing the underlying device,
>>> to modify inode-or-equivalent contents s
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> > Sounds like a case where directly editing the underlying device, to
> > modify inode-or-equivalent contents such that the slash is no longer
^
Nitpick:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> Sounds like a case where directly editing the underlying device, to
> modify inode-or-equivalent contents such that the slash is no longer
> there, might even be *advisable*.
Yeah, some sort of direct hex-edit on the unmounted file sy
On 2020-07-24 at 07:45, Greg Wooledge wrote:
> On Thu, Jul 23, 2020 at 07:16:06PM -0400, The Wanderer wrote:
>
>> On 2020-07-23 at 06:26, Andrei POPESCU wrote:
>>> Seriously? Could you please show me how would I create a file on
>>> *nix containing '/' in the name?
>>
>> It's theoretically possi
On Thu, Jul 23, 2020 at 07:16:06PM -0400, The Wanderer wrote:
> On 2020-07-23 at 06:26, Andrei POPESCU wrote:
> > Seriously? Could you please show me how would I create a file on *nix
> > containing '/' in the name?
>
> It's theoretically possible, but AFAIK basically nothing would support
> it or
On Vi, 24 iul 20, 10:58:24, to...@tuxteam.de wrote:
>
> It's as if they were copying the disruptive antipatterns of proprietary
> software companies. But we don't need those antipatterns in the free
> software context, do we?
One person's bug is another's feature.
Kind regards,
Andrei
--
http:/
On Thu, Jul 23, 2020 at 06:48:10PM -0500, David Wright wrote:
> On Thu 23 Jul 2020 at 10:12:09 (+0200), to...@tuxteam.de wrote:
[...]
> > Hours of fun :-)
>
> Sure, I agree. But they're hours I don't really have. That's one
> reason why I don't run a DE: I just don't understand what's going on
>
1 - 100 of 546 matches
Mail list logo
