Linux NOOB!!! A Couple Questions...

[Klixxer]

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey
Along with swaret, slapt-get is nice too. There is supposedly an official slack replacement for these in 10RCwhatever.

swaret has been in slackware/extra for a while and handles the repos roots as well as slapt-get these days, it's more of a matter of preference nowadays.

I have heard about a new tool too but i just figured swaret had made it into the official packs.

I heard something about bad blood between the swaret developer and, well, the rest of the world. I haven't looked into it really, just heard a few rumors. 😎

There are some X front ends for both but that is blasphemy in Slack. 😛

:Q People use X on slack?! 😉

Heheee, well, i have heard those rumours too, i don't really care though, as long as the tool is useful i will use it. 😉

Yeah, some people do use X on slack, blasphemy i tell you, BLASPHEMY! 😉

Seriously, at least they had the sense to go with x.org. 🙂

 

[n0cmonkey]

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey
Along with swaret, slapt-get is nice too. There is supposedly an official slack replacement for these in 10RCwhatever.

swaret has been in slackware/extra for a while and handles the repos roots as well as slapt-get these days, it's more of a matter of preference nowadays.

I have heard about a new tool too but i just figured swaret had made it into the official packs.

I heard something about bad blood between the swaret developer and, well, the rest of the world. I haven't looked into it really, just heard a few rumors. 😎

There are some X front ends for both but that is blasphemy in Slack. 😛

:Q People use X on slack?! 😉

Heheee, well, i have heard those rumours too, i don't really care though, as long as the tool is useful i will use it. 😉

Yeah, some people do use X on slack, blasphemy i tell you, BLASPHEMY! 😉

Seriously, at least they had the sense to go with x.org. 🙂

Is there such a thing as a Linux gossip whore? 😛

Every respectable open source/free software OS/distro has gone with x.org or is sticking with 4.4RC2.

 

[Klixxer]

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey
Along with swaret, slapt-get is nice too. There is supposedly an official slack replacement for these in 10RCwhatever.

swaret has been in slackware/extra for a while and handles the repos roots as well as slapt-get these days, it's more of a matter of preference nowadays.

I have heard about a new tool too but i just figured swaret had made it into the official packs.

I heard something about bad blood between the swaret developer and, well, the rest of the world. I haven't looked into it really, just heard a few rumors. 😎

There are some X front ends for both but that is blasphemy in Slack. 😛

:Q People use X on slack?! 😉

Heheee, well, i have heard those rumours too, i don't really care though, as long as the tool is useful i will use it. 😉

Yeah, some people do use X on slack, blasphemy i tell you, BLASPHEMY! 😉

Seriously, at least they had the sense to go with x.org. 🙂

Is there such a thing as a Linux gossip whore? 😛

Every respectable open source/free software OS/distro has gone with x.org or is sticking with 4.4RC2.

LOL, the rumours and gossip in the Linux world are probably worse than anywhere else, it's a shame i like Slack so much or i would only be running FreeBSD for desktops and OpenBSD for other things, but i started out with slackware a long time ago and even though i try other things i tend to reinstall with slack... 😛

Which distos haven't taken the step over to x.org?

 

[drag]

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey
Along with swaret, slapt-get is nice too. There is supposedly an official slack replacement for these in 10RCwhatever.

swaret has been in slackware/extra for a while and handles the repos roots as well as slapt-get these days, it's more of a matter of preference nowadays.

I have heard about a new tool too but i just figured swaret had made it into the official packs.

I heard something about bad blood between the swaret developer and, well, the rest of the world. I haven't looked into it really, just heard a few rumors. 😎

There are some X front ends for both but that is blasphemy in Slack. 😛

:Q People use X on slack?! 😉

Heheee, well, i have heard those rumours too, i don't really care though, as long as the tool is useful i will use it. 😉

Yeah, some people do use X on slack, blasphemy i tell you, BLASPHEMY! 😉

Seriously, at least they had the sense to go with x.org. 🙂

Is there such a thing as a Linux gossip whore? 😛

Every respectable open source/free software OS/distro has gone with x.org or is sticking with 4.4RC2.

LOL, the rumours and gossip in the Linux world are probably worse than anywhere else, it's a shame i like Slack so much or i would only be running FreeBSD for desktops and OpenBSD for other things, but i started out with slackware a long time ago and even though i try other things i tend to reinstall with slack... 😛

Which distos haven't taken the step over to x.org?

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

 

[Klixxer]

Originally posted by: drag

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey
Along with swaret, slapt-get is nice too. There is supposedly an official slack replacement for these in 10RCwhatever.

swaret has been in slackware/extra for a while and handles the repos roots as well as slapt-get these days, it's more of a matter of preference nowadays.

I have heard about a new tool too but i just figured swaret had made it into the official packs.

