Re: Boot Problem

Stephen P. Molnar composed on 2023-12-05 13:33 (UTC-0500): > I decided to try something. I logged in to the rescue  mode as root and > entered startx at the prompt. This generated the error: I believe if xserver-xorg-legacy is not installed that startx failure is expected. I keep it installed o

Re: Boot Problem

Please forgive me if I somehow messed up the quote attribution. There was a lot of stuff I was able to cull. :) On 12/5/23, David Christensen wrote: > On 12/5/23 10:33, Stephen P. Molnar wrote: > > I decided to try something. I logged in to the rescue mode as root and > > entered startx at the

Re: Boot Problem

On 5 Dec 2023 11:05 -0500, from s.mol...@sbcglobal.net (Stephen P. Molnar): > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back tot he > login screen, over and over and . I got the same resul

Re: Boot Problem

On 12/5/23 08:05, Stephen P. Molnar wrote: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than opening my XFCE desktop I was sent back tot he login screen, over and over and . I got the same result attempting to login as root. I ha

Re: Boot Problem

My Os is up to date and running the version XFCE4 I've attached the log files that i could find. I hope that it will help. On 12/05/2023 02:26 PM, Alexander V. Makartsev wrote: On 05.12.2023 23:33, Stephen P. Molnar wrote: I decided to try something. I logged in to the rescue  mode as root an

Re: Boot Problem

Am Dienstag, 5. Dezember 2023, 18:56:48 CET schrieb Stephen P. Molnar: Not good! You have to start startx from the shell. However, when you see the login screen (gdm, lightdm, kdm, whatever), that means, the X-server is running and ok. So you have a problem with XFCE. Look at ~/.config/xfce4 an

Re: Boot Problem

On 05.12.2023 23:33, Stephen P. Molnar wrote: I decided to try something. I logged in to the rescue  mode as root and entered startx at the prompt. This generated the error: Unable to contact settings server failed to execute child process "dbus-launch" (No such file or directory) I vaguely re

Re: Boot Problem

I decided to try something. I logged in to the rescue  mode as root and entered startx at the prompt. This generated the error: Unable to contact settings server failed to execute child process "dbus-launch" (No such file or directory) On 12/05/2023 01:03 PM, Tom Furie wrote: "Stephen P. Moln

Re: Boot Problem

"Stephen P. Molnar" writes: > On 12/05/2023 12:47 PM, Tom Furie wrote: >> "Stephen P. Molnar" writes: >> >>> I have Bookworm installed on a 1TB SSD. When I attempted logging this >>> morning I failed! Rather than opening my XFCE desktop I was sent back >>> tot he login screen, over and over and

Re: Boot Problem

I've attached the log. I hope that someone can tell me what the problem is. Thanks inn advance. On 12/05/2023 11:59 AM, Joe wrote: On Tue, 5 Dec 2023 11:05:15 -0500 "Stephen P. Molnar" wrote: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than

Re: Boot Problem

Xfce4 graphical login screen On 12/05/2023 12:47 PM, Tom Furie wrote: "Stephen P. Molnar" writes: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than opening my XFCE desktop I was sent back tot he login screen, over and over and ...

Re: Boot Problem

"Stephen P. Molnar" writes: > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back > tot he login screen, over and over and . I got the When you say "back to the login screen", do you mean ba

Re: Boot Problem

On Tue, 5 Dec 2023 11:05:15 -0500 "Stephen P. Molnar" wrote: > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back > tot he login screen, over and over and . I got the > same result attempt

Re: Boot Problem

Am Dienstag, 5. Dezember 2023, 17:05:15 CET schrieb Stephen P. Molnar: To get closer to the cause, I suggest to remove temporaryly any loginmamanger out of the way Either /usr/bin/xdm, /usr/bin/kdm, /usr/bin/gdm or /usr/bin/ xdm, whatever. Copy it somewhere, i.e. to /root Then reboot and from th

