eyt*

Find your next scenic drive!

November 23, 2006

Error Changing Samba Password...

When I went to change my Samba password earlier today, I got this error message:

eyt@zaterdag 19% smbpasswd
Old SMB password:
New SMB password:
Retype new SMB password:
Error connecting to 127.0.0.1 (Connection refused)
unable to connect to SMB server on machine 127.0.0.1. Error was : SUCCESS - 0.
Failed to change password for eyt

Googling did not say it directly, but it appears that the problem above was that my smb.conf did not mention 127.0.0.1 (localhost) for the listening interfaces; adding 127.0.0.1 to the interfaces setting in the global section resolved my problem, as demonstrated here:

[global]
...
interfaces = 127.0.0.1 192.168.1.1/255.255.255.0
...

After this quick change and restarting Samba, I was able to change my password and all was happy again.

June 24, 2006

Installing SuSE Linux 10.1...

SuSE Linux 10.1 has been recently released and it is freely available via OpenSuSE. I opted for purchasing the DVD's, though, and I just received them earlier this week.

The only part that I really dislike about Fedora and SuSE's installation procedure is that you have to shutdown the machine for anywhere between 30 minutes and 2 hours depending on how much you are paying attention to the installation process; because of this, you'll probably see this site down an hour sometime in the upcoming couple of weeks.

Last night, I decided to upgrade one of my workstations from 10.0 to 10.1, and the process went very smoothly... until the end. At the end, it wanted to configure the on-line update and to do this, it opened up Mozilla so I could go through the registration form. After filling out the form, it said that it was successful and that was it; it did not feel very well integrated, since it did not tell me what the next step was. I assumed that it was to close the window, however, the setup program just kept on insisting to open up Mozilla and have me repeat the process, until I eventually just gave up configuring the on-line updater and clicked Cancel. This ended up being the final step, and then I logged into my machine.

I then proceeded to attempt to update my machine, however, the YaST Online Update (YOU) was quite insistent that there were no updates, to which I was a little surprised since in each SuSE release that I have installed thus far, there have always been some updates afterwards. So I decided to start playing with my machine and to figure that out later, and this is when I started noticing my problem: when I started up Thunderbird and Firefox, I got a segmentation fault, but I tend not to use the SuSE default Firefox and Thunderbird, so I initially thought it was a problem with those, so then I tried the SuSE default Firefox, only to get the same results:

  • eyt@zaterdag 1$ firefox
  • /usr/bin/firefox: line 159: 11151 Segmentation fault $AOSS $MOZ_PROGRAM $@

After searching, I found that there were updates, and that this was probably one of them. Installing the BASH one really did not help any, so I then shifted my efforts to getting the Online Update to work properly.

After many failed attempts, I fell onto this which led me to resolving my problem. The deal is that with previous versions of YOU, you used to only use one source for updates, but with the new version, it works closer to how Cygwin's installer works, in that you can get put in multiple update sites for different applications. This is pretty cool, however, it is unfortunate that it does not make adding the default SuSE sites easier to set up. As such, here is what you have to do:

  1. Start yast2, under Software, select Installation Source.
  2. Once initialized, select Add, HTTP and enter these sites:
    Server NameDirectory on ServerNotes
    download.opensuse.orgdistribution/SL-10.1/non-oss-inst-source/
    suse.cs.utah.edususe/update/10.1/Or another mirror
  3. Once those are added, make sure that Status and Refresh are on for these sites. If they are not, select them, and then click the appropriate button in the lower right-hand corner.
  4. Next click Finish. This will take several minutes to complete, or at least it does the first time

Once that was done, the Software Updater icon turned into an orange exclamation mark, so I proceeded to tell it to update everything. After a few moments, it errored out with:

  • Establishing script:libzypp-patch-zmdrestart.sh-2-1533-1.noarch[20060624-115231]
  • This would invalidate script:libzypp-patch-zmdrestart.sh-2-1533-1.noarch[20060624-115231].
  • Marking this resolution attempt as invalid.

Because I had manually installed a few packages in prior to this, I thought that I would try selecting packages around this problem, but to no avail. As a final attempt, I went into YaST2, and selected Online Update from Software, and after it initialized, it downloaded a bunch of patches, one of which included some updated YOU. This required YOU to be restarted, and then it continued to download a bunch of packages.

And after all that, I am now able to start Mozilla Thunderbird and Mozilla Firefox without any segmentation faults. And besides that experience, I am so far very pleased with the changes in SuSE Linux 10.1, particularly with the look and feel, but I've only been using it for a couple hours now.

December 3, 2004

fdisk's SGI partition table fix for variable sector sizes...

I have recently discussed a bug with Linux's dvhtool when dealing with devices whose block size is greater than 512 bytes. A similar issue also exists in fdisk when creating SGI partition tables, as filed in RedHat's Bugzilla Bug 140437.

The issue is that the sector size in the volume header was hard coded to 512, and therefore, SGI IRIX's fx tool would report errors on such devices and would attempt to create filesystems that exceeded the drive's capacity. The patch resolves this issue by using the sector_size variable. I have also updated the partition table display to correctly denote what is happening.

With this patch, you must partition the drive via the base device (/dev/sda, for example), and not via SGI's volume partition (such as /dev/sda3). In the former case, the number of calculated sectors (represented by llsectors) is in blocks of 512, whereas in the latter case, it is in blocks of 4096, and therefore, the division by sector size constantly makes the device smaller.

