tune2fs change ext2 to ext3

Published by:

i have trouble install ubuntu while i already have slackware inside my comp. it said the slack uses ext2 so it had an error. so i wonder to change the ext2 system to ext3 without re-installing the system.
here what i got from the internet. using tune2fs program that already inside the slack 12.

  • Log in as root
  • Make sure /etc/fstab has /dev/hda10 mounted to /test as ext2, read write
  • umount /dev/hda10
    • If you can’t unmount it, then remount it read only (mount -o remount,ro /dev/hda10)
  • tune2fs -j /dev/hda10
  • Edit /etc/fstab, and for /dev/hda10, change ext2 to ext3
  • mount /dev/hda10
  • /sbin/shutdown -h now
  • mount | grep /dev/hda10
    • If it’s not shown as ext3, reboot, if still not, troubleshoot
    • Otherwise, you’re done.

there i think my ext2 changed ext3. now let’s try the ubuntu.

how to create iso image of xp using bcd program

Published by:

i found this way in the site of www.nu2.nu someone named Bart i guess. well thanks to him/her.
i got the xp sp2 program from my employee without the bootable program.
so here are the steps :

1. BCD installation instructions:Download BCD full package v1.1.1 (523KB).Or update from previous version: BCD update package (v1.1.0-v1.1.1) (5KB).When updating from previous versions, just extract the package over the previous version, overwrite any existing files. The bcd.cfg file will not get overwritten!Unpack the BCD package to some folder for example d:bcd. If you want to be able to run it from a server you should unpack it to a share from where your workstations can run it. You will need to map a drive letter to that share and run bcd using that drive letter.Make sure you also unpack the subdirectories!

2. Download wnaspi32.dll and copy it into BCD’s d:bcdbin directory.I have asked Ahead Software AG if I could distribute their aspi manager with my BCD package but they said: “…due to our licence agreement you could only let your users download it freely from our web site…”.

3. Download Windows XP package v1.0 (wxp10.zip) (5KB).Unpack it into the BCD directory, d:bcd.Make sure you also unpack the subdirectories!The Windows XP package contains the Windows XP bootstrap loader (same as Windows 2000) and some other files used to build the CD.

4. You must copy the i386 folder from your Windows XP installation/setup CD-Rom.For Windows XP Home Edition copy it to the d:bcdcdswxphomefiles folder.For Windows XP Professional copy it to the d:bcdcdswxpprofiles folder.Make sure you copy all files and all subdirectories!If you’re Windows XP files are already “slipstreamed” with a service pack you must also copy the win51ic.SPx or win51ip.SPx file.This will prevent the CD asking “put the SPx CD into drive A:” during install.The location of the i386 folder may differ, for example when you have a dual boot MSDN cd-rom it will be in %lang%winxp%edition%, where %lang% is your language, like “ENGLISH”, “GERMAN” and %edition% is “Home” or “Pro”. Other CD’s may have it just in the root or in some other location.
Optionally you can also copy the following files (not needed for bootable CD installation):autorun.infreadme.htmsetup.exe
If you have a Windows XP CD from MSDN…Edit the file i386txtsetup.sifsection [SetupData], and change the setup source path, it should read: SetupSourcePath = “”

5. You can apply Service Pack 1 to this installation (integrated installation). So that you have an installation CD-ROM with the service pack built in.Apply service pack 1 to your files using the “-s” option (you must supply full path).
For Windows XP Home edition:
xpsp1_en_x86.exe -s:d:bcdcdswxphomefiles
For Windows XP Professional:
xpsp1_en_x86.exe -s:d:bcdcdswxpprofiles
Notes:
The Service Pack file can have another name, like xpsp1_nl_x86.exe for Dutch language.
The xpsp1_en_x86.exe can only be run on a Windows 2000 or XP PC!
You should now have a win51ic.sp1 or win51ip.sp1 file in the files directory. Check this, to prevent the CD asking “put the SP1 CD into drive A:” during install.
All other files and folders you want on the CD-Rom must also be added to the files directory, these files will not be integrated in the Windows XP installation, they’re just parked there. Things you could add are: latest patches, internet explorer, directx.Add your files to:For Windows XP Home edition: d:bcdcdswxphomefiles.For Windows XP Professional: d:bcdcdswxpprofiles.
Open a command prompt, go to the d:bcd folder and run:For Windows XP Home edition: bcd wxphome.For Windows XP Professional: bcd wxppro.This will build the (bootable) ISO image and burn it to your recorder.