Boot Problem

I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than opening my XFCE desktop I was sent back tot he login screen, over and over and . I got the same result attempting to login as root. I have to assume that grub has been corrupted>

Re: RPI boot problem (some OT) [solved]

On 8/10/19 11:19 AM, ghe wrote: Fixed. I did a few things differently, and it came up: I verified the NOOBS file with sha256 (match). I unzipped directly to the SD chip. I moved the HDMI connector to the one toward the back. Even though I saw nothing in any dox about it making any difference, I'

Re: RPI boot problem (some OT)

ghe wrote: > I know this isn't the best place to talk about Raspberry Pis, but there > are people here who are familiar with them, and probably people who can > point me to the correct place. And they do run Debian... I don't have that modern RPI, but usually there are ready images to use. Did yo

RPI boot problem (some OT)

I know this isn't the best place to talk about Raspberry Pis, but there are people here who are familiar with them, and probably people who can point me to the correct place. And they do run Debian... My 2G RPi4 arrived yesterday, and it doesn't boot, not all the way anyway. The red power led goes

Re: Boot Problem

Le 16/06/2019 à 15:53, Stephen P. Molnar a écrit : I have just installed a new SSD in my 64 bit Stretch platform. When I boot the machine I get the following error: error: file '/boot/grub/i386-pc/normalmod' not found Entering rescue mode .. . . grub rescue>_ Pressing Contro-Alt-Delete reboots

Re: Boot Problem

In-Reply-To: <5d0649da.40...@sbcglobal.net> On Sun, 16 Jun 2019, Stephen P. Molnar wrote: > > On 06/16/2019 12:16 PM, bw wrote: > > In-Reply-To: <5d0649da.40...@sbcglobal.net> > > > Stephen P. Molnar, Ph.D. says... > > > I have just installed a new SSD in my 64 bit Stretch platform. > > > > > >

Re: Boot Problem

On 6/16/19 6:53 AM, Stephen P. Molnar wrote: I have just installed a new SSD in my 64 bit Stretch platform. When I boot the machine I get the following error: error: file '/boot/grub/i386-pc/normalmod' not found Entering rescue mode .. . . grub rescue>_ Pressing Contro-Alt-Delete reboots the s

Re: Boot Problem

Stephen P. Molnar wrote: > I have just installed a new SSD in my 64 bit Stretch platform. what do you mean by "installed"? there is a lot of difference between plugging it in vs. plugging it in and putting something on it. what did you do? give details. we don't know what you did nor c

Re: Boot Problem

In-Reply-To: <5d0649da.40...@sbcglobal.net> >Stephen P. Molnar, Ph.D. says... >I have just installed a new SSD in my 64 bit Stretch platform. > >When I boot the machine I get the following error: > >error: file '/boot/grub/i386-pc/normalmod' not found >Entering rescue mode .. . . >grub rescue>_ > >

Boot Problem

I have just installed a new SSD in my 64 bit Stretch platform. When I boot the machine I get the following error: error: file '/boot/grub/i386-pc/normalmod' not found Entering rescue mode .. . . grub rescue>_ Pressing Contro-Alt-Delete reboots the system. Pressing Delete , or F-8,during the p

Re: boot problem after updating dropbear [solved -- MANUAL initrd works required]

Hi, Okay, it turns out that the only files that were missing were ones that I had in the /etc/initramfs-tools/root/ directory. The only files in the faulty initrd image were from the /etc/initramfs-tools/root/.ssh/ directory, so missing .profile and other required files. I modified the initr

boot problem after updating dropbear

Hi, After dropbear update as follows: < ii dropbear 2012.55-1.3 amd64lightweight SSH2 server and client --- > ii dropbear 2012.55-1.3+deb7u1 amd64lightweight SSH2 server and client Debian Version 7.11 (Wheezy) Before th

Re: boot problem

