Gabor PALI p...@freebsd.org writes:
Sorry for chiming in, just a quick idea. If you find the get a
high-level language that compiled to C idea good,
I don't think it's a good idea, and I don't understand why this thread
seems stuck in that rut.
DES
--
Dag-Erling Smørgrav - d...@des.no
b. f. bf1...@googlemail.com writes:
At r211506, 'grep -wq' does not seem to work properly (in the very
least, it is not the same as with GNU grep),
Does not seem to work properly is not a very useful statement. The
least you could do is provide an example.
DES
--
Dag-Erling Smørgrav - d
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
the bits that
are most commonly used in embedded devices (Linux itself and busybox)
are still under GPLv2.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
a commercial license for us.
Does that really matter? We're not going to start building releases
with icc, are we?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
actually running the
profiling tools which pointed to the buffering as the number one thing
to fix.
There is a lesson here: people who are unsatisfied with the performance
of ${TOOL} should profile it before they start a flamefest on -current.
DES
--
Dag-Erling Smørgrav - d...@des.no
to this particular case I think
it's pretty obvious that I'm either alone, or in a very non-vocal
group; so c'est la vie.
This is madness!
Madness? This... is... CURRENT!
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
years of experience in this project, you are very, very
wrong.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd
V. T. Mueller, Continum v.t.muel...@continum.net writes:
Dag-Erling Smørgrav d...@des.no writes:
Based on my 12 years of experience in this project, you are very,
very wrong.
An 'argumentation' like the above is simply a killer phrase that ends
every discussion.
An 'argumentation' like
+464: callq 0x40176c memchr
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
on
amd64, where ${CC} has a bunch of flags (including -isystem, -L and -B)
appended.
No, what is used is a variant of method 1 *on top of* method 2 for a
very specific case. You need a special version of clang (method 2)
anyway to support cross-building.
DES
--
Dag-Erling Smørgrav - d...@des.no
Dimitry Andric dimi...@andric.com writes:
Dag-Erling Smørgrav d...@des.no writes:
No, what is used is a variant of method 1 *on top of* method 2 for a
very specific case. You need a special version of clang (method 2)
anyway to support cross-building.
Eventually, clang should support
regular file, try to mmap(2) it first, and if
that fails, fall back to the plain buffered read(2) method.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
language, but as an embeddable scripting engine. We could easily create
our own scripting language based on lua with FreeBSD-specific functions,
and there would be no fear of interfering with third-party software,
because it wouldn't be called lua.
DES
--
Dag-Erling Smørgrav - d...@des.no
Sean C. Farley s...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Did you actually test your patch? It makes absolutely no measurable
difference.
Yes, I saw a reduction,
I didn't...
DES
--
Dag-Erling Smørgrav - d...@des.no
Sean C. Farley s...@freebsd.org writes:
This should trim some time off BSD grep.
Did you actually test your patch? It makes absolutely no measurable
difference.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
for ages).
As you would know if you had followed the discussion about WD EARS
disks, gnop does what you want and is currently the recommended
solution.
I am looking into a permanent solution and would appreciate if people
held off on this for a couple of weeks.
DES
--
Dag-Erling Smørgrav - d
Ivan Voras ivo...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Marius Nünnerich mar...@nuenneri.ch writes:
I did not think of a new GEOM class that looks like glabel but one
that has no metadata stored on disk . It is then activated and
controlled by loader.conf
-legacy
Syntax error: end of file unexpected (expecting ))
*** Error code 2
Stop in /src/games/fortune/strfile.
Does anyone have any idea what caused this? The exact same error
occurred on all platforms / architectures.
DES
--
Dag-Erling Smørgrav - d...@des.no
.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
?
Only for legacy drives, but since Micahel's panic message contains
current process = 12 (irq15: ata1), his BIOS is probably in legacy
mode.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
Dag-Erling Smørgrav d...@des.no writes:
Andriy Gapon a...@icyb.net.ua writes:
Michael Butler i...@protected-networks.net writes:
I have a custom kernel for my laptop which uses ATA_CAM rather than
the now aging ATA driver ..
You do realize that ATA_CAM just (well, mostly) introduces
grep.
Ok, thanks, then I'll just document it.
Uh, no. GNU grep's behavior is consistent with just about everything
else that has --include / --exclude options, e.g. tar and rsync. Please
change BSD grep's behavior to match GNU grep's.
DES
--
Dag-Erling Smørgrav - d...@des.no
YAMAMOTO Shigeru shig...@iij.ad.jp writes:
'advertise' is added at r209607 and r209609.
please chone one of them.
I don't know what chone means.
The tinderbox uses cvsup and is therefore at the mercy of the whims and
idiosyncracies of the cvs exporter.
DES
--
Dag-Erling Smørgrav - d
the same bug would affect fetching from servers requiring
authentication, so I've made the same fix there as well.
OK, I'll trust your analysis and commit this do head, then ask portmgr
to do an exp run with the patch.
DES
--
Dag-Erling Smørgrav - d...@des.no
of it :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
, since the only resource held by the
pidfile that would persist across execve() is the file descriptor (and
hence the lock).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
buildenv
% env
and also show us your make.conf and src.conf?
Do you have any gcc ports installed?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
Dag-Erling Smørgrav d...@des.no writes:
This confirms my suspicion that ld is picking up the wrong liblzma:
attempt to open /usr/local/lib/liblzma.a succeeded
but I still can't figure out why.
Uh, I must be blind. It uses /usr/local/lib/liblzma.a because
-L/usr/local/lib was specified
Anton Shterenlikht me...@bristol.ac.uk writes:
# make buildenv
Entering world for ia64:ia64
# env
LIBRARY_PATH=/usr/local/lib
where does this come from? Your .bashrc or something?
% make buildenv
% unset LIBRARY_PATH
then run the cc command again.
DES
--
Dag-Erling Smørgrav - d...@des.no
Anton Shterenlikht me...@bristol.ac.uk writes:
However, I've got this set on 3 ia64 boxes.
On two of them I don't have this lzma problem.
Because they either don't have liblzma installed from ports, or they
have a different version that works.
DES
--
Dag-Erling Smørgrav - d...@des.no
M. Warner Losh i...@bsdimp.com writes:
I went ahead and used pidfile_close in this context because that's
what's recommended in the man page. I know it is likely redundant,
but I thought better safe than sorry...
agreed...
DES
--
Dag-Erling Smørgrav - d...@des.no
M. Warner Losh i...@bsdimp.com writes:
Why not fix pidfile_open to not return a file handle when the PID
doesn't match?
It doesn't. If it can't lock the file, or if fstat(2) fails after it
has locked the file, it returns NULL.
DES
--
Dag-Erling Smørgrav - d...@des.no
assumption that
flock will release the lock when a process terminates... That isn't
the case in BSD
Yes it is.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
Dag-Erling Smørgrav d...@des.no writes:
M. Warner Losh i...@bsdimp.com writes:
Maybe the real problem is that devd locks the file, then dies. The
file remains locked, so the flopen is failing with EWOULDBLOCK.
The lock is released when the process that holds it terminates.
But I suspect
Dag-Erling Smørgrav d...@des.no writes:
- Under flock semantics (flock(2) locks), the lock is released when
*all* file descriptors the process holds for that file is closed.
are, even, and sorry for the horrid quoting.
DES
--
Dag-Erling Smørgrav - d...@des.no
the ownership of that file? Did you run
buildworld as root and buildenv as a regular user?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
in
realpath.lo is missing and the l in fsck_ffs.lo has been replaced
with a space.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
M. Warner Losh i...@bsdimp.com writes:
Dag-Erling Smørgrav d...@des.no writes:
M. Warner Losh i...@bsdimp.com writes:
Maybe the real problem is that devd locks the file, then dies. The
file remains locked, so the flopen is failing with EWOULDBLOCK.
The lock is released when the process
it again with -Wl,--verbose in addition to -v? Like
this: cc -static -v -Wl,--verbose -o rescue ...
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
Garrett Cooper yanef...@gmail.com writes:
It leaves stray unused lockfiles in the directory:
That's normal and harmless.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
got was completely unrelated, and that patch does
*nothing* that will help Anton. Your problem seems to be that ar(1)
somehow got built before libarchive, while Anton's problem is that gcc
is picking up the wrong version of liblzma.
DES
--
Dag-Erling Smørgrav - d...@des.no
line that failed and run it again with
the -v option and show us the output.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
to switch to .o on other platforms?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
?
No, I meant /usr/lib/liblzma.a.
Do you have any other compilers installed?
On a machine where make buildworld failed, do
% cd /usr/src
% make buildenv
% echo $PATH
% which cc
% cc --version
% strings $(which cc) | grep -w tmp
DES
--
Dag-Erling Smørgrav - d...@des.no
Dag-Erling Smørgrav d...@des.no writes:
On a machine where make buildworld failed, do
% cd /usr/src
% make buildenv
% echo $PATH
% which cc
% cc --version
% strings $(which cc) | grep -w tmp
instead of that last line:
% cc -dumpspecs
(still in buildenv)
DES
--
Dag-Erling Smørgrav - d
Anton Shterenlikht me...@bristol.ac.uk writes:
Dag-Erling Smørgrav d...@des.no writes:
Anton Shterenlikht me...@bristol.ac.uk writes:
Did you mean /usr/local/lib/liblzma.a ?
No, I meant /usr/lib/liblzma.a.
This file doesn't exist on either of my other two ia64 boxes, where
this problem
to run (cc -static ...), add -v
before -static (cc -v -static ...) and run it.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
Ed Schouten e...@80386.nl writes:
In my opinion, we should just rename mailwrapper to whateverwrapper
and list the lpr programs in there as well.
Take a look at /etc/alternatives in any Debian-based Linux distro...
DES
--
Dag-Erling Smørgrav - d...@des.no
Anton Shterenlikht me...@bristol.ac.uk writes:
Dag-Erling Smørgrav d...@des.no writes:
I expect this to produce the same error as before; if not, there is
something seriously wrong.
the error is different...
echo fsck_ffs: /usr/lib/libc.a /usr/lib/libufs.a .depend
cc -O1 -I/usr/src/sbin
questions.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
/src/lib/liblzma/liblzma.a | grep physmem
and show us the result. While you're at it, do this as well:
% nm /usr/lib/liblzma.a | grep physmem
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
, which builds both libedit and sh) before I
posted it.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
installincludes
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
headers are in /usr/src/include.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
jhell.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
revision numbers? Have you tried checking out a clean copy
of r209203 and building + installing that before trying to build r209240
again?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
, and they will not solve his problem. All they
will do is muddle the tracks and reduce our chances of ever finding out
what the problem really is.
Praying for you,
I'd rather you didn't.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current
into src.conf(5)?
I'll leave that to someone who knows why it doesn't work :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
data from a file into a buffer and then
pass that buffer to iconv, because the buffer is not const (otherwise
you couldn't have read data into it). That seems like a pretty
fundamental flaw.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current
Alexander Best alexbes...@uni-muenster.de writes:
Dag-Erling Smørgrav d...@des.no writes:
Alexander Best alexbes...@uni-muenster.de writes:
.if empty(.CURDIR:M/usr/src/*) empty(.CURDIR:M/usr/obj/*)
exists(/usr/local/bin/gcc44)
CC = gcc44
CXX = g++44
CPP = cpp44
.endif
What
Garrett Cooper yanef...@gmail.com writes:
1. Script doesn't check to see whether or not it has write access (and
doesn't catch some errors):
IMHO, any shell script which is intended to be used more than twice
should start with set -e.
DES
--
Dag-Erling Smørgrav - d...@des.no
/src.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Alexander Best alexbes...@uni-muenster.de writes:
Dag-Erling Smørgrav d...@des.no writes:
The problem is that /usr/src/ is not a prefix of /usr/src.
ah i see. would something like
empty(.CURDIR:M/usr/src*) instead of empty(.aCURDIR:M/usr/src/*) work?
I think so. My hypothesis is that CC
Bernd Walter ti...@cicely7.cicely.de writes:
Dag-Erling Smørgrav d...@des.no writes:
Those are freestanding environments, where printf() and puts() don't
exist as far as the C standard is concerned.
Most controller environments have some kind of libc.
They are still freestanding
Alexander Best alexbes...@uni-muenster.de writes:
.if empty(.CURDIR:M/usr/src/*) empty(.CURDIR:M/usr/obj/*)
exists(/usr/local/bin/gcc44)
CC = gcc44
CXX = g++44
CPP = cpp44
.endif
What happens when .CURDIR = /usr/src?
DES
--
Dag-Erling Smørgrav - d...@des.no
Bernd Walter ti...@cicely7.cicely.de writes:
Dag-Erling Smørgrav d...@des.no writes:
Bernd Walter ti...@cicely7.cicely.de writes:
I'm not sure when removing a memset is allowed.
Always, if the compiler can determine that the data will not be used
later.
I'm at least sure
Bernd Walter ti...@cicely7.cicely.de writes:
Amazing - this is one of the things which can get nasty if you try some
kind of microtuning.
Only if you break the rules. Bad code is always bad, even if it
sometimes works by accident.
DES
--
Dag-Erling Smørgrav - d...@des.no
Bernd Walter ti...@cicely7.cicely.de writes:
Dag-Erling Smørgrav d...@des.no writes:
Bernd Walter ti...@cicely7.cicely.de writes:
Amazing - this is one of the things which can get nasty if you try
some kind of microtuning.
Only if you break the rules. Bad code is always bad, even
Bernd Walter ti...@cicely7.cicely.de writes:
Dag-Erling Smørgrav d...@des.no writes:
The only way you can tell that gcc did it is if you break the rules,
such as by defining your own version of printf() or puts().
Our loader stages do this for good reasons. And in microcontroller
thing anymore.
In that case, we can simply cd /usr/src/usr.bin/clang/tblgen make
make install.
Do we really want to install an application like tblgen?
Yes.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
can't pass a volatile pointer to memset.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FORCE_ASSIGN(type, var, value) \
*(volatile type *)(var) = (value)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd
(revision 209062)
+++ usr.bin/clang/Makefile (working copy)
@@ -1,5 +1,5 @@
# $FreeBSD$
-SUBDIR=clang
+SUBDIR=clang tblgen
.include bsd.subdir.mk
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
Tijl Coosemans t...@coosemans.org writes:
Dag-Erling Smørgrav d...@des.no writes:
#define FORCE_ASSIGN(type, var, value) \
*(volatile type *)(var) = (value)
memset can be optimised away as well. The only way is to declare those
variables volatile.
Assigning through a volatile
Brooks Davis bro...@freebsd.org writes:
http://wiki.freebsd.org/201005ToolchainSummitSummary
No new functionality that requires clang/llvm.
How about No new functionality with non-trivial incompatibilities with
clang/llvm?
DES
--
Dag-Erling Smørgrav - d...@des.no
looking at the bug is
immense. When you do know that the issue can be in the compiler, and
not the OS, why looking ?
...so is this.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
bugs?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Roman Divacky rdiva...@freebsd.org writes:
I would like to propose to integrate clang/LLVM into FreeBSD HEAD
in the near future (days, not weeks).
+1
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
Kostik Belousov kostik...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
It adds quite a bit of code to pretty much every UFS VOP.
No, it does not. Essentially, it adds one or two function calls per
vop that allocate or deallocate blocks or inodes, and the function
bodies verify
it affects
performance, but I suspect it's noticeable for disk-intensive workloads
such as busy databases.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
@ worked around in the driver, I forget which)
Any URLs?
Google Promise FastTrak SATA RAID
I have two or three of those, including one with on-board SDRAM (but no
battery backup)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org
Lev Serebryakov l...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Most pseudo-raid kit has nifty features like checksum offloading,
composite writes etc.
Why are they called ``PSEUDO-raids'' then?
Several reasons - they don't present the array to the OS as a single
device
out there. ataraid(4) has served it's
purpose, tiding us over until GEOM RAID facilities were in place. Now it's
time for it to be retired.
gstripe can't create a bootable striped set; ataraid can.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd
.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Alexander Motin m...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Most pseudo-raid kit has nifty features like checksum offloading,
composite writes etc. which can improve performance considerably. You
can't access those from GEOM.
Have you ever seen them documented?
ISTR
here' sade needs to be populating
$DESTDIR/etc/fstab, not sysinstall ?
At that time (when sysinstall invokes sade) there is no $DESTDIR/etc -
sysinstall hasn't yet started extracting the base distribution.
DES
--
Dag-Erling Smørgrav - d...@des.no
Garrett Cooper yanef...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
Garrett Cooper yanef...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
[restored relevant context which was removed earlier in the thread]
...which is exactly what I said
does this differ from
typing a wrong command in?
Please, please, go have a cup of coffee, then come back and *read what I
wrote* instead of just making stuff up.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
Andriy Gapon a...@icyb.net.ua writes:
P.S. DES's name looks strange in headers :-)
Get a better MUA. MIME quoted-printable has been around for what, 15
years?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
fork-exec sade instead
of duplicating the code.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
Rui Paulo rpa...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Alexander Leidinger alexan...@leidinger.net writes:
Please consider using SVN instead. A lot more users will be able
to check out from there.
We don't grant non-committers access to the Subversion repo
attempts to do this in the past.
One of them was even fully funded by the FreeBSD Foundation. They all
failed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
configure a gnop? AFAIK there is no gnop label, so you can't set up a
persistent gnop; you have to set it up manually at boot time every time,
and there's a risk that the fs (or other layers higher up) will taste
the underlying device instead of the gnop.
DES
--
Dag-Erling Smørgrav - d...@des.no
be recorded on-disk)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Alexander Leidinger alexan...@leidinger.net writes:
Dag-Erling Smørgrav d...@des.no writes:
There have been at least three or four attempts to do this in the
past. One of them was even fully funded by the FreeBSD Foundation.
They all failed.
I was told a lot of people tried to make
John Baldwin j...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
My suggestion is to add a sysinstall mode to sade where it
operates under certain (minor) constraints and reports what it did
in a format that sysinstall can parse, so sysinstall can just
fork-exec sade instead
if we forcibly and unconditionally
use 4k sectors.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
the presentation layer is actually 80% of the work. What
you call the business logic already exists (libgeom).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
201 - 300 of 408 matches
Mail list logo
