I have a few requirements of the system that I'm building essentially, and those requirements should be fairly trivial in all their glory to catch, and to handle in a discrete way to be sure about the whole thing.
There are a few things that I should probably elaborate on. I've ordered the things that I might need, or rather, the things that I need, which are highly discrete. I have some WLAN equipment coming my way, and that's going to be the definitive thing in essence. The WLAN equipment would be used as a system to check out the existing WLAN network structure that we have in our neighbourhod. This is something that I'm just very interested in, because it allows for some neat tricks to be done, along the way. The problem, as I see it, is the house I live in, and the houses nearby are behind a very strict enforced concrete walls. Nothing strange here, just a little reminder in the path that I wish to take. I'm left believing certain things about some functionality that I do have, and that will be discrete in that sense. No looking back, no nothing. Not that I will essentially ride the whole concept. Surfing on somebody else's line is not what I consider highly amicable in any possible way, to be sure about that. The things that they put me through, and things which are highly amicable.
Ugh, too much sleeping and not enough caffeine. Bad combination, atleast in my opinion.
Looking past the point is really harsh, really hard, and provides mostly invariable things which are not discrete in any way. The N800 will define the things that I should be doing, and what we should be looking at in all essence. Not that I like the N800, infact, I think it's a shitty piece of work. But it has a big screen, and that screen can be used for a few things essentially, a lot of things when you look at it, the definitive factor being that we shouldn't take many things for granted, and leave even more of them hanging. The N800 will display the essential things behind the whole thing. There are a few things that I should probably elaborate a bit on, to make a clear and distinct difference between the things. This is nothing strange, or anything intimidating in that sense. Oh well.
There are a lot of interesting things going around the place essentially, and I'm left to believe a few things about the whole concept. Nothing strange in that sense, nothing too damning. A good enough system will do for my purposes. Nothing damning should be done, and there are even less things that should be considered, and maintained in the whole concept behind this whole issue. The things that we do, and what we do properly, is the defining and the damning thing in essence. I'm pretty sure I'm left of at the place where I shouldn't be in the first place. Looking back at things, this might prove to be highly definitive, highly discrete.
I'm not sure about the facts that we do have, and what defines the whole thing in large enough quantities, or define them at all, infact. I'm standing here, to believe that C++ is a really fucking weak language. I know it, but the semantics are so out from here, that there is simply nothing that can redeem the situation. Fuck that shit, I'm going to get something to eat.
Looking past the thing, I have few regrets, nothing quite states the same as the whole point behind the thing, the thing that we hold dear, in our hearts, and so forward. Nothing essentially moves around the whole concept better than a good old fashioned assfuck. I'm left to believe certain things about the whole concept thereof, and I'm going to take the whole thing, and shove it essentially. There are some glitches, some snags, and so forth, that I will have to deal with properly at one time or another. I for some reason prefer to handle them as soon as possible, making it less likely for things to mess up completely, and when I say completely, I mean like a proper good old fashioned assfuck.
I have a plan, it's a cunning plan, and I'm going to set it forth the whole point, make things more understandable and less prone to errors. For some reason some people tend to dis the concept. I don't know the reason. But, as it stands, there are going to be two more computers instead of three more. First of all, I don't care about the whole concept of having your shit pushed in at the wrong moment, that will make it look awkward, and so forth. Shit it's atavistic out here. Sunny Espoo to be sure.
I must make things happen in a discrete fashion essentially. These things imply some things, and have as their requirements some others. I'm not sure about the whole concept thereof, but I'm left to believe certain things about the concept, something less damaging, and so forth. I'm getting a machine to act as my primary controller for things to come, that is, the brute machine, and it's going to have a companion. I'm not yet fully sure about the whole prospect, and how I should approach it, but there are a few things that I hold dear, and they are quite a lot of work, some other things aswell, as also some things that do convey the whole subject thereof. I'm going to deal with these things as well as possible, as humanly possible, because that's just what I do, what I get paid doing.
The hard and strong will never surrender. There is an ethical approach to this all. The allegory, Starship Troopers, got the thing right. There are hard and strong people. Not by any stupid militaristic measures, the harder you are, the less you're interested in somekind of fascism. The people in the military are weak. They are conformists, they don't contribute anything to society. There is need for the hard and strong. They will take the point, and move it towards an place where nothing essentially disintegrates. Only the hard can call themselves citizens, and it's up to the hard to defend the weak ones. The whole concept is easily understandable if you take into account a few things, some things that are separate for each other, and some things that should be considered essential. The hard and strong will never surrender.
I don't understand this bullshit that keeps on getting up on its feet regarding the usability and suitability of some systems for a few other things that I take as granted, and that are, infact, granted. This is KDE 4.x, and the whine that goes along with it. I don't get the point, I mean, I use KDE, and I think it's grand, and if they have changed something, but kept the fundamental issues, then I'm bound to use that too. No hassles, no nothing. This is the thing that I'm keeping and that I'm holding true, to the point where it doesn't anymore reflect my ability to operate properly. I give a flying fuck about some details they may have put into the fucking system. I mean, if Konsole works, and then some other software as well, then I'm not going to even consider changing the windowing environment. I mean, that would be stupid. I don't like stupidity, and stupid people, so why the hell not. There are always usability nazis that are going to whine about any change you do. I'm not one of them. I think that KDE provides a kick ass environment, and if it's going to be even better, judging by the essential screenshots that I've seen, then that's just super. Hopefully they have the strength and will to keep up KDE development.
I'm feeling a little bit lonely, a little bit out of context essentially. And a whole lot less amicable than something I could and should be.
Schneier writes in his Cryptogram newsletter about CCTV cameras, and their applicability in the real world, or rather, how badly the CCTV cameras fail at their potential, and the real essential flow of things that they should provide. Here's a really hilarious picture of the whole deal. For now atleast, here's a link to the Cryptogram newsletter by Schneier.
Hmm, I seem to have a solid set right here. You mean this set right here? Yes, I mean this set right here. There are all the obvious things that a man needs, and if I get to keep the Intel Core 2 Duo machine, it will be the all important stormbringer machines. I'm obviously going to have a setup of other things as well with the whole system. There is a FreeBSD machine that runs things. It should be the one I'm plugging all kinds of different GP-IB thingies into it. But as it stands, I no longer use GP-IB equipment. I have replaced them with some other things essentially. I better not get into the details about my setup here at home, because I want to maintain a level of advantage to the whole system. This means a few things, and implies some more, but the FreeBSD machine is for example running an 200MHz oscilloscope, that proves to be quite neat to have. I've programmed a interface and driver for the solution, but that's enough about that thing. Getting traces of 200MHz signals and being able to display them on some machine, it is really awkward, and to some extent really harsh. We had some long time ago at work an Tektronix oscilloscope with 4 channels and up to 100MS/sec., and the price for that thing was stellar. I mrean really fucking expensive. Well I guess they need to make their profits somehow, but as it stands, my setup could also be used for a few other things, like analyzing the narrow band spectrum through an efficient enough ADC. There are things that this is useful for. Very useful. Hum, this is because of my involvement in certain electronics projects and the kind, really. I'm not terribly devastated by the prospect. There are some things we should be doing, and there are some things we should probably avoid. The later being somewhat more classical in representation. But I'm not picky.
Do something good with your time, and do it properly. The emphasis goes on the word properly. I'm left to think that a system that I have always wanted to build, ever since I mastered UNIX back in the 90's, but it's not a easy thing at all, infact, it's quite harsh, quite hard to get right in the first place. Oh well, I have my embebbed bench right here, and it's going to serve as a platform for development for now. I may extend it, if there is such need by some place essentially. The reason for wanting to have ZFS and FreeBSD together on the case, is quite obvious. I'm very familiar with FreeBSD semantics, I've been part of a team that ported FreeBSD to a platform that wasn't supported yet, and before you ask yourself, no, it wasn't ARM, but that's all I'm going to say about it. Mind you, this was the 2.x days of FreeBSD, and the port wasn't terribly easy in any way. Oh well, I'm left wondering about the things we are doing, and what we should set as a formatted spaceholder for the whole concept to begin with. I'm envisioning a system that is highly efficient and highly usable in the case that you have something to work on, something to scale back on. This is a simple computer, but there are things that a computer may do, and there are things it may not do. Throw enough power at some problem, and you're bound to get a good response. This is how the world works, all energy flows according to the whims of the great magnet. Looking past the thing, I'm left to believe in certain additional tasks essentially.
I have some plans essentially here, some of them need some consideration, and some forethought essentially. I'm left to believe a few things about the whole concept around here. The concept can't be probably very well disintegrate the whole concept towards the point where we do work at, and handle things at.
I drew some schemantics of the embedded board, and how it should work, and what are the components in it, and so forward. The idea is ofcourse to have a board where I can sit down, fidget around with different kinds of ideas, and come to somekind of consensus thereof about the system really. I will probably end up needing a few things for this setup, that is, there will be warbringer, which shall be running on the left side of the board, two large CRT displays. Then there is a big space of things that shouldn't be taken too harshly under no circumstance essentially. There will be a keyboard to control both the machines, that is, one system with dual DVI output and one Matrox G200 MMS card to drive the other set of the whole concept. There are going to be like 6 monitors in this setup, 4 of which are LCD screens. If I felt really bold, and I do feel like that sometimes, I would go ahead, and build things out of Silicon Graphics 1600SW monitors, that would probably rock, a lot. Yes, that's going to be the plan. I plan on setting this kind of setup up as soon as I get somekind of data on how the hell the attachement of the units should be done to the wall. This is a small problem essentially. I hate using power tools. But this just calls for it, somehow.
It'll be good to get the electronics bench into working order. I need still some particulars, but it should be fairly solid at this stand. The computers, them I have, the harddisks, they are saved, each morning at 07:00 there will be a tar package made of the whole source repository filesystem entry, and that will then be rzip'ed or 7-Zipped. Then I'll push the backup to a machine that is going to be the backup host. I do fancy my shit, and I think it's wonderful, in every regard. Looking back past the point, I'm left feeling somewhat stranger than I really should, and this is probably a good thing. A good thing for me. They way I've planned the usage of the SGI 1600SW monitors, it's going to be a riot. I probably need somekind of system setup for my doings, so that there is no specific problem inherent with the whole issue. The wall of LCD's is going to be covered by a cupboard, and there are going to be some things upon it. This means some things that I really use will be setup for good on this system. The system should be separate from the rest of the network in that sense. It's a small system that I intend to run a Windows domain controller on, and do all the things that are required for remote authentication, and so forth. Just whatever the hell you have. I'm left to believe in certain things, and this could be the defining thing behind it all, the ultimate that I'm looking for, the very thing that makes people in the business tick and so forth.
The embedded board will also house somewhere, I'm not sure where yet, but it should be somewhere, behind a power circuit that has an relay that controls the flow, on or off, and I'll just make sure it doesn't draw current to the soldering iron(s), because I recon it could be dangerous to leave them like that at home for a day at the work. There are distinctive things that can be done, some of them very cool, the rest, well, very strange indeed. Why this doesn't seem to correlate very well with reality and the whole concept seems a bit flawed, I'm still left to believe in certain things, and that is essentially tinkering with electronics. There are however a lot of people that I do hate. That is, people who tinker with electronics, since usually they are wankers, bed wetters or both. Fucking wankers. I hate electronics tinkering assholes. I mean, I'm a practical guy, if there is something that needs to be done, I'll do it, but, not without reason or some argumentation in some path. Electronics for the sake of electronics is just masturbation.
I kindof wish two things right now: 1) that I had caffeine 2) that I hadn't taken 900mg of Seroquel some 3 hours ago.
The 2x2 matrix of SGI 1600SW's will be sweet, and should make it more easy for me to comprehend the whole systemic change that is required thereof from the whole system. With that in place, I can easily run just about whatever it is that I want to run, and it will just go through. No hassles here essentially. The both machines with screens are going to be Windows XP machines. They are going to run everything and such things essentially.
Ok, there are two more systems that I need, and then I should be figured out with the whole laboratory. I'll simply go ahead and define things as well as I can, and maintain a certain aptitude towards it. I'll have my hacking machines, my machines for some things, and others, and so forward. I'm going to move this whole shit towards an amicable end, essentially. There are really few things that I should be looking for. Some of them less than amicable, some of them not very neat, and so forth.
There are a few things that I should probably elaborate on. I've ordered the things that I might need, or rather, the things that I need, which are highly discrete. I have some WLAN equipment coming my way, and that's going to be the definitive thing in essence. The WLAN equipment would be used as a system to check out the existing WLAN network structure that we have in our neighbourhod. This is something that I'm just very interested in, because it allows for some neat tricks to be done, along the way. The problem, as I see it, is the house I live in, and the houses nearby are behind a very strict enforced concrete walls. Nothing strange here, just a little reminder in the path that I wish to take. I'm left believing certain things about some functionality that I do have, and that will be discrete in that sense. No looking back, no nothing. Not that I will essentially ride the whole concept. Surfing on somebody else's line is not what I consider highly amicable in any possible way, to be sure about that. The things that they put me through, and things which are highly amicable.
Ugh, too much sleeping and not enough caffeine. Bad combination, atleast in my opinion.
Looking past the point is really harsh, really hard, and provides mostly invariable things which are not discrete in any way. The N800 will define the things that I should be doing, and what we should be looking at in all essence. Not that I like the N800, infact, I think it's a shitty piece of work. But it has a big screen, and that screen can be used for a few things essentially, a lot of things when you look at it, the definitive factor being that we shouldn't take many things for granted, and leave even more of them hanging. The N800 will display the essential things behind the whole thing. There are a few things that I should probably elaborate a bit on, to make a clear and distinct difference between the things. This is nothing strange, or anything intimidating in that sense. Oh well.
There are a lot of interesting things going around the place essentially, and I'm left to believe a few things about the whole concept. Nothing strange in that sense, nothing too damning. A good enough system will do for my purposes. Nothing damning should be done, and there are even less things that should be considered, and maintained in the whole concept behind this whole issue. The things that we do, and what we do properly, is the defining and the damning thing in essence. I'm pretty sure I'm left of at the place where I shouldn't be in the first place. Looking back at things, this might prove to be highly definitive, highly discrete.
I'm not sure about the facts that we do have, and what defines the whole thing in large enough quantities, or define them at all, infact. I'm standing here, to believe that C++ is a really fucking weak language. I know it, but the semantics are so out from here, that there is simply nothing that can redeem the situation. Fuck that shit, I'm going to get something to eat.
Looking past the thing, I have few regrets, nothing quite states the same as the whole point behind the thing, the thing that we hold dear, in our hearts, and so forward. Nothing essentially moves around the whole concept better than a good old fashioned assfuck. I'm left to believe certain things about the whole concept thereof, and I'm going to take the whole thing, and shove it essentially. There are some glitches, some snags, and so forth, that I will have to deal with properly at one time or another. I for some reason prefer to handle them as soon as possible, making it less likely for things to mess up completely, and when I say completely, I mean like a proper good old fashioned assfuck.
I have a plan, it's a cunning plan, and I'm going to set it forth the whole point, make things more understandable and less prone to errors. For some reason some people tend to dis the concept. I don't know the reason. But, as it stands, there are going to be two more computers instead of three more. First of all, I don't care about the whole concept of having your shit pushed in at the wrong moment, that will make it look awkward, and so forth. Shit it's atavistic out here. Sunny Espoo to be sure.
I must make things happen in a discrete fashion essentially. These things imply some things, and have as their requirements some others. I'm not sure about the whole concept thereof, but I'm left to believe certain things about the concept, something less damaging, and so forth. I'm getting a machine to act as my primary controller for things to come, that is, the brute machine, and it's going to have a companion. I'm not yet fully sure about the whole prospect, and how I should approach it, but there are a few things that I hold dear, and they are quite a lot of work, some other things aswell, as also some things that do convey the whole subject thereof. I'm going to deal with these things as well as possible, as humanly possible, because that's just what I do, what I get paid doing.
The hard and strong will never surrender. There is an ethical approach to this all. The allegory, Starship Troopers, got the thing right. There are hard and strong people. Not by any stupid militaristic measures, the harder you are, the less you're interested in somekind of fascism. The people in the military are weak. They are conformists, they don't contribute anything to society. There is need for the hard and strong. They will take the point, and move it towards an place where nothing essentially disintegrates. Only the hard can call themselves citizens, and it's up to the hard to defend the weak ones. The whole concept is easily understandable if you take into account a few things, some things that are separate for each other, and some things that should be considered essential. The hard and strong will never surrender.
I don't understand this bullshit that keeps on getting up on its feet regarding the usability and suitability of some systems for a few other things that I take as granted, and that are, infact, granted. This is KDE 4.x, and the whine that goes along with it. I don't get the point, I mean, I use KDE, and I think it's grand, and if they have changed something, but kept the fundamental issues, then I'm bound to use that too. No hassles, no nothing. This is the thing that I'm keeping and that I'm holding true, to the point where it doesn't anymore reflect my ability to operate properly. I give a flying fuck about some details they may have put into the fucking system. I mean, if Konsole works, and then some other software as well, then I'm not going to even consider changing the windowing environment. I mean, that would be stupid. I don't like stupidity, and stupid people, so why the hell not. There are always usability nazis that are going to whine about any change you do. I'm not one of them. I think that KDE provides a kick ass environment, and if it's going to be even better, judging by the essential screenshots that I've seen, then that's just super. Hopefully they have the strength and will to keep up KDE development.
I'm feeling a little bit lonely, a little bit out of context essentially. And a whole lot less amicable than something I could and should be.
Schneier writes in his Cryptogram newsletter about CCTV cameras, and their applicability in the real world, or rather, how badly the CCTV cameras fail at their potential, and the real essential flow of things that they should provide. Here's a really hilarious picture of the whole deal. For now atleast, here's a link to the Cryptogram newsletter by Schneier.
Hmm, I seem to have a solid set right here. You mean this set right here? Yes, I mean this set right here. There are all the obvious things that a man needs, and if I get to keep the Intel Core 2 Duo machine, it will be the all important stormbringer machines. I'm obviously going to have a setup of other things as well with the whole system. There is a FreeBSD machine that runs things. It should be the one I'm plugging all kinds of different GP-IB thingies into it. But as it stands, I no longer use GP-IB equipment. I have replaced them with some other things essentially. I better not get into the details about my setup here at home, because I want to maintain a level of advantage to the whole system. This means a few things, and implies some more, but the FreeBSD machine is for example running an 200MHz oscilloscope, that proves to be quite neat to have. I've programmed a interface and driver for the solution, but that's enough about that thing. Getting traces of 200MHz signals and being able to display them on some machine, it is really awkward, and to some extent really harsh. We had some long time ago at work an Tektronix oscilloscope with 4 channels and up to 100MS/sec., and the price for that thing was stellar. I mrean really fucking expensive. Well I guess they need to make their profits somehow, but as it stands, my setup could also be used for a few other things, like analyzing the narrow band spectrum through an efficient enough ADC. There are things that this is useful for. Very useful. Hum, this is because of my involvement in certain electronics projects and the kind, really. I'm not terribly devastated by the prospect. There are some things we should be doing, and there are some things we should probably avoid. The later being somewhat more classical in representation. But I'm not picky.
Do something good with your time, and do it properly. The emphasis goes on the word properly. I'm left to think that a system that I have always wanted to build, ever since I mastered UNIX back in the 90's, but it's not a easy thing at all, infact, it's quite harsh, quite hard to get right in the first place. Oh well, I have my embebbed bench right here, and it's going to serve as a platform for development for now. I may extend it, if there is such need by some place essentially. The reason for wanting to have ZFS and FreeBSD together on the case, is quite obvious. I'm very familiar with FreeBSD semantics, I've been part of a team that ported FreeBSD to a platform that wasn't supported yet, and before you ask yourself, no, it wasn't ARM, but that's all I'm going to say about it. Mind you, this was the 2.x days of FreeBSD, and the port wasn't terribly easy in any way. Oh well, I'm left wondering about the things we are doing, and what we should set as a formatted spaceholder for the whole concept to begin with. I'm envisioning a system that is highly efficient and highly usable in the case that you have something to work on, something to scale back on. This is a simple computer, but there are things that a computer may do, and there are things it may not do. Throw enough power at some problem, and you're bound to get a good response. This is how the world works, all energy flows according to the whims of the great magnet. Looking past the thing, I'm left to believe in certain additional tasks essentially.
I have some plans essentially here, some of them need some consideration, and some forethought essentially. I'm left to believe a few things about the whole concept around here. The concept can't be probably very well disintegrate the whole concept towards the point where we do work at, and handle things at.
I drew some schemantics of the embedded board, and how it should work, and what are the components in it, and so forward. The idea is ofcourse to have a board where I can sit down, fidget around with different kinds of ideas, and come to somekind of consensus thereof about the system really. I will probably end up needing a few things for this setup, that is, there will be warbringer, which shall be running on the left side of the board, two large CRT displays. Then there is a big space of things that shouldn't be taken too harshly under no circumstance essentially. There will be a keyboard to control both the machines, that is, one system with dual DVI output and one Matrox G200 MMS card to drive the other set of the whole concept. There are going to be like 6 monitors in this setup, 4 of which are LCD screens. If I felt really bold, and I do feel like that sometimes, I would go ahead, and build things out of Silicon Graphics 1600SW monitors, that would probably rock, a lot. Yes, that's going to be the plan. I plan on setting this kind of setup up as soon as I get somekind of data on how the hell the attachement of the units should be done to the wall. This is a small problem essentially. I hate using power tools. But this just calls for it, somehow.
It'll be good to get the electronics bench into working order. I need still some particulars, but it should be fairly solid at this stand. The computers, them I have, the harddisks, they are saved, each morning at 07:00 there will be a tar package made of the whole source repository filesystem entry, and that will then be rzip'ed or 7-Zipped. Then I'll push the backup to a machine that is going to be the backup host. I do fancy my shit, and I think it's wonderful, in every regard. Looking back past the point, I'm left feeling somewhat stranger than I really should, and this is probably a good thing. A good thing for me. They way I've planned the usage of the SGI 1600SW monitors, it's going to be a riot. I probably need somekind of system setup for my doings, so that there is no specific problem inherent with the whole issue. The wall of LCD's is going to be covered by a cupboard, and there are going to be some things upon it. This means some things that I really use will be setup for good on this system. The system should be separate from the rest of the network in that sense. It's a small system that I intend to run a Windows domain controller on, and do all the things that are required for remote authentication, and so forth. Just whatever the hell you have. I'm left to believe in certain things, and this could be the defining thing behind it all, the ultimate that I'm looking for, the very thing that makes people in the business tick and so forth.
The embedded board will also house somewhere, I'm not sure where yet, but it should be somewhere, behind a power circuit that has an relay that controls the flow, on or off, and I'll just make sure it doesn't draw current to the soldering iron(s), because I recon it could be dangerous to leave them like that at home for a day at the work. There are distinctive things that can be done, some of them very cool, the rest, well, very strange indeed. Why this doesn't seem to correlate very well with reality and the whole concept seems a bit flawed, I'm still left to believe in certain things, and that is essentially tinkering with electronics. There are however a lot of people that I do hate. That is, people who tinker with electronics, since usually they are wankers, bed wetters or both. Fucking wankers. I hate electronics tinkering assholes. I mean, I'm a practical guy, if there is something that needs to be done, I'll do it, but, not without reason or some argumentation in some path. Electronics for the sake of electronics is just masturbation.
I kindof wish two things right now: 1) that I had caffeine 2) that I hadn't taken 900mg of Seroquel some 3 hours ago.
The 2x2 matrix of SGI 1600SW's will be sweet, and should make it more easy for me to comprehend the whole systemic change that is required thereof from the whole system. With that in place, I can easily run just about whatever it is that I want to run, and it will just go through. No hassles here essentially. The both machines with screens are going to be Windows XP machines. They are going to run everything and such things essentially.
Ok, there are two more systems that I need, and then I should be figured out with the whole laboratory. I'll simply go ahead and define things as well as I can, and maintain a certain aptitude towards it. I'll have my hacking machines, my machines for some things, and others, and so forward. I'm going to move this whole shit towards an amicable end, essentially. There are really few things that I should be looking for. Some of them less than amicable, some of them not very neat, and so forth.
Profile
![[info]](http://l-stat.livejournal.com/img/userinfo.gif)
paranoic_puppy- paranoic_puppy