_inky has quit [Read error: Connection reset by peer]
mp107 has quit [*.net *.split]
Danct12 has quit [*.net *.split]
joerg has quit [*.net *.split]
l_bratch has quit [*.net *.split]
ceene has quit [*.net *.split]
__20h__ has quit [*.net *.split]
avoidr has quit [*.net *.split]
__20h__ has joined #maemo-leste
avoidr has joined #maemo-leste
mp107 has joined #maemo-leste
Danct12 has joined #maemo-leste
l_bratch has joined #maemo-leste
ceene has joined #maemo-leste
Danct12 has quit [Changing host]
Danct12 has joined #maemo-leste
joerg has joined #maemo-leste
avoidr has quit [Quit: leaving]
<tmlind>
uvos: ok probably the mz608 binary won't work on anything else though
<Wizzup>
uvos: how can I test?
<tmlind>
Wizzup: hold vol down + power until you get to flash mode
<tmlind>
then from pc with usb cable connected, fastboot flash mbm allow-mbmloader-flashing-mbm.bin
<tmlind>
battery must be well chargerd, it will probably produce an error and then you have to reflash the original mbm.bin
<tmlind>
with fastboot flash mbm mbm.bin
avoidr has joined #maemo-leste
<Wizzup>
tmlind: but there is no allow-mbmloader-flashing-mbm.bin - right?
<tmlind>
Wizzup: oh i though you wanted to try out the mz608 file on mz609
<Wizzup>
well, uvos said that maybe the default is already permissive
<tmlind>
at least on mz617 you can only flash to cache partition pretty much, not sure about the user partition
<tmlind>
i just did mkfs.ext4 on the preinstall partition and untarred my rootfs there, seems to work just fine
<tmlind>
while trying to flash preinstall with an unsigned image produces an error and then you have reflash the original preinstall
<Wizzup>
freemangordon: ok yeah so this is something that changed in their dbus interface and it means wifi is broken in -devel
<tmlind>
uvos: looks like mmcblk1p15 cid partition on mz617 at least has a signature, maybe earlier models did not if that can be swapped like the link above says
mrgeanie has quit [Ping timeout: 265 seconds]
<uvos>
tmlind: well since VRZ_9.8.2OT_127_MZ609_CFC_1FF.xml contains a mbmloader.bin update and the purpose of allow-mbmloader-flashing-mbm.bin is to allow flashing mbmloader it would stand to reason that at least mbmloader partition is unlock in mbm.bin from VRZ_9.8.2OT_127_MZ609_CFC_1FF.xml
<uvos>
so maybe Wizzup should try this file
<uvos>
i know for a fact that on bionic motorola dosent blow any fuses to prevent you from downgrading
<uvos>
so you can flash any old mbm.bin
<uvos>
then if that dosent work maybe just maybe the mz608 file will work
<uvos>
obv. all this is a bit risky
<uvos>
but so is dding the rootfs and utags around
<tmlind>
uvos: worth a try, cheap toys to play with at least :)
<tmlind>
uvos: but hmm so if mbm.bin allows reflashing mbmloader, it still does not allow flashing other partitions with random images
<uvos>
tmlind: no but maybe mbm.bin from that file is in fact configured like allow-mbmloader-flashing-mbm.bin
<uvos>
ie also more permissive in other ways
<tmlind>
uvos: maybe, but i think on xt894 the difference was that flashing kexecboot to bpsw is allowed with allow-mbmloader-flashing-mbm.bin
<uvos>
there is no real reason why allow-mbmloader-flashing-mbm.bin is more permissve that mbm.bin in flashing bspw
<uvos>
right
<tmlind>
hmm or maybe it was needed to reflash utags actually
<uvos>
both i think
<uvos>
iirc
<tmlind>
on mz617, i noticed i had to use fastboot flash:raw boot boot.img to reflash the signed boot.img
<tmlind>
but i don't think flash:raw allows reflashing random images again
<freemangordon>
Wizzup: I think that's another reason to proxy it - if we use it in more than one place, we shall change all of the users next time they break the interface
<Wizzup>
freemangordon: this was more a code deficiency in my code
<Wizzup>
freemangordon: I just assumed the interface path would not change, but they made it zero indexed
<Wizzup>
freemangordon: so we make a proxy that does the same for multiple interfaces? wouldn't solve the problem per se
<freemangordon>
this is interface change by all means
<uvos>
i dont think its senseble to proxy deamon everything for this reason
<freemangordon>
that's why I said "another reason" :)
<freemangordon>
Wizzup: yeah, got it
<Wizzup>
freemangordon: that's the only change required to make it work for now
<freemangordon>
but, I have to change connui as well
<Wizzup>
shared lib maybe makes sense, proxy not so much imho
<freemangordon>
ok
<Wizzup>
Of course I can find the first interface and just use it, but as it stands, icd2 plugin cannot deal with more than one wifi interface anyway
<uvos>
we should do that...
<uvos>
and switch to presistant names
<freemangordon>
BTW, that's something we shall fix
<uvos>
instead of wlan0 wlan1 etc
<freemangordon>
I think we can use service_id, but not sure
<uvos>
since using only one interface, but allways the same one is better than using a random one depeding on what driver gets loaded first...
<Wizzup>
pull request welcome for that
<Wizzup>
Looks like I can use this: mdbus2 -s fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 fi.w1.wpa_supplicant1.GetInterface "wlan0"
freemangordon has quit [Ping timeout: 264 seconds]
<Wizzup>
all of this will get much more complicated now, blergh
_inky has joined #maemo-leste
<Wizzup>
freemangordon: parazyd: I'm building a new libicd-network-wpasupplicant which deals with the wpa supplicant interface name change, but as the current fix is a hack, it is really important that they stay in -devel for now, and independently *cannot* be moved to non-devel
inky_ has quit [Ping timeout: 264 seconds]
<parazyd>
okay
freemangordon has joined #maemo-leste
<parazyd>
New wpasupplicant is also devel only
<Wizzup>
parazyd: yes, but this is a heads up(tm)
<parazyd>
:)
<parazyd>
Noted
<Wizzup>
I will have to add InterfaceAdded and InterfaceRemoved notifiers, and all the code will have to accept interface data as arg, and it will need to be managed and won't be available on start, so it's all getting much more complicated now unfortunately
<Wizzup>
I can't write that code now
<parazyd>
Can I help?
<Wizzup>
well, it's just that the wpa_supplicant change made this more apparent
<Wizzup>
as long as we push them in sync this shouldn't cause major headaches, but it's something that needs to be done
<Wizzup>
if you want to help, sure, but I imagine it's at least a few hours of work, maybe more
<Wizzup>
and also really we'd probably just pick the first interface we find anyway
<parazyd>
Agree on the interface choice. I guess this is what the kernel sets up first.
<parazyd>
btw. if needed we can also use eudev for iface naming
<Wizzup>
yes, but this is about the wpa supplicant dbus path for the interface
jk has joined #maemo-leste
<jk>
hello #maemo-leste!!
<jk>
rock on!
<jk>
I need some assistance with my dorid4. i beleive I can't gert my wlan0 up to find and connect to wifi and lan
pagurus has joined #maemo-leste
<Wizzup>
jk: hi, are you on -devel?
<jk>
eehmm.. I think not. I am new to irc
<Wizzup>
ok, so this has been a consistent problem since you tried maemo leste?
<jk>
nop, I tried to change my user password to be able to ssh as non-root with the command passwd
<Wizzup>
ok
<Wizzup>
what image did you flash?
<jk>
the problems started after that
<jk>
let me check...
<jk>
... I flashed it last year, may I think... things have been going smooth. even the beowulf upgrade was fine
<Wizzup>
heh, neat
<Wizzup>
so some recent upgrade broke wifi for you?
<jk>
no,I don't thik it was an upgrade. I was connecting over ssh form my laptop but only as root, as I had no "user" password (I still only have the root-user and the user-user))
<jk>
so I restarted my Droid4, booted to the emergency shell or something like that
<jk>
logged in as root and ran passwd. I rewrite the root password to the same (not surre if this changed anything in the deeper level) and then changed the user password... once throrough passwd -expire but HIldon could not start automatically, so I changed it back again to empty
<jk>
this last time again over the leste emergency shell. with passwd user (if I remember right) and let it blank and also delited the hash from the shadowfile following some internet guide
<jk>
...using nano
<freemangordon>
Wizzup: ok, so, lets agree at least that icd2 plugin will expose dbus interface to get the current wlan interface, otherwise we'll have to duplicate the same code in connui
<freemangordon>
or if you have a better idea, please share
<uvos>
why is connui interacting with the interface directly anyhow?
<uvos>
thats icd's job no?
<Wizzup>
jk: hm, ok. is the wlan0 interface visible in 'ifconfig'? and it wpa_supplicant running? ('ps xua | grep wpa')
<Wizzup>
uvos: all of this stems from the hidden wlan ap hell
<Wizzup>
uvos: freemangordon wants to port the interactive UI to add a hidden AP to the settings without using the settings
<Wizzup>
uvos: this requires active scans for the hidden ap, which means the UI has to interface with something
<uvos>
yeah no
<uvos>
lets not leak the implentation details of the layer below icd to the ui
<uvos>
why cant icd2 just get a new function to scann for hidden aps
<Wizzup>
so the maemo fremantle UI also violated this by just issuing a scan directly using wlancond
<Wizzup>
uvos: yes, I was thinking that as well- let's do this in icd2
<uvos>
yeah well fremantle is badly desinged allmost everywhere
<uvos>
Wizzup: ok that sounds sane
<Wizzup>
I think this is also what freemangordon is suggesting
<Wizzup>
I am just not sure if it should be in the plugin or in icd2 itself
<uvos>
jk: did your device reboot during a recent update?
<sicelo>
Danct12: you said Dillo does JS? last i recall it didn't :-/
<jk>
@uvos: not that I remember
<uvos>
i had to run dpkg --configure -a to get wifi back on bionic after a recent update rebooted before the pacakges where configured
<jk>
@Wizzup: I am checking...
<uvos>
jk: try that
<jk>
ok!
<jk>
dpkg --configure -a run successfully as root
<jk>
wpa_supplicant found on htop (with several flags) trying ps now...
<uvos>
if dpkg --configure -a did anything you have to reboot
<uvos>
also check ip addr for the wlan0 interface
<Wizzup>
parazyd: if this is the case, we really need to figure out that random reboot ^
<sicelo>
i don't recall leste having an /etc/wpa_supplicant/wpa_supplicant.conf ...
<sicelo>
s/having/having or using/
uvos has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
<jk>
... extra info: with vipw -s on the line of user i have "user::" 'cuz I deleted the password there after my manual passwd user change aiming for ssh from laptop... most entries under vipw -s have "<name>:*:..."
<freemangordon>
Wizzup: icd is by no means wlan only daemon, neither we shall tie it to wpa_supplicant, that's why I suggested either a daemon that exposes a common interface to both plugin and ui or dbus interface in the plugin itself
uvos has joined #maemo-leste
<jk>
ip addr shows me wlan0 as number 3:
<freemangordon>
To me having a separate daemon is better, but...
<jk>
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
<uvos>
jk: i assum wifi dosent work after reboot
<uvos>
jk: please descibe symptoms in detail
uvos__ has quit [Ping timeout: 272 seconds]
<uvos>
jk: what dose not work mean
<uvos>
dose it not scann
<uvos>
not connect etc
<jk>
no scan so no connect. I can't get it up
<uvos>
ok so the network dialog dosent show anything
<uvos>
right?
<jk>
it usually connected automatically after boot (some seconds later) no I see no available connections on the gui
<jk>
jup, Select connection is empty
<uvos>
ok
<jk>
"No connections available"
<uvos>
what dose maserati-callibrate say
<Wizzup>
jk: did a reboot help after the dpkg --configure -a ?
<jk>
as root?
<Wizzup>
jk: the reboot? you can use the UI for it too
<jk>
no change after dpkg --configure -a and reboot
<Wizzup>
freemangordon: are you up for writing the code for that interface?
<jk>
maserati-calibrate as root?
<uvos>
yes
<Wizzup>
freemangordon: I think I'd like to take my hands off of this hidden AP business now, icd2 should support it OK now if it is configured from "Internet Connections" UI
<jk>
is shows MAC addr from NVS: ...
<jk>
Calibration already performed
<uvos>
ok
<Wizzup>
freemangordon: I'm fine with whatever solution you prefer, as long as it doesn't mean I have to write more dbus code
<freemangordon>
Wizzup: yes, why not
<jk>
I did that las year...
<uvos>
so its not that
<freemangordon>
I was thinking to reuse wlancond interface
<uvos>
jk ok yeah i thought cal might have goten lost somehow
<freemangordon>
afc I will first check if it fits for what we need it
<uvos>
im all for Wizzup writing more dbus code
<freemangordon>
:)
<Wizzup>
jk: so the sympton is that nothing shows up in the 'Internet Connections' status dialog?
<uvos>
dbus everywhere
<uvos>
everything dbus
<Wizzup>
uvos: I am fine if others write dbus code, but it breaks my brain
<jk>
yes, that is the symptom
<uvos>
jk: can you use wpacli to scann for networks
<uvos>
?
<Wizzup>
that's wpa_cli
<Wizzup>
the commands are 'scan' and 'scan_results'
<freemangordon>
how's that different from calling dbus?
<Wizzup>
freemangordon: this is us helping jk debug his wifi issue, not related to our discussion :)
<sicelo>
if wpa_cli has 'issues', then the problem is unlikely to be in libicd-* or icd*
lyubov has quit [*.net *.split]
lyubov has joined #maemo-leste
<jk>
oh! scan results is actually scan_results?!
diejuse has joined #maemo-leste
<Wizzup>
jk: yes
<Wizzup>
freemangordon: something else I noticed (of course), a dbus-issued scan is not the same as a scan issued over the control socket interface it seems
<Wizzup>
one calls wpa_supplicant_trigger_scan and the others calls wpa_supplicant_req_scan
<Wizzup>
freemangordon: and of course only the control socket 'scan' seems to do the right thing, I believe
<Wizzup>
jk: ok, so we need to figure out why the data is not making it to the UI
<Wizzup>
freemangordon: no
<Danct12>
sicelo: i never said dillo supports js
<sicelo>
Ok. I must have misunderstood. Apologies
<freemangordon>
Wizzup: ok, I'll think about it for a while, but maybe implementing wlancond interface by using socket interface looks sane, albeit lots of work.
<freemangordon>
in a separate daemon that is
<Wizzup>
freemangordon: the socket interface is extremely simple, but you might have the same perms problems
<freemangordon>
that way we'll be able to use Nokia icd2 wlan plugin. And your work won;t be in vain, as most of it will go in that daemon
<freemangordon>
that daemon will run as root
<Wizzup>
what do you mean? nokia icd2 wlan plugin?
<sicelo>
wlancond, iiuc
<jk>
Wizzup: ok. we can check that. so the password overwrites that I did have no importance?
<uvos>
but leste currenly explodes if you dont have sudo without pw
<Wizzup>
freemangordon: if we really go down that route I think we just want to look at NetworkManager
<uvos>
+1
<jk>
I did rewrire the sudo password to the standard
<uvos>
uh
<uvos>
yeah that causes lots of issues
<freemangordon>
Wizzup: why is that?
<uvos>
jk: please restore default sudo config
<freemangordon>
I mean - it is obvious that wpa_supplicant dbus interface has issues, no?
<uvos>
sudo usage in leste is badly broken
<jk>
ehm the root password I mean!
<uvos>
oh
<uvos>
ok
<uvos>
thats fine
<Wizzup>
freemangordon: there is a lot of work going into rewriting what essentially already exists in some other form, and it took me several months to write the wpa supplicant plugin for icd2, and I did it because you wanted it that way (which is fine), but I really don't understand why we would need to give wlancond some wpa supplicant interface and then switch to the other nokia plugin which likely will
<Wizzup>
have way more issues and backwards things
<freemangordon>
Wizzup: hold on, I was just sharing an idea
<Wizzup>
ok, sorry, I'm not upset
<Wizzup>
it just feels like a very niche interface
<freemangordon>
on the other hand we still don;t have solution for coule of things
<freemangordon>
not to say we still don;t support ad-hoc
<jk>
ok. I only rewrote the "su"-password. sudo is still possible without password
<uvos>
jk: thats fine
<uvos>
and not the issue
<Wizzup>
freemangordon: It actually is not very hard to support ad hoc I believe
<uvos>
networkmanager supports adhoc
<Wizzup>
freemangordon: I think the wpa_supplicant dbus interface isn't that bad, but apparently it's awkward regarding hidden APs
<uvos>
and bt pan and .....
<freemangordon>
uvos: please, stop that
<freemangordon>
I guess wicd does it too
<freemangordon>
none of them is mobile aware
<uvos>
bullshit
<freemangordon>
they don;t integrate with mce for example
<uvos>
mce has no role in this
<freemangordon>
yes, it does
<uvos>
no
<uvos>
it just consumes the offline state
<uvos>
it dose nothing with it
<freemangordon>
ok, it seems leste is going in a direction I am not sure I support
<freemangordon>
the project was started as a try to bring fremantle experience based on modern distro
<Wizzup>
I am not advocating for using networkmanager per se, I am just frustrated with the amount of work required for a very niche feature (hidden aps) when I'd rather focus on bigger things
<uvos>
i dont see why fremantle experiance has anything to do with what bacgriound deamons we use
<uvos>
we want fremantles ui over a modern distro no?
<freemangordon>
uvos: you dont; have experience with fremantle, right?
<uvos>
best case scenario we dont have to maintain anything but the ui
<uvos>
ofc thats not feasble in all cases
<uvos>
but the less we have to maintain the better
<freemangordon>
in which case it will turn into a mock of fremantle
<sicelo>
No. We wanted fremantle UX, at least I did. Not just UI
<freemangordon>
just a shell
jk has quit [Read error: Connection reset by peer]
<freemangordon>
sicelo: exactly my point
jk has joined #maemo-leste
<freemangordon>
and I still want it
<uvos>
right hildon-desktop should just be a xdg shell (or session in xdg language)
<freemangordon>
(fremantle UX)
<Wizzup>
freemangordon: I think the current icd2 mostly supports the fremantle ui/ux, just not yet with hidden aps
<freemangordon>
uvos: again, you have no experience with fremantle, I wonder how you are so sure what HD should become?
<Wizzup>
if there are specific UX you would like, it would be good to write them out clearly because otherwise there's no discussion to be had
<freemangordon>
fremantle is way more then just HD
<uvos>
i ment "hildon" not hd
<uvos>
as in all of the ui stuff
<Wizzup>
jk: did going to passwordless sudo solve your problem?
jk has quit [Read error: Connection reset by peer]
<freemangordon>
Wizzup: part of the UX we're discussing is the ability to add hidden wlan from the wizard
<uvos>
Wizzup: no it dident he had passwordless sudo allready
<freemangordon>
niche or not, it is there and users try to use it
<freemangordon>
see the issue we have opened
<Wizzup>
freemangordon: let me just note that with -devel you can add it to "Internet Connections" and it will work
<Wizzup>
you just check the checkbox that says it's hidden
<freemangordon>
sure, but thats not what I am talking about
jk000 has joined #maemo-leste
<Wizzup>
I agree there are outstanding issues (and we can get back to discussing those when you want), but I think if we make a poll, more users will care about some other parts :P
<uvos>
freemangordon: one thing im sure of is that we are like 4 people
<jk000>
... sorry if I had someone else's nickname! :P
<freemangordon>
uvos: so? it was only 1 at the very beginning, how that changes the things?
<uvos>
and what 4 people can credbly maintian and improve in spare time is.. not alot
<uvos>
so we must share code with others as mutch as possible
<freemangordon>
uvos: then we'll fail
<uvos>
that meas shareing with deskop where possible
<freemangordon>
not the end of the world
<uvos>
and with phosh and plamo where not
<freemangordon>
but better fail than romise and not deliver what is promised
<Wizzup>
freemangordon: uvos: we don't know if networkmanager is no longer mobile aware and what we can do with it, but from a practical point of view I think we should stick with what we have until we have a more functional experience
<Wizzup>
freemangordon: uvos: I don't think this discussion about UX is relevant, I think we more or less agree on the goals, and if someone magically did all the work to support fremantle interfaces (functionally equivalent) with networkmanager backend we'd use it, but it's not there, and it will also take a lot of work to get there
<Wizzup>
freemangordon: uvos: other mobile distros will also try to make it as mobile as possible, and some of them use networkmanager, so I am sure they will eventually have to tackle some of the same problems
<Wizzup>
freemangordon: uvos: Personally I am totally fine with telling the user to configure it through the Settings -> Internet Connections, and I'm pretty sure the user would be happy too.
<Wizzup>
freemangordon: uvos: My point really was that I don't -personally- want to invest more time in a niche side of an already niche feature that we've really now implemented already
<uvos>
sure that sounds mostly sane
<uvos>
im not sure on the same goals part tho
<Wizzup>
So I'd be fine with leaving the bug report open specifically for the easy wlan wizard with hidden ap support
<uvos>
i think freemangordon has other goals
<freemangordon>
Wizzup: UI is just missing a single call (be it dbus or whatever) to get hidden wlan properties at it should work. We just need to agree upon how that call shall be issued and I'll implement it
jk000 has quit [Read error: Connection reset by peer]
<Wizzup>
freemangordon: sounds good
<freemangordon>
*and it
jk000 has joined #maemo-leste
<Wizzup>
jk000: I am trying to think of how to help you debug this. is icd2 running?
<Wizzup>
jk000: 'ps xua | grep icd2'
<jk000>
thanx a lot!!
<jk000>
let's see
<freemangordon>
but, I involved the other things that we miss currently (like reg domain, adhoc etc) so while we plan how to implement that call which is needed for hiden wlans, if possible, to fix or at least make those issues fixanle with less effort
<jk000>
yes, it is
<Wizzup>
freemangordon: I think we can really make all of that work with the icd2 plugin I made
Daanct12 has joined #maemo-leste
<freemangordon>
ok, lets spend some time tomorrow to agree upon the interface
<Wizzup>
jk000: so I am thinking that if I had access locally, start icd2 manually with low log level, and monitor the logs, but I am not really sure what to tell you to look for, and given that you have no connectivity, if I find it hard to figure out how to continue from here
<freemangordon>
UI->icd2 plugin that is
<Wizzup>
freemangordon: ok
<Wizzup>
jk000: so if you run this as root '/etc/init.d/icd2 stop' and 'icd2 -l0' icd2 will write info to /var/log/daemon.log, but other services also log to it
<Wizzup>
you could look at those logs in real time with 'tail -f /var/log/daemon.log' and maybe see if you can spot the problem, but all of this is hard on the phone screen
<Wizzup>
jk000: do you think you could set up usbnet?
<Wizzup>
So you're saying that the usb host most just works with leste on the d4?
<Wizzup>
If you could make photo or video of that, we'd love to see it
<jk000>
... still struggling with my DAC to get highest quality audio
cockroach has joined #maemo-leste
<jk000>
I beleive usbnet will work i just gotta learn it. which will be added to my toolbox! yeah!
<jk000>
I'll try to make a video, where do I send it??
<Wizzup>
jk000: conceptually it should be as simple as 'connect the droid 4 to a PC', 'set up the IP on the PC side', ssh to the phone
<Wizzup>
jk000: if you can upload it somewhere and link it, that's perhaps easiest
<Wizzup>
I don't know what you preferred method is, you can also upload it to some site like youtube or the foss ones
inky_ has joined #maemo-leste
<jk000>
jup, and in theory that is extensible to many devices, right? i will read into that!
<Wizzup>
jk000: all leste supported devices should expose it, I use it all the time for debugging
<jk000>
alright... I'll see what I can do and get back here. I am still catching up on irc-tech. 1st time runnign Hexchat and seems preatty easy. with irssi I had some issues as I am a newbie
_inky has quit [Ping timeout: 264 seconds]
<jk000>
thanks, leste-community!! keep up the pioneer work and enable freedom further!
jk000 has quit [Quit: Leaving]
jk has joined #maemo-leste
jk has quit [Client Quit]
jk has joined #maemo-leste
jk has quit [Client Quit]
jk000 has joined #maemo-leste
jk000 has quit [Client Quit]
<Wizzup>
just debian things: installing hostapd means it gets auto started on boot, and if you configure it (via config file) for usage at some point, it will interfere with wifi
<Wizzup>
and I removed it from the runlevel, but every time it's updated, it gets added back to the runlevel
<uvos>
more like just devuan things
<uvos>
since debian on systemd dosent have this problem
<Wizzup>
uvos: it doesn't autostart services?
<uvos>
it dose but you can ask systemd if the user disabled it or something
<uvos>
(not sure how it works exactly but it only enables the service once)
<uvos>
might just be that the systemd dpkg scripts are better idk
<cockroach>
you should be able to do the same thing with normal init scripts if you do it the "proper way" (rather than just removing the symlink). I think.
<cockroach>
i.e. with update-rc.d
<Wizzup>
uvos: I think this is problem with dpkg
<Wizzup>
I think it probaly does the same thing
<Wizzup>
when I said 'I removed it from the runlevel', I meant 'rc-update del hostapd'
<Wizzup>
mbut maybe update-rc.d does more
<cockroach>
okay, sorry for the noise then
<Wizzup>
very welcome :)
<inky>
jk000 if you come and see this - so you see the mouse pointer on the screen?