Re: [Suspend-devel] why do we switch to the console, where the kernel messages are printed?
On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote: The same parameter works for 'resume', but currenty it needs to be set in the config file. However, when I finally apply the command-line-parsing patch, it'll be easy to add a command line switch for that. The module loading takes place after resuming, and we hopefully do not have to change the system wide loglevel after resume. It is generally nice to have the kernel messages on a dedicated console, just not mixed up with the s2disk messages :-) However, if the reason it is done that way is just because we like it and not a technical reason, i have no problem patching this in the SUSE package to use vt63. -- Stefan Seyfried QA / RD Team Mobile Devices| Any ideas, John? SUSE LINUX Products GmbH, Nürnberg | Well, surrounding them's out. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
Re: [Suspend-devel] why do we switch to the console, where the kernel messages are printed?
On Tuesday, 7 November 2006 15:11, Stefan Seyfried wrote: On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote: The same parameter works for 'resume', but currenty it needs to be set in the config file. However, when I finally apply the command-line-parsing patch, it'll be easy to add a command line switch for that. The module loading takes place after resuming, and we hopefully do not have to change the system wide loglevel after resume. It is generally nice to have the kernel messages on a dedicated console, just not mixed up with the s2disk messages :-) Now that's strange, because the suspend loglevel (set by s2disk) should be the current one after resuming and s2disk should switch it back to the original one. [BTW the kernel messages are available from dmesg anyway.] However, if the reason it is done that way is just because we like it and not a technical reason, i have no problem patching this in the SUSE package to use vt63. We discussed it in detail when this code was being written and the reason was certainly technical, because we had added a ioctl() to the kernel for that, but I don't remember what it was. I'll try to find it in the list archives. Still you can patch the SUSE package anyway. ;-) -- You never change things by fighting the existing reality. R. Buckminster Fuller - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
Re: [Suspend-devel] why do we switch to the console, where the kernel messages are printed?
On Tuesday, 7 November 2006 15:32, Rafael J. Wysocki wrote: On Tuesday, 7 November 2006 15:11, Stefan Seyfried wrote: On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote: The same parameter works for 'resume', but currenty it needs to be set in the config file. However, when I finally apply the command-line-parsing patch, it'll be easy to add a command line switch for that. The module loading takes place after resuming, and we hopefully do not have to change the system wide loglevel after resume. It is generally nice to have the kernel messages on a dedicated console, just not mixed up with the s2disk messages :-) Now that's strange, because the suspend loglevel (set by s2disk) should be the current one after resuming and s2disk should switch it back to the original one. Well, I've just tested it and it works as expected. Namely, if 'suspend loglevel' is set to 1, there are no kernel messages on the terminal during the suspend as well as after the resume. Besides, I think it's not a good idea to use a hardcoded terminal number, because it may be used by someone else and then unexpected things may ensue. -- You never change things by fighting the existing reality. R. Buckminster Fuller - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
Re: [Suspend-devel] [Suspend2-users] Re: [PATCH] select ususpend method based on battery charge
On Mon, 6 Nov 2006, Nigel Cunningham wrote: http://www.suspend2.net/downloads is probably better because it's clearer what the current version is. Heh. Actually, I prefer the URL: http://www.suspend2.net/downloads/all/?C=M;O=A scroll down to the bottom, and you're at the latest. -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Los Angeles H: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809 (888) 454-8181 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
Re: [Suspend-devel] why do we switch to the console, where the kernel messages are printed?
On Tue, Nov 07, 2006 at 10:02:07PM +0100, Rafael J. Wysocki wrote: On Tuesday, 7 November 2006 15:32, Rafael J. Wysocki wrote: On Tuesday, 7 November 2006 15:11, Stefan Seyfried wrote: On Tue, Nov 07, 2006 at 02:28:26PM +0100, Rafael J. Wysocki wrote: The same parameter works for 'resume', but currenty it needs to be set in the config file. However, when I finally apply the command-line-parsing patch, it'll be easy to add a command line switch for that. The module loading takes place after resuming, and we hopefully do not have to change the system wide loglevel after resume. It is generally nice to have the kernel messages on a dedicated console, just not mixed up with the s2disk messages :-) Now that's strange, because the suspend loglevel (set by s2disk) should be the current one after resuming and s2disk should switch it back to the original one. Well, I've just tested it and it works as expected. Namely, if 'suspend loglevel' is set to 1, there are no kernel messages on the terminal during the suspend as well as after the resume. And if you now load a new module, will you get those messages again on the kernel console? If yes, you'll probably also get the module loading stuff after resume there (assuming the loglevel before was big enough to display them) Besides, I think it's not a good idea to use a hardcoded terminal number, because it may be used by someone else and then unexpected things may ensue. Well, pm-utils opens vt63 anyway, and we always used vt63 in the past without problems :-) But i'm not religious about this, this is something that might very well be best handled in a distro patch - that's why i asked if there are other reasons than i like it better that way, which in itself is a perfectly valid reason :-) -- Stefan Seyfried QA / RD Team Mobile Devices| Any ideas, John? SUSE LINUX Products GmbH, Nürnberg | Well, surrounding them's out. SUSE LINUX Products GmbH, Nürnberg | -- Linus Torvalds - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
