Hi Joel, >> > > > also shows a 'boot' fs like: >> > > > /dev/sda2 123699 66119 51193 57% /boot >> > > > /dev/sda5 1692128 1209236 396936 76% / >> The df -k outputs the following: >> [EMAIL PROTECTED] df -k >> Filesystem 1K-blocks Used Available Use% Mounted on >> /dev/sdb5 634472 111828 488794 19% / >> tmpfs 253184 0 253184 0% /dev/shm >> /dev/sdb2 118964 7558 105059 7% /boot >> /dev/sdb6 1047946 8243 983789 1% /home >> >> So that the string 2/linux points to /boot and inside /boot you can find: >> >> [EMAIL PROTECTED] ll /boot/ >> total 7559 >> drwxr-xr-x 3 root root 1024 May 16 08:16 . >> drwxr-xr-x 22 root root 1024 May 17 15:48 .. >> -rw-r--r-- 1 root root 997221 Apr 29 01:39 >> System.map-2.4.26-64-smp >> -rw-r--r-- 1 root root 25783 Apr 29 00:53 >> config-2.4.26-64-smp >> drwxr-xr-x 2 root root 12288 May 16 07:59 lost+found >> -rw-r--r-- 1 root root 95 Apr 29 01:39 >> patches-2.4.26-64-smp >> lrwxrwxrwx 1 root root 21 May 16 08:16 vmlinux -> >> vmlinux-2.4.26-64-smp >> -rw-r--r-- 1 root root 6666431 Apr 29 01:39 >> vmlinux-2.4.26-64-smp >> > ^^^^^^^ >hmm the installed kernel is the 64bit 'smp' one, is it of your choise or >a default?
not it is the default one for my ws, because it a 64bit architecture >I trust that you would be able to find the 'up' one and copy it in /boot >and reboot with it. > >> where ll alias is ll='ls -la --color=auto' > >Hmm yes I always though to ack ls src to allow l, ll, lsf, lsr, lsx links >to works ala hpux ;) alias ll='ls -la --color=auto' alias lm='ls -al |less' or |more if you prefer ;-P put the string in .bashrc of your user if you use the bash, you will obtain a colored (distingishing from dir, file, links...) layout. >hey c3k is the sister of my b2k and that remember me a pb for which I never >find the right way to solve: >Can you have a look in your /boot/config-2.4.26-64-smp and see if option >CONFIG_PDC_CONSOLE=y tonight I will check! I was thinking to public access to my system from work, but I have to bypass a double NAT of my provider! >This is set by default for D or K models iirc ><see my pb report >http://lists.parisc-linux.org/pipermail/parisc-linux/2004-January/022127.html> >Apparently Grant never encounter this same pb with it's c3k. > >I worked on a patch which worked fine when PDC_CONSOLE (/dev/ttyB0) was >actualy a serial one but not when a sti one (ie when kbd is the usb one >and I never find the right way to solve :_( ). More over, I don't have any >D or K model to test it and see if it had actualy sense? I created the /dev/ttyB0 on my system, then I tried to boot using the string console=/dev/ttyB0 (erasing the sti string in the palo), but it seemed not to work. Tonight I will try again. > >> Debian GNU/Linux testing/unstable thebeast ttyS0 >> >> thebeast login: >> >> This is successfully reached for when using laptop and serial console >> connection (minicom). >> >Ah well not exactely the same behavior as my b2k which was hanging at all >;? even via serial console? SteX