Hi, you can open the Terminal and type: # grub-install /dev/sda1 And # update-grub2 This will do what you need. Em 06-03-2016 03:55, lina escreveu: > Hi, > > After install the debian, > > it goes to debian OS system directly, without showing me the option of > start Mac OS or debian OS. > > Any

Re: boot problem

g quicker. And you will get a menu. Original Message From: lina Sent: Mon Mar 07 01:01:31 AEDT 2016 To: Keith Bainbridge Cc: Debian Lists Subject: Re: boot problem df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 641M 235M 360M 40% / udev

Re: boot problem

T 2016 > To: Debian Lists > Subject: boot problem > > Hi, > > After install the debian, > > it goes to debian OS system directly, without showing me the option of > start Mac OS or debian OS. > > Any suggestions, thanks, > > > Keith Bainbridge > > 0447 667 468 > > keithrbaugro...@gmail.com > > Sent from my APad

Re: boot problem

Good afternoon Lina Try holding the alt key as you boot. You should get a few icons to choose osx or linux. If not, please send us output of command df -h Original Message From: lina Sent: Sun Mar 06 17:55:17 AEDT 2016 To: Debian Lists Subject: boot problem Hi, After

boot problem

Hi, After install the debian, it goes to debian OS system directly, without showing me the option of start Mac OS or debian OS. Any suggestions, thanks,

Re: bewildering boot problem -- a little more info

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 05, 2015 at 11:05:20PM -0600, Glenn English wrote: [...] > > Hmmm. Sorry to be so unspecific. > > No prob. Everybody's happy now. I just have some data to copy over from the > old disk. At least it wasn't the hardware... In any case, g

Re: bewildering boot problem -- a little more info

On Oct 5, 2015, at 12:51 PM, Felix Miata wrote: > Do you have an entry in /etc/hosts matching your actual IP to the content in > /etc/hostname when you observe this delay? Yup. I rely on the host files, so I keep then correct and accurate. -- Glenn English

Re: bewildering boot problem

On Oct 5, 2015, at 12:45 PM, rlhar...@oplink.net wrote: > On Mon, October 5, 2015 12:53 pm, Glenn English wrote: >> Maybe it's hardware... It wasn't. A new install fixed everything. > Have you had a lightning storm in the area recently? Yeah. That's common in Colorado. > And is everything

Re: bewildering boot problem -- a little more info

On Oct 5, 2015, at 11:53 AM, to...@tuxteam.de wrote: > Hmm. Weird. I dimly remember that tcpwrappers did something > similar: to check the host name they sometimes tried a > reverse host lookup, which took its time when it failed. I've never seen or heard of anything like this -- the kernel comp

Re: bewildering boot problem -- a little more info

Glenn English composed on 2015-10-04 18:14 (UTC-0600): > I disabled XDM (sure is nice to have text config files) and rebooted. It > came up at a regular login prompt, and no error messages. startx took a > *very* long time -- said it couldn't find the hostname (something like > that) -- but it eve

Re: bewildering boot problem

On Mon, October 5, 2015 12:53 pm, Glenn English wrote: > It seems to me that there's a networking problem, but > intermittent and from several directions. I don't understand it at all. > > Maybe it's hardware... Have you had a lightning storm in the area recently? And is everything connected to t

Re: bewildering boot problem -- a little more info

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 05, 2015 at 11:53:06AM -0600, Glenn English wrote: > > On Oct 5, 2015, at 1:04 AM, to...@tuxteam.de wrote: > > > Then try "ssh @localhost". > > Works, kinda. It does the same thing to localhost or the hostname, from the > console or fro

Re: bewildering boot problem -- a little more info

