Hi,
i wrote:
> > > What firmware file to use with qemu-system-i386 [...]
Sorry for sending this debian-user answer to the wrong thread
here on debian-bsd.
Have a nice day :)
Thomas
Hi,
i wrote:
> > What firmware file to use with qemu-system-i386 in order to demonstrate
> > EFI booting on i386 ?
Ric Moore wrote:
> I gave to wonder if the bootable flag was set during format? If not, that
> would explain much. Ric
The boot flag is set with one of the MBR partitions. Not with
Hi,
Adam Wilson wrote:
> Are GNU/kFreeBSD 7 images isohybrid?
Formally not, because "isohybrid" is a term from ISOLINUX and the
kFreeBSD ISOs rather boot by GRUB2.
Practically not, because e.g.
Hi,
my best guess for the implementation location of __acl_set_file()
is sys___acl_set_file() in
https://svnweb.freebsd.org/base/head/sys/kern/vfs_acl.c?revision=284446=markup
(I don't understand how
https://svnweb.freebsd.org/base/head/sys/kern/syscalls.master?revision=285388=markup
Hi,
i now believe that the ENOSYS is in libattr1 which has as source
attr-2.4.46 with file libattr/syscalls.c .
(There seems to be a transition underways to move this part
into eglibc.)
If this assessment is correct then currently kfreebsd aims for
ACL implemented on top of xattr (libattr1,
Hi,
the FreeBSD code in
https://svnweb.freebsd.org/base/head/lib/libc/posix1e/acl_set.c?revision=208785=markup#l53
shows that userland function acl_set_file(3) is implemented via
kernel (?) call __acl_set_file().
This means that the internal representation of an ACL is not
stored as extended
Hi,
the ENOSYS comes from a general refusal of libacl ... i'd say.
So where to inspect its source ? (Or dowload it.)
I could not tune the mounted root filesystem:
# tunefs.ufs -a enable /
tunefs.ufs: POSIX.1e ACLs set
Hi,
while answering i realize that ACL is not enabled with my UFS
filesystem and that the ENOSYS might come from this individual
shortcomming and not from lack of support.
I will try to investigate and distinguish.
Do you have a web pointer to the source of libacl as used in kfreebsd ?
Hi,
i hope it is not too obtrusive to bring up this topic
again after 6 years. :))
https://lists.debian.org/debian-bsd/2009/12/msg00146.html
I am meanwhile proud owner of a kfreebsd VM
Debian GNU/kFreeBSD 7
GNU/kFreeBSD ts6-kbsd 9.0-2-686 #0 Sun May 17 22:06:56 UTC 2015 i386 ...
which
Hi,
(cc'ing debian-bsd@lists.debian.org again)
Urm ... before we dig deeper with burn programs:
Is your laptop drive physically able to eject, at all ?
Many laptop drives need the mechanical power of the user
to come out. I.e. if you have to press the eject button
with some force and if no
Hi,
DAVID Henderson wrote:
There is something wrong regarding the kfreebsd-i386 eject command .
Looking at https://packages.debian.org/sid/eject i see
a common source tarball for Linux and kFreeBSD
http://ftp.de.debian.org/debian/pool/main/e/eject/eject_2.1.5+deb1+cvs20081104.orig.tar.gz
File
Hi,
3 Macs that don't have eject buttons.
Did you already try to eject by a burn program ?
wodim dev=/dev/cd0 -eject
cdrskin dev=/dev/cd0 -eject
xorriso -outdev /dev/cd0 -eject all
If this does not work, the SCSI logs might be of interest
wodim -V dev=/dev/cd0 -eject
cdrskin -V
Hi,
brunomaxi...@openmailbox.org wrote:
Hi, I think kFreeBSD needs an automount program.
As programmer of burn software for optical media, i would
like to add the constraint that the automounter should not
grope drives which are in the progress of writing to CD
or DVD-R media. Such burn runs
Hi,
Joel Lopes Da Silva wrote:
I tend to want to use those installs on Macs
[...]
Unfortunately, last I checked, only the mini.iso images for Debian
GNU/kFreeBSD were isohybrid images.
isohybrid usually boots from USB stick by offering an MBR to PC-BIOS.
Macs will probably not have PC-BIOS
Hi,
So it would be mainly about asking debian-cd to produce a MBR boot image
and to tell genisomage or xorriso to include it (by option -G).
The MBR is just one piece of the boot chain, you need everything else
to be in place for this to work. This includes (but is not limited
to)
Hi,
me:
None of the optional libraries and system
features is used in the buildd compile runs:
- libacl
- support for Extended Attributes
- zlib
Nevertheless, the aspects of ACL and xattr are
also porting issues.
Guillem Jover:
This is a general packaging bug, there's missing
Hi,
looking over the system dependencies in our
project i come to the xorriso mount helper.
It reads the table-of-content of multi-session
media or files and produces a mount command
for mounting a particular session.
Typically used to retrieve older states from
multi-session backups.
I read
Hi,
looking over the system dependencies in our
project i come to the xorriso mount helper.
It reads the table-of-content of multi-session
media or files and produces a mount command
for mounting a particular session.
Typically used to retrieve older states from
multi-session backups.
I read
Hi,
Sorry for sending the same old mail again.
It should have been this one:
I had a look at the buildd logs of our libisofs
https://buildd.debian.org/fetch.cgi?pkg=libisofs;ver=0.6.24-1;arch=kfreebsd-amd64;stamp=1255540287
Hi,
Petr Salinger:
Update of acinclude.m4, libburn/os.h, libburn/sg.c
will be needed at least.
George initially proposed me to use macro
__FreeBSD_kernel__
for system detection.
This text snippet brought me to
http://glibc-bsd.alioth.debian.org/porting/PORTING
where i read this
Example
Hi,
# genisoimage -o - /tmp/cdrskin-0.7.5 | cdrskin/cdrskin dev=/dev/cd0 -
...
Track 01: Total bytes read/written: 13455360/13455360 (6570 sectors).
Great. Thanks a lot.
It is quite a while that i had a success report
from FreeBSD. One never knows whether a
regression sneaked in.
The next
Hi,
as introduction to debian-bsd@lists.debian.org:
I am the current developer of libburn
http://libburnia-project.org/
which can write CD/DVD/BD on Linux and FreeBSD.
The compile time failure in
https://buildd.debian.org/build.php?pkg=libburnver=0.6.4-1arch=kfreebsd-i386file=log
is caused
22 matches
Mail list logo
