What are you trying to do? Both exec and the $1 are probably not going to do what was intended.
Let's instead call the variable $x so the shell does not replace it, and not use exec, which does not just execute the command given but replaces the running shell with it.
echo `$x` >> .xinitrc...
It works in the TTY...so where does it not work? In x11/xfce4-terminal, there is an option to set which character is generated when backspace is pressed. I have that set to Ctrl-H.
In .cshrc, I have these, which ought to be neatened and organized better:
# bindkey "^?" delete-char
bindkey...
I don't have any idea what you mean by this. Some people have trouble with backspace and delete, but it's easy enough to configure in the shell startup. Set once, never touch again.
Ah, I remember the old "pirate" option: -arR.
That is currently a loaded question. I use ports-mgmt/portmaster, which, according to some, is the most evil thing possible. Yet it still works. Other people use binary packages from the FreeBSD package repository with pkg, and that can be...
1. Yes, there is only one database, everything is a package by the time it gets installed on your system.
2. portsdb is part of portupgrade (or was). I thought it didn't use that any more. It is not a native part of the package system.
3. Duplicated origins means you are doing something wrong...
I never use these, but they are defined in my setup and worked just now when I tried them:
bindkey "\e[1;5D" vi-word-back
bindkey "\e[1;5C" vi-word-fwd
Rather than think of a bad block on the drive, think of a bug in the exfat driver, which is after all a reimplementation of a reverse-engineered proprietary filesystem. I would suggest using a non-proprietary filesystem. Which one you choose depends on which platforms need access to it...
Some responses to that, from FreeNAS-land:
1. Do not add L2ARC until you have maxed out RAM.
2. SLOG is only useful for specific use cases, and to do it right requires a special dedicated SSD. See http://doc.freenas.org/9.10/zfsprimer.html, the section starting with ZFS provides a write cache.
Thread closed. Some of these posts are relevant and insightful. Others, not as much. Please remember that, at minimum, forum participants are expected to stay polite and on-topic.
No. ISO files are not memory stick files. The widespread use of hybrid ones by Linux have people thinking they are the same thing, but that is not true.
The easiest way to make a UEFI bootable image would be to boot mfsBSD or the FreeBSD 11 install image and use shell tools available there.
I'm sorry, I approved the first post while attempting to multitask and doing it poorly. How about we move this thread to one of the more general categories? As far as content, there are always new users encountering the same problems, the forums are here to help support them also.
The thing with a VM is that the hardware isn't real. There can be bugs in the emulation. Or you might have the emulated disk set to accept writes and write them in memory, but never actually commit them to disk. So the state of the disk reverts when the VM restarts. Or there might be a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
