天天看点

W-2 Grub4dos硬盘安装BackTrack

The quieter you become, the more you are able to hear ...

<a href="http://s2.51cto.com/wyfs02/M01/82/DC/wKioL1djU3GjqD9CAAPedq6pXvM763.jpg" target="_blank"></a>

硬盘安装BackTrack4 R2(Ubuntu内核版本2.6.35.8),需要作为Desktop使用的,最好预留10G以上的空间。

1.将ISO文件中的boot、casper目录拷贝到C盘。

2.将GRUB4DOS的grldr、grub.exe、menu.lst三文件拷贝到C盘的根目录下。

3.在BOOT.ini中加入c:\grldr="Load GRUB4DOS"条目,使启动菜单加载GRUB的启动项。

4.编辑menu.lst,加入如下条目

title Boot BackTrack 4 Image

kernel (hd0,0)/boot/vmlinuz BOOT=casper boot=casper nopersistent rw vga=0x317

initrd (hd0,0)/boot/initrd.gz

如果使用persistent替代nopersistent,则确保有SWEP分区,且卷标为casper-rw

5.重新启动进入BT系统后,点击桌面的install.sh执行安装 (umount -l /cdrom)。

安装过程中让BT4安装Bootloader,修改MBR,导致无法启动原有的windows操作系统,可以用windows的系统盘的命令修复模式,命令fixmbr来恢复原有的MBR信息。但此时要手动修复BT4R2的启动项。

准备好一款可以读取ext3分区的工具,如ext2explore.exe

打开ext2explore,打开BT4R2所在的ext3分区,浏览到/boot/grub/menu.lst

将其中对应的启动项记录下来,再添加到C盘根目录下的menu.lst中。

偶机器上得看起来如下:

title BackTrack 4 R2, kernel 2.6.35.8

uuid 50d1a882-d0b1-41fb-8960-792f9427d131

kernel (hd0,5)/boot/vmlinuz-2.6.35.8 root=UUID=50d1a882-d0b1-41fb-8960-792f9427d131 ro vga=0x317

initrd (hd0,5)/boot/initrd.img-2.6.35.8

其中(hd0,5)代表BT4R2是安装在E分区上的。

安装后,自动挂载NTFS分区

察看分区资料 fdisk -l|grep NTFS

备份fstab,cp /etc/fstab /etc/fstab.bak

编辑fstab,vim /etc/fstab

在最后一行加入

+last line-&gt; /dev/&lt;your partition&gt; /media/&lt;mount point&gt; ntfs-3g silent,umask=0,locale=en_US.utf8 0 0

同样确保

vim /etc/modules

+last line-&gt; fuse

            -&gt; lp

重启动下就OK了。需要手动加载的,直接用ntfs-3g命令映射

添加中文显示和中文输入

按如下步骤拷贝微软的字体(msyh.ttf  simhei.ttf  simkai.ttf  simsun.ttc)

#mkdir /usr/share/fonts/truetype/msfont

#cp *.ttf /usr/share/fonts/truetype/msfont

#cp *.ttc /usr/share/fonts/truetype/msfont

#fc-cache -fv

#localedef -i zh_CN -f GB18030 zh_CN

#localedef -i zh_CN -f GBK zh_CN

#localedef -i zh_CN -f UTF-8 zh_CN

#localedef -i zh_CN -f GB2312 zh_CN

#localedef -i zh_HK -f UTF-8 zh_CN

#vim /etc/environment

修改或添加

LC_CTYPE=zh_CN.UTF-8

LANG=zh_CN.UTF-8

输入法偶用的是fcitx(fcitx_3.6.0-1_i386.deb),在KDE下工作的很好

默认支持了TPLINK/WN322/422G+ 芯片。网上TPLINK/WN322和422G+有两个硬件版本,v1、v2,驱动是不一样的。v2版本用的是ath9k_htc的驱动。对应的内核也要在&gt;=2.6.35.原先的BT4R1是2.6.34内核,所以对v2的支持不好。本本原配的Wireless 2200BG却因为缺了Firmware无法驱动,可以从R1的版本中或网上直接下载IPW2200的firmware,偶下得ipw2200-fw-3.1.tgz,拷贝到了/lib/firmware的目录后,工作正常了。

Nvidia的linux支持比Ati的好许多,在Nvidia主站上下得NVIDIA-Linux-x86-275.43.run的最新驱动,安装让双屏显示,当然还要安装nvidia-settings的包(apt-get install nvidia-settings)。之后就可以在KDE桌面的System找到nvdia-settings的菜单项。

在menu.lst加入如下条目

title GParted

