Now that Sidux has been scuttled, and replaced by aptosid...

Do we need to wait for an update to the smxi scripts, or will smxi handle aptosid properly simply because of the mirrors in the distro pointing to the aptosid respositories?
Back to top

it just happened, I don't know what will happen.

smxi has long since been converted to a debian script, with optional sidux stuff added, but I don't know how it will run.

Conveniently I just stripped out sidux gunk from a client's old system, the last sidux I have running out there.

I don't have time this week to look at the change, but if you post feedback on anything that doesn't work right it will give me a place to do more cleanup.

I am amazed that those guys were unable to think of a good name, and went with something so absurdly corny that it seems to seal their decision to be a geek only distro. More power to them I guess, just what the world needs, another distro aimed at a few hundred people out there....
Back to top

I agree... I think my dog could have came up with a better name for the distro... lol

I do, however, really like the sidux distro, especially it's lightning fast install, coupled with the ease of updates with the smxi script.

It makes a great distro to run virtual machines on top of... if you have a snapshot, you can have the host machine back up and going in about 7 or 8 minutes.
Back to top

Of course your dog could, unless it's mentally handicapped, but that's only a special case.

agreed re the fast install.

As long as nobody is foolish enough to use a sid based distro as a real server you're fine.

debian stable for anything that you want stable and always working, that's my choice, testing or sid for desktops where you can afford some downtime or fixing time now and then to keep it rolling.
Back to top

Aptosid, sounds like a stomach remedy to me.
Myself I doubt it will cure the sidux heartburn.
Time will tell.

I agree I wouldn't use sid for anything mission critical, but it is fun to stay current as things develop.
One definitely has to pay attention though, "It wants to remove WHAT!" and still once in a while something sneaks by.
Back to top

It seems that the things that don't work as they used to are:

1. sidux->aptosis kernel detection and kernel management
(for this, I think that a simple change in text within the script from sidux to aptosid will do)
2. aptosis mirror selection (of course)

Of course, nothing is really critical, but the above do not work (for obvious reasons)
Back to top

Same observation as crust

drb
Back to top

can someone show the new kernel name? uname -r
that is?
Back to top

2.6.35-4.slh.6-aptosid-amd64
Back to top

For 32 bit, the current kernel is

2.6.35-4.slh.6-aptosid-686
Back to top