problem with nautilus share properties in ubuntu 8.10

I got a problem when trying to configure directory share in nautilus with intrepid ibex (ubuntu 8.10). if you never using share properties with nautilus before, I'll explain it a little. Simply right click on directory that you want to share to windows network, If samba package not already installed then system will prompt you a question to install a samba package and its dependencies from repository.

A problem is appear and show a message like this when trying to click 'create share' button.
'net usershare' returned error 255: net usershare add:
cannot share path /media/Multimedia System/Movie/Archives as we are restricted to only sharing directories we own.
Ask the administrator to add the line "usershare owner only = False"
to the [global] section of the /etc/samba/smb.conf to allow this.

I forget if a directory that I want to share isn't in my home directory. I follow a message to modify a line 'susershare owner only' in /etc/samba/smb.conf and set a value to 'false' :
usershare owner only = False

Now I can share the directory. Another problem happen when I try to disable sharing properties for that directory. It's already disabled itself because a share's icon that showed on the directory is disappear. But the directory still shared in the network. So, I try to findout where the configuration file for each user has been stored, because there is nothing in /etc/samba/smb.conf about my shared directory. And I found that each user has join a "sambashare" group (in /etc/group).

When user try to share file or directory, that information will be stored in /var/lib/samba/usershares's directory. All of configuration that I was create before store in there. one file for one shared object (usually shared directory).I just delete it and that directory never showed in network again.

But I'm still curious, why my ubuntu intrepid ibex system sometimes show an icon that directory is shared when i check with nautilus, but sometimes an icon is disappear and the directory is still shared.

Slackware 12.2 is released!

Again! slackware's developer team announce new release of slackware. according to ANNOUNCE.12_2's file that come from slackware 12.2 release directory, here is some features that available on slackware 12.2 (grab from that file):

- Runs the 2.6.27.7 version of the Linux kernel from ftp.kernel.org. Also included is a kernel patched with Speakup to support speech
synthesizers providing access to Linux for the visually impaired community.

- Some packages were upgraded from slackware/x directory

- Installs gcc-4.2.4 as the default C, C++, Objective-C, Fortran-77/95, and Ada 95 compiler.

- Apache (httpd) 2.2.10 web server with Dynamic Shared Object support, SSL, and PHP 5.2.8.

- New development tools, including Perl 5.10.0, Python 2.5.2, Ruby 1.8.7-p72, Subversion 1.5.4, git-1.6.0.3, mercurial-1.0.2, graphical tools like Qt designer and KDevelop, and much more.

- Updated versions of the Slackware package management tools make it easy to add, remove, upgrade, and make your own Slackware packages. Package tracking makes it easy to upgrade from Slackware 12.1 to Slackware 12.2 (see CHANGES_AND_HINTS.TXT). The slackpkg tool can also help update from an older version of Slackware to a newer one, and keep your Slackware system up to date. In addition, the slacktrack utility (in extra/) will help you build and maintain your own packages.

- Web browsers galore! Includes KDE's Konqueror 3.5.10, SeaMonkey 1.1.13 (this is the replacement for the Mozilla Suite), and the immensely popular Firefox 3.0.4, as well as the Thunderbird 2.0.0.18 email and news client with advanced junk mail filtering.

- The complete K Desktop Environment (KDE) version 3.5.10, including the KOffice productivity suite, networking tools, GUI development with KDevelop, multimedia tools (including the amazing Amarok music player and K3B disc burning software), the Konqueror web browser and file manager, dozens of games and utilities, international language support, and more.

- using xfce 4.4.3 for a fast and lightweight but visually appealing and easy to use desktop environment. upgrade from 4.4.2 release.

- A collection of GTK+ based applications including pidgin-2.5.2, gimp-2.4.7, gkrellm-2.3.2, gxine-0.5.903, xchat-2.8.6, xsane-0.996, and pan-0.133.

- Using Java(TM) 2 Software Development Kit Standard Edition release 6 update 11 on extra directory. Upgrade from jdk-6u6.

for people who try to upgrade from previous release, don't forget to read CHANGES_AND_HINTS.TXT file before. There are some notable changes and hints that you must apply to get your slackware working properly.

