jboy

See the man page for the command: rebootin This command works if you use the lilo or grub boot loaders.

Try adding the following line to the /etc/shorewall/rules file: DROP net fw tcp 113 If you have any ACCEPT statements in the rules file, I would put this ahead of them. After making the change in the rules file, as root execute the following commands in a terminal to restart shorewall so the change takes effect (or reboot): service shorewall stop service shorewall start References: the comments in the rules file and the shorewall documentation.

Here are some rsync links and tips. Note the following useful parameters: -u updates only if files are newer -t preserve datetime stamps -n dry-run;test what would be done but don't actually do it automated backups with rsync: http://www.mikerubel.org/computers/rsync_snapshots/#Rsync Use rsync to mirror data between 2 machines: http://www.linuxquestions.org/questions/answers/80 Using rsync: https://mandrivausers.org/index.php?showtopic=26540 Backups with rsync: http://rimuhosting.com/howto/rsync.jsp Rsync over ssh: http://www.aerospacesoftware.com/rsync-ssh-howto.html Using rsync to update iso images: http://cybercfo.gkmweb.com/rsync-mandrakeiso.html Using rsync with exclude file: http://ilc.geektyme.org/viewtopic.php?t=246

1. Here are your options, from the Mandriva Starter Guide at http://doc.mandrivalinux.com/MandrakeLinux...en/Starter.html Because the process of partitioning a hard drive is usually irreversible and can lead to data loss, it can be intimidating and stressful for the inexperienced user. Fortunately, DrakX includes a wizard which simplifies this process. Depending on the configuration of your hard drive, several options are available: Use free space This option performs an automatic partitioning of your blank drive(s). If you use this option there will be no further prompts. Use existing partitions The wizard detected one or more existing Linux partitions on your hard drive. If you want to use them, choose this option. Then choose the mount points associated with each of the partitions. The legacy mount points are selected by default, and for the most part it’s a good idea to keep them. Then choose the partitions to be formatted or preserved. Use the free space on the Windows partition If Windows® is installed on your hard drive, you might have to create free space for GNU/Linux. To do so, you can delete your Windows® partition and data (see the “Erase entire disk” solution below) or resize your FAT or NTFS partition. Resizing can be performed without the loss of any data, provided you previously defragmented the Windows® partition. Backing up your data is strongly recommended. Using this option is recommended if you want to use both Mandriva Linux and Windows® on the same computer. Before choosing this option, please understand that after this procedure, the size of your Windows® partition will be smaller than when you started, which means you will have less free space to store your data or to install new software. Erase entire disk Choose this option to delete all data and partitions present on your hard drive. You won’t be able to undo this operation after you confirm. 2. Yes Other Things to Know: See these: http://www.mandrake.tips.4.free.fr/installmdv2006.html http://www.howtoforge.com/perfect_setup_mandriva_2006

No need to change $PATH. Just make a symbolic link to the java executable in /usr/bin (which is already in $PATH). As the root user, execute the following command in a terminal: ln -s /usr/java/jre1.5.0_04/bin/java /usr/bin/java Note that the jre1.5.0_04 in the command above may be different for you - the latest version is 06, I believe. Use the correct directory reference based on your install.

See this: https://mandrivausers.org/index.php?showtopic=28580

Right-click on the desktop -> Configure Desktop -> Behavior -> Device Icons tab -> check Show device icons. They will then show in a Devices folder on the desktop.

Just a wild shot in the dark thought - are you connecting the two computers together directly, rather than through a hub or switch? If so, did you use a crossover cable? A crossover cable is needed for a direct connection. http://compnetworking.about.com/od/network...f_crossover.htm http://www.homenethelp.com/web/explain/abo...t-crossover.asp

ATI, within the past couple days, has updated their proprietary driver to version 8.20.8 for the Radeon 8500 and higher video cards (available here). I saw elsewhere that this has been found to work on Xorg version 6.9 that is used in Mandriva 2006, so I thought I'd give it a try and it did work on my machine (Athlon 2500, 9200SE AGP video card). I followed the instructions on the ATI site. The installer detected that Xorg 6.9 was installed. I chose the automatic install option. Then ran fglrxconfig and rebooted. glxgears now reports 1186 fps (with the non-accelerated Mandriva radeon driver I was getting ~ 192 fps), and fgl_glxgears reports ~ 260 fps. glxinfo reports direct rendering: Yes. I needed to install package libMesaGL1-5.0.2 which had not been installed during the original system install. Installed the Mandriva tuxracer game (an OpenGL-based game) and it works great with the new driver.

