(Solved) Virtualbox-kernel Slackbuild
 

For some reason, when I click on the Slackbuild link for virtualbox-kernel (3.1.6) for virtualbox-kernel-3.1.6.tar.xz , it downloads as virtualbox-kernel-3.1.6.tar.tar . The file is misnamed.

If it is renamed virtualbox-kernel-3.1.6.tar.xz , the SlackBuild works just fine.

So why is it in no replies then ?
If you fix it, reply and say so. Don't just edit your post.

Hey smoker...

What are you talking about?!

I edited my post to enter the screenshot I took.

I decided to update VBox, ran into a problem, and solved it. Then I posted here in case anyone else, especially a noob, had a similar problem.

What's your problem?

Smoker, just in case you missed it:

Then I posted here in case anyone else, especially a noob, had a similar problem.

Hi,

It is customary to post the solution not edit the original post. By editing the original you are possibly introducing confusion. Unless you mark the original with 'EDIT' tags for each change or addition;

EDIT Some addition or solution
EDIT2: Additional append
EDIT3: Yet another append
EDIT... continuing

Plus you mark the thread as Solved via the Thread Tools.

:hattip:

EDIT: Tone it down a bit. No one was attacking you but trying to aid. BTW, see by example! :)

Hi Onebuck,

I did not post a problem/question, then solve it, and then edit my post, and then use the forum tools to mark the topic header as solved. This is not what happened.

I solved the problem and then posted. The term Solved was part of the original topic header. The edit was to include the screenshot.

I did not use the forum tools to mark the post Solved. If you notice, "Solved" is written in blue font like the rest of my topic header. For those who use the forum tools to mark the thread solved, "SOLVED" renders in black font.

But, since we're on the subject...

In the future, if I discover a problem and solve it, how should the header be written to let folks know that a problem was discovered and the solution is in the original post? Apparently if I mark it from the outset as "solved" in the original topic header, this will cause confusion. If I use the forum tools to mark the header as solved, this will cause confusion.

Thanks,
-Joe :)

BTW, the font rendering as blue vs black shows up here:
http://www.linuxquestions.org/questions/slackware-14/

Solved on this topic shows blue and SOLVED using the forum tools shows as black.

Thanks :)

Hi,

Present the question to a MOD.

I would think that to present something as a gotcha or solution would be done in the manner of normal Thread post title. Since [SOLVED] is a tag that is OP controlled. Newbies have enough problems even doing a search let alone discern of a title that misleads.

Gary,

But if I do not marked it as solved, I'm going to get yelled at for wasting people's time. Folks will click on the thread link thinking someone needs help, only to find that they've wasted their time on a problem that is already solved.
I'm pretty confident that any newbie that came across my thread would understand the title. Ironically, it seems to be giving some advanced users problems. But to keep the peace, I'll use a different approach.

I'm really not such a bad guy. I remember what it was like to be a Slackware newbie and to waste a whole weekend over some trivial problem. Or, to just give up and learn to live with the problem. This mis-named download was a trivial matter and I just wanted to pay forward some of the help I received. I guess wasn't expecting confrontation. It really caught me off guard.


-Joe

Hi Joe, FWIW I too, thought the response was a bit off the mark, and uncharacteristic for this board... and although I am not directly affected by the problem you pointed out, let me say THANK YOU for your motivation, intent and efforts - it is appreciated!

I very much appreciate the moral support!!!!!

Thank you!!!!!!!!!!!! :)

-Joe