Re: [gentoo-user-pl] amd64 - zmiana procesora
Witam, po zmianie sprzętu w pierwszej kolejności uruchom kompa z płytki Gentoo Live, potem zamontuj partycje ze swoim systemem i chroot /mnt/twój_system /bin/bash env-update. Potem zmien flagi i: emerge -e. Jesli wszystko pojdzie dobrze, bedziesz mógł odpalic swój system. -- Pozdrawiam, DeszczyK! 26-12-07, Tomasz Bakiera [EMAIL PROTECTED] napisał(a): Witam, prawdopodobnie zmienię nieco swoją maszynkę. Głównym problemem jest to, że istnieje szansa zmiany procesora z Semprona64 na coś Intela (również 64). I teraz pytanie mnie nurtujące: Obecnie moje flagi dla GCC to -k8 (architektura amd64), co zrobić, aby w przypadku podpięcia dysku do innej maszyny (już z Intelem na pokładzie), dystrybucja chodziła? Inaczej: jak przekompilować system 'k8', tak aby po zmianie procesora na Intelowskie 64, z sytemu można było kożystać ? Cz aby zapewnić zgodność to przekompilować system jako np. 686 ?? Nie bardzo wiem jak googlować, żeby znaleźć taką informację. -- Tomasz Bakiera -- Tysiace smiesznych filmikow z sieci. Sprawdz http://link.interia.pl/f1ca7 -- [EMAIL PROTECTED] mailing list -- Pozdrawiam, Michał Deszcz Nigdy nie kłóć się z głupcem. Sprowadzi Cię do swojego poziomu i pokona doświadczeniem.. z�e���+�f��)��+-
Re: [gentoo-user] Does this qualify as some bug ?
While trying to prevent 'net-dns/pdnsd' to listen on TCP and on to avoid TCP queries, I changed 'tcp_server' parameter to 'off' and 'query_method' parameter to 'udp_only' in /etc/pdnsd/pdnsd.conf . But when I restarted pdnsd I found it is still listening on TCP. I checked /etc/conf.d/pdnsd and found no option related to listening to 'TCP' set. So, then I checked /etc/init.d/pdnsd and I found that 'pdnsd' has been launched with '-t' command line argument (enables the TCP server thread. pdnsd will then serve TCP and UDP queries.) . So to disable, I need to append '--notcp' to PDNSDCONFIG in /etc/conf.d/pdnsd. So I think, listening shouldn't be made by default, even if it is, then it should be in configuration file, not in init.d script . Since noone answered, I'll try. I'm not into the details of your problem but I have the impression your suggestion should be stated to the pdnsd developing community, not on gentoo. I'd qualify it as bug, but YMMV, and again, I don't know much about it. ralf -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Does this qualify as some bug ?
Hello On Thu, Dec 27, 2007 at 08:20:37PM +0100, Ralf Stephan wrote: While trying to prevent 'net-dns/pdnsd' to listen on TCP and on to avoid TCP queries, I changed 'tcp_server' parameter to 'off' and 'query_method' parameter to 'udp_only' in /etc/pdnsd/pdnsd.conf . But when I restarted pdnsd I found it is still listening on TCP. I checked /etc/conf.d/pdnsd and found no option related to listening to 'TCP' set. So, then I checked /etc/init.d/pdnsd and I found that 'pdnsd' has been launched with '-t' command line argument (enables the TCP server thread. pdnsd will then serve TCP and UDP queries.) . So to disable, I need to append '--notcp' to PDNSDCONFIG in /etc/conf.d/pdnsd. So I think, listening shouldn't be made by default, even if it is, then it should be in configuration file, not in init.d script . Since noone answered, I'll try. I'm not into the details of your problem but I have the impression your suggestion should be stated to the pdnsd developing community, not on gentoo. I'd qualify it as bug, but YMMV, and again, I don't know much about it. If it is a problem of init script, then it is problem in gentoo. Init scripts are distribution specific (at last, gentoo has different ones that other distros AFAIK). So, if you think it is a bug, put it into bugzilla. In the best case, someone will do something about it. In the worst case, the bug will be marked as invalid, wontfix, or something like that. Just don't get annoyed if someone simply tells it is nonsense, the people going trough bugs have too many of them and they are not always completely nice. -- BOFH Excuse #430: Mouse has out-of-cheese-error Michal 'vorner' Vaner pgpMLXdP9W7oG.pgp Description: PGP signature
Re: [gentoo-user] Does this qualify as some bug ?
,--[ On Thu, Dec 27, 2007 at 08:20:37PM +0100, Ralf Stephan wrote: | While trying to prevent 'net-dns/pdnsd' to listen on TCP and on to | avoid TCP queries, I changed 'tcp_server' parameter to 'off' and | 'query_method' parameter to 'udp_only' in /etc/pdnsd/pdnsd.conf . But | when I restarted pdnsd I found it is still listening on TCP. I checked | /etc/conf.d/pdnsd and found no option related to listening to 'TCP' | set. So, then I checked /etc/init.d/pdnsd and I found that 'pdnsd' has | been launched with '-t' command line argument (enables the TCP server | thread. pdnsd will then serve TCP and UDP queries.) . So to disable, I | need to append '--notcp' to PDNSDCONFIG in /etc/conf.d/pdnsd. So I | think, listening shouldn't be made by default, even if it is, then it | should be in configuration file, not in init.d script . | | Since noone answered, I'll try. I'm not into the details of your | problem but I have the impression your suggestion should be stated | to the pdnsd developing community, not on gentoo. I'd qualify it as | bug, but YMMV, and again, I don't know much about it. Let me elaborate it a bit: pdnsd is a DNS server capable of listening on TCP/UDP ports (depending on options in configuration file and commandline). Options set on commandline override what is set is configuration file. And, in init script of this port, the option to listen on TCP ports, i.e. '-t' switch, has been explicitly passed. So, there is no way, one can disable listening on TCP from pdnsd.conf. So one, has to edit '/etc/conf.d/pdnsd' and add --notcp option. In my view, from the point-of least privileges, one has to explicitly turn on listening of daemon on port. So its a problem on Gentoo porting side, not with the pdnsd team. Thanks. -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- signature.asc Description: Digital signature
Re: [gentoo-user] 2.6.23 and xorg delayed startup
Michael George wrote: I just upgraded my kernel from 2.6.19 to 2.6.23 and it takes almost a minute for X to start now. I have changed window managers (normally ctwm, tested with twm) with the same results. I rebooted the 2.6.19 kernel and X fires right up as expected. Booting back to 2.6.23 and it's excruciatingly long. I saw some prior posts which indicated a network problem, but in that case the OP said that the loopback interface wasn't up. I checked my system (ifconfig) and both lo and eth0 are up and running. I see that you checked if it was up, but have you pinged 127.0.0.1? Also, could you possibly have firewall rules setup blocking things on lo? It's a shot in the dark but sometimes the oddest of problems have the simplest of solutions. HTH Eric -- [EMAIL PROTECTED] mailing list
[gentoo-user] Which kernel option - PCnet32 driver
In compiling a kernel for a vmware installation I'm not sure which kernel option (2.6.23) under `Network Device Support' in make menuconfig dialog is responsible for the pcnet32 driver. None of the names there give it away. Dmesg sees it like this: eth0: registered as PCnet/PCI II 79C970A So the closest match I see is: PCI NE2000 and clones support (see help) At least it contains PCI and nothing else seems to. Anyone know if that is it? -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: Which kernel option - PCnet32 driver
[EMAIL PROTECTED] writes: So the closest match I see is: PCI NE2000 and clones support (see help) At least it contains PCI and nothing else seems to. Anyone know if that is it? Never mind... after more digging I found it at: Device Drivers - Network device support --- [*] Ethernet (10 or 100Mbit) --- M AMD PCnet32 PCI support -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] 2.6.23 and xorg delayed startup
On Fri, Dec 28, 2007 at 10:18:55AM -0500, Eric Martin wrote: Michael George wrote: I just upgraded my kernel from 2.6.19 to 2.6.23 and it takes almost a minute for X to start now. I have changed window managers (normally ctwm, tested with twm) with the same results. I rebooted the 2.6.19 kernel and X fires right up as expected. Booting back to 2.6.23 and it's excruciatingly long. I saw some prior posts which indicated a network problem, but in that case the OP said that the loopback interface wasn't up. I checked my system (ifconfig) and both lo and eth0 are up and running. I see that you checked if it was up, but have you pinged 127.0.0.1? Also, could you possibly have firewall rules setup blocking things on lo? It's a shot in the dark but sometimes the oddest of problems have the simplest of solutions. Yes, it's up. However, I think this error is a wild goose... I rebooted to the 2.6.19 kernel and started X. It came right up, and this was the output of startx startx.2.6.19 21: xauth: creating new authority file /home/george/.serverauth.6547 X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: UNKNOWN Current Operating System: Linux brego 2.6.19-gentoo-r5 #5 SMP PREEMPT Thu Mar 8 19:16:48 EST 2007 x86_64 Build Date: 22 December 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 27 20:30:12 2007 (==) Using config file: /etc/X11/xorg.conf (II) Module already built-in (II) Module already built-in (II) Module already built-in (II) Module already built-in (II) Module already built-in (EE) MGA(0): Static buffer allocation failed, not initializing the DRI (EE) MGA(0): Need at least 15360 kB video memory at this resolution, bit depth (EE) MGA(1): Not initializing the DRI on the second head (EE) AIGLX: Screen 0 is not DRI capable (EE) AIGLX: Screen 1 is not DRI capable Couldn't establish a connection to :9202: IO::Socket::INET: Bad hostname ':9202' access control disabled, clients can connect from any host SetClientVersion: 0 9 ctwm: unable to find bitmap ctwm: unable to find bitmap ctwm: unable to find bitmap X Error: BadWindow (invalid Window parameter) Major Opcode: 4 fetchmail: background fetchmail at 6646 killed. xscreensaver: 20:30:27: SIGHUP received: restarting... xscreensaver: 20:30:27: running as george/george (500/500) waiting for X server to shut down XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0 after 0 requests (0 known processed) with 0 events remaining. Console: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0 xterm: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0 xterm: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0 SchedTerm: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0 SchedTerm: fatal IO error 32 (Broken pipe) or KillClient on X server :0.0 FreeFontPath: FPE /usr/share/fonts/misc refcount is 2, should be 1; fixing. Notice the 9202 error line. I then rebooted back into 2.6.23 and started X with startx startx.2.6.23 21. It took 1-2min to for me to get my window environment, and here is the output of that run: xauth: creating new authority file /home/george/.serverauth.6950 X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: UNKNOWN Current Operating System: Linux brego 2.6.23-gentoo-r3 #3 SMP PREEMPT Sun Dec 23 21:35:17 EST 2007 x86_64 Build Date: 22 December 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 27 20:32:51 2007 (==) Using config file: /etc/X11/xorg.conf (II) Module already built-in (II) Module already built-in (II) Module already built-in (II) Module already built-in (II) Module already built-in (EE) MGA(0): Static buffer allocation failed, not initializing the DRI (EE) MGA(0): Need at least 15360 kB video memory at this resolution, bit depth (EE) MGA(1): Not initializing the DRI on the second head (EE) AIGLX: Screen 0 is not DRI capable (EE) AIGLX: Screen 1 is not
[gentoo-user] Unsubscription
Can i please get some help unsubscribing from this mailing list please? Send instant messages to your online friends http://au.messenger.yahoo.com -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Unsubscription
Can i please get some help unsubscribing from this mailing list please? Send instant messages to your online friends http://au.messenger.yahoo.com -- [EMAIL PROTECTED] mailing list http://www.gentoo.org/main/en/lists.xml Go read. Please. -Kristian Herkild -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Unsubscription
Kelly Stewart wrote: Can i please get some help unsubscribing from this mailing list please? Send instant messages to your online friends http://au.messenger.yahoo.com Send a blank email (no subject necessary) to: [EMAIL PROTECTED] That should do it. Tony -- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: how would I use device names in fstab?
On Thu, 27 Dec 2007 13:31:17 +, Stroller wrote: I'm not seeing any critical error messages in your output - could you perhaps explain what the problem is exactly? I'll post some details later tonight, but data discs, blank media or music cd's -- none work. When I boot into Fedora on the same machine, both drives (CD-ROM and CD-R/W) work fine. -Thufir -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Unsubscription
On Freitag, 28. Dezember 2007, Kelly Stewart wrote: Can i please get some help unsubscribing from this mailing list please? Send instant messages to your online friends http://au.messenger.yahoo.com look at the raw code of the messages from the list, it is even written there: List-Post: mailto:gentoo-user@lists.gentoo.org List-Help: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Subscribe: mailto:[EMAIL PROTECTED] List-Id: Gentoo Linux mail gentoo-user.gentoo.org -- [EMAIL PROTECTED] mailing list
[gentoo-user] Memory stick problem
All - I am having a problem with my USB thumb drive. If the drive is connected to the system on boot, the device file /dev/sdb is created, and I'm able to mount and use my thumb drive normally. If I remove the thumb drive and then replace it, or attach the thumb drive after the system has booted, the device file is not created. Does anyone have any ideas as to what may be causing this? I have tried a kernel with the USB drivers compiled into the kernel and compiled as modules, and I get the same thing. The output of dmesg is as follows: usb 1-4: new high speed USB device using ehci_hcd and address 4 ehci_hcd :00:1d.7: port 4 high speed ehci_hcd :00:1d.7: GetStatus port 4 status 001005 POWER sig=se0 PE CONNECT usb 1-4: config 1 interface 0 altsetting 0 endpoint 0x83 has an invalid bInterval 200, changing to 11 usb 1-4: default language 0x0409 usb 1-4: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-4: Product: Actions Mtp Device 01 usb 1-4: Manufacturer: Actions Semiconductor Co., Ltd. usb 1-4: SerialNumber: 6D621ABF495E2A428FBF6E6C854E549D DEV: registering device: ID = '1-4' PM: Adding info for usb:1-4 bus usb: add device 1-4 usb 1-4: uevent usb: Matched Device 1-4 with Driver usb usb: Probing driver usb with device 1-4 usb 1-4: usb_probe_device DEV: registering device: ID = 'usbdev1.4_ep00' PM: Adding info for No Bus:usbdev1.4_ep00 usb 1-4: configuration #1 chosen from 1 choice usb 1-4: adding 1-4:1.0 (config #1, interface 0) DEV: registering device: ID = '1-4:1.0' PM: Adding info for usb:1-4:1.0 bus usb: add device 1-4:1.0 usb 1-4:1.0: uevent usb 1-4:1.0: uevent DEV: registering device: ID = 'usbdev1.4_ep01' PM: Adding info for No Bus:usbdev1.4_ep01 DEV: registering device: ID = 'usbdev1.4_ep82' PM: Adding info for No Bus:usbdev1.4_ep82 DEV: registering device: ID = 'usbdev1.4_ep83' PM: Adding info for No Bus:usbdev1.4_ep83 DEV: registering device: ID = 'usbdev1.4' PM: Adding info for No Bus:usbdev1.4 drivers/usb/core/inode.c: creating file '004' bound device '1-4' to driver 'usb' usb: Bound Device 1-4 to Driver usb Any help with this issue would be greatly appreciated. Regards, James -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] moving my instalation to new hard drive
Dear All, Thanks for the advice. I just successfully completed the transfer of my gentoo installation to the new hard drive. I was able to install grub on the external drive successfully, obviating the need to boot with the live cd after swaping the drives. I did however have one problem with the dev/ being a little messed up, but I followed the instructions in the /etc/issue file and that fix the problem, as far as I can tell :-) Cheers Matt -- %%% Dr. Matthew R. Lee CASEB ECIM Departamento de Ecologia, P. Universidad Catolica de Chile, Alameda 340, Santiago. CP 6513677 CHILE [EMAIL PROTECTED] [EMAIL PROTECTED] URL: meiochile.matthewlee.org %%% -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] rsync for backup, can anybody help
symlink /mnt/external/OneFileSystemBackup/usr/i686-pc-linux-gnu/lib/libopcodes.so - /usr/lib32/binutils/i686-pc-linux-gnu/2.18/libopcodes.so failed: Operation not permitted (1) This is most likely caused by the FAT filesystem on the target device. Just like a lot of other errors, probably. Symlinks do not exist on a regular FAT. Copying data from a unix/linux-ish filesystem to a FAT-based filesystem is impossible without losing something (special files like symlinks, sockets, devices etc., file ownership info and more). Maybe there are some modern FAT variations capable of storing all this linux-specific data (thinking of umsdos), but I dare doubt that's the case of your backup drive. If you're thinking of maybe recovering some important system files from this backup sometime, change the backup drive's filesystem to something more capable (the aforementioned ext2, for instance). -rz -- [EMAIL PROTECTED] mailing list
[gentoo-user] No help on annoying `sandbox' error
I'm having a continuing annoying problem from sandbox trying to write out of its crib. I've posted here twice before but caught no ones attention. Possibly this is something screamingly obvious and people just ignored the posts. `sandbox' doesn't like my root .bash_history. ACCESS DENIED open_rd: /root/.bash_history ACCESS DENIED open_rd: /root/.bash_history I see nothing really like this on bugzilla although their are other access violations there. I guess it needs to be turned in as a bug but fisrst tell me if its really a bug or something to do with my ill-informed setup. It happens with any usage of emerge and unless I rename /usr/bin/sandbox or remove /root/.bash_history, `sanbox' will block any emerge action. Renaming it seems the easiest, then portage reports the problem but continues anyway. I tried making bash write it history to something else like BASH_HITORY but sandbox tracks it down and squawks about BASH_HISTORY then. `file' reports .bash_history to be the expected `ascii text file' If I delete bash_history and there is a complex emerge underway like updating world, then sooner or later bash writes a new one and emerge screeches to a halt. I'm sorry but I couldn't really make much sense of the sandbox bugs on bugzilla or what to do about my problem. -- [EMAIL PROTECTED] mailing list
[gentoo-user] ksh(93) emerge failure
On a new install with profile `hardened/x86/2.6'. I'm finding that
ksh will not emerge successfully. The closing error is not very
enlightening, at least not to me:
* Messages for package app-shells/ksh-93.20040229:
* ERROR: app-shells/ksh-93.20040229 failed.
* Call stack:
*ebuild.sh, line 1701: Called dyn_compile
*ebuild.sh, line 1039: Called qa_call 'src_compile'
*ebuild.sh, line 44: Called src_compile
* ksh-93.20040229.ebuild, line 51: Called die
* The specific snippet of code:
* cd ${S}; ./bin/package only make ast-ksh CC=$(tc-getCC) || die
* The die message:
* (no error message)
In the days before ksh93 (circa 2003/4) was an ebuild (or maybe I just
didn't know it was) it was a right pain to build and install it by
hand.
I've never understood the unusual build process of the KORN tools and
I see emerge go thru truly massive work to build it too. So the
chances of me finding what went wrong is just about non-existent.
Near as I can tell the closest thing to a similar bug that got
reported was in 2004 and it appears the only helpfull part of that was
setting `nls' as one of the USE items.
emerge is using `nls' and `-static' here. `nls' enables native
language support using gettext which I do have installed, also with
`nls' use set.
==
I've just noticed something by running `emerge -vDp ksh', it wants a
different compiler than I have installed.
gcc-4.1.1-r3 got installed when I started building up this new system.
ksh apparently wants:
[ebuild NS ] sys-devel/gcc-3.4.6-r2 USE=hardened nls (-altivec)
-bootstrap -boundschecking -build -d -doc -fortran -gcj -gtk -ip28
-ip32r10k -multilib -multislot (-n32) (-n64) -nocxx -nopie -nossp
-objc -test -vanilla
as a `Deep' dependancy.
Will I be really messing up my new system if I install two version of
gcc? And secondly how does the right one get used for ksh?
I can live without ksh of course but I do have quite a few homemade
scripts that depend on ksh. Many of them will need some recoding even
to use pdksh as I recall.
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] ksh(93) emerge failure
Will I be really messing up my new system if I install two version of gcc? And secondly how does the right one get used for ksh? I believe you can maintain two different gcc versions (3.x and 4.x) with the multislot USE flag. A gentoo tool is provided for you to switch between the versions, but I'm not sure if ksh would recognize which gcc to use. AFAIK, installing both gcc 3.x and 4.x has little effect if you know exactly what you're doing. Anyway, good luck on getting that to work mate. Hieu, Luu Danh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] 2.6.23 and xorg delayed startup
On Fri, Dec 28, 2007 at 01:47:53PM -0500, Michael George wrote:
Notice there is little difference between them. I think I need to trim
out my .xinitrc file and see if there is something I'm starting from
there that is causing the delay with a different kernel...
I don't see anything in my .xinitrc file that would be causing the
problem. Here are the contents of that file:
#!/bin/sh
DISPLAY=${DISPLAY-unix:0}; export DISPLAY
RDISPLAY=${RDISPLAY-`hostname`:0}; export RDISPLAY
# I've tried taking this line out and it doesn't speed anything up...
sh /usr/local/src/ltsp-server-pkg-static-0.1/xsession-lbus-start
# Change the keys around
xmodmap .xmodmap.pass1
xmodmap .xmodmap.pass2
# Load .Xdefaults into the X resource database
xrdb -nocpp -display $DISPLAY -load .Xdefaults
# Start a console window. This line should not be removed.
xterm -T Console -n Console -name Console -C -iconic +vb -geometry =80x14-0+0
# Start another xterm
xterm -display $DISPLAY -geometry 80x50+0-0 -T Shell -n Shell
sleep 1
xterm -display $DISPLAY -geometry 80x50-1280-0 -T Shell -n Shell
# Start a terminal for the schedule screen
xterm -display $DISPLAY -name SchedTerm -geometry 80x50+0-0 -T Shell -n
Shell
sleep 1
xterm -display $DISPLAY -name SchedTerm -geometry 80x50-1280-0 -T Shell -n
Shell
xcalendar -name xIdeal -display $DISPLAY
gkrellm
xload -display $DISPLAY
gkrellm2 -c secondary
xcalendar -name xHopper11 -display $DISPLAY
xdaliclock
# open up my planner
xcalendar -display $DISPLAY
# Set the background
# I've run this script manually and it doesn't take long at all to run
(sleep 1; $HOME/bin/background)
#turn on the screensaver
xscreensaver
#disable access control
xhost +
# Make the mouse move a little faster than normal
xset m 3 4
# Make the keys repeat more quickly
xset r rate 300 20
# start fetchmail
fetchmail
#Start the window manager
ctwm
#fix keyboard
/usr/bin/kbd_mode -a
# stop fetchmail
fetchmail --quit
#clear
There isn't anything there that I can see which would cause the 2min.
delay in even getting an X mouse pointer...
I'm leaning toward some strange type of Xorg -- kernel interaction,
but I'm not sure what it might be...
--
-M
There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.
--
[EMAIL PROTECTED] mailing list