kernel (hd0,0)/live-hd/vmlinuz boot=live config union=aufs noswap noprompt vga=788 ip=frommedia live-media-path=/live-hd toram=filesystem.squashfs

initrd (hd0,0)/live-hd/initrd.img

BackTrack5安装问题总结:

在BackTrack5的ISO镜像,如果硬盘安装过程中umount -l /cdrom的话,会导致文件复制的异常,所以解决如下:

cd /

sudo mkdir halloocc

sudo umount -l /cdrom

sudo mount /dev/sda1 /halloocc

ls /halloocc | grep iso

sudo modprobe loop

sudo mount -o loop /halloocc/BT5-GNOME-32.iso /cdrom

sudo umount -l /halloocc

ls /cdrom

BIOS和系统时间同步问题的解决

sudo gedit /etc/default/rcS

将其中UTC=yes改成UTC=no

“Could not connect to wicd's D-Bus interface“的解决

root@bt:/# dpkg-reconfigure wicd

root@bt:/# update-rc.d wicd defaults

Browser's flashplayer plugin 的解决

BT5 (Ubuntu 10.04LTS) sources.list (Be available on 2013.8.25)

deb http://all.repository.backtrack-linux.org revolution main microverse non-free testing

deb http://32.repository.backtrack-linux.org revolution main microverse non-free testing

deb http://source.repository.backtrack-linux.org revolution main microverse non-free testing

(Be available on 2013.9.22)

deb http://ubuntu.uestc.edu.cn/ubuntu/ lucid main restricted universe multiverse

deb http://ubuntu.uestc.edu.cn/ubuntu/ lucid-backports restricted universe multiverse

deb http://ubuntu.uestc.edu.cn/ubuntu/ lucid-proposed main restricted universe multiverse

deb http://ubuntu.uestc.edu.cn/ubuntu/ lucid-security main restricted universe multiverse

deb http://ubuntu.uestc.edu.cn/ubuntu/ lucid-updates main restricted universe multiverse

Ubuntu 10.1 , sources.list (Be available on 2013.8.25)

deb http://old-releases.ubuntu.com/ubuntu/ maverick main restricted

deb http://old-releases.ubuntu.com/ubuntu/ maverick universe

deb http://old-releases.ubuntu.com/ubuntu/ maverick multiverse

deb http://old-releases.ubuntu.com/ubuntu/ maverick-updates main restricted

deb http://old-releases.ubuntu.com/ubuntu/ maverick-updates universe

deb http://old-releases.ubuntu.com/ubuntu/ maverick-updates multiverse

deb-src http://old-releases.ubuntu.com/ubuntu/ maverick main restricted

deb-src http://old-releases.ubuntu.com/ubuntu/ maverick universe

deb-src http://old-releases.ubuntu.com/ubuntu/ maverick multiverse

deb-src http://old-releases.ubuntu.com/ubuntu/ maverick-updates main restricted

deb-src http://old-releases.ubuntu.com/ubuntu/ maverick-updates universe

deb-src http://old-releases.ubuntu.com/ubuntu/ maverick-updates multiverse

deb http://mirror.lupaworld.com/ubuntu maverick main restricted universe multiverse

deb http://mirror.lupaworld.com/ubuntu maverick-security main restricted universe multiverse

deb http://mirror.lupaworld.com/ubuntu maverick-updates main restricted universe multiverse

deb http://mirror.lupaworld.com/ubuntu maverick-backports main restricted universe multiverse

deb-src http://mirror.lupaworld.com/ubuntu maverick main restricted universe multiverse

deb-src http://mirror.lupaworld.com/ubuntu maverick-security main restricted universe multiverse

deb-src http://mirror.lupaworld.com/ubuntu maverick-updates main restricted universe multiverse

deb-src http://mirror.lupaworld.com/ubuntu maverick-backports main restricted universe multiverse

编辑完 /etc/modprobe.d/blacklist.conf 需执行如下更新

update-initramfs -u

Different cards might manage this differently. Check /sys/class/backlight to find out.

Brightness can then be set (as root) with echo. Obviously you cannot go any higher than your screen's maximum brightness. The values for maximum brightness and brightness in general vary wildly among cards.

# echo 5 &gt; /sys/class/backlight/acpi_video0/brightness

If you see "device not managed" then probably your NIC is indeed not managed from network-manager. Please check the following file:

/etc/NetworkManager/nm-system-settings.conf

[ifupdown]

managed=?

if it's set to "false", switch it to "true", save the file and run a:

"sudo service network-manager restart"

本文转自Heartnight();博客51CTO博客,原文链接http://blog.51cto.com/181647568/1790163如需转载请自行联系原作者

tangjiashiertui

继续阅读