rc2 feedback (ostrolek)

Head_on_a_Stick · 2016-02-24 08:00:29

ostrolek wrote:

open@open:~$ su
Password: 
root@open:/home/open#

In a standard BunsenLabs installation (ie, performed from the installer on the ISO image), the root account is locked and the first user is automatically added to the "sudo" group.

You have either ran johnraff's script after a netinstall in which a root password was entered or installed by a non-standard method.

Or this is a user that has been added after installation and not added to the "sudo" group and the root account has been unlocked.

Please explain your installation process in detail.

nobody0 · 2016-02-24 11:00:44

Head_on_a_Stick wrote:

In a standard BunsenLabs installation (ie, performed from the installer on the ISO image), the root account is locked and the first user is automatically added to the "sudo" group.

It should, but it didn't for some reason, which I don't know. Looked for such problems in the net and found how to correct it. It appears to be a common problem. Anyway, all's well. It is installed in a 8GB usb 2.0 stick. Its taking ~2.4GB, so there's enough space for some work. Did some tweaks. https://forums.bunsenlabs.org/viewtopic … 786#p19786, https://forums.bunsenlabs.org/viewtopic … 800#p19800

The usb stick boots from my lappy's grub. Must think of a way to install a separate grub to the usb stick, so it'd boot in any computer, but that's another story/problem.

Head_on_a_Stick · 2016-02-24 18:49:35

ostrolek wrote:

Head_on_a_Stick wrote:
In a standard BunsenLabs installation (ie, performed from the installer on the ISO image), the root account is locked and the first user is automatically added to the "sudo" group.
It should, but it didn't for some reason, which I don't know.

OK, that sounds like a bug, thank you for reporting it.

ostrolek wrote:

It is installed in a 8GB usb 2.0 stick

How did you install the system to the USB stick?

Did you use the BunsenLabs rc2 ISO image installer, selected from the GRUB menu of the ISO image?

Or did you copy stuff over from the ISO image to the USB stick manually, as you outlined in this thread:
https://forums.bunsenlabs.org/viewtopic.php?id=727

nobody0 · 2016-02-24 22:14:21

Head_on_a_Stick wrote:

Or did you copy stuff over from the ISO image to the USB stick manually, as you outlined in this thread:
https://forums.bunsenlabs.org/viewtopic.php?id=727

I should've. I would've seen what's happening. Installers don't show everything to you.

pvsage · 2016-02-25 00:00:54

ostrolek wrote:

Head_on_a_Stick wrote:
Or did you copy stuff over from the ISO image to the USB stick manually, as you outlined in this thread:
https://forums.bunsenlabs.org/viewtopic.php?id=727
I should've. I would've seen what's happening. Installers don't show everything to you.

That doesn't answer Head_on_a_Stick's question; he asked what you did, not what you think you should have done instead.

Last edited by pvsage (2016-02-25 00:01:28)

Head_on_a_Stick · 2016-02-25 07:21:28

Also, how did you open the root account?

The standard installer asks for a user password rather than the root password, the latter is left unset to "lock" the root account.

Head_on_a_Stick · 2016-02-25 07:23:43

ostrolek wrote:

Installers don't show everything to you.

Use <Ctrl>+<Alt>+F4 to see the exact commands being run by the installer

iMBeCil · 2016-02-25 09:38:24

He probably went by netinstall route, but contrary to the BL instructions, entered root password in the netinstall ...

Happened to me, too, once.

As for the BL iso install, it works as expected: no root user, sudo works.

