Jump to content

znx

Members
  • Content Count

    1,230
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by znx

  1. znx

    mp3 file transfer

    If both machines are Linux, then an SFTP client would provide a good method (for instance Filezilla). If it is to a Windows machine then reverse the connection, using WinSCP. These will work on LAN or across the Internet but you will need the IP address of the machine you are connecting to and you will need to open an SSH port.
  2. This is like the chicken and the egg. Without a compiler you cannot compile a compiler. If the distribution does not provide a package for installation then the only other solution is to make a package yourself. Obviously this requires another distribution, which in itself can be a problem. One solution might be to use an RPM from another distribution and hope that the dependencies it requires are available. However in the case of AstLinux, I think you will find yourself installing loads of other tools in preparation for GCC. This is because AstLinux is a super-cut-down distribution intended for a single purpose. Maybe a solution would be to do the following, get a LiveCD distribution that has GCC and the other development tools present (Knoppix for instance). Mount your existing distribution on the LiveCD. That way you can compile a static version of GCC on Knoppix then pack/copy it onto your existing distribution. Certainly not ideal but I believe it would work. Ultimately the best solution would be for you to select a distribution that is more suited to your purpose.
  3. I assume that you have attempted to use Gnome/KDE's ability to set screen resolution and it isn't giving you any sizes bigger than 800x600. If not then this is the first step you want to do because it is the easiest by far. The second possibility is that your xorg.conf has the incorrect driver setting for your graphics card or is missing a setting. Take a look at the file /etc/X11/xorg.conf (it might not exist which means Xorg is just guessing all the settings). If it exists then look for the section called "Screen": Section "Screen" Identifier "Default Screen" Device "My Graphics Card Entry" Monitor "My Monitor Entry" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1024x780" "800x600" "640x480" EndSubSection EndSection This is an example, the lines you wish to check are the DefaultDepth and the Modes. Check that the depth is 24 and that the modes line contains the sizes your monitor is capable of. Make sure you backup the files before you edit it, just in case you break something. If that still doesn't provide you the ability to change the resolution, then come back here and show us: Which particular Linux system you are using (some have tools to help Xorg setup) Your xorg.conf (if it exists) The particulars of your graphics card. The particulars of your monitor (refresh rate, horizontal sync, size, et al).
  4. There is a simple fix here, see at the very end of the bashrc: ###My Aliases #open bashrc alias ebrc="nano ~/.bashrc You are missing the closing quote on that alias. SO it should be: ###My Aliases #open bashrc alias ebrc="nano ~/.bashrc" Save and there will no longer be any complaints.
  5. Linux isn't a hacker's tool any more than Windows is. Linux is an Operating System, which means it can be used for any purpose. If you upload a copy of your bashrc I will look at it and tell you what the problem is.
  6. The kernel saying that it isn't updated could be that the kernel is restricted from updating (not uncommon). Therefore you need to specify an upgrade to the kernel manually: apt-get update kernel Then reboot into the new kernel. The unrelated problem to your kernel upgrade and is more likely a personal alteration gone wrong. The /home/china/.bashrc is a personal configuration file for the user "china". I suggest that you either edit the file and fix the problem or simply move the file out of the way: mv /home/china/.bashrc /home/china/bashrc-old As suggested by the problem, the line 102 (end of the file) is where the problem is detected. You are missing a " quote somewhere inside the file.
  7. It seems like more and more companies are passing out public betas. So it is no great surprise that Novell has release a beta of their Open Enterprise Server 2 (OES2 SP2) http://download.novell.com/Download?buildid=CzEYrMAy8bM~
  8. Certainly one impressive looking piece of software. Web front-end's generally turn out to be extremely simply to use as well. If I was a Postfix user I think that I would give this a try. But it looks like you are expanding this to make it a Webmin competitor and by the looks of things, a Webmin beater. Nice!
  9. znx

    Hi

    Hi, welcome to the Linux world! I would advise that you upgrade to F11. This is because of the way that Redhat release Fedora. Only one version back is given support, that means F9 is just out of support. So any issues with RPMs et al would probably be ignored by the developers. Saying that if you are just entering the Linux world you might find that using F9 is more than good enough for playing around with. Good Luck!
  10. You should be able to find a GUI editor for the boot loader. However if you are comfortable in the terminal then you can do the following: Open terminal Become root by typing: su - Edit the grub configuration file, you will most likely find nano to be the simplest terminal editor, so: nano /boot/grub/grub.conf You should see something like this in the file: title Fedora (SomeVersion.fc11) root (hdX,Y) kernel /boot/vmlinuz-SomeVersion.fc11 ro root=LABEL=/ rhgb quiet initrd /boot/initrd-SomeVersion.fc11.img Now add the additional bits to the end of the kernel line: title Fedora (SomeVersion.fc11) root (hdX,Y) kernel /boot/vmlinuz-SomeVersion.fc11 ro root=LABEL=/ rhgb quiet noapic nolapic initrd /boot/initrd-SomeVersion.fc11.img Save the file (Ctrl+o in nano) and exit the editor (Ctrl+x in nano) Reboot! All things being well you will have a system that no longer acts weird. Obviously take care when you are editing grub.conf because it controls your boot sequence.
  11. It is always good to hear people going out to experiment with Linux. You had a couple of hurdles and have happily taken them on, which others would probably have baulked at. The direct run option on Firefox has been present since early versions and indeed IE has similar functionality. The speed of the system is normally down to the fact that Linux doesn't require 2Gb of RAM just to run unlike Vista ! I believe that BIOS bug you are experiencing could be fixed by appending some options to your kernel boot line. If you are using Grub for the boot loader (you probably are) then you need to edit the configuration file for it. Either noapic or nolapic or maybe even both. Edit the file /boot/grub/grub.conf and look for the line beginning with kernel, then add the options to the end. For instance: kernel /vmlinuz-VERSION ro root=LABEL=/ rhgb noapic nolapic By the way, APIC = Advanced Programmable Interrupt Controllers and check out these: http://en.wikipedia.org/wiki/Intel_APIC_Architecture#Hardware_Bugs and http://en.wikipedia.org/wiki/Intel_8259 APIC was a cause of unusual freezing and sudden deaths a few times for myself, it can actually cause lots of sorts of strangeness on your system, so might be the cause of the graphics issue as well. It is always difficult to point people in a direction to try and get documentation of systems. If there is one thing that truly lacks in Linux is it comprehensive user-friendly documentation. Fortunately there are places like here to try and assist you.
  12. Why must the best open source projects waver *sigh* Let us hope that someone will sort out the finer detail and get CentOS back on track. I am certain that if they don't then it is almost certain that someone will splinter the project and make a new one.
  13. So .. I think I'm back. Here's hoping anyway. I think I have been inactive for a couple of years (maybe more?) Let's see if maybe I can assist some peeps.
  14. znx

    avahi problem

    Hi, OK so yeah circular dependencies are rare and as yet portage can't sort them. However the way to solve them is by doing what you did, remove the USE flag install. Then what you do is add the USE flag again and rebuild the package that have been altered: # emerge -aN world When you hit the space bar, yes it did continue, it didn't effect the installation at all. So don't worry about it at all.
  15. Hello and welcome to the forums. Congrats on switching to Linux, it can be a little bumpy but stick it out, it will all come good in the end! Your friend is right, gentoo can help you learn a tonne of stuff about how Linux works (mainly because gentoo is still a little raw). Google can provide you an answer but sometimes it doesn't explain why that answer is the answer (if you understand what I mean!). Everyone is a noob in the beginning but you'll pick it up ! WELCOME
  16. Hi! Gentoo can be a little bit troublesome to figure out when you start out with it (I remember those days..). Lets run through the files: Portage has a default configuration file which is /etc/make.globals. This file should never be edited but it can be a good reference for settings in portage. Then there is the profile files, every different architecture has its own profile. These profiles represent the defaults for portage that are dependent on arch. There is a symlink /etc/make.profile/ to a directory in the portage tree, which contains multiple files. Again you should not edit these files, these are just setting defaults. The USE flag defaults are in /etc/make.profile/make.defaults. If you want to alter anything to make it differ from the defaults then you make a file called /etc/make.conf. This file is your master configuration for portage. All the changes you want to make go in here, all the global USE flag changes you want .. go in here too. There is also some other files you can make, which allow even finer control of portage: /etc/portage/package.mask - stop portage from ever installing packages. /etc/portage/package.unmask - allow portage to install a file, even if it isn't recommended /etc/portage/package.keywords - allow you to install packages which are marked as unstable/untested on your arch. /etc/portage/package.use - alter a USE flag for just one package, rather than for the whole system You won't have any of those files by default, you'd need to make. In conclusion, if you are just starting out with gentoo I would highly recommend that you stick to editing just /etc/make.conf. An example of adding a flag and removing another is like this: USE='flagon -flagoff' Make sure you don't put a new line in there, all on one line. Hope that helps you, welcome to the forums / Linux and gentoo!
  17. znx

    Enlightenment E17

    Oh yeah, no problem .. here is my IRC virtual desktop ..
  18. It is very important that Ubuntu and Debian users check and confirm any and all of their keys / certs are good.
  19. Hi, welcome to the world of Linux .. in a rush ! So you say you are getting a 403 error. Normally 403 are related to the file permissions or the permissions on the directories that the files lie in. Check what permissions that PDF has, does it lie in the same directory as the others? As in direct on the machine, or via a direct URL? Do you mean the webpage links, I assume so. Yes they are OK because you are getting 403 errors (you would get 404 if they were wrong). It would be my guess that they are not OK. This is the most likely cause of 403 (although there is other things that can cause it). To check do this. Lets assume that the PDF is here: /var/www/localhost/htdocs/mypdfs/ and is called weee.pdf. To check that the permissions are OK you need to do this: # ls -d /var /var/www /var/www/localhost /var/www/localhost/htdocs /var/www/localhost/htdocs/mypdfs # ls -l /var/www/localhost/htdocs/mypdfs/weee.pdf The full path needs to be checked to make sure its accessible for the web server. Normally the permissions for directories should look like this: drwxr-xr-x (thats 755) and for files they normally look like this: -rw-r--r- (thats 644). If you are still experiencing issues, then you might want to check the .htaccess files. These can have rules set in them that control the access to files within the web server. Finally checking the actual httpd.conf for the same restrictions. I hope this helps you.
  20. znx

    Enlightenment E17

    Continue with installing e17, one of the annoying things is trying to remember all the packages you have installed and therefore which to update. Here is a simple script to work through all the ebuild packages in the overlay. #!/bin/sh for EBUILD in $(ls /usr/portage/local/layman/enlightenment/*/*/*-9999*ebuild) do CUR=$(dirname ${EBUILD#*enlightenment/}) emerge --quiet ${CUR} || echo ${CUR} >>fail done That should build everything! It might cause some stuff to be installed a couple of times if they get called in as requirements earlier on. One other thing that I failed to mention is that you should do this: # cd /etc/portage # mv package.keywords package.keywords.file # mkdir package.keywords # cd package.keywords # mv ../package.keywords.file main # ln -s /usr/portage/local/layman/enlightenment/scripts/package.keywords.livecvs enlightenment That will ensure that all the packages can be built without you needing to look after the keywords!
  21. Sweet screenshots, looking as good as ever. Congrats go to McDuck for catching the ISO !
  22. So, first up. Yes that is all you need to do to install freenx (yum downloads the package for you and installs it). Next you will require the SSH port to be forwarded to your box. Knowing the internal and external IP won't help you. So at this point you will be stuck and unable to do anything. Without a forward there is no way in. yum update doesn't ever remove data, it will simply update packages that are already on your system.
  23. Um no, that is extremely odd. Unless it was updating the kernel there is no need for major reboots. It's really good that its fixed.
  24. There is also the file /proc/mounts which contains the information.
×
×
  • Create New...