Displaying 7 results from an estimated 7 matches for "booom".
Did you mean:
boom
2015 Jan 13
1
Warning - Raspberry Pi: WPA GUI & tinc crash
...t. i do have sufficent power supply and raspi is running headless with no additional peripherals.
without tinc installed, it runs flawlessly 24/7 via wlan or eth0 or even both.
with tinc installed, it runs flawlessly 24/7 via eth0
with tinc still installed, power off, plug in wlan, power on -> booom.
so there maybe a serious conflict with other software (network, wpa-gui,..?).
sven
2011 Aug 10
1
Change the IP/name of the domain member server
...server.
I have done almost everything, so the new server has the data, the ACLs
are transfered and are ok, but when I shut down the old server, change
the hostname of the new one to old one, changed the SID of the new
server to the old server (using net getlocalsid/net setlocalsid xxx)
and... booom. When I try to access the shares on the new server (from
windows) it asks for user name/password just like the new server is not
a member of the domain.
So is it possible to achieve what I want?
I'm not sure if other way, by using net ads leave (on new server) and
then join with changed n...
2015 Jan 13
4
Warning - Raspberry Pi: WPA GUI & tinc crash
tinc 1.0.19 worked fine on Raspberry Pi as long as my Pi was connected via ethernet cable.
Today i changed the connection to wlan. Pi crashed. worse, it was no longer operational, even if connected via cable.
recovery from backup before tinc was installed (yes, i had a backup ;)
tried again. installed tinc: worked as long as connected via cable. crash after connecting via wlan. no longer
2004 Jun 18
3
1.0-test17
http://dovecot.org/test/
Just mbox fixes since 1.0-test16. The logic is simpler and more correct
now. Can anyone break it anymore? I actually tested it a while with
Evolution and several mailboxes and it didn't break at least
immediately. :)
Now maybe a few more days and I dare trying this thing myself with my
real mboxes (yes, I'm still using them).
Dovecot mailing list archives could
2005 Jun 04
11
kernel oops/IRQ exception when networking between many domUs
Hi,
I try to build experimental networks with Xen and stumbled over the same
problem that has been described quite well by Mark Doll in his posting
"xen_net: Failed to connect all virtual interfaces: err=-100"
here:
http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html
As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS
and NR_DYNIRQS had been
2005 Jun 04
11
kernel oops/IRQ exception when networking between many domUs
Hi,
I try to build experimental networks with Xen and stumbled over the same
problem that has been described quite well by Mark Doll in his posting
"xen_net: Failed to connect all virtual interfaces: err=-100"
here:
http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html
As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS
and NR_DYNIRQS had been
2010 Apr 19
10
Overview of Ruby 1.9 encoding problem tickets
SUMMARY:
--------
I tried to identify the general and root causes for these problems
with 1.9, by taking into account non-utf encoding, current patches,
comments and ideas. I used ticket #2188 as base for explanations.
This is a long read. I wanted to include all the relevant information
in one place. I also included information about related tickets in LH
and their status. I decided that adding