For the command line, see the hostname man page; from konqueror: man:/hostname From MCC: Network & Internet -> Alter Misc Internet Settings -> Host name Also see files: /etc/hosts /etc/sysconfig/network

Just came across a nice article at linux.com about handy aliases to add to $HOME/.bashrc that has a suggested alias related to this topic: ( original article here). Show all programs connected or listening on a network port alias nsl='netstat -alnp --protocol=inet | grep -v CLOSE_WAIT | cut -c-6,21-94 | tail +2' The nsl alias uses netstat to show the process ID and program name of everything either connected or listening on a network port, including the sockets of the sending and receiving hosts. It uses grep to sort through the netstat output and remove lines that match CLOSE_WAIT, so you see only programs that are listening or connected. This is a great way to make sure no unexpected services are running in the background. To see all available information, run this command as root. The output from nsl will be similar to this sample: root@penguin:~# nsl Proto Local Address Foreign Address State PID/Program name tcp 0.0.0.0:771 0.0.0.0:* LISTEN 3981/rpc.statd tcp 0.0.0.0:139 0.0.0.0:* LISTEN 3830/smbd tcp 0.0.0.0:111 0.0.0.0:* LISTEN 2908/portmap tcp 0.0.0.0:80 0.0.0.0:* LISTEN 4036/apache tcp 0.0.0.0:22 0.0.0.0:* LISTEN 3838/sshd tcp 0.0.0.0:631 0.0.0.0:* LISTEN 3582/cupsd tcp 127.0.0.1:25 0.0.0.0:* LISTEN 3761/exim4 tcp 0.0.0.0:7100 0.0.0.0:* LISTEN 3875/xfs tcp 0.0.0.0:445 0.0.0.0:* LISTEN 3830/smbd tcp 192.168.1.101:50372 66.35.250.177:80 ESTABLISHED 6585/firefox-bin

From the master man page: "The master daemon is the resident process that runs Postfix daemons on demand: daemons to send or receive messages via the network, daemons to deliver mail locally, etc. These daemons are created on demand up to a configurable maximum number per service."

In a terminal, you could issue the command: netstat -pantu | grep ESTABLISHED This will show, among other things, the IP address and port number of every TCP and UDP connection, along with the Process ID and Program Name involved. If you want to see what's listening or waiting, just issue the netstat -pantu by itself.

Oh, I forgot about the ink level reporting: System -> Configuration -> Printing -> Mtink (Epson inkjet printer maintenance and ink level monitor) It did correctly show the amount of ink left in the cartridges. The binary is /usr/bin/mtink

I have a similar model - the Epson CX6600 all-in-one. I don't remember if the printer was auto-detected or not. But there were a couple drivers available for a similar model, like the CX6400 (that machine isn't running right now so I don't have exact details) but, in any event, I used the mandriva-supplied CUPS+Gimp v4.2.7 driver and it works fine. With LE2005, I was able to use configure and use the scanner using the xsane package. The scanner wasn't auto-detected but with a manual install there was an Epson CX6400 driver available, so I used that and it worked perfectly. Cannot get the scanner to work with 2006 though. Does yours have a memory card reader too? An SD memory card was detected as /dev/sda1 and auto-mounted as /mnt/removeable.

I came across a couple nice articles on ssh at linux.com which might be of general interest: http://enterprise.linux.com/article.pl?sid=05/02/02/1254222 http://tips.linux.com/article.pl?sid=05/12/02/2045226

Is sshd installed and running? If not, see this: http://www.howtoforge.com/perfect_setup_mandrake_10_2_p4 Somewhere in MCC, there is a firewall configuration (shorewall) menu item. You would need to open port 22 (default ssh port, or whichever port you're using). You may need this line in /etc/hosts.allow: sshd:<<ip address of allowed client machine>>:ALLOW This has some tips on deterring ssh attacks: https://mandrivausers.org/index.php?showtopic=26097 Also: check all the various ssh and shorewall pages. The drakxtools documentation package also has good info on MCC configuration.