On Oct 5, 2015, at 1:04 AM, to...@tuxteam.de wrote: > Then try "ssh @localhost". Works, kinda. It does the same thing to localhost or the hostname, from the console or from a terminal in XFCE. (I've got SSH running with keys around the local net(s) (no login required)). The MOTD comes up right

Re: bewildering boot problem -- a little more info

On Oct 5, 2015, at 1:04 AM, wrote: > All those 30-ish seconds timeout and the error message you mention > above smell of something trying to resolve a host name, failing > and giving up (timeout). Yup. The timeouts do, anyway. The error messages from the kernel when I start XFCE never time ou

Re: bewildering boot problem -- a little more info

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 04, 2015 at 06:14:44PM -0600, Glenn English wrote: > I disabled XDM (sure is nice to have text config files) and rebooted. It came > up at a regular login prompt, and no error messages. startx took a *very* > long time -- said it couldn't

Re: bewildering boot problem

In reply to Glenn English : Inasmuch as you are running Xfce, is there any particular reason for staying with Wheezy, which was the release which introduced the new Gnome? If not, the investment of two or three hours should have you up and running in Jessie. I have had opportunity to install Jes

bewildering boot problem -- a little more info

I disabled XDM (sure is nice to have text config files) and rebooted. It came up at a regular login prompt, and no error messages. startx took a *very* long time -- said it couldn't find the hostname (something like that) -- but it eventually started XFCE. And the messages were back. Something

bewildering boot problem

A few hours ago, my laptop (after booting Wheezy) started saying that it was trying to load a module for a network interface (CAP_SYS_MODULE) that was deprecated -- I should use CAP_NET_ADMIN instead. I'm configuring an old Cicso router using Putty to get to the RS232 port on the router -- tha

LVM boot problem

Hello, I boot my virtal machines from LVM and one of them has boot problems. Sometimes it boots fine, but 3 out of 4 times I get systemd messages about start jobs running. After some timeouts I see: (1 of 2) A start job is running for Activation of LV... 9s / no limit) Because everything is on

semi-random boot problem

Hello all, I've a problem within the initrd, *sometime* it fail to mount the root directory and after a while it fall back to the shell. My guess is a timing issue, the ssd disk "attach" before some process (udev?) is listening for disk events, but it is only a guess. I recently added an ssd disk

Re: Weird boot problem. How can this be?

On Sat, Nov 09, 2013 at 09:49:57AM -0800, Ray Dillinger wrote: > On 11/09/2013 06:08 AM, didier gaumet wrote: > > >>The machine is an Asus Sabertooth X79 motherboard, IA64 "Sandy Bridge" > >>architecture, > >[...] > > > >On the Asus website, this is not an IA64 motherboard, but a X86-64 > >(amd64)

Re: Weird boot problem. How can this be?

Le 09.11.2013 09:26, Ray Dillinger a écrit : I have a strange problem where my computer does not recognize *ANY* boot device or boot medium other than one single hard drive where a badly configured debian linux is installed. I don't think the particulars of that messed-up install are relevant,

Re: Weird boot problem. How can this be?

On 11/09/2013 06:08 AM, didier gaumet wrote: The machine is an Asus Sabertooth X79 motherboard, IA64 "Sandy Bridge" architecture, [...] On the Asus website, this is not an IA64 motherboard, but a X86-64 (amd64) one. Trying an amd64 version of Debian could help... On the ASUS website the boar

Re: Weird boot problem. How can this be?

Le 09/11/2013 09:26, Ray Dillinger a écrit : [...] > I don't understand how it can possibly happen, because I have completely > unplugged > that hard drive, flashed the BIOS of the machine with the most recent > update [...] Asus website says that Bios rev <= 1203 needs to be converted by an utili

Re: Weird boot problem. How can this be?

Okay, your bios settings are messed up on that computer. You need to go into bios settings and give them some clues about what's actually on the computer in terms of hardware. The bios settings on your machine have lost their mind somehow. On Sat, 9 Nov 2013, Ray Dillinger wrote: > > I have

Weird boot problem. How can this be?