I heard something about bad blood between the swaret developer and, well, the rest of the world. I haven't looked into it really, just heard a few rumors. 😎

There are some X front ends for both but that is blasphemy in Slack. 😛

:Q People use X on slack?! 😉

Heheee, well, i have heard those rumours too, i don't really care though, as long as the tool is useful i will use it. 😉

Yeah, some people do use X on slack, blasphemy i tell you, BLASPHEMY! 😉

Seriously, at least they had the sense to go with x.org. 🙂

Is there such a thing as a Linux gossip whore? 😛

Every respectable open source/free software OS/distro has gone with x.org or is sticking with 4.4RC2.

LOL, the rumours and gossip in the Linux world are probably worse than anywhere else, it's a shame i like Slack so much or i would only be running FreeBSD for desktops and OpenBSD for other things, but i started out with slackware a long time ago and even though i try other things i tend to reinstall with slack... 😛

Which distos haven't taken the step over to x.org?

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

Like i said, wherever i turn i just tend to stick with slack for a linux disto. Perhaps part of it is because i am used to BSD which is more like slack than any other distro and perhaps because i just like slack.

 

[n0cmonkey]

Originally posted by: Klixxer

Originally posted by: drag

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Klixxer

Originally posted by: n0cmonkey
Along with swaret, slapt-get is nice too. There is supposedly an official slack replacement for these in 10RCwhatever.

swaret has been in slackware/extra for a while and handles the repos roots as well as slapt-get these days, it's more of a matter of preference nowadays.

I have heard about a new tool too but i just figured swaret had made it into the official packs.

I heard something about bad blood between the swaret developer and, well, the rest of the world. I haven't looked into it really, just heard a few rumors. 😎

There are some X front ends for both but that is blasphemy in Slack. 😛

:Q People use X on slack?! 😉

Heheee, well, i have heard those rumours too, i don't really care though, as long as the tool is useful i will use it. 😉

Yeah, some people do use X on slack, blasphemy i tell you, BLASPHEMY! 😉

Seriously, at least they had the sense to go with x.org. 🙂

Is there such a thing as a Linux gossip whore? 😛

Every respectable open source/free software OS/distro has gone with x.org or is sticking with 4.4RC2.

LOL, the rumours and gossip in the Linux world are probably worse than anywhere else, it's a shame i like Slack so much or i would only be running FreeBSD for desktops and OpenBSD for other things, but i started out with slackware a long time ago and even though i try other things i tend to reinstall with slack... 😛

Which distos haven't taken the step over to x.org?

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

Like i said, wherever i turn i just tend to stick with slack for a linux disto. Perhaps part of it is because i am used to BSD which is more like slack than any other distro and perhaps because i just like slack.

Debian won't get to x.org until 2283.

Slack and Debian are the Linux distros I use, but that's only because OpenBSD didn't have SMP support. They do now. 😀

Although I've considered Fedora for work related reasons.

Most Linux distros will go to x.org. The BSDs might, and they might not. If x.org avoid *gpl, it might be taken up by OpenBSD. If they go gpl/lgpl it's less likely.

NetBSD bowed down to the XF86 developers and are using 4.4. I think. I don't keep up with it much though. I'm not aware of FreeBSD's stance on the issue. I avoid Net/Free whenever possible.

 

[Nothinman]

I am not sure of how many but there are lots, i have yet to encounter an unstable slackpack from linuxpackages.

Most people who argue that there are more RPM's and Deb's haven't tried Slack with swaret and linuxpackages.net yet.

According to linuxpackages.net there's just under 800 for Slackware 9.1. There's almost 15,000 packages in Debian unstable and with Debian you get very strict guidelines on how the packages are made, I know I'm biased towards Debian but I can't see how anyone could say that Slack+linuxpackages.net is anywhere near as complete as Debian.

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Eventually it'll happen, but it'll take some time to convert the current Debian packages. Hopefully once Debian starts working the X.org people most of the Debian patches will be accepted upstream, that alone would speed up the release a lot IMO.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

That's hardly a decisive reason right now, the differences between X.org and XF4.4 are extremely minor and currently the Debian tree is 'more clean' because Branden and the XSF audited the tree after the XF License debacle and removed a lot of non-DFSG-free code, most of which wasn't even used or was easily replaced anyway.

 

[n0cmonkey]

Originally posted by: Nothinman

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Eventually it'll happen, but it'll take some time to convert the current Debian packages. Hopefully once Debian starts working the X.org people most of the Debian patches will be accepted upstream, that alone would speed up the release a lot IMO.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

That's hardly a decisive reason right now, the differences between X.org and XF4.4 are extremely minor and currently the Debian tree is 'more clean' because Branden and the XSF audited the tree after the XF License debacle and removed a lot of non-DFSG-free code, most of which wasn't even used or was easily replaced anyway.

