On 2024-11-30 20:00, Roberto C. Sánchez wrote:
So, it looks like what you want is noninteractive, with preseeding. You
should probably read the entire man page, as there are lots of ways to
tweak the behavior of debconf.
Regards,
-Roberto
Thanks Roberto and Andy. I'll look at debconf and se
On Sat, Nov 30, 2024 at 05:38:40PM -0500, John Boxall wrote:
>
> Is the option "-y" in the command not enough to prevent the prompt?
>
As Andy explained, no the "-y" option will not prevent the prompt.
The "-y" as you have used it is passed to apt-
On 2024-11-30 17:48, Andy Smith wrote:
On Sat, Nov 30, 2024 at 10:45:37PM +, Andy Smith wrote:
Is the option "-y" in the command not enough to prevent the prompt?
I forgot to add:
Using -y on dist-upgrade is a good way to completely destroy your system
given the slightest an
On Sat, Nov 30, 2024 at 10:45:37PM +, Andy Smith wrote:
> > Is the option "-y" in the command not enough to prevent the prompt?
I forgot to add:
Using -y on dist-upgrade is a good way to completely destroy your system
given the slightest anomaly (and this is an upgrade to te
Hi,
On Sat, Nov 30, 2024 at 05:38:40PM -0500, John Boxall wrote:
> apt-get -y --show-progress dist-upgrade
>
> During the dist-upgrade I am presented with the following prompt:
>
>
> Setting up fwupd (1.9.26-2) ...
>
> Configuration file '/etc/fwupd/fwup
apt-get -y --only-upgrade --show-progress upgrade
apt-get -y --show-progress dist-upgrade
During the dist-upgrade I am presented with the following prompt:
Setting up fwupd (1.9.26-2) ...
Configuration file '/etc/fwupd/fwupd.conf'
==> File on system created by you or by a sc
David Wright wrote:
> On Mon 04 Nov 2024 at 17:17:44 (+), Chris Green wrote:
> > I have found how to get it to install, I removed the other (SATA SSD)
> > disk drive. It now boots successfully, phew!
>
> Good.
>
> > I've no idea why that second drive breaks things. I installed it when
> >
On Mon 04 Nov 2024 at 17:17:44 (+), Chris Green wrote:
> I have found how to get it to install, I removed the other (SATA SSD)
> disk drive. It now boots successfully, phew!
Good.
> I've no idea why that second drive breaks things. I installed it when
> I was still running xubuntu 24.04 and
On Mon, Nov 4, 2024 at 12:17 PM Chris Green wrote:
>
> On Mon, Nov 04, 2024 at 08:31:41AM -0500, Felix Miata wrote:
> [...]
> > Is a BIOS update available?
> >
> Possibly, but I bet I'd need an MS-Windows system to do the update.
This situation sucks. My father has an Acer laptop like it -- the
I have found how to get it to install, I removed the other (SATA SSD)
disk drive. It now boots successfully, phew!
I've no idea why that second drive breaks things. I installed it when
I was still running xubuntu 24.04 and that OS could see the drive OK.
I actually copied the whole of my old (xu
I have found how to get it to install, I removed the other (SATA SSD)
disk drive. It now boots successfully, phew!
I've no idea why that second drive breaks things. I installed it when
I was still running xubuntu 24.04 and that OS could see the drive OK.
I actually copied the whole of my old (xu
Hi,
Chris Green wrote:
> > (proc) (memdisk) (lvm/q957--vg-swap_1) (lvm/q957--vg-root) (hd0)
> > (hd0,apple2) (hd0,apple1) (hd0,msdos2) (hd1) (hd1,gpt1) (hd2)
> > (hd2,msdos5) (hd2,msdos1)
David Wright wrote:
> So hd0 is the USB stick.
Looks like that. Apple Partition Map is not much in use on a
Chris Green composed on 2024-11-04 15:27 (UTC):
> (proc) (memdisk) (lvm/q957--vg-swap_1) (lvm/q957--vg-root) (hd0)
> (hd0,apple2) (hd0,apple1) (hd0,msdos2) (hd1) (hd1,gpt1) (hd2)
> (hd2,msdos5) (hd2,msdos1)
On all my GPT disks, the required ESP filesystem is on (hd0,gpt1). Presumably
your
ESP
On Mon, Nov 04, 2024 at 11:19:50AM -0500, Stefan Monnier wrote:
> > If I boot from the USB stick (isohybrid image) in Legacy mode then it
> > all **appears** to work, installation completes, but then the system
> > won't boot.
>
> What kind of boot loader did you install? `grub-efi`, `grub-pc`,
>
ntinues from my "Failed Debian 12 install..." thread earlier
> > > > today.
> > > >
> > > > I can't get the USB Installation stick to boot into the Debian
> > > > installation process when I load it in UEFI mode. If I boot the USB
>
> If I boot from the USB stick (isohybrid image) in Legacy mode then it
> all **appears** to work, installation completes, but then the system
> won't boot.
What kind of boot loader did you install? `grub-efi`, `grub-pc`,
something else?
Does your Debian install's boot fail in exactly the same wa
> today.
> > >
> > > I can't get the USB Installation stick to boot into the Debian
> > > installation process when I load it in UEFI mode. If I boot the USB
> > > stick in UEFI mode it just takes me to the grub prompt.
> >
> > It may help
k to boot into the Debian
> > installation process when I load it in UEFI mode. If I boot the USB
> > stick in UEFI mode it just takes me to the grub prompt.
>
> It may help to know whether that's a grub> prompt
> or a grub rescue> prompt. The latter takes a bi
t the USB
> stick in UEFI mode it just takes me to the grub prompt.
It may help to know whether that's a grub> prompt
or a grub rescue> prompt. The latter takes a bit more
work to recover from.
Whichever, does typing ls produce a listing of some sort?
Basically, you have to l
On Mon, Nov 04, 2024 at 08:53:02AM -0500, Stefan Monnier wrote:
> > I suspect that this is why, when I boot from the USB stick in BIOS
> > compatibility mode the resulting installation doesn't work.
>
> Last time I did an install on a UEFI machine (most of my machines are
> too old, and of the two
the Debian
> > installation process when I load it in UEFI mode. If I boot the USB
> > stick in UEFI mode it just takes me to the grub prompt.
>
> > I suspect that this is why, when I boot from the USB stick in BIOS
> > compatibility mode the resulting installation doe
> I suspect that this is why, when I boot from the USB stick in BIOS
> compatibility mode the resulting installation doesn't work.
Last time I did an install on a UEFI machine (most of my machines are
too old, and of the two that aren't, one is running Coreboot 🙂),
I found out that if the installa
gt; stick in UEFI mode it just takes me to the grub prompt.
> I suspect that this is why, when I boot from the USB stick in BIOS
> compatibility mode the resulting installation doesn't work.
> Any ideas what I need to do to get the USB stick to boot properly in
> USB mode?
This has
gt; stick in UEFI mode it just takes me to the grub prompt.
> I suspect that this is why, when I boot from the USB stick in BIOS
> compatibility mode the resulting installation doesn't work.
> Any ideas what I need to do to get the USB stick to boot properly in
> USB mode?
This has
This continues from my "Failed Debian 12 install..." thread earlier
today.
I can't get the USB Installation stick to boot into the Debian
installation process when I load it in UEFI mode. If I boot the USB
stick in UEFI mode it just takes me to the grub prompt.
I suspect that th
On Sun, Sep 05, 2021 at 09:38:34AM -0400, Cindy Sue Causey wrote:
> There's also that thing about how terminals will interpret the
> different types of quotes (dumb/typewriter/ASCII versus
> typographic/curly/smart) very literally. I experienced THAT fail
> firsthand and now try to remember to plug
On 9/5/21, Greg Wooledge wrote:
> On Sun, Sep 05, 2021 at 12:28:37AM -0500, Intense Red wrote:
>> > In /root/.bashrc I use this to give a red prompt including host and
>> > full path followed by a new line.
>>
>>I take this idea a bit further, se
On Sun, Sep 05, 2021 at 12:28:37AM -0500, Intense Red wrote:
> > In /root/.bashrc I use this to give a red prompt including host and
> > full path followed by a new line.
>
>I take this idea a bit further, setting a longer prompt and setting
> workstation hosts for spe
On 9/5/21, Intense Red wrote:
>> In /root/.bashrc I use this to give a red prompt including host and
>> full path followed by a new line.
>
>I take this idea a bit further, setting a longer prompt and setting
> workstation hosts for specific colors for user logins,
> In /root/.bashrc I use this to give a red prompt including host and
> full path followed by a new line.
I take this idea a bit further, setting a longer prompt and setting
workstation hosts for specific colors for user logins, and then doing a red
prompt for servers.
Part
On 2021-04-26 02:43 PM, Steve Dondley wrote:
I downloaded and ran this docker image: https://hub.docker.com/_/debian
It works, but typically when I hit the ctrl-p key at the bash prompt,
it acts like the up arrow key and shows the previous command.
However, I have to hit ctrl-p twice to show
I downloaded and ran this docker image: https://hub.docker.com/_/debian
It works, but typically when I hit the ctrl-p key at the bash prompt, it
acts like the up arrow key and shows the previous command.
However, I have to hit ctrl-p twice to show the previous command and
twice each time to
is some basic and fairly simple may to remove that obstacle.
>
> Can someone tell me how to arrange things so that I have no prompt for
> login keyring authentication when opening mail account in `evolution'.
>
> I don't mean password for mail account but I get prompted fo
how to arrange things so that I have no prompt for
login keyring authentication when opening mail account in `evolution'.
I don't mean password for mail account but I get prompted for login
keyring auth that I know nothting about. When it comes up everything
else freezes until I deal
On Fri, Dec 13, 2019 at 04:50:18PM -0600, David Wright wrote:
> > PS1='\u@\h $(date +"%d %b %Y %H:%M:%S") :\w\$ '
>
> Could \D{format} not do that?
Oh, good catch. I've... never used that before. ;-) I scanned the
PROMPTING section of the man page too quickly and only saw
the \t \T \@ \A parts.
> if [ "$color_prompt" = yes ]; then
>
> PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\$
> '
You forgot to add "\d", in PS1 value, that explains different behavior
of prompt in console and Guake
On Fri 13 Dec 2019 at 14:36:09 (-0500), Greg Wooledge wrote:
> On Fri, Dec 13, 2019 at 07:20:53PM +, shirish शिरीष wrote:
> > Can somebody share how can I have a common prompt which is ok both by
> > bash and guake ?
>
> guake...? No idea what that is. apt-cache says
shirish ??? wrote:
> at bottom :-
>
> On 13/12/2019, Dan Ritter wrote:
> > shirish ??? wrote:
> >> Dear all,
> >>
> >> Can somebody share how can I have a common prompt which is ok both by
> >> bash and guake ?
> &g
at bottom :-
On 13/12/2019, Dan Ritter wrote:
> shirish ??? wrote:
>> Dear all,
>>
>> Can somebody share how can I have a common prompt which is ok both by
>> bash and guake ?
>>
>> bash is -
>>
>> $ guake --version
>> Gu
On Fri, Dec 13, 2019 at 07:20:53PM +, shirish शिरीष wrote:
> Can somebody share how can I have a common prompt which is ok both by
> bash and guake ?
guake...? No idea what that is. apt-cache says it's a terminal. So
I'm just going to assume that it works like any other
shirish ??? wrote:
> Dear all,
>
> Can somebody share how can I have a common prompt which is ok both by
> bash and guake ?
>
> bash is -
>
> $ guake --version
> Guake Terminal: 3.6.3
> VTE: 0.58.2
> VTE runtime: 0.58.2
> Gtk: 3.24.13
>
Dear all,
Can somebody share how can I have a common prompt which is ok both by
bash and guake ?
bash is -
$ bash -version
GNU bash, version 5.0.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.
Hi,
i meant not
[...] man bas, section PROMPTING.
but rather
[...] man bash, section PROMPTING.
Have a nice day :)
Thomas
Hi,
Stephen P. Molnar wrote:
> or some reason the Xcfc4-Termial is:
> (base) comp@AbNormal:~$
> rather than:
> comp@AbNormal:~$
Check the content of the environment variable PS1.
me@myhost:~> echo $PS1
\u@\h:\W>
The meaning of the "\"-codes is explained in man bas, section PROMPTING.
I gues
I have just installed Anaconda 19-10 on my up to date Buster platform as
user. For some reason the Xcfc4-Termial is:
(base) comp@AbNormal:~$
rather than:
comp@AbNormal:~$
which is what the installer created.
What is going on here, and how do I get the prompt back?
The root prompt is
; >
> > execute a script
> > print a string
>
> Are you actually able to discern the OP's desires? I can't. I found
> everything they said in this thread completely impenetrable. At first
> I thought they wanted to write a script that would change the bash
rn the OP's desires? I can't. I found
everything they said in this thread completely impenetrable. At first
I thought they wanted to write a script that would change the bash
prompt by setting the PS1 variable
> If you make your screen narrow before you cut and paste, you won'
On Tue 03 Sep 2019 at 15:07:43 (+), Larry Dighera wrote:
> On Mon, 02 Sep 2019 08:48:50 +0200, Computer Planet
>
> wrote:
>
> >Is It possible to print of a string at the exit of a bash script?
>
> Have a look at `man bash` and search for 'trap.'
Trap is designed to break the sequential fl
On Mon, 02 Sep 2019 08:48:50 +0200, Computer Planet
wrote:
>Is It possible to print of a string at the exit of a bash script?
Have a look at `man bash` and search for 'trap.'
trap [-lp] [[arg] sigspec ...]
The command arg is to be read and executed when the
shell receives signa
st your wishes). We don't read minds.
> Now, I ask the question in other terms:
> Is It possible to print of a string at the exit of a bash script?
> e.g.: user@mypc: # bash script has just finished! [prompt]
> with the prompt that remains immediately after the string printed.
>
On Mon, Sep 02, 2019 at 09:30:44AM +0200, Thomas Schmitt wrote:
> Hi,
>
> Computer Planet wrote:
> > Is It possible to print of a string at the exit of a bash script?
> > e.g.: user@mypc: # bash script has just finished! [prompt]
> > with the prompt that remains i
Hi,
Computer Planet wrote:
> Is It possible to print of a string at the exit of a bash script?
> e.g.: user@mypc: # bash script has just finished! [prompt]
> with the prompt that remains immediately after the string printed.
Do you mean something like this ?
$ echo -n 'use
On Mon, Sep 02, 2019 at 08:48:50AM +0200, Computer Planet wrote:
> Thanks guys,
> but this is not the solution I'm looking for ...
> Now, I ask the question in other terms:
> Is It possible to print of a string at the exit of a bash script?
Hm. You mean
echo
Still a bit confused about where y
Thanks guys,
but this is not the solution I'm looking for ...
Now, I ask the question in other terms:
Is It possible to print of a string at the exit of a bash script?
e.g.: user@mypc: # bash script has just finished! [prompt]
with the prompt that remains immediately after the string pr
On Sun, Sep 01, 2019 at 03:22:32PM -0400, Lee wrote:
[...]
> You have to source the script instead of running it.
Yes, exactly.
> I'm not entirely clear about a new shell gets it's own env that
> disappears when the shell exits thing, but try this:
It's not only a shell thing. It's a basic Uni
#\[\033[91m\] "
> so that after finishing the script the prompt will write in red...?
>
> If I try in prompt # PS1="\[\e]0;\u@\h:
> \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w
> #\[\033[91m\] "
> command no problem, write in
\033[00m\]:\[\033[01;34m\]\w
> #\[\033[91m\] "
> so that after finishing the script the prompt will write in red...?
>
> If I try in prompt # PS1="\[\e]0;\u@\h:
> \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w
> #\[\033[91m\] &
Hi guys!
I'm trying, trying and trying but...
How I Can put in hte end of a bash script this command:
PS1="\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w
#\[\033[91m\] "
so that after finishing the script the prompt wi
Schmitt wrote:
John Crawley wrote:
In Buster, the launching dash shell dies *immediately* and the bash
prompt returns, even while the new window is still open.
tomas wrote:
that most probably is due to a change
in behaviour of "x-terminal-emulator".
My suspicion too. If the x-terminal-emu
y shell.
[I don't see any photos attached. (The entire email is only 4.3kB)]
But I have struggled to find out what program is expected to issue
the prompt and collect the passphrase under various circumstances
(eg unlocking at boot, or unlocking later).
> вт, 28 мая 2019 г., 9:38 d
gt;> be prompted on each upgrade for the list of services you wish to
>> restart. You
>> can choose this option to avoid being prompted; instead, all necessary
>> restarts
>> will be done for you automatically so you can avoid being asked questions on
>> each library u
You
> can choose this option to avoid being prompted; instead, all necessary
> restarts
> will be done for you automatically so you can avoid being asked questions on
> each library upgrade.
> Restart services during package upgrades without asking?
> 1: Yes 2: No [*]
>
u can avoid being asked questions on
each library upgrade.
Restart services during package upgrades without asking?
1: Yes 2: No [*]
Prompt: '?' for help, default=2>
If I use 'DEBIAN_FRONTEND=noninteractive' it works and will use the
default value and I don't get a
> The opinion is that it is a bug. See
>
> https://lists.debian.org/debian-devel/2019/06/msg0.html
Thank you for the feedback. I have filed a bug report for this issue.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929834
Please note that this issue does not occur if using the slick-greet
rmally.
> >
> > Also, switching to another VT when the monitor turns off and switching
> > back displays the unlock prompt normally.
> >
> > The closest I could find online was this:
> > https://bbs.archlinux.org/viewtopic.php?id=240200 wherein installi
on.
>
> Typing the password without any visual feedback (while the monitor
> continues to be in the power save state) unlocks the screen and my
> session is displayed normally.
>
> Also, switching to another VT when the monitor turns off and switching
> back displays the unlock p
he monitor back on.
>
> Typing the password without any visual feedback (while the monitor
> continues to be in the power save state) unlocks the screen and my
> session is displayed normally.
>
> Also, switching to another VT when the monitor turns off and switching
> back displays the u
continues to be in the power save state) unlocks the screen and my
session is displayed normally.
Also, switching to another VT when the monitor turns off and switching
back displays the unlock prompt normally.
The closest I could find online was this:
https://bbs.archlinux.org/viewtopic.php?id
quiet) systemd stops
> on waiting for partition, but no any password prompt. I try to boot with
> plymouth (ro quiet splash), but it does not help me. I may boot only using
> "recovery mode". In this case system asks me for password and I may enter
> it (but there are lot of
I have examine initramfs image and found that it is not tries to mount
encrypted partitions other than root. Moreover, it is confirmed by dmesg
output: systemd starts before mounting of /var and /home So it is not
initrd problem. Problem somethere in system.
Best regards,
Sergey Belyashov
вт, 28
Sergey Belyashov wrote:
> As expected nothing is changed. I did not forget to run update-initramfs
> after change of fstab.
> Attached 3 photos: normal boot, recovery boot before pasword enter,
> recovery boot after password and Ctrl-D in recovery shell.
I am not a systemd expert. The images does
As expected nothing is changed. I did not forget to run update-initramfs
after change of fstab.
Attached 3 photos: normal boot, recovery boot before pasword enter,
recovery boot after password and Ctrl-D in recovery shell.
Best regards,
Sergey Belyashov
вт, 28 мая 2019 г., 9:38 deloptes :
> Serg
I'll try your suggestion. But I think problem is not here. Password ask is
after mounting all other filesystems, swapon and flush of journald:
[9.986320] intel_rapl: Found RAPL domain uncore
[ 10.203636] EXT4-fs (md0p2): mounted filesystem with ordered data mode.
Opts: (null)
[ 10.203981]
Sergey Belyashov wrote:
> Root partition is on mdraid but is not encrypted. Home is encrypted only.
> Modules are set to most already.
>
I have this setup on my server, but I removed all crypted entries from fstab
because obviously I can not sit infront of the server to type the password
when bo
Root partition is on mdraid but is not encrypted. Home is encrypted only.
Modules are set to most already.
вт, 28 мая 2019 г., 9:06 deloptes :
> Sergey Belyashov wrote:
>
> > My problem is about than year old or more. With default options (without
> > plymouth) only information about root partiti
Ross Boylan wrote:
> I've discovered that if I type my pass-phrase (waiting long enough
> that I think things have settled down), the system boots.
>
Have you tried setting up the display parameters properly in grub? Sometimes
on notebooks the default settings are different and do not match pred
Sergey Belyashov wrote:
> My problem is about than year old or more. With default options (without
> plymouth) only information about root partition mount or fsck. Later it
> replaced by partition waiting "progress" (moving red asterisks). I have
> try to wait about a minute and try to enter luks
My problem is about than year old or more. With default options (without
plymouth) only information about root partition mount or fsck. Later it
replaced by partition waiting "progress" (moving red asterisks). I have try
to wait about a minute and try to enter luks password, but no any changes.
I t
For at least the last couple of weeks I've had the screen go
completely blank during bootup, after displaying initial messages (I
changed from "quiet" to "debug" for kernel startup). This is with a
luks encrypted root. I saw it under jessie and buster. I blamed
failing hardware (I can't get into
I have system with soft raid and /home is encrypted (one of raid1
partitions is encrypted using luks with password). When I boot it using
default boot kernel options (ro quiet) systemd stops on waiting for
partition, but no any password prompt. I try to boot with plymouth (ro
quiet splash), but it
I have system with soft raid and /home is encrypted (luks with password).
When I boot it using default boot kernel options (ro quiet) systemd stops
on waiting for partition, but no any password prompt. I try to boot with
plymouth (ro quiet splash), but it does not help me. I may boot only using
Short version: why doesn't my PC prompt for its passphrase on tty1?
Long version...
I have a 'stretch' PC used as a home server, so it doesn't normally
require a monitor and keyboard. It has an encrypted filesystem and on
boot it asks for the passphrase with this prompt,
An update.
On Sun, Jun 10, 2018 at 08:03:31PM +0300, Reco wrote:
> Hi.
>
> On Sun, Jun 10, 2018 at 07:06:57PM +0300, Michelle Konzack wrote:
> > Am 2018-06-10 hackte Reco in die Tasten:
> > > Hi.
> > >
> > > On Sun, Jun 10, 2018 at 02:25:30PM +0300, Michelle Konzack wrote:
> > >> Good day
Hi.
On Sun, Jun 10, 2018 at 07:06:57PM +0300, Michelle Konzack wrote:
> Am 2018-06-10 hackte Reco in die Tasten:
> > Hi.
> >
> > On Sun, Jun 10, 2018 at 02:25:30PM +0300, Michelle Konzack wrote:
> >> Good day,
> >>
> >> I run Stretch on my Laptop with sysvinit.
> >>
> >> I had setup so
Am 2018-06-10 hackte Reco in die Tasten:
> Hi.
>
> On Sun, Jun 10, 2018 at 02:25:30PM +0300, Michelle Konzack wrote:
>> Good day,
>>
>> I run Stretch on my Laptop with sysvinit.
>>
>> I had setup some profiles and tried to start them by passing 2, 3,
>> 4, 5 at the end of the Kernel commandli
Hi.
On Sun, Jun 10, 2018 at 02:25:30PM +0300, Michelle Konzack wrote:
> Good day,
>
> I run Stretch on my Laptop with sysvinit.
>
> I had setup some profiles and tried to start them by passing 2, 3,
> 4, 5 at the end of the Kernel commandline (I use LILO) but the
> appropriated runnlevel
Good day,
I run Stretch on my Laptop with sysvinit.
I had setup some profiles and tried to start them by passing 2, 3,
4, 5 at the end of the Kernel commandline (I use LILO) but the
appropriated runnlevel ist not entered.
Do I mis something?
Since systemd anything is screwed up und nothing is w
t; The consequence (if not post hoc ergo propter hoc) of these messages
> appearing is that it makes the LUKS passphrase prompt to use bépo. Now I know
> it, it"s not really a problem for typing the passphrase, but I really think
> this is a bug, as there was no clear warning about
dead key, which allows to
type Greek letters using the Latin equivalent. I say "supposed" as Debian does
not support it yet.
The consequence (if not post hoc ergo propter hoc) of these messages appearing
is that it makes the LUKS passphrase prompt to use bépo. Now I know it, it's
On 9/19/16, Reco wrote:
>
> On Mon, Sep 19, 2016 at 11:01:33AM -0400, Tony Baldwin wrote:
>> On 09/19/2016 10:25 AM, Reco wrote:
>> >
>> >On Mon, Sep 19, 2016 at 09:59:03AM -0400, Tony Baldwin wrote:
>> >>I had, on a prior machine, changed th
* Reco [2016-09-19 18:21 +0300]:
[...]
> This line in /etc/sudoers works for me:
>
> Defaults passprompt_override,passprompt="ENTER NUCLEAR LAUNCH CODE:"
Try this:
Defaults passprompt_override,passprompt="^[[41;33;01mENTER NUCLEAR LAUNCH CODE:
^[[00m"
Elimar
--
"Talking much about onese
Hugo Vanwoerkom wrote:
> On 09/19/2016 10:21 AM, Reco wrote:
>> Defaults passprompt_override,passprompt="ENTER NUCLEAR LAUNCH CODE:"
>>
>> Of course you should use visudo, not edit /etc/sudoers directly.
> True. But I use mc, have done so for years and that seems to work. What
> am I endangerin
On 09/19/2016 10:21 AM, Reco wrote:
Hi.
On Mon, Sep 19, 2016 at 11:01:33AM -0400, Tony Baldwin wrote:
On 09/19/2016 10:25 AM, Reco wrote:
Hi.
On Mon, Sep 19, 2016 at 09:59:03AM -0400, Tony Baldwin wrote:
I had, on a prior machine, changed the password prompt for sudo by
On 09/19/2016 11:21 AM, Reco wrote:
Defaults passprompt_override,passprompt="ENTER NUCLEAR LAUNCH CODE:"
Thanks, this was exactly what I needed!
and I'll use visudo, of course.
Tony
--
http://tonybaldwin.me
all tony, all the time
Hi.
On Mon, Sep 19, 2016 at 11:01:33AM -0400, Tony Baldwin wrote:
> On 09/19/2016 10:25 AM, Reco wrote:
> > Hi.
> >
> >On Mon, Sep 19, 2016 at 09:59:03AM -0400, Tony Baldwin wrote:
> >>I had, on a prior machine, changed the password prompt for sudo b
On 09/19/2016 10:25 AM, Reco wrote:
Hi.
On Mon, Sep 19, 2016 at 09:59:03AM -0400, Tony Baldwin wrote:
I had, on a prior machine, changed the password prompt for sudo by adding
something (it was "ENTER NUCLEAR LAUNCH CODE:" in fact) to the sudoers file,
but at the moment
Hi.
On Mon, Sep 19, 2016 at 09:59:03AM -0400, Tony Baldwin wrote:
> I had, on a prior machine, changed the password prompt for sudo by adding
> something (it was "ENTER NUCLEAR LAUNCH CODE:" in fact) to the sudoers file,
> but at the moment I can not recall what/how I d
I had, on a prior machine, changed the password prompt for sudo by
adding something (it was "ENTER NUCLEAR LAUNCH CODE:" in fact) to the
sudoers file, but at the moment I can not recall what/how I did it, but
I'd like to do it again.
Anyone?
TIA
Tony
--
http://tonybaldwin.m
August Karlstrom:
> On 2015-09-27 14:40, Jochen Spieker wrote:
>>
>> That's a kernel message that is apparently considered important enough
>> to print it on all VTs, irrespective of their current content.
>
> OK, I see. Thanks for the info, Jochen. Still, I think it looks like a mess.
Sure, but
Quoting August Karlstrom (fusionf...@gmail.com):
> On 2015-09-27 14:40, Jochen Spieker wrote:
> >August Karlstrom:
> >>Today when I started my computer running Debian 8.2 the following error
> >>message was displayed at the login prompt (where the user name
1 - 100 of 633 matches
Mail list logo