And also based from CHANGES_AND_HINTS.TXT file, here are package additions since release 12.1:
a/kernel-firmware: Added. This is architecture-independent firmware for devices (mostly sound cards), which was previously embedded into the kernel image.
ap/gphoto2: Added.
ap/libx86: Added.
ap/pm-utils: Added.
ap/radeontool: Added.
ap/slackpkg: Added (moved from /extra).
ap/sqlite: Added.
ap/vbetool: Added.
d/dev86: Added. Replaces d/bin86.
l/beecrypt: Added.
l/enchant: Added (moved from /testing/packages/kde4/deps/).
l/gtkspell: Added.
l/gstreamer: Added.
l/gst-plugins-base: Added.
l/intltool: Added.
l/libcap: Added.
l/libgphoto2: Added.
l/liboil: Added.
l/libraw1394: Added (moved from /testing/packages/kde4/deps/).
l/libvisual-plugins: Added.
l/parted. Moved from /extra.
n/alpine: Added. Replaces n/pine.
n/iwlwifi-5000-ucode: Added.
x/dri2proto: Added.
x/xdg-utils: Added.
x/xf86-input-acecad: Added.
x/xf86-input-dmc: Added.
x/xf86-input-synaptics: Added. See note below.
x/xf86-input-void: Added.
x/xf86-video-mach64: Added.
x/xf86-video-openchrome: Added.
x/xf86-video-r128: Added.
xap/xmms: Added (again) :-)
/extra/wicd: Added.

and package removals since release 12.1:
d/bin86: Removed. Replaced by d/dev86.
n/pine: Removed. Replaced by n/alpine.
extra/parted: Moved to l/ series.
extra/slackpkg: Moved to ap/ series.

and many others upgraded packages. For more info just upgrade or install it! ;-)

Slackware 12.1 Released

Long live for Slackware!
another new version has released this year. It's time to upgrade my system. As usual, more packages has been upgraded by developer team. But it still looks like an old-fashioned style, because I have see no new appearance inside instead a lot of upgraded packages.

Quoted from release announcement file:

This first Slackware edition of the year combines Slackware's legendary simplicity (and close tracking of original sources), stability, and security with some of the latest advances in Linux technology. Expect no less than the best Slackware yet.

Want to know more, read the official announcement's page.

Opening freebsd partition under GUI environment

Previously, I've ever write a note when trying to mount freebsd filesystem using command line. This note just a modified version from that one. while you trying to mount freebsd partition using file manager under desktop environment (GNOME or KDE) in linux, there is an error message showed up. It's look like a message if I mount it under command line using mount tool.

Device manager feature which came with GNOME or KDE is trying to mount freebsd partition using read-write mode instead of read-only mode. But in most linux distro, an ufs module inside kernel doesn't compiled as read-write mode by default because it is still DANGEROUS. Eventhough i've ever try it successful.

Not only that, a default ufstype's option which passed to mount ufs filesystems is old. File manager try to mount the partition using old type instead of ufs2 which is not supported for mounting freebsd native filesystem (UFS/FFS). if you want to mount a partition under GUI (desktop) environment maybe this example bellow can help. Just put this line into /etc/fstab file:

e.g.
/dev/hda2 /media/hda2 ufs user,noauto,ro,ufstype=ufs2 0 0

note:
- /dev/hda2: which is your freeBSD partition
- In the option column from that line is defined to force mounting option to use read-only mode and ufs2 as ufstype.

An interactive linux kernel map

For people who wants to know what is inside linux kernel, maybe this map is helpful. This is a map that explain a lot of how kernel works. An author said it could navigated similar to google map. All indetifier on the map are linked to the LXR, a toolset for indexing and presenting linux source code. Either you can view an online version or buy the poster from that map.

Link site: http://www.linuxdriver.co.il/kernel_map

Install Slackware from ISO file with grub or lilo

pre-requirement:
- already have Linux or BSD-based (FreBSD) system installed on harddisk before using grub or lilo as bootloader.
- Slackware's iso image on your harddisk.
- at least one partition prepared for your slackware system

Here are step by step:

1. Extract kernel and initramfs image's file (initrd.img) that come from slackware's iso image (you can mount it first to get both file). The location for kernel file is in /kernel directory and initramfs file is in /isolinux directory. Then, copy both file into /boot directory in your linux/FreeBSD system.

2. Configure your linux/FreeBSD grub or lilo for including slackware's kernel and initramfs file (initrd.img).
Add this entry into /boot/grub/menu.lst if using grub:
title Slackware-12.2 Install
kernel /boot/[your-slackware-kernel]
initrd /boot/[your-initramfs-file]
quiet

