Hi,
I have just posted the text only version of my Debian Etch Installation Report to the wiki. It's available here:
http://db.glug-bom.org/wiki/index.php/Debian_Etch_Installation_Report
I have taken lots of screenshots and I'll post them tomorrow. The installer has a handy facility for taking screenshots if you're curious.
Also, I found a MAJOR security bug with respect to the sudo integration. I enabled it and found that root login with a blank password was possible. I haven't tried updating the system yet. If the bug persists, I'll report it.
Cheers.
On 2/28/07, Mrugesh Karnik mrugeshkarnik@gmail.com wrote:
I have just posted the text only version of my Debian Etch Installation Report to the wiki. It's available here:
http://db.glug-bom.org/wiki/index.php/Debian_Etch_Installation_Report
Cool. I've linked it in the Howto section. Wiki-admins, does it belong there or do we make another section for installation reports?
On 2/28/07, Siddhesh Poyarekar siddhesh.poyarekar@gmail.com wrote:
On 2/28/07, Mrugesh Karnik mrugeshkarnik@gmail.com wrote:
I have just posted the text only version of my Debian Etch Installation Report to the wiki. It's available here:
http://db.glug-bom.org/wiki/index.php/Debian_Etch_Installation_Report
Cool. I've linked it in the Howto section. Wiki-admins, does it belong there or do we make another section for installation reports?
Ok, a little Oops moment right there. There is a link in the reviews section. Oddly, I didn't get the bread-crumbs on top of the article which led me to think that it's not linked.
Link removed from the Howtos section. Wiki-admins please ignore the previous appeal for guidance ;)
On 2/27/07, Mrugesh Karnik mrugeshkarnik@gmail.com wrote:
Also, I found a MAJOR security bug with respect to the sudo integration. I enabled it and found that root login with a blank password was possible. I haven't tried updating the system yet. If the bug persists, I'll report it.
Are you talking about following bugs?
http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=388003
http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=400766
Which installer did you use? (rc 1?)
RC-2 installer will be available soon. (The current daily has that afaik.)
On Wed, 28 Feb 2007 00:59:06 +0530, Mrugesh Karnik said:
Also, I found a MAJOR security bug with respect to the sudo integration. I enabled it and found that root login with a blank password was possible. I haven't tried updating the system yet. If the bug persists, I'll report it.
I did not see a bug filed about this for the installer, so I took the liberty of forwarding this to the debian installer leads, Frans Pop and Joeyh Hess. They agreedd that if this is the case, then this is a huge bug; but so far none of the testors has reported anything similar.
However, we are now trying to reproduce this bug, and investigating how it happened. On repeated testing, we can't reproduce the passwordless root account. Frans Pop says he gets a "!" in the /etc/shadow file, which means login disabled.
http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=388003 http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=400766
have been fixed in the latest installers (use the daily installer build to get the fixed versions)
Is there any additional information you can provide us, on how to reproduce the passwordless root account, and the crashes? A formal installtion report via reportbug would be much appreciated, preferably with the latest daily build of the installer, and a sequence of steps to follow to reproduce it.
manoj
On Wednesday 28 Feb 2007 02:52:08 Manoj Srivastava wrote:
On Wed, 28 Feb 2007 00:59:06 +0530, Mrugesh Karnik said:
Also, I found a MAJOR security bug with respect to the sudo integration. I enabled it and found that root login with a blank password was possible. I haven't tried updating the system yet. If the bug persists, I'll report it.
I did not see a bug filed about this for the installer, so I
took the liberty of forwarding this to the debian installer leads, Frans Pop and Joeyh Hess. They agreedd that if this is the case, then this is a huge bug; but so far none of the testors has reported anything similar.
However, we are now trying to reproduce this bug, and
investigating how it happened. On repeated testing, we can't reproduce the passwordless root account. Frans Pop says he gets a "!" in the /etc/shadow file, which means login disabled.
Yes, I discussed that with Vihan yesterday. The bug could have been something like a missing ! in the shadow file. I realised that I should have checked that before I assigned a root password manually. Then again, this is exactly how I assigned the root password anyway. Logged in as root on the console with a blank password and simply used passwd. Anyway, I'll reinstall and see if I can reproduce it.
Is there any additional information you can provide us, on how
to reproduce the passwordless root account, and the crashes? A formal installtion report via reportbug would be much appreciated, preferably with the latest daily build of the installer, and a sequence of steps to follow to reproduce it.
Hmmm. I'll download the daily build. To be honest, the Debian website confuses me as to what exactly I should download.
Anyway, as I said above, I'll try to reproduce the bug with this set of DVDs I have first.
On Wednesday 28 Feb 2007 11:18:12 Mrugesh Karnik wrote:
Anyway, as I said above, I'll try to reproduce the bug with this set of DVDs I have first.
OK. Changed the dead DVD burner and tried to insall again. This time, it was total chaos.
I chose the exact same options during the installation as before and I was surprised to see a dictionary language chooser screen. That hadn't appeared th lime time I had installed. The first time, I chose American English. The only other choice was manual symlinking. Later, the same screen appeared twice for ispell. The first of the two was similar to the earlier one - the one I just mentioned above. The second one had the British English option. Mind you, these screens hadn't appeared the last time I had installed Etch. As far as I remember, I had chosen to install the same set of packages the last time too.
Another screen that popped up was the imapd configuration screen. Hadn't appeared the last time.
After all this, the package installation step failed anyway. Here's an excerpt from the log:
Mar 2 16:30:08 in-target: Setting up samba (3.0.23c-3) ... Mar 2 16:30:09 debconf: Obsolete command TITLE Configuring samba called Mar 2 16:30:09 debconf: Obsolete command TITLE Samba Server called Mar 2 16:30:09 in-target: Couldn't reopen stdin(/dev/tty): No such device or address at /usr/sbin/update-inetd line 29. Mar 2 16:30:09 in-target: dpkg: error processing samba (--configure): Mar 2 16:30:09 in-target: subprocess post-installation script returned error exit status 6 Mar 2 16:30:09 in-target: Setting up uw-imapd (2002edebian1-13) ... Mar 2 16:30:09 debconf: Obsolete command TITLE Configuring uw-imapd called Mar 2 16:30:09 in-target: Couldn't reopen stdin(/dev/tty): No such device or address at /usr/sbin/update-inetd line 29. Mar 2 16:30:09 in-target: dpkg: error processing uw-imapd (--configure): Mar 2 16:30:09 in-target: subprocess post-installation script returned error exit status 6 Mar 2 16:30:09 in-target: dpkg: dependency problems prevent configuration of swat: Mar 2 16:30:09 in-target: swat depends on samba (= 3.0.23c-3); however: Mar 2 16:30:09 in-target: Package samba is not configured yet. Mar 2 16:30:09 in-target: dpkg: error processing swat (--configure): Mar 2 16:30:09 in-target: dependency problems - leaving unconfigured Mar 2 16:30:10 in-target: Errors were encountered while processing: Mar 2 16:30:10 in-target: samba Mar 2 16:30:10 in-target: uw-imapd Mar 2 16:30:10 in-target: swat Mar 2 16:30:10 in-target: tasksel: aptitude failed (255)
I decided to continue with whatever that had been installed anyway. The installed system wouldn't boot though. The kernel would freeze while probing the IDE chipset.
Also, I can confirm the crash I encountered during the network configuration step. When the installer is busy doing something, only the Screenshot button appears active. Press it and it crashes.
Also, in the base system installation phase, I chose the kernel to install. A screen came up about initrd. I thought about reviewing my kernel choice, so I clicked Go Back. It dropped me back to the main menu, without crashing, instead of just one step back.
One nice touch though. The boot options I chose when starting up were automatically added to the grub configuration file.
Also, since I wasn't able to install the system properly, I was not able to try and reproduce the root login bug.
Mrugesh Karnik wrote:
I have just posted the text only version of my Debian Etch Installation Report to the wiki. It's available here:
http://db.glug-bom.org/wiki/index.php/Debian_Etch_Installation_Report
I have taken lots of screenshots and I'll post them tomorrow. The installer has a handy facility for taking screenshots if you're curious.
Also, I found a MAJOR security bug with respect to the sudo integration. I enabled it and found that root login with a blank password was possible. I haven't tried updating the system yet. If the bug persists, I'll report it.
Thans to Vihan, I got the Etch DVDs and installed them the same night. Since I never login as root, I did not check it then but now I tried to login as root w/o passwd but it does not login. Do you still face this problem?
A warning to all those planning to install etch as production. Don't do it for desktops. The GUI is quite buggy while the command line part is good and can be used. My Open-Office does a disco dance whenever I open an existing text file. Its tool buttons keep doing the disappearing act randomly. The Kde Control Center had only two links for 'Network' and 'Peripherials'. The Lost and Found has a full collection of package links.
Here are two links that help in file sharing, printer sharing and samba through command line for Debian. http://www.debiantutorials.org/content/view/110/1/ http://www.nixser.com/2006/08/22/file-sharing-on-debian/
On Wed, 28 Feb 2007 20:48:18 +0530, Rony said:
Thans to Vihan, I got the Etch DVDs and installed them the same night. Since I never login as root, I did not check it then but now I tried to login as root w/o passwd but it does not login. Do you still face this problem?
A warning to all those planning to install etch as production. Don't do it for desktops. The GUI is quite buggy while the command line part is good and can be used. My Open-Office does a disco dance whenever I open an existing text file. Its tool buttons keep doing the disappearing act randomly. The Kde Control Center had only two links for 'Network' and 'Peripherials'. The Lost and Found has a full collection of package links.
Err, if there are things in lost and found, then there was a major file system or drive issue you had. This is most likely to be a local issue than anything else.
manoj
On Wednesday 28 Feb 2007 22:06:41 Manoj Srivastava wrote:
On Wed, 28 Feb 2007 20:48:18 +0530, Rony said:
A warning to all those planning to install etch as production. Don't do it for desktops. The GUI is quite buggy while the command line part is good and can be used. My Open-Office does a disco dance whenever I open an existing text file. Its tool buttons keep doing the disappearing act randomly. The Kde Control Center had only two links for 'Network' and 'Peripherials'. The Lost and Found has a full collection of package links.
Err, if there are things in lost and found, then there was a
major file system or drive issue you had. This is most likely to be a local issue than anything else.
I doubt that. Abhishek Ambekar had also reported a similar problem if I'm not mistaken. Hopefully he's reading this.
On Wed, 28 Feb 2007 22:49:12 +0530, Mrugesh Karnik said:
On Wednesday 28 Feb 2007 22:06:41 Manoj Srivastava wrote:
On Wed, 28 Feb 2007 20:48:18 +0530, Rony said:
A warning to all those planning to install etch as production. Don't do it for desktops. The GUI is quite buggy while the command line part is good and can be used. My Open-Office does a disco dance whenever I open an existing text file. Its tool buttons keep doing the disappearing act randomly. The Kde Control Center had only two links for 'Network' and 'Peripherials'. The Lost and Found has a full collection of package links.
Err, if there are things in lost and found, then there was a major file system or drive issue you had. This is most likely to be a local issue than anything else.
I doubt that. Abhishek Ambekar had also reported a similar problem if I'm not mistaken. Hopefully he's reading this.
In which case, could you please file a bug report on this issue? Please mention the provenance of the DVD's in the report, and if anything unusual happened.
manoj
On Wednesday 28 February 2007 20:48, Rony wrote:
The Kde Control Center had only two links for 'Network' and 'Peripherials'. The Lost and Found has a full collection of package links.
I am also experiencing the same problem! There is not a single option available for me in K Control Center. But everything is there in Lost+Found
Well... before Etch i was using Sarge .... so while installing Etch i just kept /home unformatted as it was mounted on separate partition! so i thought this was the mistake i made while installing Etch but Rony's experience made me to write mail.
abhishek wrote:
On Wednesday 28 February 2007 20:48, Rony wrote:
The Kde Control Center had only two links for 'Network' and 'Peripherials'. The Lost and Found has a full collection of package links.
I am also experiencing the same problem! There is not a single option available for me in K Control Center. But everything is there in Lost+Found
Well... before Etch i was using Sarge .... so while installing Etch i just kept /home unformatted as it was mounted on separate partition! so i thought this was the mistake i made while installing Etch but Rony's experience made me to write mail.
I faced another problem too, but it was present in the earlier Ubuntu 6.10 too. The problem is that when using 'vi' in gui terminal, the keyboard goes haywire. The keys carry out functions not meant for them. Eg. 'Del' key, arrow keys add an extra blank line and the alphabet C in the blank line. It keeps adding with every stroke. Insert keeps toggling off after every entry. It also happens in console but not as bad. Editing text files is a major hassle as it has to be closed 'q!' and reopened a few times till I hit jackpot. Gedit is a way out but thats cheating. ;) However the file sharing link I had posted has mention of 'nano', a very nice text editor. It runs like butter without any circus sumersaults. Simply replace the command 'vi' with 'nano'. To save your work use 'Ctrl + O' and 'Ctrl + X' to exit.