the instruction above for xp sp1 but i use it for sp2

modified xorg.conf for nvidia geforce4 mx4000

Published by:

i found something else in the net. and i think it’s make my compie run faster when entering the kde.
write these into your /etc/X11/xorg.conf
into the device sectin

Option “AddRGBGLXVisuals” “True”
Option “AllowGLXWithComposite” “True”
Option “DisableGLXRootClipping” “True”

try it

samba – ipv6 patch

Published by:

this is what i got from http://www.litech.org/samba/

Configuring smbd for IPv6

Traditionally, Samba and Microsoft Windows have run SMB on top of the NetBIOS protocol. On the Internet, NetBIOS can be layered on top of TCP and UDP using ports 137, 138, and 139. This is called NetBIOS-over-TCP, or NBT for short, and is essentially a giant hack by Microsoft to make their old legacy networking protocols run on TCP/IP. Since IPv4 addressing is deeply embedded in NBT, it will probably never be possible to run NetBIOS on IPv6, but this is probably for the best.

Fortunately, with Windows 2000 and Windows XP, Microsoft has introduced what they call “direct-hosted SMB”, which simply means that the SMB protocol is run directly on TCP on port 445 without all the NetBIOS cruft. SMB itself has no IPv4 dependencies, so it can run on IPv6 without trouble. This is what is supported with the Samba IPv6 patch.

smbd has, for some time, had the ability to accept connections on port 445, but it does not listen on this port when started with the -D option. An Internet “superserver” like inetd must be configured to accept connections on port 445 and start smbd (without the -D flag, of course) as the backend daemon. All that is necessary to IPv6-enable the patched smbd is to ensure that inetd is listening to port 445 on IPv6.

The patch also includes improvements to the address-based access control to allow IPv6 address prefixes to be included in the “hosts allow” directive. For example:

    hosts allow = 127. ::1 192.168.0.0/255.255.0.0 3ffe:ffff:1234::/48

Using smbclient with IPv6

The patched smbclient will automatically look up IPv6 addresses as well as IPv4 addresses when resolving names with DNS. For each address that is returned, a connection will be attempted, and if an attempt fails, the next address will be tried. This will be transparent to the user but may be viewed in action with a debug level of 3 or higher. On my system, it looks like this:

    $ smbclient -L marduk -d3
  Initialising global parameters
  params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
  Processing section "[global]"
  added interface ip=192.168.123.75 bcast=192.168.123.255 nmask=255.255.255.0
  Client started (version 2.2.3a).
  resolve_hosts: Attempting getaddrinfo for name marduk<0x20>
  Connecting to 3ffe:2900:f10a::1 at port 445
  error connecting to [3ffe:2900:f10a::1]:445 (Connection refused)
  Connecting to 192.168.10.1 at port 445
  error connecting to [192.168.10.1]:445 (Connection refused)
  Connecting to 192.168.10.1 at port 139
  Password:
  Domain=[NETWORK] OS=[Unix] Server=[Samba 2.2.3a]

    Sharename      Type      Comment
    ---------      ----      -------
    [...]

Using IPv6 SMB servers works in the rest of the Samba package, too. For example, an IPv6 host may be used as a password authentication server.

Making Windows work with SMB-over-IPv6

Since Microsoft has yet to make their SMB software IPv6-capable, it is not yet possible to connect to IPv6 Samba servers with Windows. However, a “relay” program may be used to allow a Windows 2000 or XP system to listen on IPv6 at port tcp/445 and relay connections to port 445 on the IPv4 loopback address, but this setup is not recommended for use other than testing.

According to Microsoft literature, the Windows .NET server will support SMB over IPv6, but there have been no reports confirming this and the .NET server has not been tested with the Samba IPv6 patch.
but still like mr. eko and mr. zahris said in igos yesterday, sometime samba aint appear on windows network.
i have to wait for another development.

fstab and how to edit it

Published by:

these all information i got from http://www.tuxfiles.org/linuxhelp/fstab.html written by nana langsted.
remind me of someone.
fstab is a configuration file that instruct the lilo on booting, to mount devices somewhere. so we can access that device when running linux. you can also learn about mount in www.tuxfiles.org
anyway this is how to edit it in simple words.

login as root and edit your fstab with
#nano /etc/fstab
or
#pico /etc/fstab

