[b] did these folks snarf this article from segfault or something? not that i've seen it on segfault but it sounds about right for an appearance there...
does anyone actually use this distro? everything i've read about it seems to make it out to be just RH with extra stuff that RH is going to implement in the next distro anyway. sure it sounds spiffy, but except for ease of install, (which i havent actually tried on mandrake), is there any reason at all to switch to mandrake? maybe if i was a complete newbie to linux it might be usefull, but what about the rest of us?
... how many thousands of these studies will have to be published before the media/government/general public catches snap to this notion? I'll probably have died of old age by the time the idea that "computers games make kids kill" is a dead issue. Today's parents need *someone* to blame for their parental inadequacies.
What you say is only true if you are using your soundcard to make all the noise. However, I'm driving a synth/keyboard (QS8) and therefore any sequencer I use needs to have MIDI support. Seems to me that at least one of the trackers (fastracker?) incorperated MIDI, but it's been years since I've played with trackers.
As for flexibility, I'd say that is only try if you are limiting yourself to general midi. If you've got a dedicated synth to drive you can make all the crazy sounds you want. Of course, it's rather more expensive than just using your soundcard:)
The obvious question (maybe I should have added this to my previous post): Do you have any of your tunes anywhere I can get at them and have a listen?
I use cakewalk as my sequencer, and largely for the same reasons you use a sequencer: my drumming and keyboarding are of dubious quality and s/w editing fixes that problem.
As for programming, I pretty much leave it at work. On the other hand, I'm starting to seriously consider writing a class lib for reading and writing MIDI files. Dunno if that is a usefull thing, but mostly it'll force me to learn alot more about the nitty-gritty of MIDI.
YAMU (Yet Another Mackie User) here. I'll add my support for this mixer. It's bloody brilliant. Not only is it nearly infinitely reconfigurable, but the sound of the thing is great.
Somewhat off topic, but thanks to this thread and a few others, the question I have is, "how many of us slashdotters do home recording and what kinda music? what kinda gear?"
I mostly do guitar oriented stuff, but I play (poorly) various instruments. Currently I'm digging into the whole MIDI mess and making cakewalk and my Alesis QS8 play nice and do crazy things.
Sorry, no MP3's yet, but I'm planning on getting a few up on the web in a few weeks when the current project is "done".
It's great that there is some use for this otherwise floating piece of junk. However, the article, to my recolection, doesn't mention why the main scope can't be repaired. They hacked the hubble back together, why not do something similar for WIRE?
I have been pretty successful considering that i am running it under NT. Well with Patrol for LINUX goodby to NT.
Don't get too excited... If you are going to support KMs on both NT and *nix machines there may be a *lot* of porting issues, depending on what sort of stuff you are doing.
Check out Enterprise Application Management with PATROL by David Spuler for some of the porting issues.
I have even thought about sending my resume to BMC but never knew they had any interest in Linux....
I haven't seen any news of linux ports for Patrol other than the BBC story, but it wouldn't be too suprising for BMC to start pushing linux ports, considering that Tivoli is making noise about supporting linux.
Patrol is a product for managing system resources network-wide. The basic idea is that you run "Patrol Agents" on each machine you want to monitor, and each agent loads "Knowledge Modules" which tell the agent what resources to monitor, and how to monitor them.
You connect up to each agent with a "Patrol Console", and from there you can view the status of the agent, and the resources it monitors.
There is SNMP support built in, and agents can talk to each other.
I'm currently writing a KM for Patrol (I dont work for BMC) and have my own opinions of coding under the Patrol "environment" *ahem*
You can check out BMC's description of Patrol here. I work for these guys
Luckily, I'm a coder, and generally I don't have to deal with this sort of thing. However, I have done sysadmin work, and more importantly I've worked with a very experienced admin at a former job, so I have at least an inkling of what you are going thru.
I suggest that this would be a good time to inform users as to how these macro viruses work, and when/how they are harmful. Since they've recently been bitten (or at least have been scared) by a couple viruses, they are probably ammenable to hearing about what they should be doing about them.
Namely: don't run executables/view documents that aren't trusted. Sure there's more to it than that, but it's your job to tell them.
It'll probably cut down on the general hysteria, and make your job easier in the future. And, with any luck, give a few folks a clue. BTW, let them know that this wouldnt have happenned if they were runing *nix (not entirely true, but hey, spread the word, brother:)
Hold a departmental meeting, or have someone (technical) in a sufficiently high position call such a meeting. You might be suprised what comes from it.
Slashdot Mirror
[a] spiders aint insects
...
[b] did these folks snarf this article from segfault or something? not that i've seen it on segfault but it sounds about right for an appearance there
"Oh you mean like taking stuff from free software programmers and bundling it up as your own? Doh!"
.. pages actually load. I need a job that let's me work from 10pm until 6am
rofl, fair enough, but that still doesnt explain what is in the mandrake distro that is worth ripping off by RH, except for the installation GUIs
/. is so much better at 1:30 am
does anyone actually use this distro? everything i've read about it seems to make it out to be just RH with extra stuff that RH is going to implement in the next distro anyway. sure it sounds spiffy, but except for ease of install, (which i havent actually tried on mandrake), is there any reason at all to switch to mandrake? maybe if i was a complete newbie to linux it might be usefull, but what about the rest of us?
... how many thousands of these studies will have to be published before the media/government/general public catches snap to this notion? I'll probably have died of old age by the time the idea that "computers games make kids kill" is a dead issue. Today's parents need *someone* to blame for their parental inadequacies.
jetpack
I need a way to filter out these damn posts. Until free-as-in-beer /. shows up in Houston, I don't even wanna *hear* about this! :P
jetpack
What you say is only true if you are using your soundcard to make all the noise. However, I'm driving a synth/keyboard (QS8) and therefore any sequencer I use needs to have MIDI support. Seems to me that at least one of the trackers (fastracker?) incorperated MIDI, but it's been years since I've played with trackers.
:)
As for flexibility, I'd say that is only try if you are limiting yourself to general midi. If you've got a dedicated synth to drive you can make all the crazy sounds you want. Of course, it's rather more expensive than just using your soundcard
Man, are we *ever* off topic! Woohoo!
jetpack
The obvious question (maybe I should have added this to my previous post): Do you have any of your tunes anywhere I can get at them and have a listen?
I use cakewalk as my sequencer, and largely for the same reasons you use a sequencer: my drumming and keyboarding are of dubious quality and s/w editing fixes that problem.
As for programming, I pretty much leave it at work. On the other hand, I'm starting to seriously consider writing a class lib for reading and writing MIDI files. Dunno if that is a usefull thing, but mostly it'll force me to learn alot more about the nitty-gritty of MIDI.
BTW, what sorta s/w are you writing these days?
jetpack
YAMU (Yet Another Mackie User) here. I'll add my support for this mixer. It's bloody brilliant. Not only is it nearly infinitely reconfigurable, but the sound of the thing is great.
Somewhat off topic, but thanks to this thread and a few others, the question I have is, "how many of us slashdotters do home recording and what kinda music? what kinda gear?"
I mostly do guitar oriented stuff, but I play (poorly) various instruments. Currently I'm digging into the whole MIDI mess and making cakewalk and my Alesis QS8 play nice and do crazy things.
Sorry, no MP3's yet, but I'm planning on getting a few up on the web in a few weeks when the current project is "done".
jetpack
It's great that there is some use for this otherwise floating piece of junk. However, the article, to my recolection, doesn't mention why the main scope can't be repaired. They hacked the hubble back together, why not do something similar for WIRE?
Don't get too excited
Check out Enterprise Application Management with PATROL by David Spuler for some of the porting issues.
I haven't seen any news of linux ports for Patrol other than the BBC story, but it wouldn't be too suprising for BMC to start pushing linux ports, considering that Tivoli is making noise about supporting linux.
You connect up to each agent with a "Patrol Console", and from there you can view the status of the agent, and the resources it monitors.
There is SNMP support built in, and agents can talk to each other.
I'm currently writing a KM for Patrol (I dont work for BMC) and have my own opinions of coding under the Patrol "environment" *ahem*
You can check out BMC's description of Patrol here. I work for these guys
Luckily, I'm a coder, and generally I don't have to deal with this sort of thing. However, I have done sysadmin work, and more importantly I've worked with a very experienced admin at a former job, so I have at least an inkling of what you are going thru.
:)
:)
I suggest that this would be a good time to inform users as to how these macro viruses work, and when/how they are harmful. Since they've recently been bitten (or at least have been scared) by a couple viruses, they are probably ammenable to hearing about what they should be doing about them.
Namely: don't run executables/view documents that aren't trusted. Sure there's more to it than that, but it's your job to tell them.
It'll probably cut down on the general hysteria, and make your job easier in the future. And, with any luck, give a few folks a clue. BTW, let them know that this wouldnt have happenned if they were runing *nix (not entirely true, but hey, spread the word, brother
Hold a departmental meeting, or have someone (technical) in a sufficiently high position call such a meeting. You might be suprised what comes from it.
Mail me your results from the experiment
Up the Irons