The bug was tested between an IRIX and Linux workstation, where the device would be initialized and moved to the other operating system for validation.

This patch has been submitted directly to the maintainers of util-linux, and is based on Debian's util-linux 2.12i. If you see any issues with the patch, please let me know.

November 10, 2004

SuSE Linux 9.2 Upgrade...

My SuSE 9.2 Update came in today, and my first comment is that Novell is very prominent in the packaging. This is not a big surprise to me, considering all calls and e-mails I make with them regarding the ability to purchase an Update in Canada; more specifically, they announced towards the middle of October that you could pre-order SuSE. In the UK and Germany, you could purchase both the Upgrade and the Full-Version, but in the US and Canada, well, only the Full-Version. A day or so after it officially came out is when I was finally able to order it, and then it was back-ordered. Arrhgg... In the two or so other times in dealing with SuSE, it wasn't like this.

On the other hand, this is the first time that the DVD actually worked in my system. I am not sure if its my system or the other SuSE distributions, but the latest DVD is labeled and it works, and I was happy not changing the CD's around. The installer was much more refined than the last time, and very smooth. Towards the end, however, I guess I answered the question about the Firewall incorrectly, since when my box came back up, the network was not operational, and since my machines are dependent on my network, this resulted in the machine being painfully slow.

It actually took longer to solve this problem than I thought. I tried tweaking the /etc/sysconfig/SuSEfirewall2, but it still got stuck in the NFS mount problem. I then disabled the NFS drives from the fstab, and I was finally able to get it into X, but the remaining system was still slow, so I finally decided to get out of X via CTRL-ALT-F1, and logged into a normal shell. Here, I was able to go into yast and disable the firewall.

Once that was done, I rebooted, and I was then able to login for the first time. The new KDE 3.3 is nice, but I quickly noticed that my system was not normal; in previous versions of SuSE, I used the terminal Eterm, and it is no longer provided by SuSE and the downloadable RPM fails miserably because of missing dependencies that are no longer available. This was disappointing, and I am now trying to get used to konsole.

The worst of this is that it seems that this package was removed without any notification; there were some conflicts, but nothing regarding Eterm. Some of the conflicts I received had to do with the upgrade to Apache TomCat 5.0, where the packages for the installed 4.x version had an upgrade, but it decided to install 5.0 instead.

Also, in the last update, I was wondering about the XFree86 status in 9.1. Well, it seems that in 9.2, they have also moved the move to X.org, and this transition seemed seamless so far.

Overall, there were a few bumps in the road, but it seems nice so far. And at least, I still have pine (which I can't say the same for Fedora Core).

November 8, 2004

Fedora Core 3...

Back when Fedora Core 2 was released, I said that it would not be long before I upgraded to SuSE instead. Well, it never happened, and today, as Fedora Core 3, I am again upgrading it. This time I am also waiting for my shipment of SuSE Linux Pro 9.2, which was also released recently, but we'll see how that transition goes.

I have to say that I was a little nervous about upgrading this time. There seems to be a lot of little changes in the distribution that the average user could overlook, but nothing like the changes in Fedora Core 2, and SuSE 9.2 is similar in this regard also. But this makes the upgrade more interesting, since this sorta minimizes the differences. But the part that really concerned me is that for a while, the latest and greatest Fedora kernels would not boot on my machine, as reported here. Unfortunately no provided any input on this issue, so I was a little concerned as to whether the kernel would boot or not. Of course, I was not prepared for the worst case scenarios :-).

I snagged the CD's via BitTorrent, burnt them on CD's, and got to work. I started the installer, and it recognized my system; I clicked OK to continue, and then realized that I hadn't modified my /etc/fstab to disregard my software RAID, and because of this, it forced me to reboot, and I had to boot back into Fedora, update the file, and restart the process all over again.

Once that the process started going, it went fairly smooth. The upgrade took around 90 minutes; again, it started by stating 60 minutes, and it kept growing by 5 minutes for about 15 minutes. The only user interaction, however, was to change CD's, and the first CD was there for a very long time on my system.

After the process was completed, I rebooted. When I got to the Grub screen, I was expecting to see my old kernel and the new kernel, however, I only saw the new kernel, and I got a bit nervous, but pressed enter, and viola! It booted! I was pretty happy at this point. Almost everything worked out of the box, except for the services that depended on my software RAID, which I'll get to in a second. The core operating system, however, does not seem to have been updated very much, and still seems very texty compared to SuSE.

For the software RAID, however, it seems different than it was in Fedora Core 2. One of the first things I did with the machine was to uncomment my software RAID mount point in the /etc/fstab, but when I went to mount it, it complained that it couldn't and that my superblock was corrupted. My heart started to palpatate. I thought that perhaps a module was not loaded, so I looked around quickly, and then I remembered about raidstart, so I started up my RAID via raidstart /dev/md0, and after this, I was able to mount my filesystem.

But why wasn't this done for me automatically? Well, according to the Linux RAID HOWTO, this is only done if the /etc/fstab file contains a reference to an md device. To test it, I rebooted, and everything came up nicely!

There are many updates that were released today, and unfortunately, the mirrors are not yet updated completely yet, so snagging the updates may take a bit longer. But overall, the machine seems like it did before. I am sure that there will be a few quirks as I play with it some more, but so far so good.