note that many converters are autotransformer based and if an autotransformer based converter fails in the wrong way you can eailly end up with most of the input votlage accross the output.
if you wan't to run a lot of US kit and don't mind a fairly big box then i'd reccomend one of the safety isolating transformers that are intended for supplying 110V tools on construction sites.
generally you try and moderate a wiki by trying to attract more good guys than bad guys and using bans against persistant vandals.
but i can imagine for all but the largest wikis/. could be very painfull indeed. there are a lot of/.ers and many of them do not have the best of motives (/. itself seems to have quite a trolling problem but we are used to it). This organisation got cold feet over the issue rather than trying to find a way through it.
yeah i agree that the main issue isn't emulating the CPU itself its emulating the whole system to cycle perfect timing. especially when a lot of the docs on the internet are flat out wrong. The gameboy actually has a fairly small selection of memory bank controllers in use. the nes otoh has an insanely large number of the things.
link is probablly the biggest nightmare in gameboy emulation. the only way to do it well is to emulate two gameboys in the same process with lock-step timing. few emulators seem to bother to do this.
also to support some apps (particularly demos but the occasional commercial game too) requires very precise emulation of the video hardware since they rely on operating with sub frame timing.
i was just pointing out that it was an error to say that the Z80 only had 256 instructions thats all.
the nes was 6502 based iirc which did indeed have less than 256 instructions
the Z80 (as used in the gameboy and gameboy color) on the other hand has the main instructions and then it has a prefix byte which selects another set giving the possibility of just under 512 instructions total (i dunno off hand how many of them it actually uses)
its nice to see such progress being made but unless this info hits some form of big tech news its going to be a while before most linux servers are running 2.6.10 or above. many people are still running 2.4.x because they do not belive that 2.6.x is currently a proper stable series (apparently the regreesion count in 2.6.x is very high).
the thing that all TCO type studies miss is the benifit of using computers.
how much more responsive is your own machine than an overloaded terminal server? does that extra responsiveness increase productivity and if so does that justify the costs of supporting such a setup.
this sort of thing can also apply to locking down boxes. it may make support staffs life easier but if done badly it can mean that users have to do far more clicking to get the desired result (examples: show desktop/minimise all windows gone and right click menus in the gui gone)
in the standard socket apis 0 is used as a code for random/os assigned port.
ie its what you use when binding a socket for an outgoing connection or if you wan't to have a socket to listen on but don't really care about its port number since you will be telling your peer that by some other means.
otoh the temptation to hack osx to run on normal hardware will be huge. maybe it will only ever run in a vmware like virtulised environment but thats still way way faster than the full cpu emulation that is currently needed to run osx on pcs.
it depends. copyright isn't supposed to protect the idea itself just expressions of it. With some high profile projects (think java class libraries) paranoid "clean room" methods are justified because the code is going to end up looking fairly similar even if written by totally seperate coding teams as the interface constrains it so much.
otoh with say kernel code the kernels are often so different in structure that its not such a big issue as only the general ideas and not any of the details will be able to come over anyway.
using bitkeeper was only a mistake if viewed in a narrow light. if it wasn't for bitkeeper i suspect linux would still be struggling on with no version control at all.
afaict the basic story goes as follows.
linus fought off version control and in doing so painted himself into a corner.
bitkeeper came along and exploited that corner to get linus to use it.
linus was forciblly stopped from using bitkeeper and made a crude but workable version control system that suited his way of working based on his experiance using bitkeeper.
some people bend thier way of working arround the tools they have. others try to make or find tools that match thier way of working. Different approaches which suit different personalities but i wouldn't say either is wrong.
i'm in the uk and if your only number is a mobile number it will REALLY put people off calling you for long conversations etc.
it will also make it hard when dealing with certain buisnesses that have policies that only allow calls to mobiles in emergencies.
i have a similar sitation in my university residence room, its embarrasing to have a relatively expensive to call 0870 number as your main phone number.
It seems very unlikely that anyone would want to use one of theese as thier only phone given that it costs others mobile rates to call them. to do so would just be considered highly rude.
otoh as a more versatile mobile replacement for those who don't know about conventonal voip providers like sipgate this could seem very attractive indeed.
i think the ubuntu cds only cover main though so theres a lot less of them. (ubuntu put the bulk of stuff from debian into a seperate area called universe and only put a relatively small amount of stuff in the fully supported main section).
also iirc ubuntu has some rich backer who can pay for things like massive distributions of free cds.
if you need debian cds (hint: if you have a decent internet connection you need cd1 at most) there are plenty of vendors who will ship them to you for a reasonable price (it seems many of them don't have sarge yet though).
the two real issues are drivers and 16 bit userland code (which there is still quite a bit of sloshing around: i wan't to play microsoft tetris and chips challange damnit).
as for the speed argument remember that amd64 has other changes. Most importantly it has far more general perpose registers for the compilers to use. so even in code that doesn't gain anything from the 64 bitness there can still be a speedup (doubtless you can find some benchmark thats slower you always can).
also i seem to remember that i386 took some time to be fully taken advantage of. why is it worrying that its taking amd64 a while.
you could change the sources.list and attempt an upgrade to a debian version more recent than the ubuntu release you are using. you'd almost certainly end up with at least some ubuntu stuff left on your system though.
Slashdot Mirror
note that many converters are autotransformer based and if an autotransformer based converter fails in the wrong way you can eailly end up with most of the input votlage accross the output.
if you wan't to run a lot of US kit and don't mind a fairly big box then i'd reccomend one of the safety isolating transformers that are intended for supplying 110V tools on construction sites.
generally you try and moderate a wiki by trying to attract more good guys than bad guys and using bans against persistant vandals.
/. could be very painfull indeed. there are a lot of /.ers and many of them do not have the best of motives (/. itself seems to have quite a trolling problem but we are used to it). This organisation got cold feet over the issue rather than trying to find a way through it.
but i can imagine for all but the largest wikis
yeah i agree that the main issue isn't emulating the CPU itself its emulating the whole system to cycle perfect timing. especially when a lot of the docs on the internet are flat out wrong. The gameboy actually has a fairly small selection of memory bank controllers in use. the nes otoh has an insanely large number of the things.
link is probablly the biggest nightmare in gameboy emulation. the only way to do it well is to emulate two gameboys in the same process with lock-step timing. few emulators seem to bother to do this.
also to support some apps (particularly demos but the occasional commercial game too) requires very precise emulation of the video hardware since they rely on operating with sub frame timing.
i was just pointing out that it was an error to say that the Z80 only had 256 instructions thats all.
the nes was 6502 based iirc which did indeed have less than 256 instructions
the Z80 (as used in the gameboy and gameboy color) on the other hand has the main instructions and then it has a prefix byte which selects another set giving the possibility of just under 512 instructions total (i dunno off hand how many of them it actually uses)
the cheap realteks seem to be cheap reliable and compatible with every linux system of whatever age that i've thrown at them out of the box.
afaict thier only problem is they use a lot of CPU under heavy load.
its nice to see such progress being made but unless this info hits some form of big tech news its going to be a while before most linux servers are running 2.6.10 or above. many people are still running 2.4.x because they do not belive that 2.6.x is currently a proper stable series (apparently the regreesion count in 2.6.x is very high).
you can use your own cablemodem?!
here in the uk cablemodems are supplied by the isp and i don't think you can use your own.
the thing that all TCO type studies miss is the benifit of using computers.
how much more responsive is your own machine than an overloaded terminal server? does that extra responsiveness increase productivity and if so does that justify the costs of supporting such a setup.
this sort of thing can also apply to locking down boxes. it may make support staffs life easier but if done badly it can mean that users have to do far more clicking to get the desired result (examples: show desktop/minimise all windows gone and right click menus in the gui gone)
in the standard socket apis 0 is used as a code for random/os assigned port.
ie its what you use when binding a socket for an outgoing connection or if you wan't to have a socket to listen on but don't really care about its port number since you will be telling your peer that by some other means.
otoh the temptation to hack osx to run on normal hardware will be huge. maybe it will only ever run in a vmware like virtulised environment but thats still way way faster than the full cpu emulation that is currently needed to run osx on pcs.
X for local apps uses unix domain sockets and even if it did use ip the loopback interface can be up even with no external network up.
what issues exactly are you having?
it depends. copyright isn't supposed to protect the idea itself just expressions of it. With some high profile projects (think java class libraries) paranoid "clean room" methods are justified because the code is going to end up looking fairly similar even if written by totally seperate coding teams as the interface constrains it so much.
otoh with say kernel code the kernels are often so different in structure that its not such a big issue as only the general ideas and not any of the details will be able to come over anyway.
using bitkeeper was only a mistake if viewed in a narrow light. if it wasn't for bitkeeper i suspect linux would still be struggling on with no version control at all.
afaict the basic story goes as follows.
linus fought off version control and in doing so painted himself into a corner.
bitkeeper came along and exploited that corner to get linus to use it.
linus was forciblly stopped from using bitkeeper and made a crude but workable version control system that suited his way of working based on his experiance using bitkeeper.
some people bend thier way of working arround the tools they have. others try to make or find tools that match thier way of working. Different approaches which suit different personalities but i wouldn't say either is wrong.
btw are there any sites that list kernel security issues and more importantly which versions are safe from all known issues?
i.e. a site that will tell me which versions are safe to use without worrying about backporting security fixes.
hmm can USB OTG be done without special hardware?
remember IPOD-IPOD could also mean firewire...
if you actually read the gpl you will see that it clearly defines
"The source code for a work means the preferred form of the work for
making modifications to it."
why is pam "insecure by design" and what alternative does openbsd propose?
tried cdparanoia?
i'm in the uk and if your only number is a mobile number it will REALLY put people off calling you for long conversations etc.
it will also make it hard when dealing with certain buisnesses that have policies that only allow calls to mobiles in emergencies.
i have a similar sitation in my university residence room, its embarrasing to have a relatively expensive to call 0870 number as your main phone number.
It seems very unlikely that anyone would want to use one of theese as thier only phone given that it costs others mobile rates to call them. to do so would just be considered highly rude.
otoh as a more versatile mobile replacement for those who don't know about conventonal voip providers like sipgate this could seem very attractive indeed.
i think the ubuntu cds only cover main though so theres a lot less of them. (ubuntu put the bulk of stuff from debian into a seperate area called universe and only put a relatively small amount of stuff in the fully supported main section).
also iirc ubuntu has some rich backer who can pay for things like massive distributions of free cds.
if you need debian cds (hint: if you have a decent internet connection you need cd1 at most) there are plenty of vendors who will ship them to you for a reasonable price (it seems many of them don't have sarge yet though).
right until they type su while typing over a keylogged pty set up by thier login profile.
btw british pc layout has " on shift-2 you could have just imported a pc keyboard from here and set up your pc for it ;)
also if you use a gui editor you are going to wan't to be reasonablly good at 1 handed typing
32 bit userland code can run on amd64 anyway.
the two real issues are drivers and 16 bit userland code (which there is still quite a bit of sloshing around: i wan't to play microsoft tetris and chips challange damnit).
as for the speed argument remember that amd64 has other changes. Most importantly it has far more general perpose registers for the compilers to use. so even in code that doesn't gain anything from the 64 bitness there can still be a speedup (doubtless you can find some benchmark thats slower you always can).
also i seem to remember that i386 took some time to be fully taken advantage of. why is it worrying that its taking amd64 a while.
you could change the sources.list and attempt an upgrade to a debian version more recent than the ubuntu release you are using. you'd almost certainly end up with at least some ubuntu stuff left on your system though.