Re: [gentoo-user] udev-140
On Tuesday 17 March 2009 00:52:16 Paul Hartman wrote: So Putty doesn't really suck in isolation. It does work and can really operate any different way. Using Putty on it's host platform sucks to someone who is used to much more efficient way to accomplish the same task. Have you tried simply using openssh on Windows? Or is cmd.exe really the problem? I prefer Putty because I can more easily copy and paste, resize the window, scrollback, etc. versus the cmd.exe shell (which is basically useless). I'm sure there are alternative windows command shells (or you can use rxvt or something with cygwin) This was the first time I had actually done something useful on Windows (apart from a quick browser surf here and there) for about a year. It's my girlfriend's machine and has putty so I used it. I'm in the lucky position of not needing Windows for anything whatsoever, so the annoyance of navigating putty once a year is far better than trying to install something else more to my liking (which I would never use of course) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] udev-140
On Montag 16 März 2009, Alan McKinnon wrote: A quick heads-up if you upgrade to the latest udev in portage. Don't do what I did and postpone the etc-update step till later, forget about it in the rush of trying to get work done, and then need to reboot. When the machine boots, sysfs does not mount, the proc init script fails and everything thereafter fails. I suppose it's possible to boot into single user mode and manually edit the files in /etc. But in my case it was not at all obvious that this was what I had to do. I had to boot off a rescue USB stick and chroot to see what was happening. me too - and it wasn't even a voluntary reboot. I stepped on the switch of the power chord - and first I thought my raid was fucked up :( Luckily I have an usb stick with systemrescuecd on it around - booted from it, mounted everything, chroot+cfg-update But it sucked. A lot. devfs never was such troublesome.
Re: [gentoo-user] udev-140
Volker Armin Hemmann wrote: On Montag 16 März 2009, Alan McKinnon wrote: A quick heads-up if you upgrade to the latest udev in portage. Don't do what I did and postpone the etc-update step till later, forget about it in the rush of trying to get work done, and then need to reboot. When the machine boots, sysfs does not mount, the proc init script fails and everything thereafter fails. I suppose it's possible to boot into single user mode and manually edit the files in /etc. But in my case it was not at all obvious that this was what I had to do. I had to boot off a rescue USB stick and chroot to see what was happening. me too - and it wasn't even a voluntary reboot. I stepped on the switch of the power chord - and first I thought my raid was fucked up :( Luckily I have an usb stick with systemrescuecd on it around - booted from it, mounted everything, chroot+cfg-update But it sucked. A lot. devfs never was such troublesome. Hey guys , always read post emerge messages!! Portage always tells me when to update config files! signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] udev-140
On Monday 16 March 2009 21:30:19 Volker Armin Hemmann wrote: On Montag 16 März 2009, Alan McKinnon wrote: A quick heads-up if you upgrade to the latest udev in portage. Don't do what I did and postpone the etc-update step till later, forget about it in the rush of trying to get work done, and then need to reboot. When the machine boots, sysfs does not mount, the proc init script fails and everything thereafter fails. I suppose it's possible to boot into single user mode and manually edit the files in /etc. But in my case it was not at all obvious that this was what I had to do. I had to boot off a rescue USB stick and chroot to see what was happening. me too - and it wasn't even a voluntary reboot. I stepped on the switch of the power chord - and first I thought my raid was fucked up :( Luckily I have an usb stick with systemrescuecd on it around - booted from it, mounted everything, chroot+cfg-update But it sucked. A lot. devfs never was such troublesome. I'll say :-) Actually, sometimes I think MKNOD was really cool and just do everything static. I wouldn't really have minded the inconvenience, except that while all this was going on, the largest data centre in the Southern Hemisphere was dropping off the air one router at a time, my desktop machine was panicing after 4 minutes of use (so that's why I stopped using it 6 months ago!) and I had to use putty on the GF's Thinkpad to do my bit to rescue all this. Putty sucks, really badly. The only thing that sucks worse than Putty on Windows is Putty on Symbian, even on a Nokia Communicator with a semi-decent keyboard (for a phone) :-) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] udev-140
On Montag 16 März 2009, Justin wrote: Volker Armin Hemmann wrote: On Montag 16 März 2009, Alan McKinnon wrote: A quick heads-up if you upgrade to the latest udev in portage. Don't do what I did and postpone the etc-update step till later, forget about it in the rush of trying to get work done, and then need to reboot. When the machine boots, sysfs does not mount, the proc init script fails and everything thereafter fails. I suppose it's possible to boot into single user mode and manually edit the files in /etc. But in my case it was not at all obvious that this was what I had to do. I had to boot off a rescue USB stick and chroot to see what was happening. me too - and it wasn't even a voluntary reboot. I stepped on the switch of the power chord - and first I thought my raid was fucked up :( Luckily I have an usb stick with systemrescuecd on it around - booted from it, mounted everything, chroot+cfg-update But it sucked. A lot. devfs never was such troublesome. Hey guys , always read post emerge messages!! Portage always tells me when to update config files! yes, but that does not help you in case of an accidental power failure before you had a chance to update the config files.
Re: [gentoo-user] udev-140
Volker Armin Hemmann wrote: yes, but that does not help you in case of an accidental power failure before you had a chance to update the config files. power failure is always something extra ordinary! signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] udev-140
On Mon, Mar 16, 2009 at 2:40 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On Monday 16 March 2009 21:30:19 Volker Armin Hemmann wrote: On Montag 16 März 2009, Alan McKinnon wrote: A quick heads-up if you upgrade to the latest udev in portage. Don't do what I did and postpone the etc-update step till later, forget about it in the rush of trying to get work done, and then need to reboot. When the machine boots, sysfs does not mount, the proc init script fails and everything thereafter fails. I suppose it's possible to boot into single user mode and manually edit the files in /etc. But in my case it was not at all obvious that this was what I had to do. I had to boot off a rescue USB stick and chroot to see what was happening. me too - and it wasn't even a voluntary reboot. I stepped on the switch of the power chord - and first I thought my raid was fucked up :( Luckily I have an usb stick with systemrescuecd on it around - booted from it, mounted everything, chroot+cfg-update But it sucked. A lot. devfs never was such troublesome. I'll say :-) Actually, sometimes I think MKNOD was really cool and just do everything static. I wouldn't really have minded the inconvenience, except that while all this was going on, the largest data centre in the Southern Hemisphere was dropping off the air one router at a time, my desktop machine was panicing after 4 minutes of use (so that's why I stopped using it 6 months ago!) and I had to use putty on the GF's Thinkpad to do my bit to rescue all this. Putty sucks, really badly. The only thing that sucks worse than Putty on Windows is Putty on Symbian, even on a Nokia Communicator with a semi-decent keyboard (for a phone) :-) What sucks about PuTTY on Windows? I use it all the time and it seems to do everything... Granted, I just use it for simple serial port devices and SSH stuff, no exotic terminal emulations. PuTTY on Symbian only does SSH but it seems to do it well enough. Running it full-screen with the smallest font is actually not so bad, even on my 240x320 screen. Being able to connect to my computer wherever I have a cellular signal is convenient... typing with T9 on a numeric phone keypad, not so much... but that's the phone's fault, not PuTTY's. :P I've been meaning to set up a simple menu script that allows me to run all of my common tasks with phone-friendly keystrokes. emerge -uDvptN blah blah blah really sucks to tap out on the 0-9 keys :) Thank god for bash command history...
Re: [gentoo-user] udev-140
On Monday 16 March 2009 22:20:37 Paul Hartman wrote: I wouldn't really have minded the inconvenience, except that while all this was going on, the largest data centre in the Southern Hemisphere was dropping off the air one router at a time, my desktop machine was panicing after 4 minutes of use (so that's why I stopped using it 6 months ago!) and I had to use putty on the GF's Thinkpad to do my bit to rescue all this. Putty sucks, really badly. The only thing that sucks worse than Putty on Windows is Putty on Symbian, even on a Nokia Communicator with a semi-decent keyboard (for a phone) :-) What sucks about PuTTY on Windows? I use it all the time and it seems to do everything... Granted, I just use it for simple serial port devices and SSH stuff, no exotic terminal emulations. Putty itself isn't too bad if you look at it as a Windows app. It can never be anything other than a Windows app and as such is restricted to how Windows apps must behave. And therein is the problem - I'm way too used to openssh, I want a command line to fire up my ssh client, I want to 'ssh m...@there' in a console and it must work. I don't want to have to poke around in a vast tree structure to enter my options - I know what they are, I just want to type them. Without a mouse. So Putty doesn't really suck in isolation. It does work and can really operate any different way. *Using* Putty on it's host platform sucks to someone who is used to much more efficient way to accomplish the same task. PuTTY on Symbian only does SSH but it seems to do it well enough. Running it full-screen with the smallest font is actually not so bad, even on my 240x320 screen. Being able to connect to my computer wherever I have a cellular signal is convenient... typing with T9 on a numeric phone keypad, not so much... but that's the phone's fault, not PuTTY's. :P I've been meaning to set up a simple menu script that allows me to run all of my common tasks with phone-friendly keystrokes. emerge -uDvptN blah blah blah really sucks to tap out on the 0-9 keys :) Thank god for bash command history... On Symbian it's a life saver when all other methods fail. Again, Putty is OK, using the device is actually what sucks. I still can't find a pipe character! And the screen is almost unreadable (it wasn't three years ago...) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] udev-140
Justin wrote: Volker Armin Hemmann wrote: yes, but that does not help you in case of an accidental power failure before you had a chance to update the config files. power failure is always something extra ordinary! It's not here. Our power goes out sometimes just because the wind is blowing. I think it is about time for them to start trimming trees again. Trees and power lines don't go together to well. Dale :-) :-)
Re: [gentoo-user] udev-140
On Mon, 16 Mar 2009 22:34:44 +0200, Alan McKinnon wrote: And the screen is almost unreadable (it wasn't three years ago...) Pixels shrivel with age ;-) -- Neil Bothwick Fasten your seatbelt ... I wanna try something. signature.asc Description: PGP signature
Re: [gentoo-user] udev-140
On Mon, Mar 16, 2009 at 3:34 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On Monday 16 March 2009 22:20:37 Paul Hartman wrote: I wouldn't really have minded the inconvenience, except that while all this was going on, the largest data centre in the Southern Hemisphere was dropping off the air one router at a time, my desktop machine was panicing after 4 minutes of use (so that's why I stopped using it 6 months ago!) and I had to use putty on the GF's Thinkpad to do my bit to rescue all this. Putty sucks, really badly. The only thing that sucks worse than Putty on Windows is Putty on Symbian, even on a Nokia Communicator with a semi-decent keyboard (for a phone) :-) What sucks about PuTTY on Windows? I use it all the time and it seems to do everything... Granted, I just use it for simple serial port devices and SSH stuff, no exotic terminal emulations. Putty itself isn't too bad if you look at it as a Windows app. It can never be anything other than a Windows app and as such is restricted to how Windows apps must behave. And therein is the problem - I'm way too used to openssh, I want a command line to fire up my ssh client, I want to 'ssh m...@there' in a console and it must work. I don't want to have to poke around in a vast tree structure to enter my options - I know what they are, I just want to type them. Without a mouse. So Putty doesn't really suck in isolation. It does work and can really operate any different way. *Using* Putty on it's host platform sucks to someone who is used to much more efficient way to accomplish the same task. Have you tried simply using openssh on Windows? Or is cmd.exe really the problem? I prefer Putty because I can more easily copy and paste, resize the window, scrollback, etc. versus the cmd.exe shell (which is basically useless). I'm sure there are alternative windows command shells (or you can use rxvt or something with cygwin) PuTTY on Symbian only does SSH but it seems to do it well enough. Running it full-screen with the smallest font is actually not so bad, even on my 240x320 screen. Being able to connect to my computer wherever I have a cellular signal is convenient... typing with T9 on a numeric phone keypad, not so much... but that's the phone's fault, not PuTTY's. :P I've been meaning to set up a simple menu script that allows me to run all of my common tasks with phone-friendly keystrokes. emerge -uDvptN blah blah blah really sucks to tap out on the 0-9 keys :) Thank god for bash command history... On Symbian it's a life saver when all other methods fail. Again, Putty is OK, using the device is actually what sucks. I still can't find a pipe character! And the screen is almost unreadable (it wasn't three years ago...) Well the good thing about not having QWERTY is that all of the special characters are simple to access (on a pop-up menu) :) Paul