simply add this entry into /etc/lilo.conf if using lilo:
image=/boot/[your-slackware-kernel]
label=Slackware-12.2
initrd=/boot/[your-initramfs-file]
read-only

you need to update the configuration because lilo doesn't update that information automatically.
Run this command on your console:
lilo -v -v

3. Restart your pc/laptop to boot into slackware installation entry in your bootloader menu. Before you start to type "setup", make sure you already mount an iso file. If your slackware's iso image on /dev/hda2, then mount that device first before mount an iso. Assumed /dev/hda2 is a location of an iso file than mount it into a directory first. Here are a step by step:

cd /
mkdir hda2
mount /dev/hda2 /hda2
mkdir iso
mount -o loop -t iso9660 /hda2/[your-slackware-iso].iso /iso

4. now you can run setup. When prompted to select source media, choose an option to install from a pre-mounted directory. don't forget to add "slackware" directory when you insert into a pre-mounted directory column.

e.g: /iso/slackware

5. you can continue doing installation activity as usual.

There are another option for booting both kernel and initramfs file. You can use Loadlin from DOS or use Grub4Dos if you don't have any linux or bsd system before.

hope this helpful

Slackware 12.0 is released

A new slackware version has released now, after waiting for a long time. there is an issues before a release date, that said a release version would jump directly in major number without passing a minor one. A mistery question has asnwered. An issue became a surprise for me, that slackware has released into version 12.0. Maybe this is an unusual habit from a developer team.

I'm really curious what a great change was happen. Then I start to find out into README.TXT's file first, if there is an explanation for this question. There are only some info about major components inside slackware 12.0 which are only a new version from major components of slackware 11.0. Here are the componets's version:

- Linux kernel 2.6.21.5
- C compiler gcc-4.1.2
- Binutils 2.17.50.0.17
- GNU C Library glibc-2.5
- X Window System X11R7.2.0 from X.Org.
- KDE 3.5.7
- Xfce 4.4.1

But This is really surprising me, when I read a RELEASE_NOTES's file. Here are a qoute from that file:

About the only things to mention here are that Slackware now requires a recent 2.6.x kernel (I believe 2.6.18 is a minimum), but as usual unless your needs are specific you're probably better off running the included kernels that we've tested things against. The best kernel to run (even on a one CPU/core machine) is the generic SMP one, but that needs an initrd, so be sure to read the instructions in /boot after installing with a huge* kernel if you plan to switch. Since the initrd has been around since Slackware 11.0, hopefully most
Slackware users can take on this task easily and will not be "shocked and appalled".

Yeah, developer team decide to use kernel version 2.6 as default instead of 2.4 that usually being default from a release version before. I think this is a big changes that cause developer to jump a release version direct to major number. Also hotplug as device manager before has replaced with udev.

Another changes are completely documented in Changelog.txt's file and also in ANNOUNCE.12_0's file. As usual, it's time for upgrading system. If you would like to upgrade the system don't forget to read CHANGES_AND_HINTS.TXT's file. There are enough explanation and completes guide for upgrading system from 11.0 inside that file.

Happy slacking! :-)

Testing write support for UFS filesystem module in linux kernel

In previous article, I wrote a note for accessing UFS filesystem under Linux operating system. But It just in read-only mode. Now I'll try to enable write support for UFS filesystem. In this case, still use slackware version 11.0 as a linux host and using kernel release 2.6.18. First, I use config file from kernel packages that come with slackware and modify it to add this entry:

CONFIG_UFS_FS_WRITE=y

or you can use config menu interface to modify it. In file systems --> Miscellaneous Filesystems --> UFS filesystem support , and check on "UFS file system write support (DANGEROUS)" entry.

next, re-compile your kernel.

After doing some configuration and rebooting slackware system using new modified kernel, I try to mount freebsd filesystem manually using this command:

mount -t ufs -o ufstype=ufs2,rw /dev/hda3 /mnt

As far as I did, nothing wrong happen. What i've done is trying to create a file on UFS filesystem (freeBSD partition) and insert some text. Then I boot into freebsd system normally and there is a file that I create before under linux. Maybe need more test to know if it works fine or getting wrong and can cause a damage for freebsd filesystem.

hope this helpful. Use it with your own risk and without warranty.

Repair Grub with Ubuntu LiveCD

