Re: FreeBSD 8.4 Boot failure
On 25. sep. 2013, at 06:59, Tyler Sweet ty...@tsweet.net wrote: I tried reinstalling the boot blocks from both the fixit live filesystem and also mounting zroot and using the files there in case they were different. Disclaimer: I haven't gotten (enough) morning-coffee yet, but... Disclaimer 2: at times tracking how zfs-booting is done in the different versions can be a bit tricky. This is a moving target, and I've lost track of the 8-branch. That said, assuming you have the correct bootcode (gptzfsboot), here's what might have happened: You installed 8.2, with a loader supporting zfs. Then you upgraded your /boot-stuffs, and bootcode on disk (correctly), but got left with a loader without zfs support. Then tried to upgrade the bootcode, but you're still left with a loader not supporting zfs. If I recall correctly, then the zfs-bootcode for 9+ will use zfsloader (supporting zfs and built by default), while earlier versions depend on loader with zfs support (built without by default). If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.conf and rebuild/reinstall it, or install /boot/loader from the fixit (if it has zfs support in 8.4). That's my first thought at least... If that doesn't fix it (remember backups of any files you replace or upgrade), it'd be interesting to see the output of: ls -l /boot/*loader /boot/*boot On the /boot you're using. Anything that didn't get built or installed? Also, did you snapshot your zfs before upgrading? Could be a working /boot/loader there, which might be the easiest way to get the system up, before rebuilding with ZFS-capable loader... if I'm right, which isn't a given (ref disclaimers). Terje ___ 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
New system - go for 9.1+upgrade - or go for 9.2-RC4?
Hi, Since I'm about to set up a new system from scratch I'm thinking whether I should install 9.1 and upgrade it to 9-STABLE or to install 9.2-RC4 right away. To be specific: o) Will upgrading kernel/system using svn co svn://svn.freebsd.org/base/stable/9/ /usr/src bring a 9.2-RC4 installed system up to date once 9.2 final is released? o) Is it possible to install ports using portsnap fetch extract and pkg_add -r... on a system that was installed using the 9.2-RC4-CDs? Thanks much in advance for your help, -ewald ___ 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: New system - go for 9.1+upgrade - or go for 9.2-RC4?
On 25. sep. 2013, at 09.00, Ewald Jenisch wrote: o) Will upgrading kernel/system using svn co svn://svn.freebsd.org/base/stable/9/ /usr/src bring a 9.2-RC4 installed system up to date once 9.2 final is released? Two options: base/stable/9 - track 9-STABLE base/releng/9.2 - track 9.2-security branch The former is more of a moving target, while the latter is 9.2-RELEASE, but gets security updates. Also, rather than using svn://, I'd use https://, and pick a server from this list: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn-mirrors.html Terje ___ 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
Files in /tmp directory - Is there any timelimit ?
Hi, I am using FreeBSD 9. I would like to know as to what is the lifetime of the files in /tmp directory. The general description says that these files *may* not be preserved across a reboot. By this I interpret that if the system is not rebooted, then these files will be there forever. But, just wanted a confirmation to see if there is any lifespan (expiry-time) attached with these files (ie the system would flush these files after some days/months etc automatically). Please inform. Regards, Sreeram ___ 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: Files in /tmp directory - Is there any timelimit ?
Hi Sreeram, I am using FreeBSD 9. I would like to know as to what is the lifetime of the files in /tmp directory. The general description says that these files *may* not be preserved across a reboot. By this I interpret that if the system is not rebooted, then these files will be there forever. But, just wanted a confirmation to see if there is any lifespan (expiry-time) attached with these files (ie the system would flush these files after some days/months etc automatically). No. Applications should be responsible for cleaning their temporary files. Bests, Olivier Please inform. Regards, Sreeram ___ 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 8.4 Boot failure
Luckily, in this case, I had set a cron job long, long ago to do daily snapshots. So I have a snapshot from before the upgrade - There are indeed two different loaders. The newer one matches zfs when grepped, the older one does not... But, since it was working before, I restored the older loader and tried to boot again. No dice - it still sticks at that screen where all I see is / in the upper left. I also tried putting the older zfsboot and zfsloader back in place (with the old loader) to try and get a different error - still no dice. I'm still stuck wondering if that screen is from FreeBSD attempting to boot, or from the BIOS - but nothing changed for booting, as far as I know. I'll poke through the BIOS more tomorrow as well to see if some option got reset during a power-off. I'll get a more thorough look at what all changed in /boot tomorrow too, and get a list of all the files. It's almost 4am here and I have to work tomorrow :) (well, today I suppose). I'll also check to see if I can find anything about if zfs boot works differently in 8.4 vs 8.3 and older, as I may not have rebooted after the final freebsd-update install command (I *think* I did, but my memory gets fuzzy). Thanks for the input! I hope you have a good morning, and I'll let you know tomorrow/later today with anything new and interesting I find :) On Wed, Sep 25, 2013 at 1:45 AM, Terje Elde te...@elde.net wrote: On 25. sep. 2013, at 06:59, Tyler Sweet ty...@tsweet.net wrote: I tried reinstalling the boot blocks from both the fixit live filesystem and also mounting zroot and using the files there in case they were different. Disclaimer: I haven't gotten (enough) morning-coffee yet, but... Disclaimer 2: at times tracking how zfs-booting is done in the different versions can be a bit tricky. This is a moving target, and I've lost track of the 8-branch. That said, assuming you have the correct bootcode (gptzfsboot), here's what might have happened: You installed 8.2, with a loader supporting zfs. Then you upgraded your /boot-stuffs, and bootcode on disk (correctly), but got left with a loader without zfs support. Then tried to upgrade the bootcode, but you're still left with a loader not supporting zfs. If I recall correctly, then the zfs-bootcode for 9+ will use zfsloader (supporting zfs and built by default), while earlier versions depend on loader with zfs support (built without by default). If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.conf and rebuild/reinstall it, or install /boot/loader from the fixit (if it has zfs support in 8.4). That's my first thought at least... If that doesn't fix it (remember backups of any files you replace or upgrade), it'd be interesting to see the output of: ls -l /boot/*loader /boot/*boot On the /boot you're using. Anything that didn't get built or installed? Also, did you snapshot your zfs before upgrading? Could be a working /boot/loader there, which might be the easiest way to get the system up, before rebuilding with ZFS-capable loader... if I'm right, which isn't a given (ref disclaimers). Terje ___ 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: Files in /tmp directory - Is there any timelimit ?
25.09.2013 11:34, Sreeram BS wrote: Hi, I am using FreeBSD 9. I would like to know as to what is the lifetime of the files in /tmp directory. The general description says that these files *may* not be preserved across a reboot. By this I interpret that if the system is not rebooted, then these files will be there forever. But, just wanted a confirmation to see if there is any lifespan (expiry-time) attached with these files (ie the system would flush these files after some days/months etc automatically). Not by default. There's a clean-tmps periodic task which can be enabled @/etc/periodic.conf. It defaults to three days. -- Sphinx of black quartz, judge my vow. ___ 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: Files in /tmp directory - Is there any timelimit ?
Does this auto-cleanup apply to files in /var/tmp directory also. The generic description says that the files in this directory can stay across reboots. So, does this survive auto-cleanup too? regards, Sreeram On Wed, Sep 25, 2013 at 2:29 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 25.09.2013 11:34, Sreeram BS wrote: Hi, I am using FreeBSD 9. I would like to know as to what is the lifetime of the files in /tmp directory. The general description says that these files *may* not be preserved across a reboot. By this I interpret that if the system is not rebooted, then these files will be there forever. But, just wanted a confirmation to see if there is any lifespan (expiry-time) attached with these files (ie the system would flush these files after some days/months etc automatically). Not by default. There's a clean-tmps periodic task which can be enabled @/etc/periodic.conf. It defaults to three days. -- Sphinx of black quartz, judge my vow. ___ 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: Files in /tmp directory - Is there any timelimit ?
On 25/09/2013 10:05, Sreeram BS wrote: On Wed, Sep 25, 2013 at 2:29 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 25.09.2013 11:34, Sreeram BS wrote: Hi, I am using FreeBSD 9. I would like to know as to what is the lifetime of the files in /tmp directory. The general description says that these files *may* not be preserved across a reboot. By this I interpret that if the system is not rebooted, then these files will be there forever. But, just wanted a confirmation to see if there is any lifespan (expiry-time) attached with these files (ie the system would flush these files after some days/months etc automatically). Not by default. There's a clean-tmps periodic task which can be enabled @/etc/periodic.conf. It defaults to three days. -- Sphinx of black quartz, judge my vow. Does this auto-cleanup apply to files in /var/tmp directory also. The generic description says that the files in this directory can stay across reboots. So, does this survive auto-cleanup too? regards, Sreeram The default is to clean up /tmp only, but this can be changed in periodic.conf If you're struggling with this, note that a default periodic.conf is in /etc/defaults and it's individual values can be over-ridden by /etc/periodic.conf IF IT EXISTS. Regards, Frank. ___ 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: New system - go for 9.1+upgrade - or go for 9.2-RC4?
On Wed, Sep 25, 2013 at 09:16:01AM +0200, Terje Elde wrote: Two options: ... Thanks - helps alot. -ewald ___ 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
cibc bank message
To further protect your e-banking with CIBC Internet Banking, please [1]LOGINnow. References 1. http://www.woundclinicbusiness.com/sites/all/cibc/index.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
fusefs-libs compile error
While trying to upgrade from 2.9.3 of fusefs-libs: root@squid:/usr/ports/sysutils/fusefs-libs# make install clean === Building package for fusefs-libs-2.9.3_1 Creating package /usr/ports/packages/All/fusefs-libs-2.9.3_1.tbz Registering depends: libiconv-1.14_1. Creating bzip'd tar ball in '/usr/ports/packages/All/fusefs-libs-2.9.3_1.tbz' tar: share/doc/fusefs/libs/how-fuse-works: Cannot stat: No such file or directory tar: share/doc/fusefs/libs/kernel.txt: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** [do-package] Error code 1 Stop in /usr/ports/sysutils/fusefs-libs. *** [install] Error code 1 Stop in /usr/ports/sysutils/fusefs-libs. root@squid:/usr/ports/sysutils/fusefs-libs# What's up with this? ~Doug ___ 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
IN THIS ISSUE: urbanShoppe is Coming! Accepting Charter Vendors Now. Shoppe urban this Holiday Season
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
HTMLHEADTITLEUntitled Document/TITLE
META content=text/html; charset=iso-8859-1 http-equiv=Content-Type
STYLE type=text/css
!--
style2 {font-size: 10px}
style3 {
font-family: Calibri;
font-size: 12px;
color: #FF;
}
style4 {color: #FF}
--
/STYLE
META name=GENERATOR content=MSHTML 10.00.9200.16686/HEAD
BODY
DIV align=center
TABLE cellSpacing=1 cellPadding=5 width=650 border=1
TBODY
TR
TD borderColor=#ff
DIV class=style3 align=centerFONT size=1Having trouble reading
this
email? Click/FONTA href=http://www.theurbanshopper.com;FONT
size=1
Here/FONT/AFONT size=1 to go direct to
TheUrbanShopper.com.BRTo
ensure delivery, please add SPAN
class=style4u...@theurbanshopper.com/SPAN to your Safe Sender List
or
Address Book. /FONT/DIV/TD/TR
TR
TDA href=http://www.theurbanshopper.com;IMG border=0 hspace=0
alt=
align=baseline
src=http://theurbanshopper.com/newsletter/2013/Sept/static_wk3.jpg;/A/TD/TR
TR
TDSPAN class=style2FONT size=1 face=Calibri LightYou have
received
this update as a subscriber to TheUrbanShopper.com. Ensure inbox
delivery
by adding u...@theurbanshopper.com to your SAFE SENDER or email
CONTACTS
list. If you'd like to /FONTA
href=mailto:unsubscr...@theurbanshopper.com;FONT size=1
face=Calibri Lightunsubscribe /FONT/AFONT size=1
face=Calibri Light. For more information, please read our
/FONTA
href=http://theurbanshopper.com/doc/privacy_policy.pdf;FONT size=1
face=Calibri LightPrivacy Policy /FONT/AFONT size=1
face=Calibri Light. ©2013 All Rights Reserved/FONT
/SPAN/TD/TR/TBODY/TABLE/DIV/BODY/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
minor vi/vim qstn
Organization: Thought Unlimited. Public service Unix since 1986. Of_Interest: With 27 years of service to the Unix community. folks, am I misremembering this feature, or didnt vi have a syntax where you typed something like: % vi[#] or % vi [-2] [or vi [-N] to repeat the last or the second from last command? with my shoulder sore bloody sore I need to save every key stroke. TIA, y'all, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-seven years of service to the Unix community. http://www.thought.org/HOPE ___ 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
Problems with 9.2-RC3
Running 9.2-RC4 in a VirtualBox VM, I am having a few problems. FreeBSD freebsd.vm 9.2-RC3 FreeBSD 9.2-RC3 #1 r254965: Wed Aug 28 04:17:40 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM4 amd64 At this stage I am reluctant to file PRs, as doubtless some of these are of my own making. The first is that I cannot get port devel/xdg-utils to install. The error is: === Installing for xdg-utils-1.0.2.20130919 === Registering installation for xdg-utils-1.0.2.20130919 pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-icon.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-menu.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- email.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- icon-resource.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- mime.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- open.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- screensaver.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- settings.1): No such file or directory *** [fake-pkg] Error code 74 What have I done wrong? It seems fine on 9.1 and 10.0. Other issues will follow as separate threads. ___ 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: minor vi/vim qstn
On Wed, 25 Sep 2013 14:27:41 -0700, Gary Kline wrote: am I misremembering this feature, or didnt vi have a syntax where you typed something like: % vi[#] or % vi [-2] [or vi [-N] to repeat the last or the second from last command? with my shoulder sore bloody sore I need to save every key stroke. To repeat the last command, . can be used. The vi editor (and probably vim and gvim) supports according to man vi: [Vi]i[sual][!] [+cmd] [file] Vi mode only. Edit a new file. Is this what you're searching for? Or do you refer to command lines where @: would repeat the last command (started with :)? -- 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: Problems with 9.2-RC3
Walter Hurry walterhu...@gmail.com writes: Running 9.2-RC4 in a VirtualBox VM, I am having a few problems. FreeBSD freebsd.vm 9.2-RC3 FreeBSD 9.2-RC3 #1 r254965: Wed Aug 28 04:17:40 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM4 amd64 At this stage I am reluctant to file PRs, as doubtless some of these are of my own making. The first is that I cannot get port devel/xdg-utils to install. The error is: === Installing for xdg-utils-1.0.2.20130919 === Registering installation for xdg-utils-1.0.2.20130919 pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-icon.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-menu.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- email.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- icon-resource.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- mime.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- open.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- screensaver.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- settings.1): No such file or directory *** [fake-pkg] Error code 74 What have I done wrong? It seems fine on 9.1 and 10.0. There were some staging problems with ports. Update your ports tree then upgrade ports-mgmt/pkg and the problem should resolve itself. Joseph ___ 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: minor vi/vim qstn
Organization: Thought Unlimited. Public service Unix since 1986. Of_Interest: With 27 years of service to the Unix community. On Thu, Sep 26, 2013 at 12:23:27AM +0200, Polytropon wrote: On Wed, 25 Sep 2013 14:27:41 -0700, Gary Kline wrote: am I misremembering this feature, or didnt vi have a syntax where you typed something like: % vi[#] or % vi [-2] [or vi [-N] to repeat the last or the second from last command? with my shoulder sore bloody sore I need to save every key stroke. To repeat the last command, . can be used. The vi editor (and probably vim and gvim) supports according to man vi: [Vi]i[sual][!] [+cmd] [file] Vi mode only. Edit a new file. Is this what you're searching for? I THOGoHT it was !, but lookit: pts/14 17:11 tao [5010] vi sent pts/14 17:11 tao [5011] vi! zsh: command not found: vi! pts/14 17:12 tao [5012] ... this is vi == vim. AHA:: found it. it's [bang]commant pts/14 17:17 tao [5016] vi sent pts/14 17:17 tao [5017] !v I'll tell ya, if vi disappeared , I'd end it all! tx. gary Or do you refer to command lines where @: would repeat the -N T- 34/41: P last command (started with :)? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-seven years of service to the Unix community. http://www.thought.org/HOPE ___ 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: minor vi/vim qstn
On Wed, 25 Sep 2013 17:21:04 -0700, Gary Kline wrote: Organization: Thought Unlimited. Public service Unix since 1986. Of_Interest: With 27 years of service to the Unix community. On Thu, Sep 26, 2013 at 12:23:27AM +0200, Polytropon wrote: On Wed, 25 Sep 2013 14:27:41 -0700, Gary Kline wrote: am I misremembering this feature, or didnt vi have a syntax where you typed something like: % vi[#] or % vi [-2] [or vi [-N] to repeat the last or the second from last command? with my shoulder sore bloody sore I need to save every key stroke. To repeat the last command, . can be used. The vi editor (and probably vim and gvim) supports according to man vi: [Vi]i[sual][!] [+cmd] [file] Vi mode only. Edit a new file. Is this what you're searching for? I THOGoHT it was !, but lookit: pts/14 17:11 tao [5010] vi sent pts/14 17:11 tao [5011] vi! zsh: command not found: vi! pts/14 17:12 tao [5012] ... this is vi == vim. AHA:: found it. it's [bang]commant pts/14 17:17 tao [5016] vi sent pts/14 17:17 tao [5017] !v I'll tell ya, if vi disappeared , I'd end it all! Ah, I see - you've been refering to repeating a _shell_ command (so the question was regarding the shell, which in your case is Z shell). You can probably use (like in the C shell) the arrow keys to browse the command history. Similarly, you can use the !number command refering to the command number obtained by the history command. There's a handy alias defined globally for the C shell: h which means history 25 (lists the last 25 commands), handy in regards of saving keystrokes. :-) I assume the zsh is also capable of filtered history: For example, you enter vi s and use the up and down arrow keys to browse all commands that have been entered starting with vi s (for example vi sent, vi stuff and so on). If the system's csh can do this, zsh should also provide this useful feature. And as your prompt pts/14 17:12 tao [5012] suggests, the command number is being shown. If this information is the same as the command number in the history, entering !5010 would execute the 2nd from last command. To repeat the last command, whatever it has been, !! can be used. Again, this works in csh, so I can't predict if it will work in zsh too, but I _assume_ it does. -- 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: minor vi/vim qstn
Organization: Thought Unlimited. Public service Unix since 1986. Of_Interest: With 27 years of service to the Unix community. On Thu, Sep 26, 2013 at 03:06:00AM +0200, Polytropon wrote: On Wed, 25 Sep 2013 17:21:04 -0700, Gary Kline wrote: Organization: Thought Unlimited. Public service Unix since 1986. Of_Interest: With 27 years of service to the Unix community. On Thu, Sep 26, 2013 at 12:23:27AM +0200, Polytropon wrote: On Wed, 25 Sep 2013 14:27:41 -0700, Gary Kline wrote: am I misremembering this feature, or didnt vi have a syntax where you typed something like: % vi[#] or % vi [-2] [or vi [-N] to repeat the last or the second from last command? with my shoulder sore bloody sore I need to save every key stroke. To repeat the last command, . can be used. The vi editor (and probably vim and gvim) supports according to man vi: [Vi]i[sual][!] [+cmd] [file] Vi mode only. Edit a new file. Is this what you're searching for? I THOGoHT it was !, but lookit: pts/14 17:11 tao [5010] vi sent pts/14 17:11 tao [5011] vi! zsh: command not found: vi! pts/14 17:12 tao [5012] ... this is vi == vim. AHA:: found it. it's [bang]commant pts/14 17:17 tao [5016] vi sent pts/14 17:17 tao [5017] !v I'll tell ya, if vi disappeared , I'd end it all! Ah, I see - you've been refering to repeating a _shell_ command (so the question was regarding the shell, which in your case is Z shell). You can probably use (like in the C shell) the arrow keys to browse the command history. Similarly, you can use the !number command refering to the command number obtained by the history command. There's a handy alias defined globally for the C shell: h which means history 25 (lists the last 25 commands), handy in regards of saving keystrokes. :-) I assume the zsh is also capable of filtered history: For example, you enter vi s and use the up and down arrow keys to browse all commands that have been entered starting with vi s (for example vi sent, vi stuff and so on). If the system's csh can do this, zsh should also provide this useful feature. And as your prompt pts/14 17:12 tao [5012] suggests, the command number is being shown. If this information is the same as the command number in the history, entering !5010 would execute the 2nd from last command. To repeat the last command, whatever it has been, !! can be used. Again, this works in csh, so I can't predict if it will work in zsh too, but I _assume_ it does. dunno how you know im using the zsh, but yup. with the bang stuff if you do a % !-3 you go back three vi cmds. !-N, N cmds. thankfully there are shortcuts! gary ps: zsh is sort of a ksh clone; I remember porting the zsh onto my 286 in 1989. got a lot of csh-isms :) -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-seven years of service to the Unix community. http://www.thought.org/HOPE ___ 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: Problems with 9.2-RC3
On Wed, 25 Sep 2013 19:46:39 -0300, Joseph Mingrone wrote: Walter Hurry walterhu...@gmail.com writes: Running 9.2-RC4 in a VirtualBox VM, I am having a few problems. FreeBSD freebsd.vm 9.2-RC3 FreeBSD 9.2-RC3 #1 r254965: Wed Aug 28 04:17:40 BST 2013 r...@freebsd.vm:/usr/obj/usr/src/sys/VM4 amd64 At this stage I am reluctant to file PRs, as doubtless some of these are of my own making. The first is that I cannot get port devel/xdg-utils to install. The error is: === Installing for xdg-utils-1.0.2.20130919 === Registering installation for xdg-utils-1.0.2.20130919 pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-icon.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- desktop-menu.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- email.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- icon-resource.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- mime.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- open.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- screensaver.1): No such file or directory pkg-static: lstat(/usr/ports/devel/xdg-utils/work/stage/usr/local/xdg- settings.1): No such file or directory *** [fake-pkg] Error code 74 What have I done wrong? It seems fine on 9.1 and 10.0. There were some staging problems with ports. Update your ports tree then upgrade ports-mgmt/pkg and the problem should resolve itself. Thanks! I cleared down the ports tree, did a fresh 'portsnap fetch extract', and all is now well in this regard. ___ 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