Has x.org gotten past just being XF864.4RC2? 😛

I'd be interested to see the differences between Debian's XF86 and OpenBSD's. They are the two most license anal (thankfully someone is!) groups out there. With the known stability of Debian, and the sometimes small security improvements made by OpenBSD; it could be quite a team. 😉

 

[Nothinman]

If you want you can download the source archive of the Debian X package, all the patches they apply are in the debian/patches directory and are (or were the last time I checked) broken down into small, localized changes.

 

[Klixxer]

Originally posted by: Nothinman

I am not sure of how many but there are lots, i have yet to encounter an unstable slackpack from linuxpackages.

Most people who argue that there are more RPM's and Deb's haven't tried Slack with swaret and linuxpackages.net yet.

According to linuxpackages.net there's just under 800 for Slackware 9.1. There's almost 15,000 packages in Debian unstable and with Debian you get very strict guidelines on how the packages are made, I know I'm biased towards Debian but I can't see how anyone could say that Slack+linuxpackages.net is anywhere near as complete as Debian.

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Eventually it'll happen, but it'll take some time to convert the current Debian packages. Hopefully once Debian starts working the X.org people most of the Debian patches will be accepted upstream, that alone would speed up the release a lot IMO.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

That's hardly a decisive reason right now, the differences between X.org and XF4.4 are extremely minor and currently the Debian tree is 'more clean' because Branden and the XSF audited the tree after the XF License debacle and removed a lot of non-DFSG-free code, most of which wasn't even used or was easily replaced anyway.

Didn't mean to offend anyone, but i am quite happy with slack, which program do you use that cannot be found on the various slack mirrors in the swaret.conf file? No packages that i can find on *.deb either IME i have to compile them myself, but since it is so easy to make a slackpack i compile it, send it to linuxpackages after i verified it's stable and keep the pack on my own server.

Debian is ok, i prefer slack after trying stable with age old packages and unstable with instability, Slackware current is just better IME.

Branden and XSF sold out, simple as that. IMO of course.

 

[n0cmonkey]

Originally posted by: Nothinman
If you want you can download the source archive of the Debian X package, all the patches they apply are in the debian/patches directory and are (or were the last time I checked) broken down into small, localized changes.

Yeah, I know. I might, if I remember the next time I have the time to do it.

Not that I'd understand most of the patches 😛

 

[Klixxer]

Originally posted by: n0cmonkey

Originally posted by: Nothinman

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Eventually it'll happen, but it'll take some time to convert the current Debian packages. Hopefully once Debian starts working the X.org people most of the Debian patches will be accepted upstream, that alone would speed up the release a lot IMO.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

That's hardly a decisive reason right now, the differences between X.org and XF4.4 are extremely minor and currently the Debian tree is 'more clean' because Branden and the XSF audited the tree after the XF License debacle and removed a lot of non-DFSG-free code, most of which wasn't even used or was easily replaced anyway.

Has x.org gotten past just being XF864.4RC2? 😛

I'd be interested to see the differences between Debian's XF86 and OpenBSD's. They are the two most license anal (thankfully someone is!) groups out there. With the known stability of Debian, and the sometimes small security improvements made by OpenBSD; it could be quite a team. 😉

The stability of the version no one uses? Yeah, that would be great for debian, no more unstable and get to a new kernel a year after everyone else uses it?

Debian is a strange distro, standing on one leg at a time and at another another time, stability vs newer packages, newer unstable tends to be the choice but it is still more unstable than slackware current. 😀

 

[n0cmonkey]

Originally posted by: Klixxer

Originally posted by: Nothinman

I am not sure of how many but there are lots, i have yet to encounter an unstable slackpack from linuxpackages.

Most people who argue that there are more RPM's and Deb's haven't tried Slack with swaret and linuxpackages.net yet.

According to linuxpackages.net there's just under 800 for Slackware 9.1. There's almost 15,000 packages in Debian unstable and with Debian you get very strict guidelines on how the packages are made, I know I'm biased towards Debian but I can't see how anyone could say that Slack+linuxpackages.net is anywhere near as complete as Debian.

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Eventually it'll happen, but it'll take some time to convert the current Debian packages. Hopefully once Debian starts working the X.org people most of the Debian patches will be accepted upstream, that alone would speed up the release a lot IMO.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

That's hardly a decisive reason right now, the differences between X.org and XF4.4 are extremely minor and currently the Debian tree is 'more clean' because Branden and the XSF audited the tree after the XF License debacle and removed a lot of non-DFSG-free code, most of which wasn't even used or was easily replaced anyway.