I have a strange problem where my computer does not recognize *ANY* boot device or boot medium other than one single hard drive where a badly configured debian linux is installed. I don't think the particulars of that messed-up install are relevant, but I've put a note about it at the bottom jus

Re: Debian wheezy boot problem - Boot sector not identified by board

. and > it worked fine.. > Any hint on what might be going on ? Did you check if it isn't a "Secure Boot" problem? If you have UEFI instead of BIOS, try finding something like Boot Mode -> Legacy/Secure in UEFI setup and set it to Legacy. -- http://mr

RE: Debian wheezy boot problem - Boot sector not identified by board

for future reference if anyone faced this issue.disabling "EFI" in bios settings and initiating a clean install does the trick. From: r_o_l_a_...@hotmail.com To: debian-user@lists.debian.org Subject: Debian wheezy boot problem - Boot sector not identified by board Date: Mon, 7 Oct 201

Re: Debian wheezy boot problem - Boot sector not identified by board

Le 07.10.2013 09:54, Roland RoLaNd a écrit : All, I have an intel dh77kc board. it previously had windows 7 installed on it. i tried installing debian wheezy net install. installation goes perfectly fine up untill reboot. once reboot is done, i get " Initializing and establishing link" and imm

Re: Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at "Switching to clocksource tsc" )

Le 06.10.2013 18:34, Curt a écrit : On 2013-10-06, berenger.mo...@neutralite.org wrote: Any idea about how to be able to run terminal stuff correctly in recovery mode? Maybe changing the terminal (if so, how could I do that?)? export TERM=linux says google Thanks. But, this line does o

Debian wheezy boot problem - Boot sector not identified by board

All, I have an intel dh77kc board. it previously had windows 7 installed on it.i tried installing debian wheezy net install. installation goes perfectly fine up untill reboot.once reboot is done, i get " Initializing and establishing link" and immediately goes into network bootI tried resetting

Re: Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at "Switching to clocksource tsc" )

On 2013-10-06, berenger.mo...@neutralite.org wrote: > > Any idea about how to be able to run terminal stuff correctly in > recovery mode? Maybe changing the terminal (if so, how could I do > that?)? > export TERM=linux says google -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debia

Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at "Switching to clocksource tsc" )

Le 05.10.2013 14:54, berenger.mo...@neutralite.org a écrit : Hi. Since my last kernel update my desktop can not boot anymore, it is stuck at "Switching to clocksource tsc". Also, nothing at all reply, even the keyboard does just nothing. Of course, I was stupid enough to remove the last kernel w

boot problem: stuck at "Switching to clocksource tsc"

Hi. Since my last kernel update my desktop can not boot anymore, it is stuck at "Switching to clocksource tsc". Also, nothing at all reply, even the keyboard does just nothing. Of course, I was stupid enough to remove the last kernel without testing it, and I have no idea about what is wrong.

Re: Boot problem : Operating System not found.

On Sat, 17 Mar 2012 18:30:51 +0100, Bruno Costacurta wrote: Bruno, you MUA is somehow deleting both "References:" and "In-Reply-To:" header fields and thus your posts are kept unthreaded. > [snip] >> I'll also try the SuperGrub2Disk ASAP. > [snip] > > Yes, it works when booting using a SuperGru

Re: Boot problem : Operating System not found.

[snip] I'll also try the SuperGrub2Disk ASAP. [snip] Yes, it works when booting using a SuperGrub2Disk CD. From SuperGrub2Disk boot menu : Detect any OS -> Debian correctly found on /dev/sda4 -> boot is OK. So I suppose the GRUB on the hard disk is incorrectly setup. As the boot-info script r

Re: Boot problem : Operating System not found

On Fri, 16 Mar 2012 20:52:37 +, luizlmarins hotmail.com wrote: (please, no html... thanks) > See here: > > http://linuxmeu.wordpress.com/grub-nao-aparece/ But GRUB does appear in this case. What happens is that it hangs when booting Debian. Greetings, -- Camaleón -- To UNSUBSCRIBE,