After re-installing windows, my ubuntu partition have disappear. What I mean is a grub bootloader (which come from ubuntu) that already installed before on MBR cannot be accessed because windows re-write MBR partition with its own boot manager.

what I should do?
1. boot using ubuntu livecd (desktop version)
a. login as root
using command: sudo_root or sudo -s
b. mount your ubuntu partition
e.g: - mount point as /media/disk
mount /dev/sda1 /media/disk

2. mount your livecd /dev directory into your ubuntu mount point ( /media/disk )
e.g: mount --bind /dev /media/disk/dev

3. run this command: grub-install --root-directory=/media/disk /dev/sda

hope this helpful.

TopologiLinux - Running Linux inside Windows

If you think this is a stuff that tells us about a GNU/Linux operating system topology, you're completely wrong. Because this is just another kinds of GNU/Linux distro which is a slackware-based variant. An interesting part from this distro that it can run on windows partition natively.

Topologi linux come in two mode: Colinux mode and Real Mode
a. Colinuxmode:

in this mode, you can install it directly into windows partitions ofcourse with a coLinux support ( tools for optimize operating your linux in windows natively).

b. Real Mode:
which means you can install this distro likely as general linux installation especially in native slackware installation.

This distro support for installing into NTFS filesystem. Based on official site, latest release (when I wrote this article) is 6.1.0 which support 6 GB software repository. Full version is bundled into 1 installation DVD. Beside that, this distro still use native slackware's package format (.tgz) and can run under Windows Vista.

There are also some FAQ and complete installation howto on official site. But there is no full documentation that spesifically for this distro as far as I know. Maybe you can use slackware documentation as reference.

related link: www.topologilinux.com

Setup lilo into partition's superblock and load it from grub

I already have grub installed on MBR of harddisk. It's come from my ubuntu linux. Then I installing slackware and want to use slackware's lilo to load the slackware system. First, I install lilo into superblock of slackware's partition using this command:

lilo -b /dev/hda2

note:

Slackware partition is on hda2, maybe it is different with yours, depends on your system placed in harddisk (including position of disk controller and partition). In my case, I use PATA harddisk which set as primary on controller 0. And my slackware system is on second partition.

Second, edit grub's configuration file (menu.lst). Usually in /boot/grub/menu.lst. And then add this entry:
title Slackware Lilo
root (hd0,4) #for example, if your slackware partition in /dev/hda5
chainloader +1

Now, restart the system.

hope this helpful.

Slackware 12.0 is released

A new slackware version has released now, after waiting for a long time. there is an issues before a release date, that said a release version would jump directly in major number without passing a minor one. A mistery question has asnwered. An issue became a surprise for me, that slackware has released into version 12.0. Maybe this is an unusual habit from a developer team.

I'm really curious what a great change was happen. Then I start to find out into README.TXT's file first, if there is an explanation for this question. There are only some info about major components inside slackware 12.0 which are only a new version from major components of slackware 11.0. Here are the componets's version:

- Linux kernel 2.6.21.5
- C compiler gcc-4.1.2
- Binutils 2.17.50.0.17
- GNU C Library glibc-2.5
- X Window System X11R7.2.0 from X.Org.
- KDE 3.5.7
- Xfce 4.4.1

But This is really surprising me, when I read a RELEASE_NOTES's file. Here are a qoute from that file:

About the only things to mention here are that Slackware now requires a recent 2.6.x kernel (I believe 2.6.18 is a minimum), but as usual unless your needs are specific you're probably better off running the included kernels that we've tested things against. The best kernel to run (even on a one CPU/core machine) is the generic SMP one, but that needs an initrd, so be sure to read the instructions in /boot after installing with a huge* kernel if you plan to switch. Since the initrd has been around since Slackware 11.0, hopefully most
Slackware users can take on this task easily and will not be "shocked and appalled".

Yeah, developer team decide to use kernel version 2.6 as default instead of 2.4 that usually being default from a release version before. I think this is a big changes that cause developer to jump a release version direct to major number. Also hotplug as device manager before has replaced with udev.

Another changes are completely documented in Changelog.txt's file and also in ANNOUNCE.12_0's file. As usual, it's time for upgrading system. If you would like to upgrade the system don't forget to read CHANGES_AND_HINTS.TXT's file. There are enough explanation and completes guide for upgrading system from 11.0 inside that file.

Happy slacking! :-)