you will see one of this
example :
/dev/hda4 swap swap defaults 0 0
/dev/hda2 / ext2 defaults 1 1
/dev/hda1 /hda1 ntfs ro 1 0
/dev/hdb1 /home/original ntfs-3g defaults 0 0

the first column are the device that plugged in your cpu.
hda or hdb means your ide harddrive.
sda or sdb means your sata drive.
cdrom or dvdrom means your cd or dvd drive.
you can see these devices in /dev/ folder

the second column are the place that your mounting device located in your linux partition. you can edit all except the “/” and “swap” because these are you linux partition.

the third column are the type of your mounting device.
ext2 or ext3 means your linux. swap also.
vfat means fat32 or things like that. used by win 98-me-xp
ntfs means ntfs file system used by xp-vista. win 2000 uses “so 2000”

the fourth column are how these linux will be conducted.
defaults means your device will be conducted by linux system.
ro means read only
rw means read write. you can use rw on your other linux partition and vfat but not in ntfs. you need ntfs-3g to read and write.
auto noauto mean the devices will be mount automatically during startup. usually used for flash, floppy and etc.
user nouser mean normal user can mount the device or not. nouser is the defaults.
exec noexec mean your linux will run the binary or startup file on that device or not. dont use this command if you dont know what you’re doin.
sync async mean synchronously or not. used in floopy or flash.

the fifth columns is for define the dump option. whether the file system should be backup or not by fsck command. fsck is similar to chkdisk in windows. i think we are familiar with this.

the 6th columns is for for define the dump option. whether the file system should be check or not by fsck command.

that’s all. you can read it more in” tuxfiles.org”.

monitor resolution problem

Published by:

in the console mode or init 3 you can try this command  first

#xorgconfig

answer each questions appear on the screen. for the horizontal and vertical you may have to take a look to your monitor label. usually at the back of your monitor.  this is very important if the xorg doesnt configure it automatically. Especially in slackware. ubuntu can do this automatically

or you may try this command

#xorgsetup

it’s in gui mode. u have to fill all the questions appear.

but sometime those two command not work, so you have to take a look the xorg.conf manually.
still in init 3 mode, edit the xorg.conf

#nano /etc/X11/xorg.conf

see if the driver in device screen is the right driver. vesa is a universal driver but sometime it didnt work 100%. so if you have nvidia or ati graphic card, change the driver to nv or ati.  see the next line for configuration i have made

Driver “nv”
BusID “PCI:1:0:0”
VideoRam “128”

in the screen section make sure the device is the same with monitor section.
like “My Video Card” in screen section must be the same with monitor section device “My Video Card”

dont forget the default depth

DefaultDepth 24

save your xorg.conf

read write ntfs drive

Published by:

i got the information brom bayu blog wordpress

firts u should download the package ntfs-3g from the site http://www.ntfs-3g.org

then install the package

#installpkg ntfs-3g

clik Y when prompting

here is the step making the ntfs drive could be written by your linux

#mkdir /mnt/{winc,wind}

#ntfs-3g /dev/hdb0 /mnt/winc

#ntfs-3g /dev/hdb1 /mnt/wind

or

#mount -t ntfs-3g /dev/hdb0 /mnt/winc

#mount -t ntfs-3g /dev/hdb1 /mnt/wind

if you want your linux read the ntfs on booting type this in your /etc/fstab (at the end is ok)

/dev/hdb0 /mnt/winc ntfs-3g defaults 0 0

/dev/hdb1 /mnt/wind ntfs-3g defaults 0 0

check it out

problem connecting to internet in slackware because different host name

Published by:

i use two system in my comp. Vista and Slackware. and using d-links router as my internet gateway through my isp. i put a computer name in vista as sugi-pc and using static ip in my router. with hope that i would be connected faster.
but the problem came in my slackware. i put all the configuration in /etc/rc.d/rc.inet1.conf with the static ip and host name as sugi-slax. but using the same domain name: mskantor.
because i set the static ip inside my router with a vista host name, my linux wont come in to the router. coz using different host name. that ‘s why i cant ping my router ip.
so i configured back the rc.inet1.conf and activated the dhcp in eth0 and eth1. since that i use 2 lan card.
i emptied the ip address number become “” only then put the DHCP with “yes”
so i restart the slax and it took sometime when getting the ip from the router. but works fine.
i can use the internet again.