Re: Boot problem : Operating System not found.

It would've been helpful not to have snipped the "drive partition info" section! :) You have a gpt-labelled disk but sda1 isn't OK. As "File system", it should have "BIOS Boot partition". "Boot sector type" and "Boot sector info" cannot be right but I don't know what they should be. The two

Re: Boot problem : Operating System not found.

On Fri, Mar 16, 2012 at 3:13 PM, Bruno Costacurta wrote: > >  => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector >    946507840 of the same hard drive for core.img. core.img is at this >    location and looks for  on this drive. > ... > sda1: > >    File system:       vfat >

Re: Boot problem : Operating System not found.

'Operating System not found' is displayed once boot via GRUB command line. [snip] What's the output of bootinfoscript? [snip] So I ran boot_info_script.sh. Which returns the following (snipped to mainly show /dev/sda4 on which Debian is installed) : Boot Info Script 0.60from 17 May

Re: Boot problem : Operating System not found (was : how to make it verbose ?)

On Thu, 15 Mar 2012 19:55:39 +0100, Bruno Costacurta wrote: > .. >> Another thing you can test is manually booting your Debian system from >> GRUB2 boot menu by reaching the command line. This way if you're lucky >> any error you get will be printed on the screen. > .. > > Indeed you're right. >

Re: Boot problem : Operating System not found (was : how to make it verbose ?)

On Thu, Mar 15, 2012 at 2:55 PM, Bruno Costacurta wrote: >> >> Another thing you can test is manually booting your Debian system from >> GRUB2 boot menu by reaching the command line. This way if you're lucky >> any error you get will be printed on the screen. > > Indeed you're right. > 'Operating

Boot problem : Operating System not found (was : how to make it verbose ?)

.. Another thing you can test is manually booting your Debian system from GRUB2 boot menu by reaching the command line. This way if you're lucky any error you get will be printed on the screen. .. Indeed you're right. 'Operating System not found' is displayed once boot via GRUB command line. I

Re: Boot problem : how to make it verbose ?

On Wed, 14 Mar 2012 20:48:03 +0100, Bruno Costacurta wrote: >>> I installed Debian Squeeze on a multi-boot PC where Ubuntu is the >>> first and bootable distro. >> Are you chainloading GRUB2s or are you loading Debian directly from >> Ubuntu's own GRUB2 version? > > I boot direclt from the Ubuntu

Re: Boot problem : how to make it verbose ?

On Wed 14 Mar 2012 at 20:48:03 +0100, Bruno Costacurta wrote: > Yes, the GRUB2 menu is reached (in fact, it's used to boot the other > system on same PC). The Debian system hangs direcly. Nothing is > displayed. > Yes, a LiveCD Debian 6 works fine (however it was a i386, the installed > Debia

Re: Boot problem : how to make it verbose ?

I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first and bootable distro. Are you chainloading GRUB2s or are you loading Debian directly from Ubuntu's own GRUB2 version? I boot direclt from the Ubuntu's own GRUB2 version. Using GRUB2, the options 'nosplash debug --verbose

Re: Boot problem : how to make it verbose ?

On Wed, 14 Mar 2012 11:06:04 +0100, Bruno Costacurta wrote: > I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first > and bootable distro. Are you chainloading GRUB2s or are you loading Debian directly from Ubuntu's own GRUB2 version? > Using GRUB2, the options 'nosplash debug

Re: Boot problem : how to make it verbose ?

On Wed 14 Mar 2012 at 11:06:04 +0100, Bruno Costacurta wrote: > I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first > and bootable distro. > Using GRUB2, the options 'nosplash debug --verbose' are used, but Debian > freezes silently. > How to make boot verbose to see what hap

Boot problem : how to make it verbose ?

Hello, I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first and bootable distro. Using GRUB2, the options 'nosplash debug --verbose' are used, but Debian freezes silently. How to make boot verbose to see what happen ? Hereafter the /boot/grub/grub.cfg : menuentry "test

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Arno: >> Thank You for Your time and answer, Arno: >> >> > a) locking the root account (passwd -l root), which will give you >> > "sulogin: root account is locked, starting shell" >> >> That's the point - sudo is used on the system and the root account is

