Hi guys

I come from a RedHat Linux (and Solaris background. I currently work with Centos 5, to provide a point of reference. Let it be known that I do not enjoy RPM.

I gather that the init scripts (service.py) for each daemon resides in

"/var/lib/pisi/package/<package name>/comar/service.py"

directory. Assuming that is correct, how do I easily start and stop services from the command line? I am aware that Pardus is desktop-focused, however I typically SSH into a box, using the command line only. I rarely need or use a desktop/VNC connection.

With other Linuxes one could predictably expect to use

"/etc/init.d/<service> start|stop|status

With Pardus, the service.py is scattered throughout the package folders.IS there another mechanism I am not aware of, can these packages be reliably symlinked to /etc/init.d, and 3rd, will the upcoming server distro take a different approach?

I have never help onto a copy of any desktop Linux for very long, but Pardus seems to be sticking around. I like the implementation and of course once you like something you think of putting it on the server. However, I need to know this (and other) answers before I can trust what I'm doing.

Regards

Lloyd

Sounds like a good plan. I'll put it on a server and see where I get stuck. I like the idea of being involved with a startup.

I need to become familiar with the init scripts Pardus uses, will play with those over the next few days. I want to try it on my PC here at home too, since I don't always bring my laptop home from work. I hate those things, unplugging cables at night, plugging everything in in the morning at work.

If bugginthe developers from an admin perspective willl help then that will be great, in that way I can contribute. It is important that mainstream packages work well on Pardus (installation, configuration, dependencies) so there are no server nightmares.

I read through the one user's VMware experience. As a desktop system Pardus definitely has merit.

I'll try it out and bleat like a sheep when there's a problem 

I have a server or two I can try Pardus out on, however I'm keener on using a server-oriented distribution (RHEL or CENTOS) in case I have to test apps  in a familiar environment.

Maybe I'll give it a bash, but I'm sure I'll have a ton of questions, much more than now using it just as a Linux desktop. I look forward to a genuine server edition of Pardus.  It's bad enough running unknown apps, adding an unknown OS with unknown features and changes could complicate things, though I'm certain a server variant would be easier to understand and mabage from a sysadmin point of view. And I've had Pardus less than a week.

I can see Pardus originally being conceived to live behind a capable LAN firewall, but now it's definitely out of its cage and finding new roaming grounds with new needs.

Excuse my ignorance, but does Pardus have regular IPTables support?

Pardus is a Desktop system, rather than a server-based distribution. I would imagine a server-oriented version would have a different approach and follow the standard whereby servers generally have Gnome/KDE disabled or removed and init 3 being default run level.

That being said, is there any info on the Pardus init system? I am not referring to Mudur's boot-up scheme, but rather the run-levels as in init 5 and init 3. I don't have my laptop here with me for reference but it didn't look like the inittab had too much in common with RH.

Pardus has merit. I just have to get to grips with the technicalities with regards to console-based system admin, from a server point of view. I draw the line at coding, so I want admin to be painless without having to know Python like the back of my hand before I can add services and start/stop them from the command line.

I am sure the Pardus learning curve will be woth it though.

Hi Willem. Thank you for the welcome.

I have only heard good things about Debian, so I wasn't even aware that there are occasional issues with .deb files. I can see how it was a big step for the Pardus team to break from the norm and rewrite so many elements from scratch. So far, after only 3 or 4 days of experience I think they've done a great job of making a usable Linux system.

As a sysadmin we are essentially required to access our servers over the network via SSH, and the machines are booted into runlevel 3 (no GUI) anyway. Hence I prefer knowing the command line.

I use Windows XP as my desktop OS and on the major partition on my laptop (I refuse to move to Vista). I don't mind actually starting fresh with Pardus (as a novice to their new design of some of the internals) in that it's easier than confusing myself between Debian and RedHat configs. That is also a reason why I am open to Pardus. Again, I have only heard good things about Debian from colleagues and other sources.

Since this system works so smoothly it would be great to look at their upcoming (?) server OS. I would wonder if Mudur bypasses the need for traditional init, since even Solaris 10 hasn't completely done away with init. Before putting this OS on the server I would need to know the answer to some technical questions so I could run my machines reliably. I would consider putting it on one or two servers once I was comfortable with the necessary (command line) admin. Already so far my source installs are flawless.

I understand though that their main thrust right now is a usable desktop OS. They have contributed something good, and I can see it gaining more and more attention.

Lloyd

Hi all

I'm a South African sysadmin living in Dubai. I run RHEL/CENTOS on the server, however I am not a RH fan for personal use (RPM and dependencies is the major source of my pain).

I had tried PCLinuxOS, found it to be a great distro, but still RPM-based and a source of frustration despite the fact that it is so simple, mature and functional otherwise.

I was about to go with Ubuntu 7.04 on my laptop (My only issue with Ubuntu being I don't like Gnome, much prefer KDE, and would have switched. However I know XP well and prefer that even more, being clumsy at the Linux GUIs, but very comfortable at the command line), but I stumbled upon a mention of Pardus the same day. The next day it was running on my laptop and it is perhaps the best Linux experience I have had since I first discovered Slackware all those many years ago.

I have some questions to post in the forum (current ones centre around managing startup scripts from the command line), but I look forward to getting very comfortable with Pardus. I loved its package management. I installed literally in SECONDS what had taken me several hours of frustration over 4 days with RPM dependency issues just to get some simple software installed.

I was hooked from that point

On my HP laptop hardware support has been flawless. Connection to the net and LAN has been a breeze. Not a single hiccup yet.

Well done on a great Linux distribution. I'm sure your approach, methods and philosophy will soon find its way into other distributions.

Regards

Lloyd