See this post: https://mandrivausers.org/index.php?showtopic=29240

Here's a couple message threads addressing this: https://mandrivausers.org/index.php?showtop...39entry182039 https://mandrivausers.org/index.php?showtop...26entry140726 https://mandrivausers.org/index.php?showtop...38entry198038 Bottom line from the above: you should be ok installing the package.

You nailed it, bvc. I just checked and it is there. Menu -> Run Command -> kcontrol -> System -> Login Manager -> User's tab

Yes, startx does work from runlevel 3. I've done it many times. Armando, of course, as everyone has suggested, if you startx from runlevel 3, the recommendation is to do so as a regular user, not root.

You could choose the "Failsafe" option from your boot menu. This will take you to runlevel 1 as the root user (command line, no network). From there you can run XFdrake, the ATI driver install and config commands, etc. If you need network support, you can enter: init 3 (takes you to runlevel 3, which has the network started).

I can tell you three ways that this can be done, but I don't know if these are the best ways. Others may have better ideas. You're dealing with the init process and runlevels here, and there is a set of scripts for each runlevel to start/stop system services, etc. For example, normal startup is to runlevel 5 so scripts in /etc/rc.d/rc5.d are run. Failsafe mode is runlevel 1, so the scripts in /etc/rc.d/rc1.d are run. When the system is halted or rebooted, the runlevel is changed to 0 or 6, so the corresponding scripts in rc0.d or rc6.d are run. For startup, it's easy - you can edit /etc/rc.local to put in your own custom commands. I'm not aware of a corresponding user-level script file for use at shutdown, but you can do one of the following (others may post additional or better options). The first idea below is the easiest and the third is the hardest. 1. Take a look at the /etc/rc.d/rc script. Note this code at the bottom: if [[ "$newrunlevel" != "0" && "$newrunlevel" != "6" ]]; then rc_splash stop fi You can put in your own code after the 'rc_splash stop' line. 2. Take a look at /etc/rc.d/rc0.d and /etc/rc.d/rc6.d. These are scripts that involve various system services are run in sequence; e.g., K05keytable -> ../init.d/keytable is run before K09dm -> ../init.d/dm. If what you want to do is associated with one of these various service scripts, you can put your code in that script. 3. You can learn about how to create your own scripts in rc0.d and rc6.d and configure the system to run them. References: http://rute.2038bug.com/node35.html.gz man init

Yeah, it's probably a combined modem/router. If you are trying to ssh into your machine from the Internet, you have several things to check out, including: 1. The router by default probably blocks any incoming ssh requests from the Internet. So you would need to use the router's built-in configuration screens to do port forwarding (your ssh server uses port 22 by default, so you would need to configure the router to forward port 22 traffic to your machine). If you're not sure how to access the configuration screens for this device (and there may be default passwords you'll need to know about), and you don't have a manual for it, do a google on the make/model number and you'll probably find a manual out there somewhere, or maybe your ISP can provide one for you. 2. If you're running a firewall on your machine (e.g., shorewall), you'll need to configure it to accept tcp port 22 requests. If you read up on shorewall, you'll see that you have options to restrict access to only certain ip addresses. 3. You probably also need to check /etc/hosts.allow. You may need a line that says: sshd:<<allowed_ip_address>>:ALLOW 4. If you're just trying to ssh into that machine from within a local network, then only 2 and 3 above will apply. 5. Of course, there are security considerations to allowing ssh requests from the Internet. You can search on keywords for techniques to minimize the risk. Lots of posts here and elsewhere about that. The above is not necessarily complete. But it's a starter anyway. If you're having problems, do searches on the problem keywords, and ask further questions if you're stuck.

Your computer is undoubtedly behind a NAT router or some sort of NAT firewall. If this machine were directly connected to the Internet rather than behind the NAT firewall, then the ifconfig and route commands would show the static IP address assigned to you by your ISP. You can see your ISP-assigned static IP address by going to a site like http://www.dnsstuff.com, where it shows in the upper right corner of your browser. More on NAT: http://en.wikipedia.org/wiki/NAT http://computer.howstuffworks.com/nat.htm/