Re: Passwordless root shell is offered when boot problem occurs.

Sthu Deus (sthu.d...@gmail.com on 2011-12-06 01:18 +0700): > Thank You for Your time and answer, Arno: > > > a) locking the root account (passwd -l root), which will give you > > "sulogin: root account is locked, starting shell" > > That's the point - sudo is used on the system and the root

Re: Passwordless root shell is offered when boot problem occurs.

On Lu, 28 nov 11, 13:47:59, Sthu Deus wrote: > Good time of the day. > > Once mount error occurs while OS booting, I get root shell - w/o even > asking for password... How I can change the behavior (to ask for > password before granting root shell)? Hi Sthu, From reading the thread I understand

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Arno: > a) locking the root account (passwd -l root), which will give you > "sulogin: root account is locked, starting shell" That's the point - sudo is used on the system and the root account is blocked. So, what's the strategy to protect systems in such

Re: Passwordless root shell is offered when boot problem occurs.

On Fri, 02 Dec 2011 14:04:15 +0700, Sthu Deus wrote: > Thank You for Your time and answer, Camaleón: > You mean "Busybox"? :-? >>> >>> I do not know - it appears when something wrong during boot process. >> >>It should be printed out, something like: >> >>*** >>BusyBox v1.10.2 (Debian x-x-x-

Re: Passwordless root shell is offered when boot problem occurs.

Sthu Deus (sthu.d...@gmail.com on 2011-12-03 17:53 +0700): > >[..] A standard Debian config > >should not offer a passwordless root shell unless you explicitly ask > >for it, > > Oh, no! I didn't! :) > > Do You have an idea where to look for that? - I have no ideas, > absolutely. Just as a point

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Joel: >Recently had fun with Fedora, when it didn't like the way I specified >my HDs, it would drop me into the ctrl-d prompt, but I couldn't go >anywhere beyond that. Any key I pressed, including ctrl-d, would cycle >me another ctrl-d prompt. When I had the pr

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Arno: >> Hmm. I thought everybody has the same OS behavior in such >> condition... And the problem here is only improper/default >> configuration. > >That could very well be, but I haven't had a boot problem in years >(well, ex

Re: Passwordless root shell is offered when boot problem occurs.

havior in such condition... > And the problem here is only improper/default configuration. That could very well be, but I haven't had a boot problem in years (well, except when trying out systemd). A standard Debian config should not offer a passwordless root shell unless you explicitly ask

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Arno: >From here it's all guesswork. You'd need to provide a full bootlog up >to the point where the shell is started to get any meaningful answers. Hmm. I thought everybody has the same OS behavior in such condition... And the problem here is only improper/def

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Camaleón: >>>You mean "Busybox"? :-? >> >> I do not know - it appears when something wrong during boot process. > >It should be printed out, something like: > >*** >BusyBox v1.10.2 (Debian x-x-x-x) Built-in shell (xxx) >*** Oh, no. It's not my case. Nor I have

Re: Passwordless root shell is offered when boot problem occurs.

Sthu Deus (sthu.d...@gmail.com on 2011-12-01 23:54 +0700): > > >fsck errors should drop into a sulogin shell, which asks for the > >password. The only way you could get a root shell is if your root > >device cannot be found. In that case, there is no way to ask for a > >password because there is n

Re: Passwordless root shell is offered when boot problem occurs.

On Thu, 01 Dec 2011 23:49:00 +0700, Sthu Deus wrote: > Thank You for Your time and answer, Camaleón: > >>> Once mount error occurs while OS booting, I get root shell - w/o even >>> asking for password... >> >>You mean "Busybox"? :-? > > I do not know - it appears when something wrong during boot

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Arno: >> Once mount error occurs while OS booting, I get root shell - w/o even >> asking for password... How I can change the behavior (to ask for >> password before granting root shell)? >> > >Do you get a message 'root account locked, starting shell?' No. >

Re: Passwordless root shell is offered when boot problem occurs.

Thank You for Your time and answer, Camaleón: >> Once mount error occurs while OS booting, I get root shell - w/o even >> asking for password... > >You mean "Busybox"? :-? I do not know - it appears when something wrong during boot process. >> How I can change the behavior (to ask for password

Re: Passwordless root shell is offered when boot problem occurs.

Sthu Deus (sthu.d...@gmail.com on 2011-11-28 13:47 +0700): > Once mount error occurs while OS booting, I get root shell - w/o even > asking for password... How I can change the behavior (to ask for > password before granting root shell)? > Do you get a message 'root account locked, starting shell

Re: Passwordless root shell is offered when boot problem occurs.

On Mon, 28 Nov 2011 13:47:59 +0700, Sthu Deus wrote: > Once mount error occurs while OS booting, I get root shell - w/o even > asking for password... You mean "Busybox"? :-? > How I can change the behavior (to ask for password before granting root > shell)? If you refer to busybox, AFAIK is no

Passwordless root shell is offered when boot problem occurs.

Good time of the day. Once mount error occurs while OS booting, I get root shell - w/o even asking for password... How I can change the behavior (to ask for password before granting root shell)? Thanks for Your time. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a su

Re: Debian 6 iSCSI root boot problem

On 9/14/2011 10:39 AM, Andrés Durán wrote: Hello to all, and sorry for may bad english, i'm Spanish. I'm trying to install Debian 6 on one server without internal disks, I have a Workstation running Debian 6 too that run as an iSCSI Target. This work station is configured as iSCSI targ

Debian 6 iSCSI root boot problem

Hello to all, and sorry for may bad english, i'm Spanish. I'm trying to install Debian 6 on one server without internal disks, I have a Workstation running Debian 6 too that run as an iSCSI Target. This work station is configured as iSCSI target with the package iscsitarget, it is runni

Debian 6 iSCSI root boot problem

Hello to all, and sorry for may bad english, i'm Spanish. I'm trying to install Debian 6 on one server without internal disks, I have a Workstation running Debian 6 too that run as an iSCSI Target. This work station is configured as iSCSI target with the package iscsitarget, it is runni

apt pinning (Re: Boot problem after crashed update)

Javier Barroso (javibarr...@gmail.com on 2011-05-12 19:11 +0200): > > Other possible solution would be pinning all packages from sid to > their current version (upgrading glibc with the bug, of course), and > removing sid from sources.list, and again wait, but this time you > could upgrade your sys

Re: Boot problem after crashed update

On Thu, May 12, 2011 at 8:35 PM, Jochen Schulz wrote: > Javier Barroso: >> >> So, why not, simply wait one month without upgrading, remove sid from >> your sources.list (and keep only wheezy), and then aptitude update; >> aptitude safe-upgrade; aptitude full-upgrade ? > > Because the OP would stil

Re: Boot problem after crashed update

12/05/2011 14:59, Simon Hoerder wrote: > Jochen Schulz wrote: > [...] >> Since you still have a bootable operating system, you may try the hint >> at . > > After taking a second look at Sven's link after lunch I discovered > similar hints

Re: Boot problem after crashed update

Javier Barroso: > > So, why not, simply wait one month without upgrading, remove sid from > your sources.list (and keep only wheezy), and then aptitude update; > aptitude safe-upgrade; aptitude full-upgrade ? Because the OP would still run some kind of more or less mixed wheezy/sid system even th

  1   2   3   4   >