Jump to content

linux_learner

OTW
  • Posts

    892
  • Joined

  • Last visited

Posts posted by linux_learner

  1. i have read threads, about how that in order to get your web based mail, you need hotwayd, mr postman or such. i thought wait a minute, there has to be another way. the good news is, there is. it is possible to get your hotmail with out hotwayd or mr postman. all you need is the servers.

     

    POP3: pop3hot.com

    SMTP: mx01.hotmail.com

     

    this is not intended as a howto. you can use either pop settings or imap.

     

    i have tested this out on evolution and thunderbird. thunderbird wont let me do two hotmail accounts (not sure why). i havent tried two accounts in evolution yet. LiquidZoo did this in kmail, so i know it works in kmail as well.

     

    (if you need help setting this up, just ask)

  2. i think the distro should make the n00b install, where it installs one desktop. from this point, the n00b should have the choice as to which packages they want installed, with out knowing that they are packages. they could be asked if they want gnome office (if they go with gnome) or koffice (if they go with kde) or openoffice, and a choice of media palyer/s.

     

    we could still offer more control to the more experienced user on install.

     

     

    by going this way, we make the bloat up to the user and make it simple for the n00b while powerfull and flexable for the experienced.

  3. So what your are saying linux_learner is not to operate the software near a microwave?

     

    :jester:

     

    FX

     

    lol no. a pacemaker does not involve software. i was just comparing the body's resusitation to a computers reboot.

     

    um... all it is is a virtual keyboard on your skin that uses your sweat to transmit a _minute_ electric signal.

     

    if your not talking voltage. sure. our bodies actually hold charges of arround 20,000 volts. just miniscule amounts of amps. our bodies are like inductive capacitors.

  4. I can't wait until some has to "reboot" themselfs for the first time. Would there be a next?

     

    FX

     

     

    well, if you consider a flat line as a power down, and defibulating as powering up, completing the "reboot", then we already do that.

     

    everytime we bring a person back, you could consider that a successful "reboot".

     

    still.....would any of us trust any technology to this extent? pacemakers are one thing, but this is a whole nother level.

  5. kde forum http://www.kde-forum.org/index.php

     

    kde system administrators guide http://www.kde.org/areas/sysadmin/

     

    firefox forum http://forums.mozillazine.org/viewforum.ph...853a94317d99429

     

     

    iptables/netfilter howto http://www.netfilter.org/documentation/ind...mentation-howto

     

    a nice link covering linux, freebsd, redhat, and suse http://elibrary.fultus.com/technical/index...suse/index.html

     

    maybe mystified can add these ;)

     

    these are just some links i've found. if yall have more, please add them.

     

    Links added - mystified

  6. I personally like having many different ways to doing things in Linux.

     

    If everyone did it the same way we woould be just like M$ except with different eyecandy.

     

    It also places one more level of difficulty for the hacker. He can't just assume I'm running things the same as everyone else. He has to actually get better than a typical script kiddie.

     

    In the end the best shall remain and the stuff that doesn't get better falls away. How many distros are out there and exactly how many will be supported or updated in five years? very few compaired to how many there are.

    i agree pzatch.

     

    all these "different" tools, really arent that different. all they are, are front end to the cli. in YAST network section or in MCC network section its just a front end to things like netconfig, ifconfig, and so on.

     

    i started out on slackware (no linuxconf) then tried redhat. redhat ofcourse had the linuxconf, as did the earlier mandrakes, but while i found it usefull and effective, it was cumbersome. i could (and did) get lost in there. thats never happened in YAST or MCC.

     

    webmin seems to be (at least for now) *the standard* config tool. its in virtually every distro. just the distro makers like to promote their tool. nothing wrong with that.

     

    with YAST being gpl'd and intigrated into kde, mandrake would have to seriously alter kde to bypass that. i dont forsee that happening.

     

    deps are probably one of the most annoying things for a newb. i see this as a critical area to resolve. this gui tools stuff, i dont. why? simple. no matter what distro, you can always use the same or similar commands in the cli or edit the same or similar files. /etc/resolv.conf is gonna always be in /etc/resolv.conf. ifconfig up is always gonna be ifconfig up.

     

    look at nvidia. they dont make distro specific packages. they make it an executeable, a bin/sh/run. this package will run on any distro. how about limewire? its also a bin. it to runs on every distro as long as java is installed.

     

    the gui tools i dont see as the problem. they are based on a standard. we could always go back to ncurses. that WAS the standard, and for some it still is. the gui tools just give us options. for firewalls we have, guarddog, firestarter, shorewall, to name but a few. they all are front end to iptables.

     

    i think webmin should be the standard, and should stay the standard (at least for now). it has modules. it can be used from a browser. its in virtually every distro. there is only one problem with webmin, it doesnt do system installation, like yast or MCC does (talking boot disk here).

     

    i run suse 9.0 pro, and i have webmin. i had to get it from apt-get, but i have it. it runs well. no conflicts.

     

    to say that techs would need 200+ manuals though, is just plain wrong. linux is linux. the kernel operates the same in any distro. the commands are the same. where they start to differ on are the distro specific tools.

     

    i can configure X manually with XFree86Setup (or whatever the command is now) or i can run SaX2 or XFdrake. or i can run xf86config, or even pull out my favorite editor and edit the config file that way.

     

    all a tech needs to know is what way will work on every distro. period. end of story. of which, the examples i gave, work in every distro.

     

    source or bin packages install where the coder wants them (most of the time). but then, this is one reason i suggested the package manager i did. in which most have told me "your crazy".

  7. i'm sorry yall, but i'm a bit confused. from the partimage howto

    4.4 How to create an eltorito bootable CD-Rom ?

     

    This section will help you to create a bootable CD-Rom, from the image file provided on partimage web site. Then, you just have to start your computer on this CD-Rom to able to run Partition Image, and to save/restore partitions. You won't need to have a linux system installed on your computer, or to use floppy disks to use partimage.

     

    You will need to download the file partimage-x.y.z-bootcd-w.img first. (2.88 MB)

     

    1) Create your main burning directory: for example "CDBurning".

     

    2) Go in your main burning directory, and create a sub-directory named ".eltorito", and copy the 2.88 MB image file in this directory.

     

    3) Copy all the other files in the main "CDBurning" directory. For example, your can copy all your image files. You can put 650 MB files here.

     

    4) Now, create the ISO image with "mkisofs" Go in your main burning directory, with a console. Type the following command: mkisofs -o /tmp/cd-rescue.iso -R -V "Partition Image rescue" -v -J -T -d -D -b .eltorito/partimage-x.y.z-bootcd-w.img -c .eltorito/eltorito.boot -A "Partition Image" .

     

    Don't forget the final point "." and update the file name with the name of the current version.

     

    /tmp/cd-rescue.iso is the image file to create. You may need up to about 700 MB of free space to create this file. Then, if you don't have enough space on your root directory, please choose another temp path.

     

    mkisofs will create a 650 MB image file (or smaller if you don't have a full CD), it can take time it's around 15 minutes usually.

     

    5) It's time to burn your CD. You can use "cdrecord in console mode", or another GUI, as gCombust. See the man pages for cdrecord for more info if you need it.

     

    6) Your bootable CD-Rom is now ready

     

    You can also burn the bootable CD-Rom with Nero under Windows. That's very easy: You just have to choose the image file, and select that's a 2.88 MB floppy disk.

     

    http://www.partimage.org/doc/index-4.html

     

    notice it says

    You will need to download the file partimage-x.y.z-bootcd-w.img first.
    so i'm a bit confused.

     

    i found an iso of partimage (lots of other cool iso's to) http://ftp.coe.psu.ac.th/ISO-images/00-index.html

     

    notice that this is listed in the above url ftp://ftp.psu.ac.th/pub/partimage/partima....2-bootcd-1.iso

     

    :help:

  8. i have never used partimage before. i have read the howtos and faq's. i still dont get it. if anyone could help me i'd appreciate it. i need to create a (or series of) bootable iso's.

     

    i need all of hda made into an image. hda has a fat32, swap, rieserfs (only 3 partitions). this way i can "ghost" my system back.

  9. i was thinking about the database issue. every linux distro has at least one database. we use updatedb so that locate and slocate can work. using either this database or a principle like this would resolve the database issue.

     

    1) it searches actual dirs and files

    2) not package specific

     

    this seems to be the best solution to resolve this issue, unless someone else has a better idea.

  10. i dont know if you have the debian apt-get or apt4rpm. if it is the debian apt-get then this goes to show that its a database issue, since yours only showed 27 packages.

     

    i have apt4rpm. this is a port of apt-get, but it only deals with rpms. since mine is apt4rpm it scans the rpms and the list on the net and gives results like its supposed to. now to do this with the debian apt-get. to be able to work with debian packages, just like rpms.

     

    they have ported portage over to suse, and i dont mean like they did with apt4rpm. this is the real portage. and since it is, it has its own database. http://forums.suselinuxsupport.de/index.ph...=796&hl=portage

  11. i had heard mdk was bringing their software back to an unnamed store, just that us customers would be pleased. today, i walk in to a favorite bookstore of mine to look at linux books and some A+ books. while looking at the linux books i saw mandrake 10.0 Discovery going for $50 (roughly). this bookstore is also supposed to cary suse 9.1 pro verry soon. which bookstore? Borders! go check it out people. support linux, and those who sell linux.

  12. i can come up with ideas, but for now i cant code. i understand the concepts, but dont know the functions, and i barely have time.

     

    i was talking with tyme about this, although it was a limited conversation. he pointed out http://www.autopackage.org/ in which i said, thats close, but not quite what i dreamt up.

     

    so what then is my idea? here it is.

     

    my idea, much like autopackage is to unify the package managers. but my approach is different. what i want to do, is combine debian apt-get, urpmi, and portage into a single package manager. to have an interface like red carpet, or maybe intigrated with webmin. where the user can uninstall, upgrade and install all at once.

     

    the idea behind this is whether the package is on the system or on the net, the use can click on it and install it. the user could install source packages just by clicking on it, or debian packages or rpm. it doesnt matter.

     

    the tough part would be the data base. portage, urpmi, and apt-get all use different data bases, so we'd have to somehow resolve this into a single database.

     

    ofcourse the first line of business would be to get the cli part working, then worry about the front end.

     

    i'm open to ideas. i really think this is one area that linux could work on. it would go along way to smooth the transition from windows to linux.

  13. with harddrives as big as they are, have a swap partition is no biggie.

     

    with ram as big as it is, one would think we dont need swap, but programmers seem to code apps to use that ram. as long as programmers code this way, we will need swap, unless we come out with a whole new way of memory management.

  14. this seems to be a little known area in linux, so i thought i'd take a minute and give yall a few links.

     

    DansGuardian http://dansguardian.org/

     

    SurfControl Web Filter VS for Linux http://www.surfcontrol.com/products/web/vs/

     

    ContentKeeper http://www.contentkeeper.com/ this one came recomended by Linux Online

     

    SquidGuard http://www.squidguard.org/ (squidGuard is a combined filter, redirector and access controller plugin for Squid. )

  15. i read the article mentioned in this thread and pretty much have to agree. but this......this gets me. this maybe one reason people "hate" redhat. http://software.silicon.com/os/0,39024651,...39116741,00.htm

     

    now dont get me wrong, i do, and have recomended windows for some people. and there might be "some" advantages of windows over linux (eg. gaming). what i do is i find out what a person is looking for in their pc. then make my recomendation, and go over the pros and cons. of all options (windows, mac, linux).

     

    i would never do as the ceo of redhat has done and flatly recomend windows over linux.

     

    the ceo talks about drivers

    "I would argue that from the device-driver standpoint and perhaps some of the other traditional functionality, for that classic consumer purchaser, it is my view that [Linux] technology needs to mature a little bit more."

     

    ok. lets look at my box. my box is a compaq pressario 5000US. ftp://ftp.compaq.com/pub/supportinformati...000_rev3_us.pdf the only thing that is not compatible with linux, is the pctel modem. of which there is a pctel driver. http://linmodems.technion.ac.il/pctel-linux/

     

    only one thing in my box was incompatible with linux and it has a driver. that kinda shows up redhat ceo's statement.

     

    also most of the device drivers are that are incompatible with linux were designed specifically for windows and are closed source. this is not the fault of linux. it is also true that linux provides more drivers than windows. with windows you may need the devices cd or get the driver off the net. just by shear numbers liux has more drivers.

     

    :wall::wall::wall::angry::devil: :deal: :deal: :furious3::furious3:

     

    yeah, i'm a bit ticked off.

×
×
  • Create New...