Posts Tagged ‘lenny’
Server
apt-get install nfs-kernel-server nfs-common portmap
Client
apt-get install nfs-common portmap
edit /etc/exports to identify the path to the directory you wish to share, and indicate the IP address(es) (use * as a wildcard) you wish to have access to you files.
/home/user/myfiles 192.168.0.*(rw,root_squash)
sudo exportfs -a
Access from Windows XP
Download the MS Unix layer and run self extractor and execute SfuSetup. click change the default behavior to case sensitive and enable set uid behavior select local username mapping server and password group files. copy /etc/passwd and /etc/group to your windows computer and specify path and reboot computer
run services for Unix administrations and in the NFS client make all user groups and others read and writable. open Windows Explorer under network places you should see a NFS tree, and within it you should see your servers IP address. if everything worked you should have access to your NFS directories via windows.
Access in Linux
To mount as root (create desired mount point first and replace IP with your servers IP):
mount 200.100.10.1:/home/nfs /mnt/nfs
to mount on boot edit/etc/fstab the extra options control read and write access by blocks)
200.100.10.1:/home/nfs /pub nfs rsize=8192,wsize=8192,timeo=14,intr
it should be noted that vfat and ntfs filesytems have issues with the nfs protocol and can result in sporadic performance and data corruption.
Download the netinst cd
Remove all partition tables on pendrive
Download boot image
As root preform (where as /dev/sdX is your USB device):
zcat boot.img.gz > /dev/sdX
Copy iso image to flashdrive
Plug the pendrive into the netbook and boot (hold escape at the bios splash to select the boot device). Begin install as normal. No network device will be found, select no etherent card and continue as normal. When it came to configuring apt I hit the go back button till I am asked if I want to continue without a network connection. The install will finish and reboot. Upon reboot you are presented with a base line system.
Format pendrive to ext3 and copy the 2.6.31 kernel image and headers packages; thanks to Robertalks.com
Login as root and mount flash drive and install the image first then the headers with dpkg. reboot and the 2.6.31 kernal will be the default on grub. Log into root again, plug in an ethernet cable connected to a router/modem and issue the command:
dhclient eth0
Check the connection by updating apt and see that all entries in the sources.list where found. Edit /etc/apt/sources.list with nano and add my favorite mirror.
deb http://mirror.its.uidaho.edu/pub/debian/ lenny main cont rib non-free
Apt-get update and upgrade and all is well. Now, install a basic X environment and configure
apt-get install x-window-system-core fluxbox
Xorg -configure
cp xorg.conf.net /etc/X11/xorg.conf
Install sudo with apt-get and configure
apt-get install sudo
visudo
Towards the end remove the comment from the %sudo line and replace NOPASSWD: with (All) and hit ctrl X to exit. Add the regular user to the sudo group
gpasswd -a myuser sudo
Exit root and login as regular user and edit .xinitrc
exec startfluxbox
Test X with the command startx and there should be a working fluxbox desktop.
Open up a terminal and type sudo tasksel. Select laptop and press ok, tasksell will then fetch all laptop related packages and configure them. Then I install synaptic, which has the added benefit of installing a general gtk enviroment for future gtk application. Also install gtk-theme-switch and gtk-engines. Type switch2 to adjust the gtk-theme for you X enviroment (I selected crux). Underneath applications system package management find synaptic. Upon running it the gksu dialog pops up; type in root (to change to sudo mode open terminal and type gksu-properties). With synaptic, install laptop-mode-tools laptop-net.
To get wireless access add to the /etc/apt/sources.list
deb http://www.backports.org/debian lenny-backports main contrib non-free
Update apt and install debian-backports-keyring and wicd. Afterwards add the user to the netdev group and restart dbus.
Sudo gpasswd -a user netdev.
Sudo /etc/init.d/dbus restart
Exit fluxbox and exit user. Log back in as user and startx. In the applications under network and monitor WICD is now listed. Click on it and it loads in the system tray. Right click and find the available wireless services.
to get sound working install alsa-utils and its dependencies. Then run sudo alsaconf and select hda-intel
add deb http://eeepc.debian.net/debian lenny main contrib non-free to /etc/apt/sources.list then:
wget http://eeepc.debian.net/debian/archive-key-eeepc.asc
sudo apt-key add archive-key-eeepc.asc
Install eeepc-acpi-scripts
To get the webcam to work first download the 2.6.31 source and install. Now, install v4l-conf dov4l gspca-source libpt-plugins-v4l2 gcc-4.2 and run as root:
I spent over 3 hours trying to get the webcam working with no luck. After walking away from it, I downgraded to the 2.6.30 image and headers found in the backports, and could see myself when I ran luvcview.However, the trade off is that my eth0 device is no longer availible, but I always connect with wireless with my netbook.
And now I have a basic environment in which I can start to install applications and configure my netbook. I will continue in another post to describe specific configurations to get the most out of Debian on the Asus eee PC 1005HA.
I wated some good hours trying to figure out how to get the Sansa Fuze tow work on my Debian Lenny Desktop. The first time I plugged it in it opened the device in Thunar and I dragged a folder of music into the MUSIC folder. I unplugged the Fuze and found the tags were not preserved. So I booted into windows and the files where not there, So I dragged them in again. Checked my fuse and I had two entries of the same music, one with the tags and one without the tags. Went back to Linux, plugged it in and it slowed down my file-system. So I did some research and some testing and many hours later I think I have this figured out.
The problem I was having is that the Fuze is set to autodetect the MTP and MSC/UMS practicals. I am 95% sure this is what screwed me up! So this is what I did. First I went into windows and updated my firmware via these instructions (if you don’t have windows access try these instructions) Now, went into the Fuze settings and formatted the device (the music I had on there was already on my computer). Next I entered the Fuze settings and found the USB mode and changed it from auto detect to MSC. Plugged it into my Debian Lenny Desktop and dragged my music into the Music folder, and did the same in Windows and all seems to work now.
Apparently using the device interchangeably between the two systems and using both practicals was a lethal combination, but everything seems to be working now and the salution is rather simple, but the cause of the problem was not as obvious. I had to spend a few hours bouncing from forum to forum hearing smiler problems, but non of the solutions worked for me. It should also be noted there are differences between the V01 and V02 firmware sets for the Fuze.
SSH allows you to remotely access your system through command line on Linux. When I was visiting family, one of the things I wanted to do with their home system was enable SSH access so that I could remotely login from my home computer 500 miles away to do any needed maintenance or troubleshooting. I had become exhausted by trying to troubleshoot Ubuntu over the telephone when they where having simple problems. The issue is that I speak techno babble, particularly the Linuxese dialect, and the speak the Microsoftish dialect of the layman. After I had them running with a basic desktop on Debian Lenny I did some research on SSH. The first thing to understand is the computer you wish to access with SSH is the host/server. The computer in which you are accessing the host/server is the Client. You first need to configure your host computer. The host needs to be running the SSH daemon.
sudo apt-get install openssh-server
you can edit the /etc/ssh/sshd_config file to indicate changes such as the port number to be used. This includes denying and granting access to specific users and groups. It is highly recommended to deny access to the user and group root:
DenyUsers root
DenyGroups root
if you wish to allow a specific user or group:
AllowUsers username
AllowGroups groupname
The user names and group names can be strung together and seperated by a space. Once finished save the file and exit. Restart the daemon
sudo /etc/init.d/ssh restart
Now your host server is completed and ready to be accessed from a remote computer. Use ifconfig to find your local network IP address, or alternatively you can use your that computer’s host. Generally Debian comes with the SSH client out of the box. You can double check to see if openssh-client is installed. To login to the host computer you use the ssh command and identify the user name and host:
ssh user@127.168.0.2
You will be prompted if you wish to continue connection (type yes) and then it will ask for the password for your user. Once succsessfully logined in you will be given a command line indicating the user and host name such as:
remote@fileserver:~$
Even though SSH sounds complicated, it is reletively easy to implement. There are varius configuration for tightened security one can try with SSH. One of the simplest security precautions is to change your port number in the /etc/ssh/sshd_config file. The SSH client will default to port 22. To specify a different port type:
ssh -p 188 remote@127.168.0.2
You are now ready to remote access your computer with SSH.
Following a modified instruction from Softlayer I was able to get my full 4gigs of ram recognized by Debian Lenny 32bit with the help of bigmem. I also had to install the bigmem linux-headers and nvidia-kernel.
sudo apt-get install linux-images-2.6-686 linux-headers-2.6.26-2-686-bigmem linux-image-2.6.26-2-686-bigmem nvidia-kernel-2.6.26-2-686-bigmem
I also had to download the proprietary nVidia driver and repeated these instructions. Reboot the system and check you memory ussage.
free -m




