SUSE Linux 的inode概念

SUSE Linux 預設使用 reiserfs為預設的檔案系統

reiserfs 是屬於 dynamic inode allocation 的 fs，
而不像是 ext3 是採用格式化就先建立一定數量的 inode 配置

故下指令
#df -i 的時候會看到
inode的顯示為0

但是
#ls -li
還是會看到 inode number的顯示

故#df -i 沒有顯示inode count為正常現象

SUSE Linux 下觀察super block

SUSE Linux 下觀察super block

之前在Redhat 習慣使用dumpe2fs 來觀察super block
[root@localhost ~]# whatis dumpe2fs
dumpe2fs (8) - dump ext2/ext3 filesystem information

但是dumpe2fs為ext2/ext3 的filesystem 指令

所以如果要觀察reiserfs的 superblock
那就要使用
debugreiserfs /dev/裝置位置

SUSE Linux下的Vim

SUSE Linux下的Vim 預設沒有將backspace功能寫入
如果習慣使用Backspace
可以
#vi /etc/vimrc

set backspace=2

也可以順便把語法檢查開啟(取消前面的" 註解)
syntax on

就可以支援 backspace鍵的使用及語法檢查

SUSE Linux 下的lsattr and chattr

在 SUSE Linux上面預設使用reiserfs 檔案系統
對於有些人會使用lsattr 及 chattr會出現
lsattr: 不希望的裝置輸出入控制 (ioctl) While reading flags on /目錄名稱/檔案名稱

如果要使用lsattr 或chattr
Step 1:::
要確定該filesystem 有加上attrs的屬性
假設要在/data的目錄下使用, 裝置為/dev/sda6
#vi /etc/fstab
/dev/sda6 /data reiserfs acl,user_xattr,attrs 12

#mount
#mount -o remount /data
#mount

確定有attrs屬性掛載

Step2:
使用
#reiserfsck --clean-attributes /dev/sda6
輸入Yes確定要清除屬性

Step 3:
測試
#touch /data/test
#lsattr /data/test


Notes:
[root@localhost ~]# whatis lsattr
lsattr (1) - list file attributes on a Linux second extended file system
[root@localhost ~]# whatis chattr
chattr (1) - change file attributes on a Linux second extended file system

OpenSUSE 安裝來源

OpenSUSE 10.2的安裝來源

#yast2 inst_source
-->新增 --> Ftp --> 下一個
-->伺服器名稱: ftp.cs.pu.edu.tw
-->伺服器上得目錄: Linux/OpenSuse/distribution/10.2/repo/oss
-->下一個 -->會去檢查安裝來源並點選同意的協定
-->如此就可以新增安裝來源

#yast2 inst_source
-->新增 --> Ftp --> 下一個
-->伺服器名稱: ftp.cs.pu.edu.tw
-->伺服器上得目錄: Linux/OpenSuse/distribution/10.2/repo/non-oss
-->下一個 -->會去檢查安裝來源並點選同意的協定
-->如此就可以新增安裝來源
可以多利用靜宜大學的ftp來源
ftp://ftp.cs.pu.edu.tw/Linux/OpenSuse/distribution/10.2/repo/oss
ftp://ftp.cs.pu.edu.tw/Linux/OpenSuse/distribution/10.2/repo/non-oss

[轉貼]Novell decided to make ext3 the default file system in SUSE Linux Enterprise 11

全文link
http://www.novell.com/linux/filesystems/faq.html

大意是Novell 順應客戶的要求把default filesystem把ReiserFS 換成 EXT3

Frequently Asked Questions

Why has Novell decided to make ext3 the default file system in SUSE Linux Enterprise 11 instead of remaining with ReiserFS or choosing OCFS2?

This change is almost completely in response to recent customer demand. Novell is seeing increasing numbers of customers who prefer ext3 to ReiserFS, and our choice of default for SUSE Linux Enterprise 11 reflects this. Today, ext3 and ReiserFS v3 are mostly on par: ext3 has very recently gained some scalability enhancements (h-trees) and online expansion support (in SUSE Linux Enterprise Server 10). Furthermore, ext3 now features more than three years of journaling hardening, which makes it competitive with ReiserFS v3. OCFS2 is a parallel cluster file system designed for specific workloads, but it is unlikely that it will have root/boot support by SUSE Linux Enterprise 11. Finally, Novell is following the development of ext4, and expects it to become a solid nextgeneration enterprise file system.

Is Novell abandoning ReiserFS?

Not at all. Novell continues to support and improve ReiserFS v3. It is also included in mainline kernel distributions and will continue to receive enterprise support in future SUSE Linux Enterprise distributions. Customers who deploy SUSE Linux Enterprise Server 9 or SUSE Linux Enterprise 10—and determine that ReiserFS is best for their companies’ applications or service use cases—should use ReiserFS. Novell has always recommended using the best file system for the application or service. File systems seem to “live forever,” so ReiserFS v3 will be supported for the foreseeable future in SUSE Linux Enterprise distributions.

Why did SUSE Linux Enterprise use ReiserFS in the first place?

About seven years ago, SUSE needed an enterprise scalable journaled file system, and ReiserFS was the only one available. After arranging for support with NameSys (the Reiser development team) and building internal expertise, ReiserFS was the obvious choice. At that time, ext3 did not yet exist; it did not appear until about four years later. In addition, ext3 has only recently (within the last year) gained key enterprise-level features such as online expansion and scalability, which ReiserFS v3 has had for years.

After ReiserFS v4 is accepted in the mainline kernel, will Novell switch back to supporting it in future versions of SUSE Linux Enterprise?

While it is possible that Novell will support ReiserFS v4 in future enterprise deployments (when it is stable, enterprise worthy and included in the mainline kernel), it is unlikely that it will become the default installation choice.

Will Novell support ext4 in future versions of SUSE Linux Enterprise?

Novell anticipates that future versions of SUSE Linux Enterprise will support ext4, but only after it is accepted in the mainline kernel and is deemed enterprise worthy and stable. There are compatibility questions that still need to be resolved between ext3 and ext4 (for example, 48-bit block numbers), which will dictate when and how Novell supports this new file system.

Is this change in the default file system going to appear in the future service packs of SUSE Linux Enterprise 10?

No. Novell doesn't make default configuration changes in service packs. Doing so would cause too much disruption to customer deployments of SUSE Linux Enterprise 10.

There are other file systems included in SUSE Linux Enterprise 10 besides ReiserFS, ext3, XFS and OCFS2. Are they supported?

The other file systems are included for convenience and are not directly supported by Novell. Other vendors may offer support for these systems (for example, IBM for the JFS file system). In addition, there are third-party addon file systems (such as PolyServe or Symantec–Veritas), which are supported by their respective vendors on SUSE Linux Enterprise.

SUSE® Linux Enterprise : File System Support

File Systems in SUSE Linux Enterprise 10

The SUSE Linux Enterprise platform—including its related products, SUSE Linux Enterprise Server and SUSE Linux Enterprise Desktop—is the only Linux* distribution that offers broad out-of-the-box support for a number of file systems. In SUSE Linux Enterprise 10, Novell® provides enterprise support for the ReiserFS v3, ext3, XFS, and OCFS2 file systems. Each of these file systems has its strengths for specific types of applications and workloads. This gives customers more flexibility, enabling them to deploy the file system that best meets the needs of their existing environment. For a more detailed overview of file systems, including those delivered with SUSE Linux Enterprise 10, please refer to the Novell File System Primer

In SUSE Linux Enterprise 10 and prior versions, the best file system for scalability and all-around performance has been ReiserFS v3. For more specific uses, other file systems have been recommended. For example, OCFS2 is the recommended file system for organizations with Oracle* RAC workloads running on both SUSE Linux Enterprise Server 9 SP2 and the latest SUSE Linux Enterprise 10 release. Similarly, ext3 has been recommended for small file systems, typically those used in edge services in prior distributions. XFS has been recommended for large file systems that also contain large files (such as video rendering). Novell will continue to support all of these file systems well into the future.

File System Future Directions

Today’s open source developers expect organizations to communicate software changes as early as possible. Novell realizes this and is committed to keeping the community up to date. For the upcoming SUSE Linux Enterprise 11, Novell will be changing the default file system in new installations from ReiserFS v3 to ext3. The openSUSE™ builds will first reflect this change, starting with openSUSE 10.2. The openSUSE community builds provide the foundation for the next enterprise distribution release: SUSE Linux Enterprise 11.

什麼的注音方法

每次要輸入''什麼''這兩個字,注音輸入法老是會忘記
乾脆就把他寫在blog上面


http://www.edu.tw/EDU_WEB/EDU_MGT/MANDR/EDU6300001/allbook/kyjd/z4.html?open

將Linux 放進USB 隨身碟~~Slax Linux

最近有一個1GB的USB隨身碟閒置, 剛好今天做完星期一的論文摘要,
有一些空閒時間, 就想說利用時間玩一下USB 開機的Linux

找了一些文章, 後來發現帝國反抗君的Slax介紹比較符合自己的需求
http://blog.roodo.com/ystuan/archives/1327524.html

就想說來實作一下, 想不到還算很順利的成功呢^^

以下為Lab 步驟
O.S: Fedora core 6
USB 隨身碟: 1GB (假設裝置於/dev/sda,假設掛載目錄為/media/disk)

1.到SLAX 的下載頁面下載要使用SLAX版本(我選的是SLAX KillBill Edition v 5.1.8.1)
http://www.slax.org/download.php
下載回來的是 slax-killbill-5.1.8.1.iso 這個iso檔
假設下載的位置在/home/max/Desktop

2.參考在GNU/Linux上製作Slax USB的方法
網頁如下
http://os.newsforge.com/article.pl?sid=05/07/08/1522251

首先建立一個資料夾來掛載iso檔
＃mkdir /mnt/usb

將iso檔掛載到/mnt/usb
#mount -o loop /home/max/Desktop/slax-killbill-5.1.8.1.iso /mnt/usb/

將SLAX的檔案複製到USB 隨身碟上
#cp -ra /mnt/usb/* /media/disk

把核心及initrd 複製到USB 隨身碟下
#cd /media/disk/boot
#cp vmlinuz /media/disk
#cp initrd.gz /media/disk

將isolinux.cfg 重新命名為 syslinux.cfg
#cd /media/disk
#mv isolinux.cfg syslinux.cfg

修改syslinux.cfg的內容, 將原本有/boot 或是 boot路徑移除, 因為已經把vmlinuz 及initrd.gz複製到USB 隨身碟下面
#vim syslinux.cfg
原內容
label slax
kernel boot/vmlinuz
append vga=769 changes=slaxsave.dat max_loop=255 initrd=boot/initrd.gz init=linuxrc load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=4444 root=/dev/ram0 rw

label linux
kernel boot/vmlinuz
append vga=769 changes=slaxsave.dat max_loop=255 initrd=boot/initrd.gz init=linuxrc load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=4444 root=/dev/ram0 rw

修改為(就是把boot/ 或是 /boot的路徑去除)
label slax
kernel vmlinuz
append vga=769 changes=slaxsave.dat max_loop=255 initrd=initrd.gz init=linuxrc load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=4444 root=/dev/ram0 rw

label linux
kernel vmlinuz
append vga=769 changes=slaxsave.dat max_loop=255 initrd=initrd.gz init=linuxrc load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=4444 root=/dev/ram0 rw

使用syslinux 製作開機
#syslinux -s /dev/sda1

解決中文化的問題
到SLAX multilang modules 網頁下載modules
http://www.slax.org/modules.php?category=multilang
下載這三個
Taiwan(cht) input method - gcin
Taiwan(cht) Language Pack
CJK Display Support (optimized) 1.0
假設存放在/home/max/Desktop

將下載下來的 .mo檔 複製到 /media/disk/base 下面
#cp /home/max/Desktop/CJK_Display_Support_optimized_1_0-3.mo /media/disk/base
#cp /home/max/Desktop/Taiwan_cht_input_method_gcin_1172.mo /media/disk/base
#cp /home/max/Desktop/Taiwan_cht_Language_Pack_2006_0801.mo /media/disk/base


3.重開機,將電腦的BIOS設定為USB開機

enjoy it.......^^
以後走到哪裡都是Linux真是愉快

Beryl on Fedora core 6

今天去參加SA@Taipei的研討會
看到 jserv 大大的PDF 可旋轉以及可以在螢幕上書寫文字
就覺得很好用

問了一下~~~他是自己做的~~~
所以就回來找類似的功能~~爬了一下文
發現 Beryl 有類似的功能

參考以下網頁
http://cha.homeip.net/blog/archives/2006/12/_fc6_gnome_vist.html
http://blog.pixnet.net/kewang/post/3275525

後來使用 yum search beryl
發現Fedora core 6 就可以直接安裝
於是用
#yum install beryl-gnome

就會自動安裝, 總共裝了九個套件

啟動的方式
應用程式 -- 系統工具 -- Beryl Manager

就可以^^

自己喜歡的功能
1.滑鼠移到畫面右上角選取視窗
設定方式為
應用程式 -- 系統工具 -- Beryl Setting Manager (simple)
會出現 Hotcorners 選取右上角 --> 選取 Initiate

2.使用螢幕畫筆
設定方式為
應用程式 -- 系統工具 -- Beryl Setting Manager
其餘功能 --> 勾選註解 --> Shortcuts --> 工具 --> 自訂自己的快速鍵
由於IBM thinkpad R50e 沒有Windows 鍵(也就是他說的Super key)
故自己把他自訂為
Alt + z 啟動
Alt + x 啟動清除
Alt + c 清除全部

3.畫面放大縮小
應用程式 -- 系統工具 -- Beryl Setting Manager
輔助控制 --> 勾選 "匯入啟用縮放" --> shortcuts --> 組合鍵 --> 自訂自己的快速鍵
由於IBM thinkpad R50e 沒有Windows 鍵(也就是他說的Super key)
故自己把他自訂為
Ctrl + Shift + = 放大
Ctrl + = 縮小

^^
忙了一個晚上~~~終於搞定^^

Adobe Reader plug-in for firefox

之前安裝Adobe Reader 在閱讀網頁的PDF文件比較不方便
沒有像IE一樣預設可以嵌入瀏覽器內
故要安裝Plug-in for firefox
安裝方式
1.先安裝Adobe Reader for linux
2.cp /usr/local/Adobe/Acrobat7.0/Browser/intellinux/nppdf.so /usr/lib/mozilla/plugins/


這樣以後瀏覽就會嵌入網頁之內了
^^

新的rpm 儲存庫

最近在Fedora core 6安裝mplayer
發現freshrpms 少了一個lib 套件
所以就搜尋了一下官方網站
加上之前有使用Fedora core 6 的nvidia 在桌面上XGL安裝
所以找到這一個 extra 套件資料庫
網址如下
http://rpm.livna.org/rlowiki/UsingLivna

也可以直接使用

rpm -ivh http://rpm.livna.org/livna-release-6.rpm
來安裝