Hello,
On my network, all workstations are diskless (Linux, FreeBSD, NetBSD,
even OpenVMS). Main server runs NetBSD 10.0 and acts as:
- boot server
- nfs server (/ and /home)
- iSCSI (for swap)
Pythagore runs FreeBSD 14.0 and is a diskless workstation.
Legendre
> > I would like to virtualize FreeBSD on Windows 11 with qemu-kvm (for
> Windows). I've end up with the following parameters which are working :
> >
> >
> > |I:\OS\qemu\Linux\qemu\qemu-system-x86_64w.exe -accel whpx -machine q35
> \ -cpu
> Westmere,vendor=Genui
efreshed. There is no such problem on
7.4 or 8.4 using regular fusefs-kmod from ports.
Luke
> -Original Message-
> From: Yamagi Burmeister [mailto:li...@yamagi.org]
> Sent: Tuesday, October 08, 2013 2:03 PM
> To: f...@freebsd.org
> Cc: freebsd-hackers@freebsd.org; ad...@
I've been doing a few one-on-one sessions at iXsystems explaining the
git model to developers and have had much success.
Tomorrow at BAFUG
(http://www.meetup.com/BAFUG-Bay-Area-FreeBSD-User-Group/events/144351492/)
I will be doing a quick talk on git and then doing a breakaway sessio
ber 08, 2013 2:03 PM
> To: f...@freebsd.org
> Cc: freebsd-hackers@freebsd.org; ad...@3dr.org
> Subject: Re: Fuse on FreeBSD 9.2
>
> There's already a backport which can be found here:
> http://people.freebsd.org/~flo/fusefs-kmod.tar.bz2
>
> 1. Download, untar and
[mailto:li...@yamagi.org]
> Sent: Tuesday, October 08, 2013 2:59 PM
> To: ad...@3dr.org
> Cc: freebsd-hackers@freebsd.org
> Subject: Re: Fuse on FreeBSD 9.2
>
> Responding to myself...
>
> On Tue, 8 Oct 2013 14:13:35 +0200
> Yamagi Burmeister wrote:
>
> >
> >
age: www.yamagi.org
XMPP: yam...@yamagi.org
GnuPG/GPG: 0xEFBCCBCB
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
make deinstall reinstall
clean
4. Rebuild sysutils/fusefs-libs and all fuse filesystems (don't
know if that's necessary but it doesn't hurt either).
I've been running with this kernel module on FreeBSD 9-STABLE,
9.1 and 9.2 four about one year without any problem. I don&
no longer get panics when
doing mass file operations including rsync. :-)
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Thank you!
> -Original Message-
> From: Yamagi Burmeister [mailto:li...@yamagi.org]
> Sent: Tuesday, October 08, 2013 2:14 PM
> To: ad...@3dr.org
> Cc: f...@freebsd.org; freebsd-hackers@freebsd.org
> Subject: Re: Fuse on FreeBSD 9.2
>
>
> On Tue, 8 Oct 201
ile system have you used?
Mostly sysutils/fusefs-smbnetfs to access file servers and sometimes
sysutils/fusefs-ntfs with Win XP and Win 7 disks.
--
Homepage: www.yamagi.org
XMPP: yam...@yamagi.org
GnuPG/GPG: 0xEFBCCBCB
___
freebsd-hackers@freeb
On Tue, Oct 8, 2013, at 6:34, Mark Felder wrote:
>
> I think the "fix" is the new from-scratch fuse module in FreeBSD 10,
> which in my experience works flawlessly. Perhaps you should instead see
> if someone is willing to backport that fuse module to 9.x?
>
Well actual
On Tue, Oct 8, 2013, at 5:21, Łukasz P wrote:
> Hello,
>
> Please let me know if anyone is up to fix fuse on FreeBSD 9.x ?
>
> Particularly this bug:
> <http://www.freebsd.org/cgi/query-pr.cgi?pr=182739>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=182739
>
>
Hello,
Please let me know if anyone is up to fix fuse on FreeBSD 9.x ?
Particularly this bug: <http://www.freebsd.org/cgi/query-pr.cgi?pr=182739>
http://www.freebsd.org/cgi/query-pr.cgi?pr=182739
I'm willing to pay for the fix.
Thank
Dear FreeBSD Community,
This is another gentle reminder that the deadline for submissions for
the third Quarterly Status Report is tomorrow! Please find the
details quoted below.
On Sun, Sep 29, 2013 at 12:22 PM, Gabor Pali wrote:
> Dear FreeBSD Community,
>
> Please note that
revision from you are upgrading
> ($Rev1)
> b) way to get Original configs/files from revision to you are upgrading
> ($Rev100)
> c) have ability to ignore differencies in comments
> d) have ability to treat special cases (as $FreeBSD$ - just took newer line)
>
> Then, your
are upgrading
($Rev100)
c) have ability to ignore differencies in comments
d) have ability to treat special cases (as $FreeBSD$ - just took newer line)
Then, your each new file will be $Rev100 + diff_changes(CURRENT, $Rev1) +
diff_changes($Rev100, $Rev1).
Note, that in case that your diffs are none
On 01/10/2013 10:16, Ivan Voras wrote:
> This is the first time I've used freebsd-update in years, and I'm
> immediately flagging it as something I won't use in the future. For
> the last half hour it has been forcing me to manually resolve, one by
> one, in an editor, h
On 2013-10-01 11:16, Ivan Voras wrote:
This is the first time I've used freebsd-update in years, and I'm
immediately flagging it as something I won't use in the future. For
the last half hour it has been forcing me to manually resolve, one by
one, in an editor, hundreds of &
of maybe opening the file in the editor for me to merge
> again).
You can merge files from freebsd-update, using (m) if I remember well.
Then you choose right or left for each step.
But there is something strange since you have hundreds of conflicts… Did
you built each release from
This is the first time I've used freebsd-update in years, and I'm
immediately flagging it as something I won't use in the future. For
the last half hour it has been forcing me to manually resolve, one by
one, in an editor, hundreds of "merge conflicts" such as these:
Dear FreeBSD Community,
Please note that the next submission date for the July to September
Quarterly Status Reports is October 7th, 2013, bit more than a week
away. Please consult my previous message for the details:
On Mon, Sep 9, 2013 at 12:04 AM, Gabor Pali wrote:
> They do not have to
On Sun, Sep 22, 2013 at 05:56:07PM -0600, Ian Lepore wrote:
> > You can hard-code /bin/sh directly, but what I was getting at with the
> > '#!/usr/bin/env sh' is that the 'sh' interpreter of the build
> > environment could be used (instead of /bin/sh directly). Then you don't
> > need to worry abo
hat the 'sh' interpreter of the build
> environment could be used (instead of /bin/sh directly). Then you don't
> need to worry about the path to sh(1).
>
> Glen
>
My point is that the #! isn't used at all in this case, it doesn't
matter what's there.
On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote:
> On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
> > On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
> > > What's the right way to launch the bourne shell from a makefile? I had
> > > assumed the ${SHELL} variable would
have "make buildenv" put me right into bash (of course, you have
to have bash in the chroot).
The flavor of hashbang to use shouldn't matter, since what I'm after
here is launching the shell to run the script without using the hashbang
mechanism.
-- Ian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
> What's the right way to launch the bourne shell from a makefile? I had
> assumed the ${SHELL} variable would be set to "the right" copy
> of /bin/sh (like maybe the one in tmp or legacy at various stages). It
> appears that that's not
On 9/22/2013 6:18 PM, Ian Lepore wrote:
> What's the right way to launch the bourne shell from a makefile? I had
> assumed the ${SHELL} variable would be set to "the right" copy
> of /bin/sh (like maybe the one in tmp or legacy at various stages). It
> appears that that's not the case, and ${SHEL
with
the script name (as opposed to launching the script and letting the #!
do its thing, which doesn't work if the source dir is mounted noexec).
-- Ian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
In the last episode (Sep 18), Mark Saad said:
> On Tue, Sep 17, 2013 at 2:11 PM, Dan Nelson wrote:
> > In the last episode (Sep 17), Mark Saad said:
> > > Can someone shed some light on a OID mystery I have. I am using
> > > cacti to trend some snmp data off
On Tue, Sep 17, 2013 at 2:11 PM, Dan Nelson wrote:
> In the last episode (Sep 17), Mark Saad said:
> > Can someone shed some light on a OID mystery I have. I am using cacti
> > to trend some snmp data off a bunch of FreeBSD servers.
> >
> > I noticed someone add
All
Can someone shed some light on a OID mystery I have. I am using cacti
to trend some snmp data off a bunch of FreeBSD servers.
I noticed someone added a graph to a cluster for UCDavis - ssRawSwapIn /
UCDavis - ssRawSwapOut . The OIDs are .1.3.6.1.4.1.2021.11.62 /
.1.3.6.1.4.1.2021.11.63
In the last episode (Sep 17), Mark Saad said:
> Can someone shed some light on a OID mystery I have. I am using cacti
> to trend some snmp data off a bunch of FreeBSD servers.
>
> I noticed someone added a graph to a cluster for UCDavis - ssRawSwapIn /
> UCDavis - ssRawSwapOut
Dear FreeBSD Community,
Please note that the next submission date for the July to September
Quarterly Status Reports is October 7th, 2013, less than a month away.
They do not have to be very long -- basically they may be about
anything that lets people know what is going on around the FreeBSD
On Sep 4, 2013, at 3:38 AM, Vincent Hoffman wrote:
> On 03/09/2013 21:29, Kim Shrier wrote:
>> Does anyone know if work on booting FreeBSD on modern Apple hardware
>> was ever completed? I have looked on the wiki, forums, and email archives
>> but I don't see anything
On 03/09/2013 21:29, Kim Shrier wrote:
> Does anyone know if work on booting FreeBSD on modern Apple hardware
> was ever completed? I have looked on the wiki, forums, and email archives
> but I don't see anything definitive.
>
> I would like to have a GPT partitioned disk
Hi Kim,
I had some trouble bootin FreeBSD on my macbook pro last year. It seems
that you have to boot FreeBSD in BIOS mode (UEFI bootloader is not
available yet on amd64) and this can only be achieved on the SATA hard
drive (not an external one).
I don't know how are you trying to boot it b
Does anyone know if work on booting FreeBSD on modern Apple hardware
was ever completed? I have looked on the wiki, forums, and email archives
but I don't see anything definitive.
I would like to have a GPT partitioned disk with a freebsd-boot, freebsd-swap,
and multiple freebsd-ufs parti
--
> Florent Peterschmitt | Please:
> flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail.
> +33 (0)6 64 33 97 92 | * Send PDF for documents.
> http://florent.peterschmitt.fr | * Trim your quotations. Really.
> Proudly powered by Open Source | Thank you :
Le 03/09/2013 16:53, Alan Somers a écrit :
> GELI is full-disk encryption. It's far superior to ZFS encryption.
Yup, but is there a possibility to encrypt a ZFS volume (not a whole
pool) with a separate GELI partition?
Also, in-ZFS encryption would be a nice thing if it could work like an
LVM/LU
t; flor...@peterschmitt.fr| * Avoid HTML/RTF in E-mail.
> +33 (0)6 64 33 97 92 | * Send PDF for documents.
> http://florent.peterschmitt.fr | * Trim your quotations. Really.
> Proudly powered by Open Source | Thank you :)
>
___
Le 03/09/2013 14:14, Emre Çamalan a écrit :
> Hi,
> I want to encrypt some disk on my server with Zfs encryption property but it
> is not available.
"That would require ZFS v30. As far as I am aware Oracle has not
released the code under CDDL."
From http://forums.freebsd.org/showthread.php?t=30
B SID (eg: "S-1-234-567-89")
[root@HP ~]#
-
How can I use or add encryption property to FreeBsd 8.3?
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
t setting KDE_FORK_SLAVES=1 in environment works around
> >>> the problem.
> >>
> >> I reported this same problem in this[1] thread on freebsd-ports@.
> >> In that post I provided a link to a similar report for KDE on
> >> openSUSE that required a dbus pat
ck to what they should have been originally.
> VirtualBox does not do any (re-)exec of itself after the above manipulations.
>
> 2. issetugid(2) (which is apparently a BSD extension) on FreeBSD does not
> consider the above manipulations as sufficient to mark an executable as
> untainted.
problem where any file opening dialog would fail with this
>>> message: "Cannot talk to klauncher: Not connected to D-Bus server"
>>>
>>> I found that setting KDE_FORK_SLAVES=1 in environment works around the
>>> problem.
>>
>> I reported th
>
> On 08/07/2013 01:56, Wojciech Puchar wrote:
> >
> > not possible in FreeBSD with UFS.
> >
> > but if you run virtualbox under linux i cannot say much...
>
> This happened with FreeBSD guest with UFS (journaled soft-updates) and
> FreeBSD host.
> What
On 08/07/2013 01:56, Wojciech Puchar wrote:
not possible in FreeBSD with UFS.
but if you run virtualbox under linux i cannot say much...
This happened with FreeBSD guest with UFS (journaled soft-updates) and
FreeBSD host.
What is out of normal, it rolled back for many hours (~20).
Yuri
Virtualbox is very aggressive about caching writes. This is how it
achieves its perceived speed. I wouldn't expect to see this happen on
real hardware. I might have to try this out though and see if I can
reproduce it reliably.
___
freebsd-ha
I hit this unexpected problem: my host had an ungraceful shutdown while
FreeBSD 9.1 STABLE was running in the VirtualBox VM. After reboot of the host
and VM, local ufs file system was missing all recent updates for at least 20
hours (!!!)
My question is, how is this possible? Is this related to
I hit this unexpected problem: my host had an ungraceful shutdown while
FreeBSD 9.1 STABLE was running in the VirtualBox VM. After reboot of the
host and VM, local ufs file system was missing all recent updates for at
least 20 hours (!!!)
My question is, how is this possible? Is this related to
On Sunday, July 07, 2013 7:41:43 am mangesh chitnis wrote:
> Hi,
>
> What is the memmap equivalent of Linux in FreeBSD?
>
> In Linux memmap is used to reserve a portion of physical memory. This is
used as a kernel boot argument. E.g.: memmap=2G$1G will reserve 1GB memory
above
em at vicor where I had a temporary "beneath" /etc
that had all its files linked to files of the same name in /etc.boot/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
. I was unaware of it
On a side-note, I didn't write bsdinstall -- I'm going to maintain it, but I
wrote bsdconfig ^_^ (smiles)
Thank you very much for your appreciation. Certainly a labor of love and I'm
happy that others have kicked the wheels at least.
--
Devin
_____
restrictive in a
way that burns them)
Devin, thank you IMMENSELY for bsdinstall and especially bsdconfig. I
use them both at work and they make life so much better. And thank you
for the simplification using kenv. I was unaware of it
_______
freebsd-hacke
SOLUTION:
Hi,
USB memstick img file is solution for me.
I try FreeBSD-8.3-RELEASE-amd64-memstick.img.
I downloaded this img file and copy to USB, not burn it to USB.
Then attach to İLO such as USB virtual image then sysinstall start, BUT I
selected installation from usb install NOT CD/DVD
her than the intended recipient. Thank you.
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
tually adding to the ISO which FBSD-current can't do?
If it's not upstream already - will it be contributed upstream?
Please reply further on freebsd-chat, I'd like to consolidate any
discussion this may garner.
This doesn't provide anything to the core OS that can&#
On 07/ 8/13 05:28 AM, Alfred Perlstein wrote:
On 7/7/13 3:05 PM, "C. Bergström" wrote:
On 07/ 8/13 04:58 AM, Chad J. Milios wrote:
Outline of features:
Extends plain old FreeBSD 9.1 (RELEASE or STABLE) and maintains
total compatibility
We seek to remain nimble
Expect a
On 7/7/13 3:05 PM, "C. Bergström" wrote:
On 07/ 8/13 04:58 AM, Chad J. Milios wrote:
Outline of features:
Extends plain old FreeBSD 9.1 (RELEASE or STABLE) and maintains total
compatibility
We seek to remain nimble
Expect a production-ready seal of approval to lag behind re
On 07/ 8/13 04:58 AM, Chad J. Milios wrote:
Outline of features:
Extends plain old FreeBSD 9.1 (RELEASE or STABLE) and maintains total
compatibility
We seek to remain nimble
Expect a production-ready seal of approval to lag behind releases
by no more than a week or two
and
PLEASE reply to this only in freebsd-chat. I have posted this
announcement to five freebsd mailing lists, I hope I am not overstepping.
Hello everybody. My name's Chad J. Milios. Long-time lurker, sparse rare
sporadic poster.
TL;DR? -- Skip below to our summary of features in an ou
Hi,
What is the memmap equivalent of Linux in FreeBSD?
In Linux memmap is used to reserve a portion of physical memory. This is used
as a kernel boot argument. E.g.: memmap=2G$1G will reserve 1GB memory above
2GB, incase I have 3GB RAM. This 1GB reserved memory is not visible to the OS
r information, today is the deadline for submitting those reports.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Hi,
I'm trying to install FreeBSD with an HP ILO 4 advanced, web interface. I tried
to install FreeBSD 8.2, FreeBSD 8.3 and FreeBSD 8.4. I tried to use acd0 and
cd0 as media. I got the same result. Details about the problem I attach
pictures.
ERROR: I'm trying to add freebsd8.3is
ly 7th, 2013 - less than a month away.
>
> Note that you have a little less than 2 weeks left to prepare and send
> us your reports.
There is only 5 days left... :-)
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/
le less than 2 weeks left to prepare and send
us your reports.
> They don't have to be very long - anything that lets people know what
> is going on inside FreeBSD is useful. Note that submission of reports
> is not restricted to committers - anyone who is doing anything
> interestin
$ uname -a
FreeBSD fbsd91x64 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec
4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
$ id
uid=1001(hunger) gid=1002(hunger) groups=1002(hunger)
$ gcc fbsd9lul.c -o fbsd9lul
$ ./fbsd9lul
FreeBSD 9.{0,1} mmap/ptrace
ou that the next submission date for the April to June quarterly
> status reports is July 7th, 2013 - less than a month away.
>
> They don't have to be very long - anything that lets people know what
> is going on inside FreeBSD is useful. Note that submission of reports
>
on inside FreeBSD is useful. Note that submission of reports
is not restricted to committers - anyone who is doing anything
interesting and FreeBSD-related can write one!
The preferred and easiest submission method is to use the XML
generator linked to from
http://www.freebsd.org/news/status/status.html
Hi,
i am not a skilled user of FreeBSD but have knowledge about
DVD burners and growisofs.
> growisofs is from dvd+rw-tools-7.1, which hasn't been updated from 2008.
That's the current release. It should be ok for DVD burning.
> :-? the LUN appears to be stuck writing
I have DVD burner Pioneer DVR-112D failing on FreeBSD-9.1 amd64. It
begins to write ok, but later gets stuck at some percentage point with
"the LUN appears to be stuck" message (log is below).
Command used to burn is:
$ growisofs -dvd-compat -speed=4 -Z /dev/acd0=my.iso
growisofs is f
%3D%0A&r=Mrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=BFNRw%2Fl9%2B28%2BnxLbdzO4ji0pUaEPGB%2BV9%2BaaBuFSGWM%3D%0A&s=3bbe977edd2b122e6d4bc08d7650eb11e412fe03c97b25b3aa86cbf4c96e9ba6>.
Other major ones are IPv6 (maybe this has changed?) and no jail setup feature.
Most of the existing disk partitioning code in pc-sysinstall, which is the only
thing
> pc-sysinstall could be augmented. This is the first I've heard of that.
> All the other complaints have been based on portability.
>
> Is that all that is required now, wireless?
>
> There are more, as well. A partial list of missing features on both sides
> is here:
ure. Most of the existing disk
partitioning code in pc-sysinstall, which is the only thing in a FreeBSD
installer that is at all complicated, is also *extremely* fragile and needs in
all likelihood to be entirely replaced. The merge effort stalled because of
this kind of issue -- doing a "mer
partitioning code in pc-sysinstall, which is
the only thing in a FreeBSD installer that is at all complicated, is
also *extremely* fragile and needs in all likelihood to be entirely
replaced. The merge effort stalled because of this kind of issue --
doing a "merge" rapidly became rewrit
red now, wireless?
There are more, as well. A partial list of missing features on both
sides is here: https://wiki.freebsd.org/PCBSDInstallMerge. Other major
ones are IPv6 (maybe this has changed?) and no jail setup feature. Most
of the existing disk partitioning code in pc-sysinstall, which i
s.
-Nathan
I'm sure if there was a list of reasonable things, such as wireless then
pc-sysinstall could be augmented. This is the first I've heard of
that. All the other complaints have been based on portability.
Is that all that is required now, wireless?
-Alfred
-Alfred
sclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
ed up having
time to finish. Probably a reasonable thing to do is to start with
supporting only a minimal set of features. If anyone felt like actually
writing this code, I'm sure it would be appreciated by all and be more
productive than email exchanges.
-Nathan
______
difficult, or just never happening, then we can't limit
everyone's experience based on the more difficult and/or resource
strapped platforms.
It's just not good business.
-Alfred
___
freebsd-hackers@freebsd.org mailing list
http://li
now as well.
-Nathan
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
them first in case there's some
problem that means it can't be done, in which case we'd need to use a
different backend.
--
Bruce
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To un
I heard there was some discussion at BSDCan about the direction of a future
FreeBSD installer. Considering we currently have bsdinstall, pc-sysinstall,
the best would be removing it at all and adding instruction how to install
by hand.
At least someone that install FreeBSD will know what he
On 5/27/13 11:40 AM, Bruce Cran wrote:
On 27/05/2013 19:03, Alfred Perlstein wrote:
Do we always have to seek the lowest common denominator for our user
experience?
Yes.
Is this a joke?
-Alfred
___
freebsd-hackers@freebsd.org mailing list
http
please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the
On 27/05/2013 19:03, Alfred Perlstein wrote:
Do we always have to seek the lowest common denominator for our user
experience?
Yes.
--
Bruce
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
we
update bsdinstall to use it, then it won't work on other platforms.
This still doesn't make sense to me. Why can bsdinstall not
conditionally use it?
Do we always have to seek the lowest common denominator for our user
experience?
-Alfred
___
't work on other platforms.
--
Bruce
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
7;s all down to familiarity. I suppose sh is more resistant to
many stupid bugs and handles strings well But it has its own troubles
too of course.
Chris
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
right… we can't in all seriousness even think about
using pc-sysinstall until it is solid on all architectures as bsdinstall
already is.
GSoC project is: "Making pc-sysinstall FreeBSD ready by porting it to multiple
architectures"
Why can we not use in the interim use pc-sy
n't worry.
Why is that exactly?
A number of people are using it successfully to install ZFS based systems.
-Alfred
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any ma
aving something more
strongly typed certainly helps understanding.
(*) Assuming some level of complexity (I know that's
subjective).
--
DE
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
evice_{name}" (where {name} is something
like "da0") and the struct holds many properties for the device.
I don't think there's any reason why we have to write it in C if we can write
it in sh.
> Still, thanks for pointing all that out, but I rather wanted to look at
>
On 27/05/2013 00:27, Dirk Engling wrote:
Still, thanks for pointing all that out, but I rather wanted to look at
the installer from another angle, as it is supposed to provide everyone
from FreeBSD novices to experts with a comfortable way to do things the
right way and yet be flexible enough to
.
Still, thanks for pointing all that out, but I rather wanted to look at
the installer from another angle, as it is supposed to provide everyone
from FreeBSD novices to experts with a comfortable way to do things the
right way and yet be flexible enough to avoid abandoning the tool once
the requirement
r domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Bruce Cran
_______
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
an't in all seriousness even think about
using pc-sysinstall until it is solid on all architectures as bsdinstall
already is.
GSoC project is: "Making pc-sysinstall FreeBSD ready by porting it to multiple
architectures"
--
Devin
>
> On Sat, May 25, 2013 at 9:01 PM, Dirk E
1 - 100 of 10231 matches
Mail list logo
