Cannot run Snort
Dear All, I had installed Snort but cannot run it. Error Message: Can't load library liblzma.s0.2.0 What need to install? I had install the lzlib but still cannot solved it. Which packages need to install or how to tell snort to look up the shared library? -- Linux
Re: hp laptop with nvidia - slow X11
Hi Alexandre, Alexandre Ratchov wrote: Sorry, I don't know. I got mine while debugging the vesa bits of a boot loader. Try increasing X log verbosity. Or possibly guess it from the output of memconfig list, it's likely to be the only variable-length entry large around 256GB-512GB, with ending address right below 4GB. the output of my memconfig list is the following: 0/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 1/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 2/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 3/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 4/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 5/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 6/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 7/1 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 8/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 84000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 88000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 8c000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 9/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 94000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 98000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active 9c000/4000 BIOS write-back fixed-base fixed-length set-by-firmware active fix-active a/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active a4000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active a8000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active ac000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active b/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active b4000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active b8000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active bc000/4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active c/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c1000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c2000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c3000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c4000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c5000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c6000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c7000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c8000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active c9000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active ca000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active cb000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active cc000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active cd000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active ce000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active cf000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d1000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d2000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d3000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d4000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d5000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d6000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d7000/1000 BIOS write-protect fixed-base fixed-length set-by-firmware active fix-active d8000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active d9000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active da000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active db000/1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active fix-active dc000/1000 BIOS write-protect fixed-base fixed-length
Re: Dual Booting OpenBSD vs Windows7
This have been documented in FAQ: http://www.openbsd.org/faq/faq4.html#Multibooting cheers, gsoares Em 27/06/2015 11:11 AM, Mohammad BadieZadegan mbzade...@gmail.com escreveu: Hi, I want to dual booting OpenBSD with Windows7 and read many more pages about customizing windows *bcdedit* tools to booting dual OS like *http://cromwell-intl.com/linux/multiboot-windows-openbsd/ http://cromwell-intl.com/linux/multiboot-windows-openbsd/* *BUT*, all of these pages nothing changed and could not running dual OS. Is that any hints about dual booting OpenBSD vs Windows7?
Re: Dual Booting OpenBSD vs Windows7
Read the FAQ. http://www.openbsd.org/faq/faq4.html#Multibooting On Sat, Jun 27, 2015 at 9:09 AM, Mohammad BadieZadegan mbzade...@gmail.com wrote: Hi, I want to dual booting OpenBSD with Windows7 and read many more pages about customizing windows *bcdedit* tools to booting dual OS like *http://cromwell-intl.com/linux/multiboot-windows-openbsd/ http://cromwell-intl.com/linux/multiboot-windows-openbsd/* *BUT*, all of these pages nothing changed and could not running dual OS. Is that any hints about dual booting OpenBSD vs Windows7?
Re: ftp://ftp.fr
On Fri, Jun 26, 2015 at 05:40:19PM +0200, Antoine Jacoutot wrote: Everything else will remain the same (cvs, rsync, ...); it's *only* the FTP service that is going away. Thank you. The hosting place of ftp.fr was going under major electrical maintenance this morning. Everything should be back to normal now and all services should be available. Sorry for the inconvenience. -- Antoine
Dual Booting OpenBSD vs Windows7
Hi, I want to dual booting OpenBSD with Windows7 and read many more pages about customizing windows *bcdedit* tools to booting dual OS like *http://cromwell-intl.com/linux/multiboot-windows-openbsd/ http://cromwell-intl.com/linux/multiboot-windows-openbsd/* *BUT*, all of these pages nothing changed and could not running dual OS. Is that any hints about dual booting OpenBSD vs Windows7?
Re: Cannot run Snort
On 06/27/15 09:12, Wong Peter wrote: Dear All, I had installed Snort but cannot run it. Error Message: Can't load library liblzma.s0.2.0 What need to install? I had install the lzlib but still cannot solved it. Which packages need to install or how to tell snort to look up the shared library? try xz, it should have been installed with snort, current version does include the dependency. For 5.7 the dependency is missing. $ pkg_info -Sq snort snort-2.9.7.3,@daq-2.0.5,@libdnet-1.12p10,@pcre-8.37p0,@xz-5.2.1,c.80.0,crypto.34.0,daq.2.1,dnet.1.0,lzma.2.1,m.9.0,pcap.8.0,pcre.3.0,pthread.19.0,z.5.0 $ pkg_info -f xz | grep lzma.so @lib lib/liblzma.so.2.1 The pkglocatedb package should help to find any missing packages... $ pkg_locate lzma.so.2 xz-5.2.1:archivers/xz:/usr/local/lib/liblzma.so.2.1
Re: lynx question
Zoran Kolic zko...@sbb.rs writes: I updated to lattest snapshot, from the one, that still had lynx in the base. After upgrading packages, I manualy removed old lynx version from /usr/bin and installed new version in /usr/local/bin, using pkg_add. Is there something that might trigger any problem, doing manual removal? http://www.openbsd.org/faq/upgrade56.html says to remove /usr/bin/lynx manually, so I would not expect any problems from doing so.
Re: ThinkPad X1 Carbon Gen3
On Sat, Jun 27, 2015 at 04:37:23AM BST, Masao Uebayashi wrote: - zzz - I can almost resume it from RAM with Security Chip (TPM) disabled in the BIOS setting. Except display remains off. With TPM enabled, I couldn't power on the machine after suspend to RAM. - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Hi Masao, The sendbug(1) utility is the best way to report bugs :^) Regards, Raf
Re: Dual Booting OpenBSD vs Windows7
I had read this FAQ page more than 10 times. It have wrongs hints: suggestion 1 about active partition did not work for me suggestion 2 worked correctly but need a second media. suggestion 3 is completely wrong! I have tested more than 3 times. maybe it wrote for specialy windows 7 suggestion 4 identify some tools that run on 32 bit windows and now Only Grub maybe can resolve my problem. At now I work on GRUB and wish to resolve the dual booting. On Jun 27, 2015, at 6:51 PM, James Hartley jjhart...@gmail.com wrote: Read the FAQ. http://www.openbsd.org/faq/faq4.html#Multibooting On Sat, Jun 27, 2015 at 9:09 AM, Mohammad BadieZadegan mbzade...@gmail.com wrote: Hi, I want to dual booting OpenBSD with Windows7 and read many more pages about customizing windows *bcdedit* tools to booting dual OS like *http://cromwell-intl.com/linux/multiboot-windows-openbsd/ http://cromwell-intl.com/linux/multiboot-windows-openbsd/* *BUT*, all of these pages nothing changed and could not running dual OS. Is that any hints about dual booting OpenBSD vs Windows7?
lynx question
I updated to lattest snapshot, from the one, that still had lynx in the base. After upgrading packages, I manualy removed old lynx version from /usr/bin and installed new version in /usr/local/bin, using pkg_add. Is there something that might trigger any problem, doing manual removal? Too late, I might do some pkg_delete. Should I move old lynx back and remove it that way? Best regards Zoran
Re: ThinkPad X1 Carbon Gen3
On Sat, Jun 27, 2015 at 12:37:23PM +0900, Masao Uebayashi wrote: - zzz - I can almost resume it from RAM with Security Chip (TPM) disabled in the BIOS setting. Except display remains off. With TPM enabled, I couldn't power on the machine after suspend to RAM. - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Does it start to unpack the hibernated image, then reboot? Or does it not find any image in the signature block? (eg failed to write out the image?) Your bug report leaves a lot to be desired. -ml
Re: Dual Booting OpenBSD vs Windows7
Have you tried EasyBCD? https://neosmart.net/EasyBCD/
Re: Dual Booting OpenBSD vs Windows7
Yes ofcourse When I installed that I can boot to my FreeBSD but OpenBSD could not loaded for unknown reason. On Jun 27, 2015, at 10:40 PM, Maurice McCarthy m...@mythic-beasts.com wrote: Have you tried EasyBCD? https://neosmart.net/EasyBCD/
Re: openssh client alive not default
On Sat, Jun 27, 2015 at 05:10:54PM -0700, jungle Boogie wrote: Hello All, I know fewer defaults the better for all, but if there a reason TCPKeepAlive in openssh is disabled along with the clientalive option? Is it just too risky and/or unneeded? Well, Mr. Boogie, TCPKeepAlive is enabled and ClientAliveInterval is 0, which is disabled, in both 5.7 and -current, if I'm reading the source file correctly. And, according to sshd_config(5), It is important to note that the use of client alive messages is very different from TCPKeepAliveThe client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. How do you folks manage ssh sessions not dying? Do you enable these options every time you install openssh on a new machine? Is there a better option? The man page continues with, The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive. I don't adjust the defaults for these. I use some terrible WiFi connections and occaisionally have to reconnect. If I need to keep a shell running in the event of an unintentional disconnect --- or an intentional one -- I use tmux(1). I can reconnect and continue operating one or more shells without any operational impact.
Re: ThinkPad X1 Carbon Gen3
On Sat, Jun 27, 2015 at 11:45:01AM -0700, Mike Larkin wrote: On Sat, Jun 27, 2015 at 12:37:23PM +0900, Masao Uebayashi wrote: - zzz - I can almost resume it from RAM with Security Chip (TPM) disabled in the BIOS setting. Except display remains off. With TPM enabled, I couldn't power on the machine after suspend to RAM. - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Does it start to unpack the hibernated image, then reboot? I've tried 50 ZZZ and never seen this (reboot). I also believe that in some cases, unpacking failed and booted normally. Or does it not find any image in the signature block? (eg failed to write out the image?) Yes. (As mentioned above; ``not recognizing hibernation''.) Success ratio is like 10%.
Re: ThinkPad X1 Carbon Gen3
On Sun, Jun 28, 2015 at 10:40:42AM +0900, Masao Uebayashi wrote: On Sat, Jun 27, 2015 at 10:33:50PM +0200, David Dahlberg wrote: Am 27.06.2015 um 05:37 schrieb Masao Uebayashi uebay...@tombiinc.com: - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Cannot confirm this here. Unhibernation works fine. Did you disable that Intel Rapid Start thingy in the BIOS' Power settings? Do you mean hibernation has never failed there? That's great. I've disabled Rapid Start and Security Chip in BIOS. Disabling Intel(R) AMT and Intel(R) NFF seeems to make ZZZ very reliable. Those BIOS functions seem to have been added lately. From BIOS Main menu of mine: UEFI BIOS Version N14ET29W (1.07 ) UEFI BIOS Date (Year-Month-Day) 2015-05-08 Embedded Controller Version N14HT30W (1.03 ) ME Firmware Version 10.0.29.1000 Machine Type Model20BSCT01WW :
Re: ThinkPad X1 Carbon Gen3
Am 27.06.2015 um 05:37 schrieb Masao Uebayashi uebay...@tombiinc.com: - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Cannot confirm this here. Unhibernation works fine. Did you disable that Intel Rapid Start thingy in the BIOS' Power settings?
Re: Dual Booting OpenBSD vs Windows7
hi. Maybe you can try grub4dos? Sorry for spam. have a nice $day_time On Sat, 27 Jun 2015 22:22 mbzade...@gmail.com wrote: Yes ofcourse When I installed that I can boot to my FreeBSD but OpenBSD could not loaded for unknown reason. On Jun 27, 2015, at 10:40 PM, Maurice McCarthy m...@mythic-beasts.com wrote: Have you tried EasyBCD? https://neosmart.net/EasyBCD/
openssh client alive not default
Hello All, I know fewer defaults the better for all, but if there a reason TCPKeepAlive in openssh is disabled along with the clientalive option? Is it just too risky and/or unneeded? How do you folks manage ssh sessions not dying? Do you enable these options every time you install openssh on a new machine? Is there a better option? -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: openssh client alive not default
On 2015-06-28 02:59, Josh Grosse wrote: How do you folks manage ssh sessions not dying? Do you enable these options every time you install openssh on a new machine? Is there a better option? The man page continues with, The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive. I don't adjust the defaults for these. I use some terrible WiFi connections and occaisionally have to reconnect. If I need to keep a shell running in the event of an unintentional disconnect --- or an intentional one -- I use tmux(1). I can reconnect and continue operating one or more shells without any operational impact. Also keep in mind that keepalives are both a blessing and a curse... On the one hand, they can save you from those horrible home routers (mostly) that timeout your TCP sessions after a while (often a non-configurable, but invariably too short, while at that), whether they actually need to conserve their state-keeping space or not. But on the other hand, if you have a stable connection through a REAL (OpenBSD :-) ) firewall, that *doesn't* snip your TCP sessions just for the fun of it, they may actually *cause* a disconnect. Let's say you have an open, but idle, ssh session to your remote server and there's a short outage in the network somewhere between the two endpoints. If there are no keep-alive packets trying to get through and the actual session remains idle, then you'll never notice that there was an outage. But if there are keep-alive packets being sent that never reaches the destination the endpoints will terminate the connection and you will lose your terminal session no matter what. (Moral of the story: +1 for using tmux/screen/nohup/batch/at/whatever to keep long-running jobs safe. And when interactive, save your work often. :-) ) Regards, /Benny -- internetlabbet.se / work: +46 8 551 124 80 / Words must Benny Lofgren/ mobile: +46 70 718 11 90 / be weighed, / fax:+46 8 551 124 89/not counted. /email: benny -at- internetlabbet.se
Re: Dual Booting OpenBSD vs Windows7
mbzade...@gmail.com said: suggestion 1 about active partition did not work for me Details? suggestion 3 is completely wrong! Details? I've tried these options, and they worked as charm. -- Dmitrij D. Czarkoff
Leap second
As you may have heard, a leap second will be upon us at 23:59:60 UTC on June 30. The sky will fall, civilization will end, and dinosaurs will roam the earth again. Well, maybe not. Neither the OpenBSD kernel nor OpenNTPD handle leap seconds in any way. So what will happen? After the leap second, your OpenBSD system's time will be off by, well, one second. Gasp, shock. Let's say you synchronize your clock with ntpd against a server that does have the correct time. At the next poll, i.e. within about half an hour, ntpd will notice the offset and correct it, which will take a few minutes. That's it. (I expect ntpd will drop down to a short poll interval and the frequency correction will fishtail a bit since it's a differentiator reacting to a jump.) Unless you obsessively watch your ntpd, you won't notice a thing. All the terrible things you may read that might happen, or that did happen to Linux in the past, are side effects of systems that do attempt to handle leap seconds, so that they always have the correct time at the price of a confusing extra second popping into existence. Finally, if you are one of the exceedingly few people for whom the clock being off by a second actually matters, then I'm pretty sure you also know how to deal with it. PS: Any hate mail about leap seconds should be directed to (1) the people who insist that Earth's celestial wobbling around must have primacy for time keeping and (2) the people at POSIX who specified that time_t must not include leap seconds, which means we can't just let the time zone database handle this. -- Christian naddy Weisgerber na...@mips.inka.de
Re: Dual Booting OpenBSD vs Windows7
Sat, Jun 27, 2015 at 17:39:38 +0330, Mohammad BadieZadegan may have written: Hi, I want to dual booting OpenBSD with Windows7 and read many more pages about customizing windows *bcdedit* tools to booting dual OS like *http://cromwell-intl.com/linux/multiboot-windows-openbsd/ http://cromwell-intl.com/linux/multiboot-windows-openbsd/* *BUT*, all of these pages nothing changed and could not running dual OS. Is that any hints about dual booting OpenBSD vs Windows7? I use http://gag.sourceforge.net/ for that. -- Perfection [in design] is achieved not when there is nothing left to add, but rather when there is nothing left to take away. -- Antoine de Saint-Exupery
Re: Dual Booting OpenBSD vs Windows7
On 06/27/15 12:41, mbzade...@gmail.com wrote: I had read this FAQ page more than 10 times. well, then you need to keep reading it. The windows 7 multiboot process WORKS. I'm using it on at least two computers. It works. You are doing something wrong. The lack of details in your problem report makes me sure of that. Nick. Facebook logo = Email or Phone Password Keep me logged in Forgot your password? [IMAGE] Sign Up Log In Messenger Facebook Lite Mobile Find Friends Badges People Pages Places Games Locations About Create Ad Create Page Developers Careers Privacy Cookies Ad Choices Terms Help Facebook © 2015English (US)
Re: Dual Booting OpenBSD vs Windows7
On 06/27/15 18:52, Nick Holland wrote: ... Nick. Facebook logo = ... (wtf? and it's even weirder looking in my outmail box. sorry for the noise)
Re: Dual Booting OpenBSD vs Windows7
2015/06/28 1:43 mbzade...@gmail.com: I had read this FAQ page more than 10 times. It have wrongs hints: suggestion 1 about active partition did not work for me This needs interpolation for gpt/guid partitioned disks, and requires, as I understand things, a custom option in the kernel, among other things. I'm trying to learn how to do this with MSWindows8 right now, and I'm learning a lot of useful stuff. suggestion 2 worked correctly but need a second media. Boot floppy is for really old hardware. Re-interpret that as using an entirely external drive. And a second hard disk is not necessarily a bad idea. In fact, I'm using a USB3 external rotating drive for some of the playing/research I mentioned above. Built the kernel and userland from source entirely on the external drive. Mis-calculated about /usr/xenocara, so I made /usr/xobj my last partition (on /dev/sd1p). Now I'm starting over and should have xenocara built from source in about three to six hours. Yes, it builds faster on the internal drive. But that doesn't seem to be an option for you right now. But, as a thought, have you made an MSWindows full system restore DVD along with backing up your data? suggestion 3 is completely wrong! NTLDR was dropped by Microsoft before MSWindows7, so, if that's what you mean, yeah, don't bother with NTLDR. I have tested more than 3 times. maybe it wrote for specialy windows 7 If you are trying bcdedit for MSWindows7, are you sure you got the disk's GUID copied correctly from the results of the bcdedit /create step? suggestion 4 identify some tools that run on 32 bit windows and now Only Grub maybe can resolve my problem. If you are talking about the other boot loaders, they are independent of the 32bit/64bit issues. At now I work on GRUB and wish to resolve the dual booting. If your MSWindows7 is on a GPT partition, things are not going to be easy. You'll really want to consider using an external drive for the time being. Anyway, anyone here with time to help you needs more information about how and where things are not working for you -- error messages that you may have to copy into your mail by hand, etc. -- Joel Rees On Jun 27, 2015, at 6:51 PM, James Hartley jjhart...@gmail.com wrote: Read the FAQ. http://www.openbsd.org/faq/faq4.html#Multibooting On Sat, Jun 27, 2015 at 9:09 AM, Mohammad BadieZadegan mbzade...@gmail.com wrote: Hi, I want to dual booting OpenBSD with Windows7 and read many more pages about customizing windows *bcdedit* tools to booting dual OS like *http://cromwell-intl.com/linux/multiboot-windows-openbsd/ http://cromwell-intl.com/linux/multiboot-windows-openbsd/* *BUT*, all of these pages nothing changed and could not running dual OS. Is that any hints about dual booting OpenBSD vs Windows7?
Re: ThinkPad X1 Carbon Gen3
On Sat, Jun 27, 2015 at 10:33:50PM +0200, David Dahlberg wrote: Am 27.06.2015 um 05:37 schrieb Masao Uebayashi uebay...@tombiinc.com: - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Cannot confirm this here. Unhibernation works fine. Did you disable that Intel Rapid Start thingy in the BIOS' Power settings? Do you mean hibernation has never failed there? That's great. I've disabled Rapid Start and Security Chip in BIOS.
Re: ThinkPad X1 Carbon Gen3
On Sun, Jun 28, 2015 at 11:19:02AM +0900, Masao Uebayashi wrote: On Sun, Jun 28, 2015 at 10:40:42AM +0900, Masao Uebayashi wrote: On Sat, Jun 27, 2015 at 10:33:50PM +0200, David Dahlberg wrote: Am 27.06.2015 um 05:37 schrieb Masao Uebayashi uebay...@tombiinc.com: - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Cannot confirm this here. Unhibernation works fine. Did you disable that Intel Rapid Start thingy in the BIOS' Power settings? Do you mean hibernation has never failed there? That's great. I've disabled Rapid Start and Security Chip in BIOS. Disabling Intel(R) AMT and Intel(R) NFF seeems to make ZZZ very reliable. Those BIOS functions seem to have been added lately. From I spoke too early... I did see 5 sucessive successful ZZZ, from minimal, single user + apmd setup, after applying said BIOS settings. Then I tried ZZZ from within X, and failed, and afterwards my failure ratio goes back to 10%. :((( BIOS Main menu of mine: UEFI BIOS Version N14ET29W (1.07 ) UEFI BIOS Date (Year-Month-Day) 2015-05-08 Embedded Controller Version N14HT30W (1.03 ) ME Firmware Version 10.0.29.1000 Machine Type Model20BSCT01WW :
Re: Dual Booting OpenBSD vs Windows7
My Windows is 64Bit and Grub4DOS run only 32Bit Systems! On Sun, Jun 28, 2015 at 1:15 AM, Ruslanas Gžibovskis rusla...@lpic.lt wrote: hi. Maybe you can try grub4dos? Sorry for spam. have a nice $day_time On Sat, 27 Jun 2015 22:22 mbzade...@gmail.com wrote: Yes ofcourse When I installed that I can boot to my FreeBSD but OpenBSD could not loaded for unknown reason. On Jun 27, 2015, at 10:40 PM, Maurice McCarthy m...@mythic-beasts.com wrote: Have you tried EasyBCD? https://neosmart.net/EasyBCD/ -- [image: See you on my WEB] http://933k.ir
Re: openssh client alive not default
Hi Josh, On 27 June 2015 at 17:59, Josh Grosse j...@jggimi.homeip.net wrote: On Sat, Jun 27, 2015 at 05:10:54PM -0700, jungle Boogie wrote: Hello All, I know fewer defaults the better for all, but if there a reason TCPKeepAlive in openssh is disabled along with the clientalive option? Is it just too risky and/or unneeded? Well, Mr. Boogie, TCPKeepAlive is enabled and ClientAliveInterval is 0, which is disabled, in both 5.7 and -current, if I'm reading the source file correctly. I'm sure you're reading it correctly. Maybe in the portable its disabled, I'll have to check closely. And, according to sshd_config(5), It is important to note that the use of client alive messages is very different from TCPKeepAliveThe client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. quite interesting, thanks! How do you folks manage ssh sessions not dying? Do you enable these options every time you install openssh on a new machine? Is there a better option? The man page continues with, The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive. I don't adjust the defaults for these. I use some terrible WiFi connections and occaisionally have to reconnect. If I need to keep a shell running in the event of an unintentional disconnect --- or an intentional one -- I use tmux(1). I can reconnect and continue operating one or more shells without any operational impact. Yes, tmux is wonderful and I'm thankful for Nicholas' work on it! The problem is if you're doing reverse tunnelling, the tmux connection doesn't really solve that problem, though. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
Re: Dual Booting OpenBSD vs Windows7
Nice Project was Resolved with bootice [ http://reboot.pro/topic/8986-bootice-a-boot-sector-manipulation-utility-v078- released/] and grub4dos! Thanks to all for helping me. On Sun, Jun 28, 2015 at 7:47 AM, Mohammad BadieZadegan mbzade...@gmail.com wrote: My Windows is 64Bit and Grub4DOS run only 32Bit Systems! On Sun, Jun 28, 2015 at 1:15 AM, Ruslanas Gžibovskis rusla...@lpic.lt wrote: hi. Maybe you can try grub4dos? Sorry for spam. have a nice $day_time On Sat, 27 Jun 2015 22:22 mbzade...@gmail.com wrote: Yes ofcourse When I installed that I can boot to my FreeBSD but OpenBSD could not loaded for unknown reason. On Jun 27, 2015, at 10:40 PM, Maurice McCarthy m...@mythic-beasts.com wrote: Have you tried EasyBCD? https://neosmart.net/EasyBCD/ -- [image: See you on my WEB] http://933k.ir -- [image: See you on my WEB] http://933k.ir
Re: openssh client alive not default
On 27 June 2015 at 18:17, Benny Lofgren bl-li...@lofgren.biz wrote: Let's say you have an open, but idle, ssh session to your remote server and there's a short outage in the network somewhere between the two endpoints. If there are no keep-alive packets trying to get through and the actual session remains idle, then you'll never notice that there was an outage. But if there are keep-alive packets being sent that never reaches the destination the endpoints will terminate the connection and you will lose your terminal session no matter what. Ah, that's a very interesting and likely to happen example. ssh sessions can die when you don't have these two enabled but it seems to take much longer. (Moral of the story: +1 for using tmux/screen/nohup/batch/at/whatever to keep long-running jobs safe. And when interactive, save your work often. :-) ) my favorite is definitely tmux! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
