Re: daily insecurity says my swap device changed
On Thu, Sep 11, 2014 at 04:25:04PM -0400, System Administrator wrote: > On 11 Sep 2014 at 12:23, Scott Bonds wrote: > > > On Thu, Sep 11, 2014 at 07:35:47PM +0200, Christer Solskogen wrote: > > > On Thu, Sep 11, 2014 at 7:21 PM, Ingo Schwarze wrote: > > > > Hi Scott, > > > > > > > > Scott Bonds wrote on Thu, Sep 11, 2014 at 09:38:10AM -0700: > > > > > > > >> My daily insecurity email on one of my boxes says this: > > > >> > > > >> Block device changes: > > > >> brw-r- 1 root operator 0, 1 Aug 16 17:44:40 2014 /dev/wd0b > > > >> brw-r- 1 root operator 0, 1 Sep 8 18:43:56 2014 /dev/wd0b > > > >> > > > >> On all my other (openbsd) boxes, the swap partition has the same date > > > >> as > > > >> all the other block devices. And all the other devices on *this* box > > > >> have the same timestamp of August 16. After this insecurity report, I > > > >> ran a script that eats up memory and started to use swap space and I > > > >> verified that at least in that case, the swap device timestamp didn't > > > >> change...so it would seem that using swap wouldn't lead to the > > > >> timestamp > > > >> change in my daily insecurity report. > > > >> > > > >> Does anyone know why the date would change on a swap device like this? > > > > > > > > One obvious possibility would be that maybe somebody ran mknod(1) > > > > or touch(1) on the file /dev/wd0b. > > > > > > > > > > The script /dev/MAKEDEV was run, perhaps? > > > > Understood. I'm the only user on this box and I did not run mknod, > > touch, or MAKEDEV. I'm wondering whether something nefarious is going > > on, or if there's some system process that's doing something normal. > > > > > > Does anyone know whether system crash dump (which goes to the swap > device) updates the timestampt? And did the system crash with a dump? I think you've got it. There's a core dump in /var/crashes with the same time stamp. Thanks!
Re: daily insecurity says my swap device changed
On Thu, Sep 11, 2014 at 10:13:14PM +0200, Christer Solskogen wrote: > On Thu, Sep 11, 2014 at 9:23 PM, Scott Bonds wrote: > > > Understood. I'm the only user on this box and I did not run mknod, > > touch, or MAKEDEV. I'm wondering whether something nefarious is going > > on, or if there's some system process that's doing something normal. > > > > Not upgraded in the last few days either? Correct, I did not upgrade the OS.
Re: random.seed and read only root
previously on this list Kevin Chadwick contributed: > After noticing random.seed change failure messages on shutdown. I have > been modding /etc/rc? > > --- etc/rc Fri Aug 8 07:05:50 2014 > +++ etc/rc.new Mon Aug 18 19:04:49 2014 > @@ -267,6 +267,7 @@ > _rc_parse_conf > > if [ X"$1" = X"shutdown" ]; then > + /sbin/mount -uw / > if echo 2>/dev/null >>/var/db/host.random || \ > echo 2>/dev/null >>/etc/random.seed; then > random_seed So I guess I am either missing something or should just wait for an actual release or two to see what's planned for ro root. In case it is of any use to anyone. I've added this one liner to an existing boot script of mine so I don't need to remember to edit /etc/rc. printf "/X\"shutdown\"\n+1\ni\n\t\/sbin\/mount -uw \/\n.\nw\nq\n" | /bin/ed /etc/rc -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) In Other Words - Don't design like polkit or systemd ___
Re: [Bulk] Re: Real time programming in OpenBSD
Hi Matti, Matti Karnaattu wrote on Thu, Sep 11, 2014 at 08:57:30PM +0300: > And if I understand correctly, priorities goes like this: > simplicity > licensing purity > correctness > completeness Most definitely not. That's more than just a bit misleading. None of these can be put into an unambiguous linear ordering. To be of any use *qualitative* statements are required - and if accompagnied by a clarifying qualitative statement, maybe even the "is more important than" symbol is semi-acceptable: * fully free license > everything else New code will not be added to the tree unless fully free, whatever other qualities it may have, full stop. However, if the system as a whole critically depends on specific GPL code that already is in the tree and no way has yet been found to replace it, it will remain for now (example: binutils). * correctness > completeness Usually, bugs should be fixed before adding features. However, it does occasionally happen that specific features are so urgently needed that implementing them takes precendence over fixing some non-critical bugs. Also, when talking about standards, the very fact that a feature is missing can be a bug. * correctness > simplicity Fixing bugs is more urgent than refactoring for simplicity. However, keeping and making interfaces and code simple is very important, too, because useless complexity almost always causes bugs and harms usability. * completeness > simplicity If a feature is really useful and much needed, it should be added even if it entails some additional complexity: In this case, the complexity is required by the task to be solved. However, we rarely add non-standard features to standard (e.g. POSIX) utilities because standardization is quite important. Also, we don't add features that are of little usefulness. Even though simplicity seems to figure *last* in my ordering, it is still a highly important goal (and a personal favourite). And yes, that is one of the things making OpenBSD special. Most other projects seem to assign no value whatsoever to simplicity and sacrificy it to almost anything, including rank growth and lazyness. We make sure we reach our goals (in that sense, freedom, correctness, and completeness still take precendence), but only accept as much complexity as required by the goals, not more. Note that some critical project goals are missing from your list, most notably * usability * standard-conformance * security * portability Please don't try to rank these. It won't work. Most are qualitatively, essentially different, incommensurable. Many have intricate inter-dependencies, like "correctness is almost impossible without simplicity", "security is impossible without correctness", "usablity is unavoidably low without simplicity", "correctness is almost pointless without usability" and so on. We only call it success when we reach a high level of *all* of these. Yours, Ingo
Re: daily insecurity says my swap device changed
On 11 Sep 2014 at 12:23, Scott Bonds wrote: > On Thu, Sep 11, 2014 at 07:35:47PM +0200, Christer Solskogen wrote: > > On Thu, Sep 11, 2014 at 7:21 PM, Ingo Schwarze wrote: > > > Hi Scott, > > > > > > Scott Bonds wrote on Thu, Sep 11, 2014 at 09:38:10AM -0700: > > > > > >> My daily insecurity email on one of my boxes says this: > > >> > > >> Block device changes: > > >> brw-r- 1 root operator 0, 1 Aug 16 17:44:40 2014 /dev/wd0b > > >> brw-r- 1 root operator 0, 1 Sep 8 18:43:56 2014 /dev/wd0b > > >> > > >> On all my other (openbsd) boxes, the swap partition has the same date as > > >> all the other block devices. And all the other devices on *this* box > > >> have the same timestamp of August 16. After this insecurity report, I > > >> ran a script that eats up memory and started to use swap space and I > > >> verified that at least in that case, the swap device timestamp didn't > > >> change...so it would seem that using swap wouldn't lead to the timestamp > > >> change in my daily insecurity report. > > >> > > >> Does anyone know why the date would change on a swap device like this? > > > > > > One obvious possibility would be that maybe somebody ran mknod(1) > > > or touch(1) on the file /dev/wd0b. > > > > > > > The script /dev/MAKEDEV was run, perhaps? > > Understood. I'm the only user on this box and I did not run mknod, > touch, or MAKEDEV. I'm wondering whether something nefarious is going > on, or if there's some system process that's doing something normal. > > Does anyone know whether system crash dump (which goes to the swap device) updates the timestampt? And did the system crash with a dump?
Re: [Bulk] Re: Real time programming in OpenBSD
On Thu, Sep 11, 2014 at 10:57 AM, Matti Karnaattu wrote: > What I meant was to clarify OpenBSD culture, priorities and coding > practices and like to know whichever was the lesser of two evils: > > -simplicity vs. licensing purity > -licensing purity vs. completeness > -pragmatic licensing and completeness vs. licensing purity > -correctness vs. simplicity > -licensing purity vs. simplicity > > And if I understand correctly, priorities goes like this: > > simplicity > licensing purity > correctness > completeness That's certainly not what Ingo said.
Re: daily insecurity says my swap device changed
On Thu, Sep 11, 2014 at 9:23 PM, Scott Bonds wrote: > Understood. I'm the only user on this box and I did not run mknod, > touch, or MAKEDEV. I'm wondering whether something nefarious is going > on, or if there's some system process that's doing something normal. > Not upgraded in the last few days either? -- chs
Re: daily insecurity says my swap device changed
On Thu, Sep 11, 2014 at 07:35:47PM +0200, Christer Solskogen wrote: > On Thu, Sep 11, 2014 at 7:21 PM, Ingo Schwarze wrote: > > Hi Scott, > > > > Scott Bonds wrote on Thu, Sep 11, 2014 at 09:38:10AM -0700: > > > >> My daily insecurity email on one of my boxes says this: > >> > >> Block device changes: > >> brw-r- 1 root operator 0, 1 Aug 16 17:44:40 2014 /dev/wd0b > >> brw-r- 1 root operator 0, 1 Sep 8 18:43:56 2014 /dev/wd0b > >> > >> On all my other (openbsd) boxes, the swap partition has the same date as > >> all the other block devices. And all the other devices on *this* box > >> have the same timestamp of August 16. After this insecurity report, I > >> ran a script that eats up memory and started to use swap space and I > >> verified that at least in that case, the swap device timestamp didn't > >> change...so it would seem that using swap wouldn't lead to the timestamp > >> change in my daily insecurity report. > >> > >> Does anyone know why the date would change on a swap device like this? > > > > One obvious possibility would be that maybe somebody ran mknod(1) > > or touch(1) on the file /dev/wd0b. > > > > The script /dev/MAKEDEV was run, perhaps? Understood. I'm the only user on this box and I did not run mknod, touch, or MAKEDEV. I'm wondering whether something nefarious is going on, or if there's some system process that's doing something normal.
Re: Alix 3D3 disconnects from network after random amount of time
On Sat, 6 Sep 2014 17:56:59 + Артур Истомин wrote: > On Sat, Sep 06, 2014 at 11:36:55AM +0200, Erwin Geerdink wrote: > > On Fri, 05 Sep 2014 16:05:14 +0200 > > "Boudewijn Dijkstra" wrote: > > > > > Op Sat, 30 Aug 2014 14:20:43 +0200 schreef Erwin Geerdink > > > : > > > > pcibios0: bad IRQ table checksum > > > > pcibios0: PCI Exclusive IRQs: 5 10 11 > > > > pcibios0: Warning, unable to fix up PCI interrupt routing > > > > vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: > > > > irq 11, auglx0 at pci0 dev 15 function 3 "AMD CS5536 Audio" rev > > > > 0x01: irq 11, > > > > > > Could there be a problem with IRQ sharing? > > > > > > > Good suggestion, I disabled onboard audio and am now > > testing/tcpbenching again to see if the problem persists. I was not > > able to configure IRQ addresses in the bios settings (did I > > overlook?), but when the connection is reliable I intend to use an > > usb audio interface anyway. > > I had the same problem when used usb flash drive as additional storage > on Alix 2D13. I suspect problem was with AC power adapter, > insufficient power for device. The problem was solved by failure of > usb-drive :) > After some testing, I found that the problem persists even when onboard audio is disabled such that vr0 has an exclusive IRQ. Disconnecting all external devices (except VGA monitor and USB keyboard) did not make a difference, although it seemed likely that the usb audio interface was too power hungry (500 mA according to usbdevs). Updating to -current did not help either. Currently I'm trying Debian, so far I haven't been able to trigger a disconnection. Best, --- Erwin
Re: [Bulk] Re: Real time programming in OpenBSD
>I find it far more useful and easier to work with and control than >"modern desktops" and wish modern programs went back to older config >standards and used text rather than *conf rubbish and that freedesktop >followed the older principles more closely when doing desktop >unification features etc.. I don't find fvwm to be problem either. However, while all new things are not necessarily better, it is usually best to follow defined practices in order to be unified with others. This is kind of idea of standards. What I meant was to clarify OpenBSD culture, priorities and coding practices and like to know whichever was the lesser of two evils: -simplicity vs. licensing purity -licensing purity vs. completeness -pragmatic licensing and completeness vs. licensing purity -correctness vs. simplicity -licensing purity vs. simplicity And if I understand correctly, priorities goes like this: simplicity > licensing purity > correctness > completeness
Re: daily insecurity says my swap device changed
On Thu, Sep 11, 2014 at 7:21 PM, Ingo Schwarze wrote: > Hi Scott, > > Scott Bonds wrote on Thu, Sep 11, 2014 at 09:38:10AM -0700: > >> My daily insecurity email on one of my boxes says this: >> >> Block device changes: >> brw-r- 1 root operator 0, 1 Aug 16 17:44:40 2014 /dev/wd0b >> brw-r- 1 root operator 0, 1 Sep 8 18:43:56 2014 /dev/wd0b >> >> On all my other (openbsd) boxes, the swap partition has the same date as >> all the other block devices. And all the other devices on *this* box >> have the same timestamp of August 16. After this insecurity report, I >> ran a script that eats up memory and started to use swap space and I >> verified that at least in that case, the swap device timestamp didn't >> change...so it would seem that using swap wouldn't lead to the timestamp >> change in my daily insecurity report. >> >> Does anyone know why the date would change on a swap device like this? > > One obvious possibility would be that maybe somebody ran mknod(1) > or touch(1) on the file /dev/wd0b. > The script /dev/MAKEDEV was run, perhaps? -- chs
Re: daily insecurity says my swap device changed
Hi Scott, Scott Bonds wrote on Thu, Sep 11, 2014 at 09:38:10AM -0700: > My daily insecurity email on one of my boxes says this: > > Block device changes: > brw-r- 1 root operator 0, 1 Aug 16 17:44:40 2014 /dev/wd0b > brw-r- 1 root operator 0, 1 Sep 8 18:43:56 2014 /dev/wd0b > > On all my other (openbsd) boxes, the swap partition has the same date as > all the other block devices. And all the other devices on *this* box > have the same timestamp of August 16. After this insecurity report, I > ran a script that eats up memory and started to use swap space and I > verified that at least in that case, the swap device timestamp didn't > change...so it would seem that using swap wouldn't lead to the timestamp > change in my daily insecurity report. > > Does anyone know why the date would change on a swap device like this? One obvious possibility would be that maybe somebody ran mknod(1) or touch(1) on the file /dev/wd0b. Yours, Ingo
daily insecurity says my swap device changed
My daily insecurity email on one of my boxes says this: Block device changes: brw-r- 1 root operator 0, 1 Aug 16 17:44:40 2014 /dev/wd0b brw-r- 1 root operator 0, 1 Sep 8 18:43:56 2014 /dev/wd0b On all my other (openbsd) boxes, the swap partition has the same date as all the other block devices. And all the other devices on *this* box have the same timestamp of August 16. After this insecurity report, I ran a script that eats up memory and started to use swap space and I verified that at least in that case, the swap device timestamp didn't change...so it would seem that using swap wouldn't lead to the timestamp change in my daily insecurity report. Does anyone know why the date would change on a swap device like this?
Re: wildcard poisoning
i think that this is not something related with OBSD security but with the correct use of the shell of course this is something that could happen > Date: Tue, 9 Sep 2014 21:21:30 -0700 > Subject: Re: wildcard poisoning > From: pkesh...@gmail.com > To: stur...@hotmail.com > CC: misc@openbsd.org > > On 9/9/14, Stefan Olsson wrote: > > I came across an interesting article on wildcards in shell: > > http://www.defensecode.com/public/DefenseCode_Unix_WildCards_Gone_Wild.txt > > > > > > Tested some of the above in pdksh on a current OpenBSD-host: > > $ mkdir test > > $ cd test > > $ touch file1 file2 file3 "-rf" > > $ mkdir DIR1 DIR2 > > $ ls -al > > total 16 > > -rw-r--r-- 1 sturban sturban 0 Sep 10 04:26 -rf > > drwxr-xr-x 4 sturban sturban 512 Sep 10 04:26 ./ > > drwxr-xr-x 10 sturban sturban 1024 Sep 10 04:25 ../ > > drwxr-xr-x 2 sturban sturban 512 Sep 10 04:26 DIR1/ > > drwxr-xr-x 2 sturban sturban 512 Sep 10 04:26 DIR2/ > > -rw-r--r-- 1 sturban sturban 0 Sep 10 04:26 file1 > > -rw-r--r-- 1 sturban sturban 0 Sep 10 04:26 file2 > > -rw-r--r-- 1 sturban sturban 0 Sep 10 04:26 file3 > > $ rm * > > $ ls -al > > total 8 > > -rw-r--r-- 1 sturban sturban 0 Sep 10 04:26 -rf > > drwxr-xr-x 2 sturban sturban 512 Sep 10 04:26 ./ > > drwxr-xr-x 10 sturban sturban 1024 Sep 10 04:25 ../ > > $ touch file1 file2 file3 "-rf" > $ mkdir DIR1 DIR2 > $ ls -al > total 16 > -rw-r--r-- 1 sidster wheel 0 Sep 9 21:19 -rf > drwxr-xr-x 4 sidster wheel 512 Sep 9 21:19 ./ > drwxrwxrwt 8 root wheel 1024 Sep 9 21:19 ../ > drwxr-xr-x 2 sidster wheel 512 Sep 9 21:19 DIR1/ > drwxr-xr-x 2 sidster wheel 512 Sep 9 21:19 DIR2/ > -rw-r--r-- 1 sidster wheel 0 Sep 9 21:19 file1 > -rw-r--r-- 1 sidster wheel 0 Sep 9 21:19 file2 > -rw-r--r-- 1 sidster wheel 0 Sep 9 21:19 file3 > $ rm ./* > rm: ./DIR1: is a directory > rm: ./DIR2: is a directory > noir $ ls -al > total 16 > drwxr-xr-x 4 sidster wheel 512 Sep 9 21:20 ./ > drwxrwxrwt 8 root wheel 1024 Sep 9 21:19 ../ > drwxr-xr-x 2 sidster wheel 512 Sep 9 21:19 DIR1/ > drwxr-xr-x 2 sidster wheel 512 Sep 9 21:19 DIR2/ > > be smarter than that. > > --patrick
Re: [Bulk] Re: Real time programming in OpenBSD
previously on this list Ingo Schwarze contributed: > There are problems with fvwm, yes. It is old, crufty code of > horrible quality. I was under the impression that when it was audited it was found to be far better than expected and I believe something like quite clean or surprising little cleanup was mentioned. Perhaps that was simply due to the expectation of GUI code to be absolutely horrific? I find it far more useful and easier to work with and control than "modern desktops" and wish modern programs went back to older config standards and used text rather than *conf rubbish and that freedesktop followed the older principles more closely when doing desktop unification features etc.. Little things like xfce launchers having random names and config (which like logs is relatively tiny) being hard to find or wanting local tools or processing binary configs when the speed gain simply isn't required and the negative sides having not been considered akin to systemd binary logging. > But regarding functionality, i would rather > call it bloated than ask for more features. Yeah, I think it has all the features required and things like gkrellm can fill any gaps. > Then again, i don't > care enough about GUIs to waste my time trying anything else. -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) In Other Words - Don't design like polkit or systemd ___
Re: Hard drives don't spin down
On Thu, Sep 11, 2014 at 1:59 PM, Laurence Rochfort wrote: > If I set it for both drives they spin down. I take it that's the time > in seconds the system has to be idle for before they spin down? Exactly. man 8 atactl > What's the difference between idle and standby? For what I've understood, standby puts the disk in a even more deep sleep state than idle. Btw, you can put the two commands into /etc/rc.local, so they will survive a reboot. Ciao! David
Re: Hard drives don't spin down
If I set it for both drives they spin down. I take it that's the time in seconds the system has to be idle for before they spin down? What's the difference between idle and standby? On 11 September 2014 12:30, David Coppa wrote: > On Thu, Sep 11, 2014 at 1:22 PM, Laurence Rochfort > wrote: >> Hello, >> >> I'm running 5.5 on amd64. >> >> I have two non-identical SATA drives in softraid RAID 1 that never >> spin down, even when the system has been idle for hours. >> >> Should I expect them to automatically spin down when using soft raid >> and apmd -C, or do I have to script something with atactl? The BIOS >> doesn't mention drive power management specifically, but does have APM >> enabled and reports SMART for the drives. > > What happens with: > > # atactl wd0 setidle 5 > > ??
Re: Hard drives don't spin down
On Thu, Sep 11, 2014 at 1:22 PM, Laurence Rochfort wrote: > Hello, > > I'm running 5.5 on amd64. > > I have two non-identical SATA drives in softraid RAID 1 that never > spin down, even when the system has been idle for hours. > > Should I expect them to automatically spin down when using soft raid > and apmd -C, or do I have to script something with atactl? The BIOS > doesn't mention drive power management specifically, but does have APM > enabled and reports SMART for the drives. What happens with: # atactl wd0 setidle 5 ??
Hard drives don't spin down
Hello, I'm running 5.5 on amd64. I have two non-identical SATA drives in softraid RAID 1 that never spin down, even when the system has been idle for hours. Should I expect them to automatically spin down when using soft raid and apmd -C, or do I have to script something with atactl? The BIOS doesn't mention drive power management specifically, but does have APM enabled and reports SMART for the drives. bioctl, atactl, apm and dmesg follow. Regards, Laurence. $ sudo bioctl sd0 Volume Status Size Device softraid0 0 Online 100029196288 sd0 RAID1 0 Online 100029196288 0:0.0 noencl 1 Online 100029196288 0:1.0 noencl $ sudo atactl wd0 identify Model: TOSHIBA MK1032GSX, Rev: AS022D, Serial #:762G2643T Device type: ATA, fixed Cylinders: 16383, heads: 16, sec/track: 63, total sectors: 195371568 Device capabilities: ATA standby timer values IORDY operation IORDY disabling Device supports the following standards: ATA-1 ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 Master password revision code 0xfffe Device supports the following command sets: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set Security Mode feature set SMART feature set Flush Cache Ext command Flush Cache command Device Configuration Overlay feature set 48bit address feature set Automatic Acoustic Management feature set Set Max security extension commands Advanced Power Management feature set DOWNLOAD MICROCODE command IDLE IMMEDIATE with UNLOAD FEATURE SMART self-test SMART error logging Device has enabled the following command sets/features: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set SMART feature set Flush Cache Ext command Flush Cache command Device Configuration Overlay feature set 48bit address feature set Automatic Acoustic Management feature set Advanced Power Management feature set DOWNLOAD MICROCODE command $ sudo atactl wd1 identify Model: Hitachi HTS541612J9SA00, Rev: SBDOC7DP, Serial #: SB2541H6CN0EZE Device type: ATA, fixed Cylinders: 16383, heads: 16, sec/track: 63, total sectors: 234441648 Device capabilities: IORDY operation IORDY disabling Device supports the following standards: ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 ATA-7 Master password revision code 0xfffe Device supports the following command sets: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set Security Mode feature set SMART feature set Flush Cache Ext command Flush Cache command Device Configuration Overlay feature set 48bit address feature set Automatic Acoustic Management feature set Set Max security extension commands Set Features subcommand required Power-up in standby feature set Advanced Power Management feature set DOWNLOAD MICROCODE command IDLE IMMEDIATE with UNLOAD FEATURE SMART self-test SMART error logging Device has enabled the following command sets/features: NOP command READ BUFFER command WRITE BUFFER command Host Protected Area feature set Read look-ahead Write cache Power Management feature set SMART feature set Flush Cache Ext command Flush Cache command Device Configuration Overlay feature set 48bit address feature set Set Features subcommand required Advanced Power Management feature set DOWNLOAD MICROCODE command $ apm Battery state: absent, 0% remaining, unknown life estimate A/C adapter state: not known Performance adjustment mode: cool running (1596 MHz) $ dmesg OpenBSD 5.5 (GENERIC.MP) #315: Wed Mar 5 09:37:46 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1048313856 (999MB) avail mem = 1011851264 (964MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xfd480 (40 entries) bios0: vendor American Megatrends Inc. version "080014" date 05/08/2009 bios0: O.E.M O.E.M acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S4) PS2M(S4) EUSB(S4) MC97(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) USB0(S3) USB1(S3) USB2(S3) USB3(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot
SOLVED mc: can't load library 'libssh2.so.6.0'
Hello Antoine, that fixed it. Thanks a lot :) Heiko Am 11.09.2014 um 11:35 schrieb Antoine Jacoutot: > pkg_add libssh2
Re: mc: can't load library 'libssh2.so.6.0'
On Thu, Sep 11, 2014 at 11:31:59AM +0200, Heiko Zimmermann wrote: > Hallo community, > > today I updated 5.6 current GENERIC.MP#57 amd64 and the packages. > > Now I get: "mc: can't load library 'libssh2.so.6.0'" > ( mc-4.8.12 ) > > libssh2.so.6.0 does not exist. > > Is this a known issue? What is the best way to fix it? Looks like libssh2 was picked up during compilation. Temporary fix until the mc package is fixed is to: # pkg_add libssh2 -- Antoine
mc: can't load library 'libssh2.so.6.0'
Hallo community, today I updated 5.6 current GENERIC.MP#57 amd64 and the packages. Now I get: "mc: can't load library 'libssh2.so.6.0'" ( mc-4.8.12 ) libssh2.so.6.0 does not exist. Is this a known issue? What is the best way to fix it? Thank you in advance. Regards, Heiko
