sudo -i
Thank you!
I am unsure what UUID you mean.
At Manjaro:
grubx64.efi is at the sdb1 - EFI vfat /dev/sdb1
grub.cfg is at the sdb2 - crypto_LUKS /dev/sdb2
grubx64.efi contains data UUID=""a8...b7" of /dev/sdb2 which is
TYPE="crypto_LUKS".
`blkid` output:
/dev/sdb2: UUID="a8...b7" T
Hellow David,
On Sun, 2024-02-04 at 13:41 -0600, David Wright wrote:
> On Sun 04 Feb 2024 at 13:57:13 (+0900), Byunghee HWANG (황병희) wrote:
> > On Fri, 2024-02-02 at 10:41 -0600, David Wright wrote:
> > > On Fri 02 Feb 2024 at 07:37:34 (+), Tixy wrote:
> > > > On Wed, 2024-01-31 at 22:12 -0600,
On Mon 05/02/2024 at 00:45, Greg Wooledge wrote:
...
> If you're one of these "I want every command I ever run to be in my
> shell history, retained forever, and I don't care how much space it
> takes" people, then there are web pages out there that can help you.
> I don't follow that philosophy m
(Re)posting the below as requested, and can confirm
history -r
seems to have the desired effect.
Thanks.
- Original message -
From: Will Mengarini
To: Gareth Evans
Cc: debian-user@lists.debian.org
Subject: Re: script/history
Date: Monday, 5 February 2024 01:02
* Gareth Evans [24-02
* Gareth Evans [24-02/04=Su 09:46 +]:
> Re the script command, does anyone know of a way to make
> commands run during a script session appear in bash history too?
You want the 'history -r' command, "explained" by `help history`.
After you end the script, you're back in the bash instance you
On Mon, Feb 05, 2024 at 12:28:38AM +, Gareth Evans wrote:
> I was trying to view the history of commands run during a script session.
>
> user@qwerty:~$ script foo
> Script started, output log file is 'foo'.
> user@qwerty:~$ date
> Mon 5 Feb 00:21:16 GMT 2024
> user@qwerty:~$ exit
> exit
> Sc
On Sun 04/02/2024 at 19:45, David Wright wrote:
...
> According to this man page for csh (but includes tcsh):
>
> https://linux.die.net/man/1/csh
>
> the "a" that modifies modifiers is a "[feature] of tcsh not found
> in most csh(1) implementations (specifically, the 4.4BSD csh)". It
> appears t
On Sun 04/02/2024 at 17:33, Greg Wooledge wrote:
...
> The script(1) utility has NOTHING to do with running ordinary shell
> scripts.
I understand that.
I was trying to view the history of commands run during a script session.
user@qwerty:~$ script foo
Script started, output log file is 'foo'.
Lee writes:
> I figure there's a high percentage of keyboard jockeys here so ..
> which keyboard do you like and why?
I've had a fnatic ministreak for a few years. Why?
- RGB backlight, I set it to a pleasant green.
- remappable keys, remappings stored in the keyboard so it works the
same ever
On Sun, Feb 04, 2024 at 01:45:27PM -0600, David Wright wrote:
> SCRIPT(1) User Commands SCRIPT(1)
> [ … ]
> HISTORY
>The script command appeared in 3.0BSD.
>
> I have no idea why "the history mechanism" is even mentioned
> in the man page for script.
It appear
On Sun 04 Feb 2024 at 16:01:29 (+), Gareth Evans wrote:
> On Sun 04/02/2024 at 13:24, Max Nikulin wrote:
> > On 04/02/2024 16:46, Gareth Evans wrote:
> >> Re the script command, does anyone know of a way [ … ]
> > [...]
> >> man script says
> >>
> >> "SEE ALSO
> >> csh(1) (for the his
On Sun 04 Feb 2024 at 13:57:13 (+0900), Byunghee HWANG (황병희) wrote:
> On Fri, 2024-02-02 at 10:41 -0600, David Wright wrote:
> > On Fri 02 Feb 2024 at 07:37:34 (+), Tixy wrote:
> > > On Wed, 2024-01-31 at 22:12 -0600, David Wright wrote:
> > > > On Tue 30 Jan 2024 at 07:05:55 (+), Tixy wrot
On 4 Feb 2024 12:08 -0600, from n...@n0nb.us (Nate Bargmann):
> xmodmap trickery? I am running GNOME on Wayland.
Or whatever the equivalent in Wayland (or GNOME) might be. Either way,
surely there must be _some_ way to map (sets of) keyboard scan codes
to symbols or actions, and that way is almos
* On 2024 04 Feb 11:57 -0600, Michael Kjörling wrote:
> On 4 Feb 2024 11:36 -0600, from n...@n0nb.us (Nate Bargmann):
> >> Unicomp[1] still makes these keyboards, and you can get them for USB.
> >
> > I don't like their swapping of the right Alt and Menu keys unless the
> > keyboard can be configu
On 4 Feb 2024 11:36 -0600, from n...@n0nb.us (Nate Bargmann):
>> Unicomp[1] still makes these keyboards, and you can get them for USB.
>
> I don't like their swapping of the right Alt and Menu keys unless the
> keyboard can be configured to swap them back.
The keyboard doesn't care what's printed
hw wrote:
> On Fri, 2024-02-02 at 20:09 -0600, Nate Bargmann wrote:
>> [...]
>> I have several of the now classic IBM Model M keyboards I procured in
>> the '90s. Modern BIOSes don't like them even with a PS/2 to USB
>> adapter so I gave up on them.
>
> They might work with a so-called active adap
* On 2024 04 Feb 04:23 -0600, hw wrote:
> On Fri, 2024-02-02 at 20:09 -0600, Nate Bargmann wrote:
> > [...]
> > I have several of the now classic IBM Model M keyboards I procured in
> > the '90s. Modern BIOSes don't like them even with a PS/2 to USB
> > adapter so I gave up on them.
>
> They migh
On Sun, Feb 04, 2024 at 04:01:29PM +, Gareth Evans wrote:
> It seemed to me initially (as I should perhaps have stated) that man script
> was suggesting that csh was a component or depedency (of script), which
> seemed to be contradicted by it not being installed. On reflection,
> possibly,
On 30/01/2024 12:50, David Wright wrote:
On 30/01/2024 02:51, David Wright wrote:
. Press HOME,
. Type any letter that makes a "wrong" command name (eg aokular),
. Press END,
[...]
However, using my "wrong" command method, Tab Tab lists are complete
all the way down the path. You can then corr
hw writes:
> On Fri, 2024-02-02 at 20:09 -0600, Nate Bargmann wrote:
>> [...]
>> I have several of the now classic IBM Model M keyboards I procured in
>> the '90s. Modern BIOSes don't like them even with a PS/2 to USB
>> adapter so I gave up on them.
>
> They might work with a so-called active a
On Sun 04/02/2024 at 13:24, Max Nikulin wrote:
> On 04/02/2024 16:46, Gareth Evans wrote:
>> Re the script command, does anyone know of a way to make commands run during
>> a script session appear in bash history too?
> [...]
>> man script says
>>
>> "SEE ALSO
>> csh(1) (for the history
On 2/4/24 09:03, Marco Moock wrote:
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
It is not needed if the network is se
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
> I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
--
kind regards
Marco
Spam und Werbung bitte an ichschickerekl...@cartoonie
Oh you're right, I entirely overlooked the usage of 'script' and
didn't understand the question right, sorry.
On Sun, 2024-02-04 at 06:28 -0500, Michael Grant wrote:
> > $ script foo.txt
> > Script started, output log file is 'foo.txt'.
> > $ date
> > Sun 4 Feb 09:44:00 GMT 2024
> > $ exit
> > ex
On 04/02/2024 16:46, Gareth Evans wrote:
Re the script command, does anyone know of a way to make commands run during a
script session appear in bash history too?
[...]
man script says
"SEE ALSO
csh(1) (for the history mechanism)"
but
$ man csh
No manual entry for csh
echo $SH
On Sun, Feb 04, 2024 at 09:46:09AM +, Gareth Evans wrote:
> man script says
>
> "SEE ALSO
>csh(1) (for the history mechanism)"
>
> but
>
> $ man csh
> No manual entry for csh
I'm so glad that we're entering an era where it's normal *not* to have
csh installed and used. That shell
On 03/02/2024 22:32, Dmitry wrote:
2. sudo bash
sudo -i
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
I am unsure what UUID you mean.
Summary: GRUB installation not only involves configuration of text
files, but
also it i
On 2/4/24 02:39, Marco Moock wrote:
Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:
On 2/2/24 16:28, Greg Wooledge wrote:
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192
On Fri, 2024-02-02 at 16:47 -0700, Charles Curley wrote:
> On Fri, 2 Feb 2024 15:52:41 -0700
> Charles Curley wrote:
>
> > But I don't think that will solve the routing problem.
>
> Well, I was wrong. That did solve the routing problems.
>
> I moved the apt-proxy line for the VMs' benefit into
> $ script foo.txt
> Script started, output log file is 'foo.txt'.
> $ date
> Sun 4 Feb 09:44:00 GMT 2024
> $ exit
> exit
> Script done.
> $ history|tail -n2
> 30797 2024-02-04 09:43:57 script foo.txt
> 30798 2024-02-04 09:44:21 history|tail -n2
>
> I did try to search on this but just got lo
On Sun, 2024-02-04 at 09:46 +, Gareth Evans wrote:
> Re the script command, does anyone know of a way to make commands
> run during a script session appear in bash history too?
Maybe this:
https://serverfault.com/questions/16204/how-to-make-bash-scripts-print-out-every-command-before-it-execut
On Fri, 2024-02-02 at 20:25 -0500, Lee wrote:
> [...]
> I figure there's a high percentage of keyboard jockeys here so ..
> which keyboard do you like and why?
It comes down to your personal preference and on how much you're
willing to pay for a good keybard. I'm using [1].
I'm using it because
On Fri, 2024-02-02 at 20:09 -0600, Nate Bargmann wrote:
> [...]
> I have several of the now classic IBM Model M keyboards I procured in
> the '90s. Modern BIOSes don't like them even with a PS/2 to USB
> adapter so I gave up on them.
They might work with a so-called active adapter. IIRC it has
s
Re the script command, does anyone know of a way to make commands run during a
script session appear in bash history too?
$ script foo.txt
Script started, output log file is 'foo.txt'.
$ date
Sun 4 Feb 09:44:00 GMT 2024
$ exit
exit
Script done.
$ history|tail -n2
30797 2024-02-04 09:43:57 sc
34 matches
Mail list logo
