Linux Experts
  • Content Count

  • Joined

  • Last visited

Everything posted by iccaros

  1. iccaros


    wow you have caps in NZ? most of us are used to unlimited, but in eaither case. you do not need all security updates? I say agian, you do not need all security updates. here is why, in windows the security updates are for everyone, because windows updates only fix the OS in Ubuntu there are 100 of other non os progrmas and they put out patches when they are ready, and most are not security they are bug fixes. here is the rule of thumb, if you do not use the software that is being patched, then uncheck its box. or note the patch and ask one of us to mail you a disk with them, I can do that. remember the updates are for everything installed on ubuntu while in windows its only the Core OS.. Trust me the US Navy has this same mind set that they must download and test every patch, and they came to the conclusion that Linux must be less secure because its always being fixed. after a couple days of talks, they finally got the picture that they may not need all the patches at all, but are so ingrained in the windows patch Tuesday's, that they cant get over all the patches.. also since Linux is open they let you know when there are issues, so they are stuck fixing them. I know many a MS worker her 20 miles out of Redmond, and all will tell you that windows has security holes they plan on never fixing. here is another rule of thumb if it works don't just get the newest version unless it contains things you want. I ignore most if not all kbuntu/ubuntu patches as I do not need the upgrades. just something to think about.
  2. hmm the update I track this error code to is this http://support.microsoft.com/kb/936357 it is suggested that you can retry to install the patch or roll it back but the one you found may be intertwined..
  3. can you post the BSOD error message ? I see nothing in this log out of whack
  4. Line one of the "Function" is opening the rs232 FIFO and assigning its buffer the name #1 reading in random mode and not sequencal next they are creating an integer and two strings. next comes the work a$ = CHR$(27) + "P": PRINT #1, a$ this is really two lines in one see the : so we assign ascii char 27 (see http://game-editor.com/tutorials/images/ascii.jpg) followed by the P so we have a$ = "^[P" and the second half puts that string to the serial port (in basic you print to a port like you do the screen, and read from it like a keyboard) s1$ = "": c1$ = "" this is also two lines that assign blank strings to s1$ and c1$ it looks like (with out the rest of the code this is just a guess) a$ = INPUT$(15, #1) is assigning the first 15 chars from the serial port to a$ or INPUT$ is an Array and we are looking up a value that is at position 15 x the value on the serial port then close does what it says , it closes the serial port the rest is simple s1$ = LEFT$(a$, 1) assign the value of the array LEFT$ at position of value of a$ x 1 c1$ = MID$(a$, 3, 8 ) again assign c1$ the value from an array based on the value of a$ c1! = VAL(c1$) 'inst value change string c1$ to an integer IF in = 2 THEN c1! = c1! * 10 I assume this is correct for qbasic but in other languages its IF in == 2 Then, so we evaluate the value of 'in' and if it equals 2 then we multiply 10 to c1! and assign that value back to its self IF s1$ = "-" THEN c1! = -c1! 'Convert to -ve val if -sign check if s1$ = - and if so make c1! a negative number hope that helps..
  5. this may be the problem 1 long 1 short: DRAM or M/B error by the way, nice system :-) Thanks shanenin it's more two short beeps. At the post screen there is no error code shown. It seems that once I install the motherboard driver cd that came with the motherboard thats when it started acting up. I'm not 100% sure though. Thanks again Sceeter32 two short beeps are normal.. if you get a bunch of short beeps after that it saying it can not find your keyboard. as is listed above more than three short beeps is a bios problem, try hard resetting your bios with the jumper , and see if that ends the issue. note, it says two small beeps are a bios setting problem, but I have found it to do two beeps if it thinks you have changed anything.
  6. what is the question... do you want fail over?
  7. just on battery. and it is an issue on all OS with specific hard drives (Ie Windows..) . not just Ubuntu, as these are the default setting from the hard drive manufacture.
  8. hmm, I had no issues, but I did the upgrade from the Ubuntu add or remove software and not from a DVD/CD It even fixed my aixgl stuff and my mono I broke before.. I also break OS, too much configuring, this is why I like Gentoo, even though I break that just as much, as it seams that its easier to fix. I also do some things diffrent, like my home folder is on a flash drive as I move it between distributions and VM images and I let the upgrade do use all of its defaults.. maybe this will help
  9. is it slow running from a captured partition on a NTFS partition ?
  10. did you choose LPT #1 as your parallel port in setting it up, remember that a parallel port is not plug-n-plan. windows sees the printer because you installed the driver.
  11. PXE is a standard for booting a OS from a network, and most BIOS are already setup to do this http://syslinux.zytor.com/pxe.php http://www.2x.com/pxes/ (this has the server in it)
  12. there are many languages and any would work, I would use a Pic processor to grab what ever information and send it over serial (need usb to serial converter) then pick a language you like java, mono(C#, VB, ironpython, boo), c++, objective C would all work, just pick one and read up on it.. this may help it uses java to read a serial port.. as for drawing graphes.. that is after you can do this much.. http://java.sun.com/developer/Books/javapr...cookbook/11.pdf
  13. http://www.cs.binghamton.edu/~reckert/360/7.html here is clipboard information for C# System.Windows.Forms.Clipboard.GetImage() should work
  14. did you install M4? http://www.gnu.org/software/m4/m4.html and if so then what program are you trying to build?
  15. Marty ,email makes no difference,your used to the way windows email clients can receive scripted email. there is no , and I mean no email program for Linux that you can do this with. also to do anything to your system the program would have to run sudo and then have your root password. as for finding K-Mail or Konquror open command shell and type the programs name in like kmail.. if that works you can then create an icon like hitest wrote before and for link just put the name of the program.
  16. this project is simple. you can use a basic stamp mac software for it http://www.muratnkonar.com/otherstuff/macbs2/ or just the microchip pic processor http://www.mactech.com/articles/mactech/Vo...ller/index.html in either case you have the "processor" send its output to a file, I would save it as csv then its up to you, but you could use excel at lest to graph it from a csv file or use nay other programing language to graph the output.. I say easy because use pic processors all the time , but hopefully I gave you enough information to get started. ps this is written with the mind set that you want to do it your self, not just buy one.
  17. clamAV you can use the kbuntu install software and search for it, check it and install we need to know which email program to tell you how to integrate. since there are no know active viruses for Linux, you can put your mind at rest that your system will be ok, but its always good practice to help protect anyone from you forwarding on an email with a windows virus good link http://librenix.com/?inode=21
  18. try a live linux cd and run fsck on the disk.. it should fix any issues. you may have to run the fsck for your format type (fsck.ext2 for example) Name fsck - check and repair a Linux file system Synopsis fsck [ -sAVRTNP ] [ -C [ fd ] ] [ -t fstype ] [filesys ... ] [--] [ fs-specific-options ] Description fsck is used to check and optionally repair one or more Linux file systems. filesys can be a device name (e.g. /dev/hdc1, /dev/sdb2), a mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Normally, the fsck program will try to handle filesystems on different physical disk drives in parallel to reduce the total amount of time needed to check all of the filesystems. If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in /etc/fstab serially. This is equivalent to the -As options. The exit code returned by fsck is the sum of the following conditions: 0 - No errors 1 - File system errors corrected 2 - System should be rebooted 4 - File system errors left uncorrected 8 - Operational error 16 - Usage or syntax error 32 - Fsck canceled by user request 128 - Shared library error The exit code returned when multiple file systems are checked is the bit-wise OR of the exit codes for each file system that is checked. In actuality, fsck is simply a front-end for the various file system checkers (fsck.fstype) available under Linux. The file system-specific checker is searched for in /sbin first, then in /etc/fs and /etc, and finally in the directories listed in the PATH environment variable. Please see the file system-specific checker manual pages for further details. Options -s Serialize fsck operations. This is a good idea if you are checking multiple filesystems and the checkers are in an interactive mode. (Note: e2fsck(8) runs in an interactive mode by default. To make e2fsck(8) run in a non-interactive mode, you must either specify the -p or -a option, if you wish for errors to be corrected automatically, or the -n option if you do not.) -t fslist Specifies the type(s) of file system to be checked. When the -A flag is specified, only filesystems that match fslist are checked. The fslist parameter is a comma-separated list of filesystems and options specifiers. All of the filesystems in this comma-separated list may be prefixed by a negation operator 'no' or '!', which requests that only those filesystems not listed in fslist will be checked. If all of the filesystems in fslist are not prefixed by a negation operator, then only those filesystems listed in fslist will be checked. Options specifiers may be included in the comma-separated fslist. They must have the format opts=fs-option. If an options specifier is present, then only filesystems which contain fs-option in their mount options field of /etc/fstab will be checked. If the options specifier is prefixed by a negation operator, then only those filesystems that do not have fs-option in their mount options field of /etc/fstab will be checked. For example, if opts=ro appears in fslist, then only filesystems listed in /etc/fstab with the ro option will be checked. For compatibility with Mandrake distributions whose boot scripts depend upon an unauthorized UI change to the fsck program, if a filesystem type of loop is found in fslist, it is treated as if opts=loop were specified as an argument to the -t option. Normally, the filesystem type is deduced by searching for filesys in the /etc/fstab file and using the corresponding entry. If the type can not be deduced, and there is only a single filesystem given as an argument to the -t option, fsck will use the specified filesystem type. If this type is not available, then the default file system type (currently ext2) is used. -A Walk through the /etc/fstab file and try to check all file systems in one run. This option is typically used from the /etc/rc system initialization file, instead of multiple commands for checking a single file system. The root filesystem will be checked first unless the -P option is specified (see below). After that, filesystems will be checked in the order specified by the fs_passno (the sixth) field in the /etc/fstab file. Filesystems with a fs_passno value of 0 are skipped and are not checked at all. Filesystems with a fs_passno value of greater than zero will be checked in order, with filesystems with the lowest fs_passno number being checked first. If there are multiple filesystems with the same pass number, fsck will attempt to check them in parallel, although it will avoid running multiple filesystem checks on the same physical disk. Hence, a very common configuration in /etc/fstab files is to set the root filesystem to have a fs_passno value of 1 and to set all other filesystems to have a fs_passno value of 2. This will allow fsck to automatically run filesystem checkers in parallel if it is advantageous to do so. System administrators might choose not to use this configuration if they need to avoid multiple filesystem checks running in parallel for some reason --- for example, if the machine in question is short on memory so that excessive paging is a concern. -C [ "fd" ] Display completion/progress bars for those filesystem checkers (currently only for ext2 and ext3) which support them. Fsck will manage the filesystem checkers so that only one of them will display a progress bar at a time. GUI front-ends may specify a file descriptor fd, in which case the progress bar information will be sent to that file descriptor. -N Don't execute, just show what would be done. -P When the -A flag is set, check the root filesystem in parallel with the other filesystems. This is not the safest thing in the world to do, since if the root filesystem is in doubt things like the e2fsck(8) executable might be corrupted! This option is mainly provided for those sysadmins who don't want to repartition the root filesystem to be small and compact (which is really the right solution). -R When checking all file systems with the -A flag, skip the root file system (in case it's already mounted read-write). -T Don't show the title on startup. -V Produce verbose output, including all file system-specific commands that are executed. fs-specific-options Options which are not understood by fsck are passed to the filesystem-specific checker. These arguments must not take arguments, as there is no way for fsck to be able to properly guess which arguments take options and which don't. Options and arguments which follow the -- are treated as file system-specific options to be passed to the file system-specific checker. Please note that fsck is not designed to pass arbitrarily complicated options to filesystem-specific checkers. If you're doing something complicated, please just execute the filesystem-specific checker directly. If you pass fsck some horribly complicated option and arguments, and it doesn't do what you expect, don't bother reporting it as a bug. You're almost certainly doing something that you shouldn't be doing with fsck. Options to different filesystem-specific fsck's are not standardized. If in doubt, please consult the man pages of the filesystem-specific checker. Although not guaranteed, the following options are supported by most file system checkers: -a Automatically repair the file system without any questions (use this option with caution). Note that e2fsck(8) supports -a for backwards compatibility only. This option is mapped to e2fsck's -p option which is safe to use, unlike the -a option that some file system checkers support. -n For some filesystem-specific checkers, the -n option will cause the fs-specific fsck to avoid attempting to repair any problems, but simply report such problems to stdout. This is however not true for all filesystem-specific checkers. In particular, fsck.reiserfs(8) will not report any corruption if given this option. fsck.minix(8) does not support the -n option at all. -r Interactively repair the filesystem (ask for confirmations). Note: It is generally a bad idea to use this option if multiple fsck's are being run in parallel. Also note that this is e2fsck's default behavior; it supports this option for backwards compatibility reasons only. -y For some filesystem-specific checkers, the -y option will cause the fs-specific fsck to always attempt to fix any detected filesystem corruption automatically. Sometimes an expert may be able to do better driving the fsck manually. Note that not all filesystem-specific checkers implement this option. In particular fsck.minix(8) and fsck.cramfs(8) does not support the -y option as of this writing. Author Theodore Ts'o ([email protected]) Files /etc/fstab. Environment Variables The fsck program's behavior is affected by the following environment variables: FSCK_FORCE_ALL_PARALLEL If this environment variable is set, fsck will attempt to run all of the specified filesystems in parallel, regardless of whether the filesystems appear to be on the same device. (This is useful for RAID systems or high-end storage systems such as those sold by companies such as IBM or EMC.) FSCK_MAX_INST This environment variable will limit the maximum number of file system checkers that can be running at one time. This allows configurations which have a large number of disks to avoid fsck starting too many file system checkers at once, which might overload CPU and memory resources available on the system. If this value is zero, then an unlimited number of processes can be spawned. This is currently the default, but future versions of fsck may attempt to automatically determine how many file system checks can be run based on gathering accounting data from the operating system. PATH The PATH environment variable is used to find file system checkers. A set of system directories are searched first: /sbin, /sbin/fs.d, /sbin/fs, /etc/fs, and /etc. Then the set of directories found in the PATH environment are searched. FSTAB_FILE This environment variable allows the system administrator to override the standard location of the /etc/fstab file. It is also useful for developers who are testing fsck. See Also fstab(5), mkfs(8), fsck.ext2(8) or fsck.ext3(8) or e2fsck(8), cramfsck(8), fsck.minix(8), fsck.msdos(8), fsck.jfs(8), fsck.nfs(8), fsck.vfat(8), fsck.xfs(8), fsck.xiafs(8), reiserfsck(8). REFERENCED BY findfs(8), fs(5), jfs_tune(8), logsave(8), mkfs.minix(8), quotacheck(8), shutdown(8), tune2fs(8)
  19. I think that would be sdb1 (first partition on the drive ) also I think its vfat for fat 32 msdos is used for fat16 and older
  20. Deaf Girl, we need more information on which wireless card are you using? here is some starter reading http://www.linuxmint.com/forum/viewtopic.p...=wpa&t=3296
  21. I think its -f for Linux NAME tail - output the last part of files SYNOPSIS tail [OPTION]... [FILE]... DESCRIPTION Print the last 10 lines of each FILE to standard output. With more than one FILE, precede each with a header giving the file name. With no FILE, or when FILE is -, read standard input. Mandatory arguments to long options are mandatory for short options too. --retry keep trying to open a file even if it is inaccessible when tail starts or if it becomes inaccessible later -- useful only with -f -c, --bytes=N output the last N bytes -f, --follow[={name|descriptor}] output appended data as the file grows; -f, --follow, and --follow=descriptor are equivalent -F same as --follow=name --retry -n, --lines=N output the last N lines, instead of the last 10 --max-unchanged-stats=N with --follow=name, reopen a FILE which has not changed size after N (default 5) iterations to see if it has been unlinked or renamed (this is the usual case of rotated log files) --pid=PID with -f, terminate after process ID, PID dies -q, --quiet, --silent never output headers giving file names -s, --sleep-interval=S with -f, sleep for approximately S seconds (default 1.0) between iterations. -v, --verbose always output headers giving file names --help display this help and exit --version output version information and exit If the first character of N (the number of bytes or lines) is a `+', print beginning with the Nth item from the start of each file, otherwise, print the last N items in the file. N may have a multiplier suffix: b for 512, k for 1024, m for 1048576 (1 Meg). With --follow (-f), tail defaults to following the file descriptor, which means that even if a tail'ed file is renamed, tail will continue to track its end. This default behavior is not desirable when you really want to track the actual name of the file, not the file descriptor (e.g., log rotation). Use --follow=name in that case. That causes tail to track the named file by reopening it periodically to see if it has been removed and recreated by some other program. SEE ALSO The full documentation for tail is maintained as a Texinfo manual. If the info and tail programs are properly installed at your site, the command info tail should give you access to the complete manual.
  22. try this under media create a folder then try to mount it to that folder mount /dev/sdc1 /media/foldername at the same time tail -v /var/syslog I think its v anyways .. or maybe that is just unix.. you can try it with out the -v..
  23. would you not do a mount and see what the drive mounted is named then grep for the other.. also if the bigger drive is NTFS, I do not Believe that NTFS driveres are loaded by default in Ubuntu.. http://ubuntuforums.org/showthread.php?t=217009
  24. that is why I moved to http://www.beryl-project.org/, as if that happens you right click the diamond and tell it to restart the windows manager. it does not kill X but it does give you back window control. the issue is that computz is still alpha and crashes, but the default way of install gives you no way to restart cleanly.. also beryl lets you turn it on and off, useful for video player that have problems with the 3d desktop