(Although: ostrloke's user account 'open' seems to be the same as his hostname - also 'open'. Is it possible that it could cause the problem for BL iso install?)

nobody0 · 2016-02-25 10:34:49

Head_on_a_Stick wrote:

Also, how did you open the root account?
The standard installer asks for a user password rather than the root password, the latter is left unset to "lock" the root account.

True. I only set the user password. Only, somehow something didn't get configured. This is a problem of the installer, not bunsenlabs. If you google "sudo: unable to resolve host" you'd find it is a common problem. I found the answer in the net, so learnt something too. BLRC2 in the USB stick is doing well.

Sector11 · 2016-02-25 15:57:53

iMBeCil wrote:

(Although: ostrloke's user account 'open' seems to be the same as his hostname - also 'open'. Is it possible that it could cause the problem for BL iso install?)

If you are talking:

sector11@bunsen
vs
sector11@sector11

It should make no difference .. I ran sector11@sector11 for years on #! - it started when I really didn't like sector11@ubuntu.

If that's not is -- OOPS! sorry.

Head_on_a_Stick · 2016-02-25 19:30:02

ostrolek wrote:

I only set the user password. Only, somehow something didn't get configured. This is a problem of the installer, not bunsenlabs.

So, did you use the installer that is loaded from the GRUB menu when a USB stick containing the BunsenLabs rc2 ISO image is booted?

Which command did you use to transfer the ISO image to the USB stick that was used to load the installer?

For the second time: how did you unlock the root account?

You say you only entered the user password but that this was not configured.

If that was the case, how did you log in to the system at all?

spacex · 2016-02-26 00:20:26

You guys have made me curious. I think I need to test the ISO

Just did. Great work, and to anyone wondering, I picked the same username as the hostname, "tweak@tweak", and it caused no issue at all. Root-account locked, tweak added to the sudo group, works fine as you can see:

tweak@tweak:~$ sudo apt-cache search linux-image
[sudo] password for tweak: 
linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64
linux-headers-4.3.0-0.bpo.1-amd64 - Header files for Linux 4.3.0-0.bpo.1-amd64
linux-image-4.3.0-0.bpo.1-amd64 - Linux 4.3 for 64-bit PCs
linux-image-4.3.0-0.bpo.1-amd64-dbg - Debugging symbols for Linux 4.3.0-0.bpo.1-amd64
tweak@tweak:~$

Last edited by spacex (2016-02-26 01:43:43)

iMBeCil · 2016-02-26 08:38:22

Sector11 wrote:

iMBeCil wrote:
(Although: ostrloke's user account 'open' seems to be the same as his hostname - also 'open'. Is it possible that it could cause the problem for BL iso install?)
If you are talking:
sector11@bunsen
vs
sector11@sector11
It should make no difference .. I ran sector11@sector11 for years on #! - it started when I really didn't like sector11@ubuntu.

Yes, tha's what I had in mind. Apparently, this doesn't cause ostrolek's trouble. Good that you have cleared that up Sector. I almost made a fresh install to test this

spacex · 2016-02-26 16:10:45

iMBeCil wrote:

Yes, tha's what I had in mind. Apparently, this doesn't cause ostrolek's trouble. Good that you have cleared that up Sector. I almost made a fresh install to test this

LOL; I actually made a fresh install to test this

nobody0 · 2016-02-26 18:59:06

^ Did you install it to a usb stick?

Head_on_a_Stick · 2016-02-26 19:31:35

@ostrolek: will you please answer my questions.

So, did you use the installer that is loaded from the GRUB menu when a USB stick containing the BunsenLabs rc2 ISO image is booted?
Which command did you use to transfer the ISO image to the USB stick that was used to load the installer?
For the second time: how did you unlock the root account?
You say you only entered the user password but that this was not configured.
If that was the case, how did you log in to the system at all?

If you don't wish to help track down this bug then please tell me.

Sector11 · 2016-02-26 21:27:04

iMBeCil wrote:

Sector11 wrote:
I ran sector11@sector11 for years on #!
Yes, tha's what I had in mind. Apparently, this doesn't cause ostrolek's trouble. Good that you have cleared that up Sector. I almost made a fresh install to test this

Well, if you ask the right questions and get the right answers it can save a lot of work.

nobody0 · 2016-02-26 21:28:12

^ I installed it to the usb stick the normal way. It was just an experiment. I'd keep it in the usb for some time. Like I wrote before, this is not a bunsenlabs bug, but a Debian bug. It had been this way for a long time.

It happens from time to time for lot of users, and it is so common, the answer is in the net. The first entry I "binged" is dated 2007-10-25. Its a random problem, and without a solution...yet.

Head_on_a_Stick · 2016-02-26 21:55:56

ostrolek wrote:

I installed it to the usb stick the normal way

What does "the normal way" mean?

Please explain how you transferred the ISO image to the USB stick.

Please explain how you directed the installer to install the system to your USB stick.

These are important details and knowing these facts will help greatly with the developement of BunsenLabs.

ostrolek wrote:

this is not a bunsenlabs bug, but a Debian bug. It had been this way for a long time.
http://s6.postimg.org/q20gm2qhp/Screenshot_3.jpg

The first link in that screenshot is this:
http://forums.debian.net/viewtopic.php?t=20647

As you can see, it has *nothing* to do with the Debian installer...

ostrolek wrote:

It happens from time to time for lot of users, and it is so common, the answer is in the net. The first entry I "binged" is dated 2007-10-25. Its a random problem, and without a solution...yet.

Please provide some links to this "common bug" and explain it better.

As far as I can understand from your feedback, the user is not added to the sudo group and the root account is locked -- is that correct?

If this is your assertion then that is not the sort of bug that is just left unsolved -- the user would not be able to do anything at all without unlocking the root account!

For the record, I have used the standard Debian installer on USB stick systems several times without this problem.

nobody0 · 2016-02-26 22:51:39

I think, I found the problem here, that is, your questions. https://forums.bunsenlabs.org/viewtopic … 824#p19824
You are asking questions around this,

open@open:~$ su
Password:
root@open:/home/open#

How did this root@open came by?
All I wanted was to open some app as root. So, it is either sudo or su. Sudo didn't work, but su worked. A long time ago, Arch was using only su, not sudo. Many other Linux distros did the same. So, I remembered and wrote su. That's all.

Then, it became a headache not to have sudo, while it was installed, I "googled" the problem and got the answer. And, as soon as I found it, I posted it. Now, I'm "binging," rather than "googling" and playing with my new system--that usb stick would be retired at least for few weeks. I like being a noob for while.

BTW, one question was not answered from the #1

@johnraff
If Synaptic Package Manager is installed, does offering to install some apps through pipe-menus has any real value as Synaptic offers to install any app in the repos, whatever the repos?

Last edited by nobody0 (2016-02-26 22:52:17)

#21 2016-02-24 08:00:29

Re: rc2 feedback (ostrolek)

#22 2016-02-24 11:00:44

Re: rc2 feedback (ostrolek)

#23 2016-02-24 18:49:35

Re: rc2 feedback (ostrolek)

#24 2016-02-24 22:14:21

Re: rc2 feedback (ostrolek)

#25 2016-02-25 00:00:54

Re: rc2 feedback (ostrolek)

#26 2016-02-25 07:21:28

Re: rc2 feedback (ostrolek)

#27 2016-02-25 07:23:43

Re: rc2 feedback (ostrolek)

#28 2016-02-25 09:38:24

Re: rc2 feedback (ostrolek)

#29 2016-02-25 10:34:49

Re: rc2 feedback (ostrolek)

#30 2016-02-25 15:57:53

Re: rc2 feedback (ostrolek)

#31 2016-02-25 19:30:02

Re: rc2 feedback (ostrolek)

#32 2016-02-26 00:20:26

Re: rc2 feedback (ostrolek)

#33 2016-02-26 08:38:22

Re: rc2 feedback (ostrolek)

#34 2016-02-26 16:10:45

Re: rc2 feedback (ostrolek)

#35 2016-02-26 18:59:06

Re: rc2 feedback (ostrolek)

#36 2016-02-26 19:31:35

Re: rc2 feedback (ostrolek)

#37 2016-02-26 21:27:04

Re: rc2 feedback (ostrolek)

#38 2016-02-26 21:28:12

Re: rc2 feedback (ostrolek)

#39 2016-02-26 21:55:56

Re: rc2 feedback (ostrolek)

#40 2016-02-26 22:51:39

Re: rc2 feedback (ostrolek)

Board footer