debian.org/debian <http://archive.debian.org/debian>
>> >
>> > and it worked ok,but when I try to chroot within it :
>> >
>> > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
>>
>> > chroot ./jessie-armhf /bin/bash
&
http://archive.debian.org/debian <http://archive.debian.org/debian>
> >
> > and it worked ok,but when I try to chroot within it :
> >
> > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
>
> > chroot ./jessie-armhf /bin/bash
&g
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
7-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
but I see the file bash within the directory /bin of the debootstrapped
directory called
From: Me
Date: Thu, 15 Jun 2023 19:23:26 +0200
Message-id: <[🔎] 568e7aa9-e061-194a-13f8-8e2379f69...@nodatagrabbing.com>
In-reply-to: <[🔎]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
References: <[🔎]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
and
Hi,
15 juin 2023, 20:15 de m...@nodatagrabbing.com:
> Although I have never used it myself (I am 100% a vim and by extension a
> vimwiki person)
>
+1 for vimwiki.
> I know someone who used (not sure if he still does) Basket Notes
> (https://basket-notepads.github.io/) and loves it.
>
In that ca
On 2023-06-15 12:54, Susmita/Rajib wrote:
My dear illustrious Leaders of the Debian-user List and Senior List Members,
There is Wiki.js but a Debian package for wiki.js isn't available.
Then there is libreoffice-wiki-publisher in Debian, the LibreOffice
extension for working with MediaWiki arti
Susmita/Rajib wrote:
> From: Michel Verdier
> Date: Thu, 15 Jun 2023 13:54:35 +0200
> Message-id: <[🔎] 87edmdaql0@free.fr>
> In-reply-to: <[🔎]
> caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
> References: <[🔎]
> caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gm
From: Michel Verdier
Date: Thu, 15 Jun 2023 13:54:35 +0200
Message-id: <[🔎] 87edmdaql0@free.fr>
In-reply-to: <[🔎]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
References: <[🔎]
caeg4czxryyivofecor24n8o8bkbrvvuc+hhu2mmrzwyjrlj...@mail.gmail.com>
[ ... ]
> emacs ?
Tha
On Thu, 2023-06-15 at 13:54 +0200, Michel Verdier wrote:
> On 2023-06-15, Susmita/Rajib wrote:
>
> > I require a WYSIWYG editor. Zim is one. But I also need another
> > supporting editor to further polish up files.
>
> emacs ?
>
+1; emacs is good! Also i use emacs very heavy ^^^
Sincerely,
-
On 2023-06-15, Susmita/Rajib wrote:
> I require a WYSIWYG editor. Zim is one. But I also need another
> supporting editor to further polish up files.
emacs ?
My dear illustrious Leaders of the Debian-user List and Senior List Members,
There is Wiki.js but a Debian package for wiki.js isn't available.
Then there is libreoffice-wiki-publisher in Debian, the LibreOffice
extension for working with MediaWiki articles.
But files created with zim don't appe
Hello, I'm trying to repply to an old thread, not sure if it will work
(I'm using the link from
https://lists.debian.org/debian-user/2021/02/msg00394.html openned with
thunderbird)
*** Old thread ***
I have just find a posible solution
https://www.linuxuprising.com/2020/04/how-to-cast-your-gn
Darac Marjal writes:
On 10/06/2023 16:08, S M wrote:
On Sat, Jun 10, 2023 at 02:12:14PM +0100, Darac Marjal wrote:
Is command-line editing part of POSIX, then? Are you suggesting that dash is
missing some bit of POSIX compliance? That's possible.
Command-line editing in vi-mode is defined by
On 10/06/2023 16:08, S M wrote:
On Sat, Jun 10, 2023 at 02:12:14PM +0100, Darac Marjal wrote:
Is command-line editing part of POSIX, then? Are you suggesting that dash is
missing some bit of POSIX compliance? That's possible.
Command-line editing in vi-mode is defined by POSIX, but it's not m
around that start with "#!/bin/sh" and fail to work with dash -
> these are the reasons I can think of.
I have serious doubts about that. I'm sure that *in Debian*, virtually
all scripts have been fixed to use the correct syntax for their shebang.
But outside of Debian? The worl
On 2023-06-09 12:06 -0400, The Wanderer wrote:
> On 2023-06-09 at 12:00, Charles Curley wrote:
>
>> On Fri, 9 Jun 2023 13:38:25 +
>> S M wrote:
>>
>>> I noticed on a newly installed system with Debian 12 that
>>> dpkg-reconfigure no longer allows t
On Sat, Jun 10, 2023 at 09:49:14AM -0400, Greg Wooledge wrote:
> There's no point debating any further. S M has a unique desire, which
> is not shared by any other person I've ever heard of, and they're going
> to do what they want.
I didn't mean this to be a d
On 6/9/23 20:33, S M wrote:
On Fri, Jun 09, 2023 at 08:00:51PM -0400, Greg Wooledge wrote:
On Fri, Jun 09, 2023 at 05:45:04PM -0500, S M wrote:
Regarding a workaround, I ended up creating a symlink /usr/local/bin/sh
pointing to bash and chsh to that.
Why? Why not simply chsh to /bin/bash if
On Sat, Jun 10, 2023 at 02:12:14PM +0100, Darac Marjal wrote:
> Is command-line editing part of POSIX, then? Are you suggesting that dash is
> missing some bit of POSIX compliance? That's possible.
Command-line editing in vi-mode is defined by POSIX, but it's not mandatory as
far as I know.
to me.
> Is command-line editing part of POSIX, then? Are you suggesting that dash is
> missing some bit of POSIX compliance? That's possible.
There's no point debating any further. S M has a unique desire, which
is not shared by any other person I've ever heard of, and they're going
to do what they want.
On 10/06/2023 01:32, S M wrote:
On Fri, Jun 09, 2023 at 08:00:51PM -0400, Greg Wooledge wrote:
On Fri, Jun 09, 2023 at 05:45:04PM -0500, S M wrote:
Regarding a workaround, I ended up creating a symlink /usr/local/bin/sh
pointing to bash and chsh to that.
Why? Why not simply chsh to /bin/bash
On Fri, Jun 09, 2023 at 08:00:51PM -0400, Greg Wooledge wrote:
> On Fri, Jun 09, 2023 at 05:45:04PM -0500, S M wrote:
> > Regarding a workaround, I ended up creating a symlink /usr/local/bin/sh
> > pointing to bash and chsh to that.
>
> Why? Why not simply chsh to /bin/bash if that's what you wan
On Fri, Jun 09, 2023 at 05:45:04PM -0500, S M wrote:
> Regarding a workaround, I ended up creating a symlink /usr/local/bin/sh
> pointing to bash and chsh to that.
Why? Why not simply chsh to /bin/bash if that's what you want as your
interactive shell?
Are you somehow relying on bash's disabling
On Fri, Jun 09, 2023 at 04:07:03PM -0400, Greg Wooledge wrote:
> Nothing you wrote here is incorrect, but none of it explains the policy
> change that has occurred. I won't even say it's a bad policy change.
> It makes at least a little bit of sense...
Yeah, I'd also like to know what was the re
Greg Wooledge wrote:
...
> Huh. Well, that's rather important, isn't it?
>
> The package maintainers seem to have forgotten to TELL us this, at least
> in the NEWS.Debian.gz file, which still says only:
>
> unicorn:/usr/share/doc/dash$ zless NEWS.Debian.gz
> dash (0.5.5.1-2.1) unstable; urgency=l
On Fri, Jun 09, 2023 at 08:20:52PM +0200, didier gaumet wrote:
> Le 09/06/2023 à 15:38, S M a écrit :
> > I noticed on a newly installed system with Debian 12 that dpkg-reconfigure
> > no longer allows to switch the /bin/sh symlink from dash to bash. This is
> > apparently i
Le 09/06/2023 à 15:38, S M a écrit :
Good day.
I noticed on a newly installed system with Debian 12 that dpkg-reconfigure no
longer allows to switch the /bin/sh symlink from dash to bash. This is
apparently intentional as per the following:
https://launchpad.net/debian/+source/dash/0.5.11
On 2023-06-09 at 12:00, Charles Curley wrote:
> On Fri, 9 Jun 2023 13:38:25 +
> S M wrote:
>
>> I noticed on a newly installed system with Debian 12 that
>> dpkg-reconfigure no longer allows to switch the /bin/sh symlink from
>> dash to bash.
>
> You can
On Fri, 9 Jun 2023 13:38:25 +
S M wrote:
> I noticed on a newly installed system with Debian 12 that
> dpkg-reconfigure no longer allows to switch the /bin/sh symlink from
> dash to bash.
You can still change it manually (rm ; ln -s).
--
Does anybody read signatures any mor
On Fri, Jun 09, 2023 at 07:20:29AM -0700, Kushal Kumaran wrote:
> >From the comments on
> https://salsa.debian.org/debian/dash/-/commit/c322a1c9fc6be11d7eb4439407c0a398aba8bbb7,
> this is intentional and permanent. /bin/sh pointing to bash is no
> longer supported.
Huh. Well
On Fri, Jun 09 2023 at 01:38:25 PM, S M wrote:
> Good day.
>
> I noticed on a newly installed system with Debian 12 that
> dpkg-reconfigure no longer allows to switch the /bin/sh symlink from
> dash to bash. This is apparently intentional as per the following:
>
> https:/
Good day.
I noticed on a newly installed system with Debian 12 that dpkg-reconfigure no
longer allows to switch the /bin/sh symlink from dash to bash. This is
apparently intentional as per the following:
https://launchpad.net/debian/+source/dash/0.5.11+git20210903+057cd650a4ed-4
I couldn&#
Hello,
I'm not an expert but I think you can use package `broadcom-sta-dkms`.
You will find it in the non-free repo.
Please refer to (Debian
Packages)[https://packages.debian.org/bullseye/broadcom-sta-dkms] also.
If you don't want use non-free packages I see not a real chance to get
it unfo
On 5/31/23 21:20, Aleix Piulachs wrote:
i’m using bullseye 7 in a hp compaq 6830s i386 intel pentium dual t3400 and
i can’t find the network drivers broadcom BCM4312 802.11b/g LP-PHY (rev 01)
STFW "debian BCM4312", the first hit is:
https://wiki.debian.org/bcm43xx
David
i’m using bullseye 7 in a hp compaq 6830s i386 intel pentium dual t3400 and
i can’t find the network drivers broadcom BCM4312 802.11b/g LP-PHY (rev 01)
, it looks
like that laptop has one fan and one heat sink/ heat pipe:
https://support.hp.com/us-en/product/hp-compaq-6830s-notebook-pc/3688712/manuals
The fan runs from windows7 because stays in ram but from bullseye no and
the temperature is over 55 or so degrees
Again, please "Reply to lis
ory heat sink and fan with the
factory connection (3- or 4-wire), and no other fans.
Does the fan run at any time? Does it change speeds?
Please answer the remaining questions:
>> Boot the computer into Setup and reply with all available fan control
>> settings for all fa
On 5/28/23 19:27, Aleix Piulachs wrote:
i use an hp with bullseye7-386 and it does not support pwm. what can i use
instead of pwm because it gets very hot
Computer model? Processor? Does it have the factory heat sink and fan?
Is the motherboard CPU fan pin header 3- or 4-wire? Is the fan 3
i use an hp with bullseye7-386 and it does not support pwm. what can i use
instead of pwm because it gets very hot
Good morning
Dear Gene
Sorry I could no find Your anwswer
Thank You
Regards
Sophie
Von: gene heskett
Gesendet: Samstag, 20. Mai 2023 11:51
An: debian-user@lists.debian.org
Betreff: Re: AW: PANIC Debian 11 LXDE After update no booting is possible
On 5/20/23
On 5/20/23 07:32, Schwibinger Michael wrote:
AW: PANIC Debian 11 LXDE After update no booting is possible
Good afternoon
Thank You for email.
I think
in Linux
I shall post here a file
where the other users of the group can see the mistake I did.
Which file shall I read out and mail here to
AW: PANIC Debian 11 LXDE After update no booting is possible
Good afternoon
Thank You for email.
I think
in Linux
I shall post here a file
where the other users of the group can see the mistake I did.
Which file shall I read out and mail here to the group?
Regards
Sophie
The computer is using
want to run an NTP daemon to get the time from a selection of
> >> other servers.
> > Nowadays, time is something that can be handled locally with a Gossip
> > protocol. Let your watch or phone or television or toaster tell your
> > computer what time it is. No need for a
wadays, time is something that can be handled locally with a Gossip
> protocol. Let your watch or phone or television or toaster tell your
> computer what time it is. No need for a remote call to a server.
>
>> Debian runs a pool, which is configured by default in ntp-server
>>
had gone straight
> down the line and changed everything directly under "/" to a third
> party username. No root, no 1001 for that one back then.
After thinking about it again, I take that back. I THINK Adobe
affected only the directories it touched, not all "/" direct
g it this time.
And they're perping it in a different way. Adobe had gone straight
down the line and changed everything directly under "/" to a third
party username. No root, no 1001 for that one back then.
Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *
Good afternoon
I did the update and
when doing new start:
Crash
Regards
Sophie
Von: CL
Gesendet: Donnerstag, 18. Mai 2023 08:34
An: Schwibinger Michael ; Andrew M.A. Cater
; debian-user@lists.debian.org
Betreff: Re: NEW problem PANIC AW: SOLUTION AW: EPSON ..
On Thu, 2023-05-18 at 10:42 -0600, Charles Curley wrote:
> On Thu, 18 May 2023 10:07:05 -0400
> Default User wrote:
>
> > If I am running systemd-timesyncd on a single-user, internet-
> > connected
> > computer, not needing to serve time signals to any other device,
> > would
> > there be any rea
On Thu, 18 May 2023 10:07:05 -0400
Default User wrote:
> If I am running systemd-timesyncd on a single-user, internet-connected
> computer, not needing to serve time signals to any other device, would
> there be any reason to use ntp instead?
NTP is a protocol, like TCP or UDP. One program that
On Thu, 2023-05-18 at 10:20 -0400, Dan Ritter wrote:
> Default User wrote:
> > On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote:
> > > On Wed, 17 May 2023 12:48:28 -0400
> > > Dan Ritter wrote:
> > >
> > > > Assuming you have network access close to boot time, you might
> > > > want to ru
Default User wrote:
> On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote:
> > On Wed, 17 May 2023 12:48:28 -0400
> > Dan Ritter wrote:
> >
> > > Assuming you have network access close to boot time, you might
> > > want to run an NTP daemon to get the time from a selection of
> > > other ser
On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote:
> On Wed, 17 May 2023 12:48:28 -0400
> Dan Ritter wrote:
>
> > Assuming you have network access close to boot time, you might
> > want to run an NTP daemon to get the time from a selection of
> > other servers.
>
> Concur.
>
> >
> > Debi
On Wed, 17 May 2023 12:48:28 -0400
Dan Ritter wrote:
> Assuming you have network access close to boot time, you might
> want to run an NTP daemon to get the time from a selection of
> other servers.
Concur.
>
> Debian runs a pool, which is configured by default in ntp-server
> and chrony, at l
Good evening
Is it polite to delete all EPSON emails?
I think Yes.
Thank You to all
Sophie
05-16 11:15:22.564093+00:00
>
> Assuming you have network access close to boot time, you might
> want to run an NTP daemon to get the time from a selection of
> other servers.
++. Let the software handle it.
Nowadays, time is something that can be handled locally with a Gossip
proto
Albretch Mueller wrote:
> In case someone runs into the same problem, for some reason I can't
> quite understand "sudo hwclock --set" wasn't working. Someone helped
> me:
>
> https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html
> https://wiki.debian.org/DateTime
>
> and "date" wo
> Yes, I did. I had to reset the BIOS to "factory settings" which also
> changed the clock time which then I couldn't change with hwclock ...
"Another day another problem": computer clock back to BIOS factory settings
Your Computer Clock is Wrong:
Your computer thinks it is 8/7/2022, which pre
s
NTFS of my laptop and my employer's as well without any problems
whatsoever. I just open the file browser/viewer and click the drive to
mount it in order to unmount, eject it you right click on it. It
works.
>> $ cp "No space left on device" > No_space_left_on_device.txt
>
Albretch Mueller writes:
> I have been mounting an NTFS file system on a Windows laptop without
> any problems whatsoever with a Debian Live DVD:
Mounting how exactly? And what is the contents of /proc/mounts? Maybe
you mounted the partition read only?
Joe wrote:
>
> First thing to try is to boot back into Windows and see if there is a
> message about the drive. If so, let Windows 'fix' it. I've had cases
> where the drive was not cleanly unmounted and Linux has mounted it
> read-only. Windows was able to repair it, whatever the problem was.
Oh
0F Sun 14 May 2023 07:13:43 PM UTC
> > 166G/media/user/60320G593EB7250F
> >
> > real0m45.230s
> > user0m1.073s
> > sys 0m15.443s
> > $
> >
> > when I try to save or download a file I consistently get the same
> > error message:
> >
&
On Mon, 15 May 2023 00:32:01 +
Albretch Mueller wrote:
> when I try to save or download a file I consistently get the same
> error message:
>
> $ cp "No space left on device" > No_space_left_on_device.txt
> bash: No_space_left_on_device.txt: No space left on devi
hen I try to save or download a file I consistently get the same error
> message:
>
> $ cp "No space left on device" > No_space_left_on_device.txt
> bash: No_space_left_on_device.txt: No space left on device
>
> that started happening right after a WiFi connection at a
7:13:43 PM UTC
166G/media/user/60320G593EB7250F
real0m45.230s
user0m1.073s
sys 0m15.443s
$
when I try to save or download a file I consistently get the same error message:
$ cp "No space left on device" > No_space_left_on_device.txt
bash: No_space_left_on_device.txt:
On Tue 02 May 2023 at 12:10:48 (+0200), DdB wrote:
> I notice, that, even though i did change the name of the sda2 partition,
> the PARTLABEl remained unchanged.
It's rather confusing that gdisk (my preferred partitioner, which
I use outside the installer) refers to the PARTLABEL as the
partition
DdB wrote:
...
> I notice, that, even though i did change the name of the sda2 partition,
> the PARTLABEl remained unchanged.
> This proves my previous post wrong and i am sorry for the confusion,
> this may have caused. You were correct all along.
> DdB
yes, but i also recall you saying somethi
Am 02.05.2023 um 05:50 schrieb David Wright:
> On Tue 02 May 2023 at 02:21:20 (+0200), DdB wrote:
>> Am 01.05.2023 um 21:38 schrieb David Wright:
>>> And PARTLABELs aren't interfered with even by the installer.
>>
>> This at least i can contradict for a fact.
>
> So is this post the rebuttal, or a
tand
and consider. Just keep in mind, that if a problem arises, i might not
be able too deal with, i will be cut off from everything, no paper based
calendar even exists. So i am careful.
DdB
It seems like you are trying to solve several issues at the same time:
1. How to install Debian onto
On Tue 02 May 2023 at 02:21:20 (+0200), DdB wrote:
> Am 01.05.2023 um 21:38 schrieb David Wright:
> > And PARTLABELs aren't interfered with even by the installer.
>
> This at least i can contradict for a fact.
So is this post the rebuttal, or are you posting the evidence elsewhere?
> VM is funct
Am 01.05.2023 um 21:38 schrieb David Wright:
> And PARTLABELs aren't interfered with even by the installer.
This at least i can contradict for a fact. VM is functional with known
and documented partlabels, then the installer handles partitions
(reformat is permitted) and the UUID's AND the PARTUUI
erns, somthing i am trying to understand
and consider. Just keep in mind, that if a problem arises, i might not
be able too deal with, i will be cut off from everything, no paper based
calendar even exists. So i am careful.
DdB
ption here: (1)
Funny little detail: Ubuntu is suffering way less, because their
distribution is based on more recent version than debian stable is.
At least i saw some guy posting a video on youtube showing, how he
upgraded gnome-shell to experimental thereby creating a frankendebian,
something,
On Mon 01 May 2023 at 13:08:56 (+0200), DdB wrote:
> One explanation of my choice to stick with PARTUUID's:
> In my overall stategy of using my computer, i am sometimes copying (dd)
> whole partitions into a backup, a secondary partition or a VM, which can
> easily lead to difficulties, if the sam
method Device-mapper (dm-crypt)
Encryption aes
Key size256
IV algorithmxts-plain64
Encryption key Random key
Erase data no
Bootable flag
;Debian Desktop" selected, the installer chooses a Desktop
Environment for you. And guess which one it chooses by default? That's
right: GNOME. Assuming you're using a standard installer image, and
not one that has a DE in its name.
I have no idea why this confusing default auto-selection exists, but
it does.
Am 01.05.2023 um 10:23 schrieb Michel Verdier:
> Le 1 mai 2023 DdB a écrit :
>
>> But omitting GNOME from the list lead to a system failing to boot with
>> tons of messages stating the absense of all kind of gnome parts.
>
> To install without gnome I select the task ssh server then after I
> man
Le 1 mai 2023 DdB a écrit :
> Any suggestions/questions/hints from the power-users in here?
> ... would be wildly appreciated ...
When installing you have to stop on your first problem. The others could
be created from it. It's longer but easier to cope with. So give us full
details on your first
Le 1 mai 2023 DdB a écrit :
> But omitting GNOME from the list lead to a system failing to boot with
> tons of messages stating the absense of all kind of gnome parts.
To install without gnome I select the task ssh server then after I
manually select what I want, and a WM if needed.
tall failures due to the 4GB of RAM apparently
> not being enough for that VM.
I can install bullseye and bookworm-RC1 standard software (no DE) on
an i386 laptop with ½GB memory using no swap, so that surprises me.
> Another problem, similar but distinctly different happens around the OS
>
Hello list,
after receiving so much good advice, i finally made up my mind and began
playing through the installation (debian bullseye, current stable) in my
simulation-VM in order to learn about the pitfalls to avoid. After more
than a dozen tries, i am running out of fuel, because i am continuou
Hello everyone,
I partly solved my problem and I would like to share my solution:
Until now, I thought that the EFI removable media path (\EFI\BOOT\BOOTX64.EFI)
is really a fallback location, i.e. a location for putting the boot loader that
just always works. Therefore I thought that I could fo
On Thu 27 Apr 2023 at 10:18:56 (+0700), Max Nikulin wrote:
> On 26/04/2023 22:57, Valentin Caracalla wrote:
> > the issue with the BIOS boot interface (see my original posting) is still
> > unsolved
>
> I had impression that there was no issue with booting in BIOS (legacy,
On 26/04/2023 22:57, Valentin Caracalla wrote:
the issue with the BIOS boot interface (see my original posting) is still
unsolved
I had impression that there was no issue with booting in BIOS (legacy,
compatibility, CSM) mode, of course when it is chosen in firmware/BIOS
setup (requires
at it uses the EFI fallback location which is
guaranteed to work in every EFI implementation and doesn't depend on EFI
variables.
On my hardware, the problem exists no matter which of the two recipes I use.
Can you reproduce the issue on your hardware? Or is it just my old hardware
causing the p
David Wright (12023-04-25):
> Don't knock it! The Human Era is much easier for us to parse than
;-)
> the French Republican calendar (pre 2018).
I had not realized I had fans devoted to the point of tracking the eras
of my mail attribution. ;-)²
Regards,
--
Nicolas George
signature.asc
De
Greg Wooledge (12023-04-25):
> find /mnt/boot/efi -exec ls -dl {} +
zsh
ls -dl /mnt/boot/efi/**/*
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
On Wed 26 Apr 2023 at 09:14:25 (+0700), Max Nikulin wrote:
> On 26/04/2023 00:42, Nicolas George wrote:
> > Steve McIntyre (12023-04-25):
[ … ]
> P.S. Nicolas, it seems your mailer has issues with parsing or
> formatting timestamps.
Don't knock it! The Human Era is much easier for us to parse th
On Wed, Apr 26, 2023 at 09:34:11AM +0700, Max Nikulin wrote:
> On 26/04/2023 05:02, Valentin Caracalla wrote:
> >
> > user@host:~$ ls -dl $(find /mnt/boot/efi)
>
> find /mnt/boot/efi -print0 | xargs -0 ls -dl --
>
> should be more resistant to peculiar file names, but it does not matter in
> thi
On 26/04/2023 05:02, Valentin Caracalla wrote:
user@host:~$ ls -dl $(find /mnt/boot/efi)
find /mnt/boot/efi -print0 | xargs -0 ls -dl --
should be more resistant to peculiar file names, but it does not matter
in this case.
...
-rwxr-xr-x 1 root root 126 Apr 25 13:59 /mnt/boot/efi/EFI/
On 26/04/2023 00:42, Nicolas George wrote:
Steve McIntyre (12023-04-25):
If you do not intend to install a Microsoft bootloader or anything
besides GRUB, 16 megaoctets is plenty enough, probably can work with
less.
Please STOP giving this advice to people!
That was not advice, that was inform
Valentin Caracalla (12023-04-26):
> EFI variables are not supported on this system.
To install GRUB in UEFI, you need to have booted the kernel in UEFI.
Try to find a live image that does, and you can reinstall GRUB from
there.
Regards,
--
Nicolas George
signature.asc
Description: PGP sign
Here's the output you requested:
user@host:~$ ls -dl $(find /mnt/boot/efi)
drwxr-xr-x 3 root root 32768 Jan 1 1970 /mnt/boot/efi
drwxr-xr-x 3 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI
drwxr-xr-x 2 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI/debian
-rwxr-xr-x 1 root root 108
Steve McIntyre (12023-04-25):
> >If you do not intend to install a Microsoft bootloader or anything
> >besides GRUB, 16 megaoctets is plenty enough, probably can work with
> >less.
> Please STOP giving this advice to people!
That was not advice, that was information. Make your own advice with it.
Nicolas George wrote:
>Max Nikulin (12023-04-25):
>> 0.5GB is usually enough, e.g. 550MiB recommended by
>> https://www.rodsbooks.com/gdisk/advice.html#esp_sizing)
>
>If you do not intend to install a Microsoft bootloader or anything
>besides GRUB, 16 megaoctets is plenty enough, probably can work
Max Nikulin (12023-04-25):
> 0.5GB is usually enough, e.g. 550MiB recommended by
> https://www.rodsbooks.com/gdisk/advice.html#esp_sizing)
If you do not intend to install a Microsoft bootloader or anything
besides GRUB, 16 megaoctets is plenty enough, probably can work with
less.
Regards,
--
On 25/04/2023 21:40, Valentin Caracalla wrote:
I checked my partition table using "sudo parted /dev/sda print"
Number Start End Size File system Name Flags
1 1049kB 128GB 128GB fat32 init boot, esp
2 128GB 256GB 128GB ext4 root
Please, show
vorubergeh...@tutanota.com wrote:
>By the way:
>
>The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
>following will not show a GRUB command line:
>
>sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
>
>The same thing works for the BIOS boot interface, however (as in my
Valentin Caracalla (12023-04-25):
> The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the
> following will not show a GRUB command line:
>
> sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda
Oh, I must check if the KVM virtual machine booting on UEFI I have been
toying w
301 - 400 of 7070 matches
Mail list logo
