Call for Paper October 2013 |Volume 3 : Issue 10|
Call for Paper Dear Colleagues You are cordially invited to submit or recommend papers to: [1]http://www.grjournals.com October 2013 (Volume 3 | Issue 10) · Journal of Physiology and Pharmacology Advances (JPPA) [2]http://grjournals.com/Default.aspx?tabid=6605articleType=CategoryVi ewcategoryId=2302 · Journal of Animal Production Advances (JAPA) [3]http://grjournals.com/Default.aspx?tabid=6606articleType=CategoryVi ewcategoryId=2301 · Journal of Veterinary Advances (JVA) http://grjournals.com/Default.aspx?tabid=6604articleType=CategoryView; categoryId=2303 · Journal of Animal Science Advances (JASA) [4]http://grjournals.com/Default.aspx?tabid=6529articleType=Category ViewcategoryId=2272 Top 20 Hottest Articles (Last 7 Days) [5]http://www.scopemed.org/ Global Researchers Journals, a fast track peer-reviewed and open access academic journal published by Grjournals Publishing, which is one of the largest open access journal publishers around the world. Grjournals is using online article submission, review and tracking system for quality and quick review processing. Journal provides rapid publication of research article. After 30 days Rapid Review Process by the editorial/review board members or outside experts, an accepted paperwill be placed under In Press within 24 hours and will be published in the next issue. Instructions for authors are available on our website: [6]http://www.grjournals.com Submitted papers must follow the Instructions to authors to be considered for review and publication. Refereeing of manuscripts is conducted anonymously and the identity of the referees is not disclosed. The manuscripts which get an acceptance will publish with DOI number. Your Manuscript(s) can be one of these kinds: Review, Original Article, Case Report, Short Communications, Technical Notes, Mini Review Article and Hypothesis. Some of Abstracted/Index in: CAB reviews, Chemical Abstract Service (CAS), Genamics JournalSeek, Index Directory of Open Access Journals (DOAJ), Index Electronic Journals Library and SCIRUS, ISC and the World most Popular University Electronic Library. [7]http://grjournals.com/Defaul t.aspx?tabid=7329 Now you can clear the clutter by accessing your favorite journals online: · Full text, full archive that's always there when you need it · Easy access anywhere, anytime and anyhow · Impact your practice, not the environment NOTICE: Authors that cite [8]www.grjournals.com manuscripts as reference in their ISI articles, they can send their manuscripts to one of above journals as FREE of charge. After evaluation and get an acceptance it will publish without any Article Processing Fee with DOI. We apologize if you have received this email twice, or our journal is not your field. With Warm Regards Sincerely, Grjournals team Site: [9]www.grjournals.com E_Mail: [10]grjourn...@gmail.com References 1. http://www.grjournals.com/ 2. http://grjournals.com/Default.aspx?tabid=6605articleType=CategoryViewcategoryId=2302 3. http://grjournals.com/Default.aspx?tabid=6606articleType=CategoryViewcategoryId=2301 4. http://grjournals.com/Default.aspx?tabid=6529articleType=CategoryViewcategoryId=2272 5. http://www.scopemed.org/ 6. http://www.grjournals.com/ 7. http://grjournals.com/Default.aspx?tabid=7329 8. http://www.grjournals.com/ 9. http://www.grjournals.com/ 10. mailto:grjourn...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.1 - 9.2 upgrade
On 8 October 2013, at 16:40, Polytropon free...@edvax.de wrote: On Tue, 8 Oct 2013 11:20:40 -0700, Doug Hardie wrote: I tried downloading the src with: svn co https://svn0.us-west.FreeBSD.org/base/releng/9.2 /mnt/usr/src I didn't get Release 9.2. The first entry in UPDATING is: 20130705: hastctl(8)'s `status' command output changed to terse one-liner format. Scripts using this should switch to `list' command or be rewritten. There is an entry earlier for Release 9.1. but no entry for Release 9.2. You could try downloading and extracting the src distribution: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.2-RELEASE/src.txz Before I saw this I built from the src obtained via svn. The system now boots. I still have no idea what was preventing it from booting. It was something between displaying the Beastie menu and waiting for user input. There had to be at least 2 issues as the messages changed after the first attempt to rebuild the system. I tried to chase down the boot code for the first error message and it appears to be generated when there is a problem with a directory. I couldn't find any further diagnostic info to identify the directory. I have not yet tried to chase down the second set of messages in the source. The system now says its 9.2. UPDATING still looks the same. Interestingly enough, on another system that I updated earlier to 9.2 via freebsd-update, UPDATING there is identical to the one on this system. There is no 9.2 entry. Also of note is that most of the ports/packages are still present. However SASL2 vanished without a trace. Its easily replaced, but why is certainly interesting. I have no ideas at this point. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gpart weirdness: diskid/DISK-3EV0P4PZ00007250010X GPT (17G)
# gpart show = 34 35566411 da1 GPT (17G) 34 35566411 - free - (17G) = 34 35566411 diskid/DISK-3EV0P4PZ7250010X GPT (17G) 34 35566411- free - (17G) = 34 35566411 da2 GPT (17G) 34 35566411 - free - (17G) = 34 35566411 diskid/DISK-3EV0PWCX72500ZNJ GPT (17G) 34 35566411- free - (17G) # This is on ia64 10.0-CURRENT #5 r255488. Both disks appear twice in gpart show output. Is there some corruption in gpart data. What am I do to? Thanks Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Booting problem
Dear Sir, Please be kind enough to provide solution to the following problem. I have an old, assembled desk top loaded with win7 ultimate. It has got 80 GB hard disk and 1 GB RAM. Earlier there was XP. That time CD drive was not working at all. Subsequently I upgraded to win7. After few days suddenly I discovered that CD drive was working. I could burn files also through this drive. Though booting was not possible from CD. After few days suddenly, system stopped loading win7. I wanted to re install win7, but was not possible without the option of booting from CD. Whenever I tried to boot, one welcome screen and another screen came after one beep each and then it halts with a blank screen. I prepared a bootable USB drive with XP with an intention to install XP and thereafter upgrade to win7 (instructions for XP alone was available in the internet). After preparing the USB, I checked it in another system to see if it was working. In the BIOS there is no option to boot from USB. So I disabled all three boot options (Floppy, CD, HDD) and enabled “other” boot option and tried to boot from USB. Out of my nearly ten attempts, only twice, USB drive was displayed in the boot menu as a boot option, though it did not boot from it. Presently system does not boot either from HDD or from CD or from USB.(Floppy drive is not active since the relative cable is missing). My question is:- 1.Why should the boot menu display the USB drive only twice? Only in case of a loose connection such things can happen. I believe there is no question of any loose connection here. So either it should display all the time or it should not display at all. There is no specific option in the BIOS for booting from USB. If that means system does not support USB booting, then it should not have come in the boot menu at all. Fact that it appeared in the boot menu, means system supports booting from USB. 2. Why does not the system boot? I have a feeling that perhaps there is a component which is responsible for detecting drives or booting in general was failing slowly because of which CD drive was not working (when XP was there) and there after it was not booting from CD and again there after it stopped booting altogether from all the drives. Can there be a problem with mother board? 3. Someone told me that, in case of RAM failure, system will not start the boot process at all. Here since boot process goes few steps producing two screens and two beeps, perhaps it is trying to boot but why unable to detect the drives. 4. There are two separate cables for hard disk and CD drive. CD drive is primary and hard disk secondary. When I exchange the cables, it is reflected in the BIOS that is CD drive becomes secondary and vice versa. That means BIOS is recognizing the drives. 5. I tried with different boot order in the BIOS as well as by making the BIOS setting as default. 6. I tried the installation CD, so there is no question of whether the CD is bootable or not. Similarly if MBR is corrupt, it should give problem only for HDD booting and not for others like CD and USB. Then where is the problem? 7. Why doesn’t any error message displayed during boot process? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
On Tue, Oct 8, 2013, at 22:32, Mike Brown wrote: alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. If your sources are in /usr/src, do this: grep -v # /usr/src/sys/conf/newvers.sh | head -4 If he had sources on the box he probably would have just compiled the fixes himself. The version number shouldn't be embedded in the kernel like that so it's easier for people to audit their systems. I have VMs right now in Xen that report different FreeBSD versions and it's confusing for other sysadmins who aren't intimately familiar with FreeBSD. Some were updated by freebsd-update, some were updated by src. But they don't report the same OS version so I get asked why we haven't updated those servers yet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gpart weirdness: diskid/DISK-3EV0P4PZ00007250010X GPT (17G)
On Wed, Oct 9, 2013, at 4:33, Anton Shterenlikht wrote: # gpart show = 34 35566411 da1 GPT (17G) 34 35566411 - free - (17G) = 34 35566411 diskid/DISK-3EV0P4PZ7250010X GPT (17G) 34 35566411- free - (17G) = 34 35566411 da2 GPT (17G) 34 35566411 - free - (17G) = 34 35566411 diskid/DISK-3EV0PWCX72500ZNJ GPT (17G) 34 35566411- free - (17G) # This is normal. Gpart is showing you both the physical dev versions of the devices and the GPT label versions of the devices. I'll admit it can be confusing, though. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gpart weirdness: diskid/DISK-3EV0P4PZ00007250010X GPT (17G)
From: Mark Felder f...@freebsd.org To: freebsd-questions@freebsd.org Subject: Re: gpart weirdness: diskid/DISK-3EV0P4PZ7250010X GPT (17G) Date: Wed, 09 Oct 2013 06:56:17 -0500 On Wed, Oct 9, 2013, at 4:33, Anton Shterenlikht wrote: # gpart show = 34 35566411 da1 GPT (17G) 34 35566411 - free - (17G) = 34 35566411 diskid/DISK-3EV0P4PZ7250010X GPT (17G) 34 35566411- free - (17G) = 34 35566411 da2 GPT (17G) 34 35566411 - free - (17G) = 34 35566411 diskid/DISK-3EV0PWCX72500ZNJ GPT (17G) 34 35566411- free - (17G) # This is normal. Gpart is showing you both the physical dev versions of the devices and the GPT label versions of the devices. I'll admit it can be confusing, though. Well, I haven't seen this before. And it only shows this for some disks, not all: # gpart show = 34 143374671 da0 GPT (68G) 34 4096001 efi (200M) 409634 1429650712 freebsd-ufs (68G) = 34 35566411 da1 GPT (17G) 34 35566411 - free - (17G) = 34 35566411 da2 GPT (17G) 34 35566411 - free - (17G) = 34 142255508 da3 GPT (67G) 34 1422555081 freebsd-ufs (67G) = 34 35566411 diskid/DISK-3EV0P4PZ7250010X GPT (17G) 34 35566411- free - (17G) = 34 35566411 diskid/DISK-3EV0PWCX72500ZNJ GPT (17G) 34 35566411- free - (17G) = 34 142255508 da4 GPT (67G) 34 1422555081 freebsd-swap (67G) = 34 142255508 da5 GPT (67G) 34 1422555081 freebsd-ufs (67G) = 34 286744118 da6 GPT (136G) 34 2867441181 freebsd-ufs (136G) # Thanks Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
On Tue, 8 Oct 2013 21:32:39 -0600 (MDT) Mike Brown m...@skew.org wrote: alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. That there's no kernel changes doesn't mean that uname -a info is not updated. If you update the system from p5 to current (p12), and it shows p9 instead p12 the first thing you think is that something on the system update went wrong, not that everything was fine except the update of the file that uname -a reads. If release info patch is p12, it must update the whole system to p12. If you update an app from 2.24.1 to 2.24.2 and doing 'app -v' shows 2.24.1 it means something went wrong, not that update only modified config files and not the binary. If your sources are in /usr/src, do this: grep -v # /usr/src/sys/conf/newvers.sh | head -4 No, uname -a should give the correct answer. Has uname other utility than show information about the operating system implementation? No, and it must be accurate. --- --- Eduardo Morras emorr...@yahoo.es ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Help vote for FreeBSD
Hi, Could you guys help vote for FreeBSD over at Digital Ocean? https://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/3232571-support-bsd-os- Basically it's the only SSD cloud hosting provider (https://www.youtube.com/watch?v=vHZLCahai4Q) in existence and if the response is good enough, they'll start offering FreeBSD. Thanks! O.D. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help vote for FreeBSD
On Wed, Oct 9, 2013 at 10:11 AM, openda...@hushmail.com wrote: Hi, Could you guys help vote for FreeBSD over at Digital Ocean? https://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/3232571-support-bsd-os- Basically it's the only SSD cloud hosting provider ( https://www.youtube.com/watch?v=vHZLCahai4Q) in existence and if the response is good enough, they'll start offering FreeBSD. Thanks! uhmmm their not the only SSD cloud provider, and though its a shame they dont provide FreeBSD while others do. I do know of another with support for 8, 9, and 10 FreeBSD with SSD storage. matter of fact their whole SAN is FreeBSD based also. email me offlist for info if you like. O.D. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
Mike Brown: $ grep ^BRANCH /usr/src/sys/conf/newvers.sh BRANCH=RELEASE-p12 $ then again, I used freebsd-update and not /usr/src, but it makes sense what you said with kernel, so I guess I _AM_ on the latest -p12 and kernel is on -p9 as there was no changes after that to kernel. thank you. On Tue, Oct 8, 2013 at 11:32 PM, Mike Brown m...@skew.org wrote: alexus wrote: ok, I just did fetch install and got bumped from p5 to p9 # uname -a FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 19:47:58 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # can I take it all the way to -p12? -p10 through -p12 probably didn't involve any kernel changes. Bumping the reported patchlevel isn't considered important enough to warrant building a new kernel. If your sources are in /usr/src, do this: grep -v # /usr/src/sys/conf/newvers.sh | head -4 -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NAT: Handbook vs mailing list
On 2013-10-08 06:21, Chris Stankevitz wrote: http://www.freebsd.org/doc/handbook/network-natd.html http://lists.freebsd.org/pipermail/freebsd-questions/2011-April/229017.html Hello, Handbook section 31.9.3 suggests I should, among other things, add the line ipdivert_load=YES to /boot/loader.conf when setting up NAT. The mailing list message linked above suggests that the handbook information is the old way and that the correct way is to set ipfw_enable and natd_enable in rc.conf. Then /etc/rc.d/ipfw will load ipfw.ko, and if natd_enable is set, will invoke /etc/rc.d/natd, which loads ipdivert.ko at the right time. My inclination is to follow the handbook, but I thought I should first check to ensure the handbook is up-to-date. Thank you, This is my rc.conf with ipf (ipfilter) firewall. # Bring up the ipfilter software ipfilter_enable=YES ipmon_enable=YES # Start IP monitor log ipmon_flags=-D -f /var/log/ipf.log ## Tell ipfilter where to get its rules ipfilter_rules=/etc/ipf.rules #Enable ipnat ipnat_enable=YES #Tell ipnat where to get its rules ipnat_rules=/etc/ipnat.rules ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: install packages with pkg_add(1) into another file system
El día Tuesday, October 08, 2013 a las 03:31:16PM +0200, Matthias Apitz escribió: Meanwhile I did: # cp -Rp ~guru/PKGDIR/mnt # PKG_PATH=/PKGDIR # export PKG_PATH # chroot /mnt pkg_add xorg-7.7 # chroot /mnt pkg_add kde-4.10.5 # chroot /mnt pkg_add vim-7.3.1314 ... # chroot /mnt pkg_info | wc -l 654 which went fine without any errors (only the normal messages about creation of users, etc.); I will test the resulting image and report back. I have transferred the image with dd(1) to a 16 marketing-GByte USB key; it boots fine in my little EeePC 900, takes around 90 secs until login: and KDE4 starts fine too, takes around 240 secs from startx to be able to start an xterm application in KDE4 desktop; i.e. it works, even from such a slow USB key which has a read performance of 1 to 17 MByte per sec, depending of the blocksize 512 or 8m; All this is only a proof of concept to prepare such USB key to boot from and reinstall from it the system on my EeePC netbook whic runs at themoment r235646 with KDE3 (which is now dropped from our ports tree). It seems that KDE4 launches a lot of application or services which I will not need, for example all these akonadi_maildir processes (see attached ps -ax output; for what they are good for? Ok, this question goes more to the kde@ mailing list. Thx matthias PID TT STATTIME COMMAND 0 - DLs 0:00.05 [kernel] 1 - ILs 0:00.02 /sbin/init -- 2 - DL 0:00.00 [sctp_iterator] 3 - DL 0:00.00 [xpt_thrd] 4 - DL 0:00.11 [pagedaemon] 5 - DL 0:00.00 [vmdaemon] 6 - DL 0:00.00 [pagezero] 7 - DL 0:00.00 [bufdaemon] 8 - DL 0:00.09 [syncer] 9 - DL 0:00.00 [vnlru] 10 - DL 0:00.00 [audit] 11 - RL 2:53.86 [idle] 12 - WL 0:02.35 [intr] 13 - DL 0:00.84 [geom] 14 - DL 0:00.05 [rand_harvestq] 15 - DL 0:00.90 [usb] 16 - DL 0:00.03 [acpi_thermal] 17 - DL 0:00.00 [softdepflush] 1391 - Ss 0:00.03 /sbin/devd 1536 - Ss 0:00.04 /usr/sbin/syslogd -s 1560 - DL 0:00.04 [md0] 1641 - Is 0:00.60 /usr/sbin/moused -p /dev/psm0 -t auto 1686 - Is 0:00.00 /usr/sbin/sshd 1689 - Ss 0:00.02 sendmail: accepting connections (sendmail) 1692 - Is 0:00.00 sendmail: Queue runner@00:30:00 for /var/spool/clientmque 1696 - Ss 0:00.05 /usr/sbin/cron -s 1796 - Is 0:19.46 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-a 1802 - Is 0:00.91 kdeinit4: kdeinit4 Running... (kdeinit4) 1803 - I0:00.60 kdeinit4: kdeinit4: klauncher --fd=8 (kdeinit4) 1805 - I0:05.90 kdeinit4: kdeinit4: kded4 (kdeinit4) 1807 - I0:00.07 /usr/local/libexec/gam_server 1811 - I0:02.99 kdeinit4: kdeinit4: kglobalaccel (kdeinit4) 1817 - I0:06.23 /usr/local/kde4/bin/knotify4 1819 - I0:02.45 kdeinit4: kdeinit4: ksmserver (kdeinit4) 1820 - I0:11.72 kwin -session 10d6114d4e60001381347192001812_1381 1824 - I0:14.72 kdeinit4: kdeinit4: plasma-desktop (kdeinit4) 1827 - I0:20.26 /usr/local/kde4/bin/akonadi_control 1828 - I0:02.79 akonadiserver 1830 - I0:03.56 /usr/local/libexec/mysqld --defaults-file=/home/guru/.loc 1838 - I0:02.07 /usr/local/kde4/bin/kuiserver 1840 - I0:00.08 kdeinit4: kdeinit4: nepomukserver (kdeinit4) 1843 - I0:04.73 kdeinit4: kdeinit4: krunner (kdeinit4) 1845 - I0:02.35 kdeinit4: kdeinit4: kmix -session 10d6114d4e6000138134736 1846 - IN 0:00.93 /usr/local/kde4/bin/nepomukservicestub nepomukstorage 1849 - I0:00.60 /usr/local/kde4/bin/nepomukcontroller -session 10d6114d4e 1852 - I0:01.04 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1853 - I0:01.07 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1854 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1855 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_akonot 1856 - I0:03.81 /usr/local/kde4/bin/akonadi_archivemail_agent --identifie 1857 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_ical_r 1858 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1859 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1860 - I0:01.12 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1861 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1862 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1863 - I0:01.10 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1864 - I0:01.06 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1865 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1866 - I0:01.02 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1867 - I0:01.03 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1868 - I0:01.01 /usr/local/kde4/bin/akonadi_agent_launcher akonadi_maildi 1869 - I0:01.02
Upgrade 9.1 - 9.2
I used 'freebsd-update upgrade -r 9.2-RELEASE' to upgrade a test system. All went well, until the point at which it said: Kernel updates have been installed. Please reboot and run /usr/sbin/freebsd-update install again to finish installing updates. Stupidly, I did NOT reboot, but started the /usr/sbin/freebsd-update install without rebooting first. As soon as I realised my mistake (a few minutes later), I issued ctrl-c to exit, rebooted and ran /usr/sbin/freebsd-update install again. It appeared to finish successfuly. Have I screwed up my system, or am I OK? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mounting a .iso image? ... missing man page
For some strange reason, my 9.1 system seems to be missing the section 1 man page for tar, although everything else seems to be there. I have an iso9660 image of 9.1 release which I tried to mount to copy the missing file, but that didn't work (can't find the CD I burned...). #mount -t cd9660 -o ro FreeBSD-9.1-RELEASE-amd64-disc1.iso /mnt/tmp mount_cd9660: /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso: Block device required Seems like it must be possible to mount a cd9660 image somehow without burning an actual disc? Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mounting a .iso image? ... missing man page
On 10/09/2013 10:14 pm, Gary Aitken wrote: For some strange reason, my 9.1 system seems to be missing the section 1 man page for tar, although everything else seems to be there. I have an iso9660 image of 9.1 release which I tried to mount to copy the missing file, but that didn't work (can't find the CD I burned...). #mount -t cd9660 -o ro FreeBSD-9.1-RELEASE-amd64-disc1.iso /mnt/tmp mount_cd9660: /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso: Block device required Seems like it must be possible to mount a cd9660 image somehow without burning an actual disc? Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org mdconfig -a -t vnode -f /path/to/file.iso this will create a /dev/md# where # starts at 0 for first one mount it with mount -t cd9660 -o ro /dev/md# /mnt -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mounting a .iso image? ... missing man page
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote: Seems like it must be possible to mount a cd9660 image somehow without burning an actual disc? Of course. :-) It is possible by using a virtual node connected to the ISO file. Without having tested, according to your example: # mdconfig -u 0 -t vnode -f /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso # mount -o ro -t cd9660 /dev/md0 /mnt/tmp ... do stuff ... # umount /mnt/tmp # mdconfig -u 0 -d An alternative would be to use tar to extract the files from the image, change whatever you want, and use mkisofs afterwards to rebuild the (new) image, in case you want to modify its content. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mounting a .iso image? ... missing man page
On 10/09/13 21:25, Polytropon wrote: On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote: Seems like it must be possible to mount a cd9660 image somehow without burning an actual disc? Of course. :-) I guess knowing it's possible is a start; couldn't figure out where to look to get the magic combination. It is possible by using a virtual node connected to the ISO file. Without having tested, according to your example: # mdconfig -u 0 -t vnode -f /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso for the record, that's: mdconfig -a -t vnode -u 0 -f file # mount -o ro -t cd9660 /dev/md0 /mnt/tmp ... do stuff ... # umount /mnt/tmp # mdconfig -u 0 -d and that one is mdconfig -d -u 0 order appears to be important Thanks again, Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
Eduardo Morras wrote: [...] uname -a should give the correct answer. Has uname other utility than show information about the operating system implementation? No, and it must be accurate. That's what I thought, but when I asked about it here last year, I was told that this is the way things are; our expectations of uname are at fault. I believe if he were to compile his own kernel, it would say -p12. Suggestions were made for how to deal with it, but I don't know if they were ever followed up on. They wouldn't affect 7.x in any case. Start reading the thread here: http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/240666.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mounting a .iso image? ... missing man page
On Wed, 09 Oct 2013 22:18:41 -0600, Gary Aitken wrote: for the record, that's: mdconfig -a -t vnode -u 0 -f file Correct, I noticed too late that -a was missing. But man mdconfig mentions all parts that are needed. :-) # mount -o ro -t cd9660 /dev/md0 /mnt/tmp ... do stuff ... # umount /mnt/tmp # mdconfig -u 0 -d and that one is mdconfig -d -u 0 order appears to be important The manpage doesn't seem to explicitely mention this, but if I remember correctly, it actually matters, as you said. By the way, the manpage mentions mount -t cd9660 /dev/`mdconfig -f cdimage.iso` /mnt as an interesting construction in the EXAMPLES section. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mounting a .iso image? ... missing man page
Gary Aitken wrote:
On 10/09/13 21:25, Polytropon wrote:
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
Seems like it must be possible to mount a cd9660 image somehow without
burning an actual disc?
Of course. :-)
I guess knowing it's possible is a start;
couldn't figure out where to look to get the magic combination.
It is possible by using a virtual node connected to the
ISO file. Without having tested, according to your example:
# mdconfig -u 0 -t vnode -f
/hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso
for the record, that's:
mdconfig -a -t vnode -u 0 -f file
# mount -o ro -t cd9660 /dev/md0 /mnt/tmp
... do stuff ...
# umount /mnt/tmp
# mdconfig -u 0 -d
and that one is
mdconfig -d -u 0
order appears to be important
Thanks again,
Gary
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
To avoid having to recall the arguments for mdconfig(8):
#/bin/sh
#start_isofs
#two commands to attach and mount or umount file.iso
#
isofs_stop() {
(umount -f /mnt
mdconfig -d -u $NUM)
}
NUM=3
DEV=/dev/md${NUM}
IMGFS=$1
case $2 in
start)
# first check whether target mount point is in use
if mount | grep -q /mnt; then
printf Exiting: mount point '/mnt' currently unavailable.\n
exit 1
fi
(mdconfig -a -t vnode -f $IMGFS -u $NUM
mount -o ro -t cd9660 $DEV /mnt) ;;
stop)
isofs_stop ;;
*)
if [ $IMGFS = stop ]; then
isofs_stop
else
your_script=$(basename $0)
printf Usage: %s [isofile] start|stop\n $your_script
fi
;;
esac
exit
--
c...@sdf.org
SDF Public Access UNIX System - http://sdf.org
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help vote for FreeBSD
Keep them coming guys! Couple hundred more and FreeBSD will top the list: https://digitalocean.uservoice.com/forums/136585-digital-ocean/filters/top This would be great PR for FreeBSD too. Thank you! On 9. oktober 2013 at 2:11 PM, openda...@hushmail.com wrote: Hi, Could you guys help vote for FreeBSD over at Digital Ocean? https://digitalocean.uservoice.com/forums/136585-digital- ocean/suggestions/3232571-support-bsd-os- Basically it's the only SSD cloud hosting provider (https://www.youtube.com/watch?v=vHZLCahai4Q) in existence and if the response is good enough, they'll start offering FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