Didn't mean to offend anyone, but i am quite happy with slack, which program do you use that cannot be found on the various slack mirrors in the swaret.conf file? No packages that i can find on *.deb either IME i have to compile them myself, but since it is so easy to make a slackpack i compile it, send it to linuxpackages after i verified it's stable and keep the pack on my own server.

Debian is ok, i prefer slack after trying stable with age old packages and unstable with instability, Slackware current is just better IME.

Everyone has opinions. 😉 I haven't tried the other site you mention, but I've found plenty of things that aren't available in swaret/slapt-get, but are available in apt for Debian. And I'm told the MySQL installation is still a bit borked in slack 10RCwhatever.

I am running Slack 9.1 though, and over all find it just fine. Definitely my favorite. 🙂

Branden and XSF sold out, simple as that. IMO of course.

??

 

[n0cmonkey]

Originally posted by: Klixxer

Originally posted by: n0cmonkey

Originally posted by: Nothinman

Why DEBIAN, of course. They just (unstable) upgrade to 4.3.0 just a bit ago, don't think they are going to use X.org any time soon.

Eventually it'll happen, but it'll take some time to convert the current Debian packages. Hopefully once Debian starts working the X.org people most of the Debian patches will be accepted upstream, that alone would speed up the release a lot IMO.

Ok, i didn't know that, but i am not surprised at all, to me that is another reason not to go from slack to Debian. For linux those are the only two distros i would consider.

That's hardly a decisive reason right now, the differences between X.org and XF4.4 are extremely minor and currently the Debian tree is 'more clean' because Branden and the XSF audited the tree after the XF License debacle and removed a lot of non-DFSG-free code, most of which wasn't even used or was easily replaced anyway.

Has x.org gotten past just being XF864.4RC2? 😛

I'd be interested to see the differences between Debian's XF86 and OpenBSD's. They are the two most license anal (thankfully someone is!) groups out there. With the known stability of Debian, and the sometimes small security improvements made by OpenBSD; it could be quite a team. 😉

The stability of the version no one uses? Yeah, that would be great for debian, no more unstable and get to a new kernel a year after everyone else uses it?

Debian is a strange distro, standing on one leg at a time and at another another time, stability vs newer packages, newer unstable tends to be the choice but it is still more unstable than slackware current. 😀

When I was using Debian I was using the testing branch. I think the thing that frustrated me the most was the stupid names. I never did figure them out. 😛

They upgrade their kernel versions when necessary. No point in putting out a package that doesn't need to be.

And I think the only important differences between XF86 4.3 and 4.4 is the drivers. The Debian guys do a great job of keeping a system that will be stable as long as your hardware is and your admin is half way intelligent. Slack is definitely up there too. I'd guess that they're two of the most stable Linux distros out there, probably the top two. Debian just has a lot of testing to do before they'll trust something. It's a little ridiculous, but I don't think it's bad. 🙂

 

[Nothinman]

Didn't mean to offend anyone, but i am quite happy with slack, which program do you use that cannot be found on the various slack mirrors in the swaret.conf file? No packages that i can find on *.deb either IME i have to compile them myself, but since it is so easy to make a slackpack i compile it, send it to linuxpackages after i verified it's stable and keep the pack on my own server.

I don't know of any particular package off the top of my head, but it's nice to have things like Gnome packaged, a well-integrated menu system, Cyrus-IMAPd and SASL, etc.

Debian is ok, i prefer slack after trying stable with age old packages and unstable with instability, Slackware current is just better IME.

I've been running Debian unstable for around 5 years straight and I can count the number of instabilities on one hand.

Branden and XSF sold out, simple as that. IMO of course.

Huh? They have the most free tree available. I would be surprised if the X.org people didn't accept their patches to clean up their own tree.

The stability of the version no one uses? Yeah, that would be great for debian, no more unstable and get to a new kernel a year after everyone else uses it?

Noone? Even the people using X.org are using XF4.3-RC2 because that's what X.org is a fork of. And strangely I see Linux 2.6.6 kernel packages in unstable, it'll probably be a bit before 2.6.7 makes it in because of all the custom patches again, but what's the big deal anyway?

Debian is a strange distro, standing on one leg at a time and at another another time, stability vs newer packages, newer unstable tends to be the choice but it is still more unstable than slackware current.

I'd really like to see why you think that Debian unstable is actually unstable, like I said I've been using it for about 5 years and I can't remember the last time my machine was actually broken by a buggy package.

When I was using Debian I was using the testing branch. I think the thing that frustrated me the most was the stupid names. I never did figure them out.

They're in alphabetical order, stable->testing->unstable. Packages get uploaded to unstable and after being in unstable for 2 weeks, I think, without any critical bugs filed against them they automatically get moved into testing. I also think the package has to compile properly on either all or a certian high percentage of Debian's supported architectures, but I'm not sure on that one.