On 09/12/2024 08:35 AM, Richard Owlett wrote:
On 09/12/2024 07:13 AM, Stefan Monnier wrote:
i Ricard,
It has a keyboard failure - the "h" key is intermittent and my primary
account is "Richard" ;/
[ I presume you know tat tis kind of failure can often (sadly not
always) be fixed by cleani
Hi Richard,
exchanging the keyboard yourself might be not a great thing. If it is not an
apple computer, where you have to strip the whole computer, most keyboards are
very simple to echange.
There are often some videos on youtube, which show, how to do it.
On most, there are 1 - 3 screws to
On 09/13/2024 03:56 AM, Hans wrote:
Hi Richard,
exchanging the keyboard yourself might be not a great thing. If it is not an
apple computer, where you have to strip the whole computer, most keyboards are
very simple to echange.[snip]
ROFL
The keyboard is not the only problem.
I was an electron
David Wright writes:
> On Tue 10 Sep 2024 at 11:56:25 (+0300), Anssi Saari wrote:
>> Why do you think that? Which part of the fsync manpage explicitly covers
>> fsync's effect on device files? Share share, it's fair.
> “fsync() transfers ("flushes") all modified in-core data of (i.e.,
> modi
On Friday, 13-09-2024 at 20:17 Richard Owlett wrote:
> On 09/13/2024 03:56 AM, Hans wrote:
> > Hi Richard,
> >
> > exchanging the keyboard yourself might be not a great thing. If it is not an
> > apple computer, where you have to strip the whole computer, most keyboards
> > are
> > very simple
Hi list,
I have put the private key into my debian VPS (in ~/.ssh/ dir).
When I scp a file from this VPS to another one by hand without password,
it works.
But when I put this scp into crontab, it seems not work. The scp in
crontab via private key didn't run as I expect, nothing was copied t
On 13.09.24 14:24, Marcus Park wrote:
Hi list,
I have put the private key into my debian VPS (in ~/.ssh/ dir).
When I scp a file from this VPS to another one by hand without password,
it works.
But when I put this scp into crontab, it seems not work. The scp in
crontab via private key didn'
On Fri, Sep 13, 2024 at 20:24:51 +0800, Marcus Park wrote:
> I have put the private key into my debian VPS (in ~/.ssh/ dir).
Does this private key have a passphrase?
> When I scp a file from this VPS to another one by hand without password, it
> works.
>
> But when I put this scp into crontab, i
On 09/13/2024 07:03 AM, George at Clug wrote:
On Friday, 13-09-2024 at 20:17 Richard Owlett wrote:
On 09/13/2024 03:56 AM, Hans wrote:
Hi Richard,
exchanging the keyboard yourself might be not a great thing. If it is not an
apple computer, where you have to strip the whole computer, most key
On Fri, 13 Sep 2024 20:24:51 +0800
Marcus Park wrote:
> Hi list,
>
> I have put the private key into my debian VPS (in ~/.ssh/ dir).
The private key of what?
And to ~/.ssh/ on which computer. you are talking about transferring a
file from one computer to another; which one?
And why the privat
Le 11/09/2024 à 17:55, Max Nikulin a écrit :
grep -r system.conf /usr/share/dbus-1/
/usr/share/dbus-1/system.conf: ignore_missing="yes">/etc/dbus-1/system.conf
I do not have this file as well. I suggest Pierre to compare config
files of live and installed environments.
I recommend to read
On 13/09/2024 21:09, Pierre Willaime wrote:
I do not think it was related to non-free-firmware repository (Here is
my sources.list below)
deb http://deb.debian.org/debian bookworm main contrib non-free
non-free-firmware
It seems repositories are properly configured. In general however "apt
my personal experience:
On 9/10/24 05:37, debian-u...@howorth.org.uk wrote:
Larry Martell wrote:
What are these driving glasses? I can no longer drive at night and
would love to know about them.
As well as uncorrected visual faults, such as short-sightedness or
astigmatism, another reason for
On Fri, Sep 13, 2024 at 03:00:14PM +0300, Anssi Saari wrote:
> David Wright writes:
>
> > On Tue 10 Sep 2024 at 11:56:25 (+0300), Anssi Saari wrote:
>
> >> Why do you think that? Which part of the fsync manpage explicitly covers
> >> fsync's effect on device files? Share share, it's fair.
>
> >
On Fri, Sep 13, 2024 at 8:00 AM Anssi Saari
wrote:
>
> David Wright writes:
>
> > On Tue 10 Sep 2024 at 11:56:25 (+0300), Anssi Saari wrote:
>
> >> Why do you think that? Which part of the fsync manpage explicitly covers
> >> fsync's effect on device files? Share share, it's fair.
>
> > “fsync()
On Fri, Sep 13, 2024, at 5:00 AM, Anssi Saari wrote:
...
> So the answer to
> the question "is running sync needed after dd to block device" is
> no. Someone else posted that too on this list recently, in another
> thread.
On the other hand, it may not be necessary, but it doesn't do any harm.
Hi list,
When I run 'crontab -e' the screen shows some errors like,
$ crontab -e
Error detected while processing /usr/share/vim/vim82/filetype.vim:
line 10:
E319: Sorry, the command is not available in this version: let
did_load_filetypes = 1
line 13:
E319: Sorry, the command is not availa
On Sat, Sep 14, 2024 at 05:44:42 +0800, Marcus Park wrote:
> Hi list,
>
> When I run 'crontab -e' the screen shows some errors like,
>
> $ crontab -e
> Error detected while processing /usr/share/vim/vim82/filetype.vim:
> line 10:
> E319: Sorry, the command is not available in this version: let
Hi,
On Sat, Sep 14, 2024 at 05:44:42AM +0800, Marcus Park wrote:
> When I run 'crontab -e' the screen shows some errors like,
>
> $ crontab -e
> Error detected while processing /usr/share/vim/vim82/filetype.vim:
I'm pretty sure that these errors will be coming from the editor
binary that is set
Andy Smith :
As to why whatever it is set as right now is doing that, first work
out where it is getting the setting from, so echo $EDITOR and echo
$VISUAL. If neither of those are set then ls -la /usr/bin/editor.
Thanks Andy.
either $EDITOR or $VISUAL in my system is empty.
And /usr/bin/
basti:
/usr/bin/scp -i /home/userYX/.ssh/myKEY r...@example.com ...
updated: it's really due to environment issue, after I add the '-i' path
to scp, jobs run well now.
Thanks basti.
Hi,
On Sat, Sep 14, 2024 at 06:12:02AM +0800, Marcus Park wrote:
> either $EDITOR or $VISUAL in my system is empty.
>
> And /usr/bin/editor points to nano.
Well, I do not really understand what is going on then as you are
definitely running an editor that looks at vim config files, and
nano won'
You are getting Vim error messages from a version of Vim that does
not support scripting (probably vim.tiny). That version is probably
installed on your system ALONG WITH a version that does support
scripting, but cron does not have the scripting version of Vim on PATH.
(Typically, your $HOME & ro
Or ... disambiguate which Vim crontab -e is using, so it's not vim.tiny.
* Will Mengarini [24-09/13=Fri 15:47 -0700]:
> You are getting Vim error messages from a version of Vim that does
> not support scripting (probably vim.tiny). That version is probably
> installed on your system ALONG WITH a
On 9/13/24 12:06, Jeffrey Walton wrote:
To add a datapoint...
My daily driver workstation is really fast with lots of RAM. It has
3.4 GHz cpu and 64 GB of RAM. I also set swappiness to a low value
to avoid spilling out of RAM.
I use a lot of SBC's/dev boards for testing. They usually use a
S
i have installed latest 12.7, after running about 10 hours, it doesn't
respond to my keyboard pressing, power LED on front panel of pc case
become red, i have to reboot
i run journalctl, i am not sure if msg below are related to my problem
Sep 13 18:06:54 debian kernel: INFO: task RTW_CMD_
On Fri, Sep 13, 2024 at 22:46:09 +, Andy Smith wrote:
> I just ran crontab -e as a fresh user and it actually invoked
> /usr/bin/sensible-editor and asked me which editor I wanted to use
> (now and in future). So perhaps the man page for crontab is out of
> date.
Agreed.
hobbit:~$ strings /us
Avoid setting non-standard GRUB_DISTRIBUTOR in /etc/default/grub if you
use Debian 12 bookworm with enabled Secure Boot and signed grub image
from Debian. Alternatively install grub-2.12 from backports.
On 23/08/2024 11:39, Felix Miata wrote:
I don't know what vexing secure boot might introdu
Max Nikulin composed on 2024-09-14 10:59 (UTC+0700):
> So multiple loaders from the same vendor is tricky in the case of UEFI
> SecureBoot. Behavior of grub may vary across Linux distributions.
Thus, consider to KISS. Pick one installation's bootloader to depend on. Install
no others.
--
Evolut
29 matches
Mail list logo
