Issue #3319 has been reported by tonyc.
Bug #3319: setproctitle() calls can change effect of later setproctitle() calls
http://bugs.dragonflybsd.org/issues/3319
* Author: tonyc
* Status: New
* Priority: Normal
* Target version: 6.4
* Start date:
Issue #745 has been updated by tuxillo.
Status changed from Feedback to Closed
Target version changed from Unverifiable to 6.4
Over a decade marked as Unverifiable.
Bug #745: the evil interrupt stats monster is still around!
Issue #696 has been updated by tuxillo.
Category changed from Unverifiable to Kernel
Status changed from New to Closed
Target version changed from Unverifiable to 6.4
IPSEC was removed in commit:755d70b8f2c28b016b6c0330273e7daa38038f27
Bug #696: IPSEC
Issue #3305 has been updated by tuxillo.
Status changed from In Progress to Closed
For now, this can be closed as confirmed with cbsd.
Bug #3305: CBSD: Add NVMM support in DragonFly BSD
http://bugs.dragonflybsd.org/issues/3305#change-14388
* Author:
Issue #3318 has been updated by zabolekar.
tuxillo wrote in #note-1:
> We'll try t at least handle that case but we're also considering how useful
> process checkpointing really is. If anybody has any feedback about it now it
> would be the time to share it :-)
To clarify, I don't actually
Issue #1921 has been updated by tuxillo.
Still pending of doing the the rlimit work, this is a reminder to myself.
Bug #1921: we miss mlockall
http://bugs.dragonflybsd.org/issues/1921#change-14386
* Author: alexh
* Status: In Progress
* Priority: Normal
Issue #3317 has been updated by tuxillo.
Ok, we will have to check route(8) then, there might be a bug that needs fixing
there.
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317#change-14385
* Author:
Issue #3318 has been updated by tuxillo.
Status changed from New to In Progress
Assignee set to tuxillo
Target version set to 6.4
Back in the day we added two memory mappable devices (/dev/upmap and
/dev/kpmap) which provide certain data from the kernel without the need of a
system call. See
Issue #3317 has been updated by mneumann.
Assignee deleted (tuxillo)
debugged it further:
route add 172.31.1.1/32 -iface vtnet0
will result in:
add net 172.31.1.1: gateway vtnet0
while
route add 172.31.1.1 -iface vtnet0
will result in
add host 172.31.1.1: gateway vtnet0
An IP
Issue #3317 has been updated by tuxillo.
Status changed from New to In Progress
Assignee set to tuxillo
mneumann wrote in #note-19:
> "We" probably should :). I guess DragonFly uses a different "dhclient" than
> FreeBSD, so diffing is not an option. Is "dhclient" going to be deprecated in
>
Issue #3317 has been updated by mneumann.
Found the bug. So when I change:
route add 172.31.1.1/32 -iface vtnet0
to
route add 172.31.1.1 -iface vtnet0
it works! Might be a parsing problem in `route`.
Bug #3317: Network vtnet0 not working on
Issue #3317 has been updated by mneumann.
File clipboard-202206171102-blgae.png added
There is `/sbin/dhclient-script` which is invoked with the following env
variables set:
!clipboard-202206171102-blgae.png!
I could image that this script is doing something wrong.
The script is calling the
Issue #3317 has been updated by mneumann.
"We" probably should :). I guess DragonFly uses a different "dhclient" than
FreeBSD, so diffing is not an option. Is "dhclient" going to be deprecated in
DragonFly, or why is there a working alterantive (dhcpcd)?
Issue #3317 has been updated by tuxillo.
Nice!
The question is now, should we find out what's the problem with dhclient?
Because it might be uncovering at the very least a _route(8)_ issue.
Bug #3317: Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann.
yes,
dhcpcd_enable="YES"
alone works!
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317#change-14377
* Author: mneumann
* Status: New
* Priority: Normal
*
Issue #3317 has been updated by tuxillo.
It seems to be related with our dhclient, it's definitely route related becuase
if I use the config below in my rc.conf I'll get the bug you're reporting.
ifconfig_vtnet0="DHCP"
However, if I just use dhcpcd, all seems to work fine, can you please
Issue #3317 has been updated by tuxillo.
I didn't know DHCP was supposed to work, I'll give it a try and see what's up.
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317#change-14375
* Author: mneumann
*
Issue #3317 has been updated by mneumann.
Hi tuxillo,
1000x thanks!
With your snippet above, it works!
Now I can install things and maybe we can figure out why DHCP does not work
properly.
Bug #3317: Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo.
Can you please try this in your rc.conf?
[...]
static_routes="hetzner default"
route_hetzner="172.31.1.1 -interface vtnet0"
route_default="default 172.31.1.1"
ifconfig_vtnet0="inet x.x.x.x netmask 255.255.255.255"
[...]
Issue #3317 has been updated by mneumann.
I'd like to setup the routes manually (not via dhclient), but I am strugging
with it. This is what I do:
ifconfig vtnet0 inet 192.119.117.156 netmask 255.255.255.255 up
route add -interface 172.31.1.1 vtnet0
route add default 172.31.1.1
But, it's
Issue #3317 has been updated by mneumann.
File clipboard-202206140730-vzpkc.png added
This error message might be of interest:
rtsock: received more addr bits than sockaddrs.
!clipboard-202206140730-vzpkc.png!
Bug #3317: Network vtnet0 not
Issue #3317 has been updated by mneumann.
I also checked the integrity of the ISO image by doing an `dd if=/dev/cd0s0
bs=2k | md5` and it is correct (d41d8...27e; 6.2.1).
Bug #3317: Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann.
File clipboard-202206140707-0biu1.png added
Some dmesg output:
!clipboard-202206140707-0biu1.png!
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317#change-14369
*
Issue #3317 has been updated by mneumann.
I have to correct myself. It's possible to mount a custom ISO. You just need to
ask the support to do it (the dragonfly ISO is a custom ISO)
Bug #3317: Network vtnet0 not working on Hetzner cloud
Issue #3318 has been reported by zabolekar.
Bug #3318: Segmenation fault when a process resumed with checkpt exits
http://bugs.dragonflybsd.org/issues/3318
* Author: zabolekar
* Status: New
* Priority: Normal
* Start date: 2022-06-12
Issue #3317 has been updated by mneumann.
No, it's not possible to mount a custom ISO image. But I asked the support, and
~30 minutes later, they had the DragonFly (dfly-...) image uploaded and made
available!!! Kudos.
Bug #3317: Network vtnet0 not
Issue #3317 has been updated by tuxillo.
Also, is it possible to mount a custom image from the Hetzner Cloud panel? I
dont' see an option for that.
Bug #3317: Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann.
I will try to use `kgdb` at the weekend. Yes, I think it's KVM. The "garbage"
changes when I remove the routes and add them again.
Bug #3317: Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo.
I wonder if those characters are garbage. Have you tried using kgdb to inspect
the kernel structures? I don't know from the top of my head which ones are.
I'm assuing that's a KVM VM (since it's using vtnet)
Bug
Issue #3317 has been updated by mneumann.
ah wait, no, I can't get `ping` to work. when I `route delete 172.31.1.1` and
then `route add default 172.31.1.1` I have again two routes and one of them
contains the strange characters in the Gateway column.
Issue #3317 has been updated by mneumann.
I can get `ping` to work when I flush the default route and add it again.
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317#change-14362
* Author: mneumann
* Status:
Issue #3317 has been reported by mneumann.
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317
* Author: mneumann
* Status: New
* Priority: Normal
* Category: Networking
* Target version: 6.4
* Start date:
Issue #3316 has been updated by dillon.
The directory hash collision space does not guarantee name uniqueness, so the
iterator is there on purpose to deal with hash collisions (names might be
different, but key calculates to the same value). Higher levels are
responsible for ensuring that
Issue #3316 has been reported by tkusumi.
Bug #3316: hammer2_dirent_create() allows creating >1 dirents with the same name
http://bugs.dragonflybsd.org/issues/3316
* Author: tkusumi
* Status: New
* Priority: Normal
* Target version: 6.4
* Start date:
Issue #933 has been updated by tuxillo.
Description updated
Status changed from Feedback to Closed
% Done changed from 0 to 100
Although it may have worked at some point for some specific hardware, we don't
support suspend/resume.
Bug #933: em(4)
Issue #389 has been updated by tuxillo.
Description updated
Category set to PF
Status changed from Feedback to Closed
Assignee set to bastyaelvtars
Although pf was updated, no feedback was provided.
Bug #389: modulate state
Issue #572 has been updated by tuxillo.
Description updated
Category set to installer
Status changed from In Progress to Closed
Assignee set to corecode
% Done changed from 0 to 100
Irrelevant as of today.
Bug #572: Installer: no option to set
Issue #558 has been updated by tuxillo.
Description updated
Category set to Kernel
Status changed from Feedback to Closed
Assignee set to c.turner
% Done changed from 0 to 100
Ancient bug and no feedback was reported even tho it was stated there have been
significant changes that could
Issue #1864 has been updated by tuxillo.
Description updated
Category set to Userland
Status changed from New to Closed
Assignee set to dillon
% Done changed from 0 to 100
The debugging message was removed in
commit:696974900a518360ea4481af2e71d5f8a9628248
Issue #2519 has been updated by tuxillo.
Description updated
Category set to Kernel
Status changed from In Progress to Closed
% Done changed from 0 to 100
Two fixes were made and no further reports of this problem.
Bug #2519: panic: assertion
Issue #2513 has been updated by tuxillo.
Description updated
Category set to installer
Status changed from New to Closed
% Done changed from 0 to 100
No i386 anymore plus user reported success.
Bug #2513: Installer w/ UFS set subpartitions too big
Issue #2505 has been updated by tuxillo.
Description updated
Category set to Userland
Status changed from In Progress to Closed
Assignee set to davshao
No i386 support anymore plus davshao reported success.
Bug #2505: i386 buildkernel cc1: error: too
Issue #2402 has been updated by tuxillo.
Description updated
Category set to Other
Status changed from New to Closed
Assignee set to tuxillo
3.2 was released long ago.
Bug #2402: Showstopper panics for Release 3.2
Issue #2410 has been updated by tuxillo.
Description updated
Category set to Other
Status changed from New to Closed
Assignee set to tuxillo
% Done changed from 0 to 100
Enought time given :)
Bug #2410: Placeholder for Bug Notes by Varialus
Issue #2372 has been updated by tuxillo.
Description updated
Category set to Other
Status changed from New to Closed
Assignee set to tuxillo
We no longer use pkgsrc but in dports we got:
$ sudo make -DBATCH test
===> Testing for libsigsegv-2.14
Making check in src
Making check in tests
Issue #2204 has been updated by tuxillo.
Description updated
Category set to Userland
Status changed from New to Closed
Assignee set to marino
% Done changed from 0 to 100
This was dealt with in:
commit:d66febebfcbe87509f4e19c8e51cc6a3a490996a
commit:a0ba0189b9089fb6630d9e0244b373af683cbe9c
Issue #2360 has been updated by tuxillo.
Description updated
Category set to Feature request
None of the links in the description are available anymore.
Bug #2360: Wishlist: virtio driver import
http://bugs.dragonflybsd.org/issues/2360#change-14341
*
Issue #2309 has been updated by tuxillo.
Description updated
Category set to Bugtracker
Status changed from New to Closed
% Done changed from 0 to 100
Bug #2309: Catch all ticket for Bugtracker problems
Issue #2333 has been updated by tuxillo.
Status changed from Feedback to Closed
Back then when we had this, it was desirable to have submit@ opened, but since
then we have had to even close the bugtracker registration process because of
the spam.
I've verified that unknown users can't send
Issue #3028 has been updated by tuxillo.
File fn_get_passphrase.patch added
Status changed from New to In Progress
Assignee set to tuxillo
Maybe something like this would work? (Untested!!)
Bug #3028: installer: confusion of set/get disk encryption
Issue #3017 has been updated by tuxillo.
Status changed from New to Closed
Assignee set to bycn82
Fixed in commit:992b3001a225605640debab1be6feab6e367bb5e
Bug #3017: sbin/ipfw3/ipfw3.c:2519: redundant compare ?
Issue #3016 has been updated by tuxillo.
Status changed from New to Closed
Assignee set to tuxillo
It was removed in commit:f8a108fb1b0a6a6f4cd533e9fa0b110ef124160d
Bug #3016: sbin/hammer2/cmd_snapshot.c:113]: (error) Memory leak: xname
Issue #2982 has been updated by tuxillo.
Status changed from New to Closed
Assignee set to tuxillo
Just include @sys/param.h@ before including fetch.h, as you yourself mentioned
:)
Closing this one!
Bug #2982: Failed compile due to fetch.h and
Issue #1476 has been updated by tuxillo.
Category set to VFS subsystem
Status changed from In Progress to Closed
Assignee set to tkusumi
Added back in commit:74fa2560ac77f9db4a34b2a7c72450126fec4ed6
Bug #1476: We miss fdatasync()
Το θέμα #3313 ενημερώθηκε από τον rempas.
daftaupe wrote in #note-1:
> Hello,
>
> I'm usually creating the bootable medium with the following command. Please
> make sure to use the .img file, not the iso if you are using a USB stick.
> In the following line, /dev/yourusbstick is to be
Issue #2304 has been updated by tuxillo.
Description updated
Status changed from Feedback to Closed
Assignee set to tuxillo
No feedback at the time, also we don't support i386 anymore.
Bug #2304: DFBSD v3.1.0.32.g4d37d - assertion "p" failed in
Issue #1954 has been updated by tuxillo.
Status changed from Feedback to Closed
Assignee set to tuxillo
As of commit:f9602a12d5f0345feed0941d0b9e3b4e1816a411, /tmp is tmpfs.
Bug #1954: installer creates /tmp/ as HAMMER pfs instead of tmpfs
Issue #2273 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee set to tuxillo
No vkernel and no i386 support anymore.
Bug #2273: UFS panic on vkernel i386
http://bugs.dragonflybsd.org/issues/2273#change-14324
*
Issue #2079 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to tuxillo
tap(4) was reworked not long ago and removing tap devices does not crash.
Bug #2079: DFBSD v2.11.0.179.gc4383 - Panic upon
Issue #2040 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to tuxillo
We no longer are able to select from UP or SMP kernels.
Bug #2040: kernel selection on installer cd is broken
Issue #2034 has been updated by tuxillo.
Status changed from New to Closed
Assignee set to tuxillo
We no longer use pkgsrc. Also, invoking vlc or tinyproxy does not trigger this
anymore.
Bug #2034: assertion: z->z_Magic == ZALLOC_SLAB_MAGIC in _slabfree
Issue #243 has been updated by tuxillo.
Description updated
Status changed from New to Feedback
Assignee deleted (0)
In linux, tcsh:
debian:~# .
/usr/bin/.: Permission denied.
Any other shell I've tried other than csh does not show this behavior. Can this
be closed?
Issue #1989 has been updated by tuxillo.
Status changed from New to Closed
Assignee set to tuxillo
It is stated it was solved at the time.
Bug #1989: Panic on reboot, DFly 2.8.2
http://bugs.dragonflybsd.org/issues/1989#change-14313
* Author: dl
*
Issue #2019 has been updated by tuxillo.
Status changed from New to Closed
Seems it was a problem with the KVM limit in i386. We no longer support i386.
Bug #2019: panic: file desc: malloc limit exceeded
Issue #2001 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to tuxillo
No longer valid.
Bug #2001: kqueue - Firefox and thunderbird CPU usage
http://bugs.dragonflybsd.org/issues/2001#change-14309
Issue #2000 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to tuxillo
Seems not anymore:
devbox# ktrace -C
devbox# ktrace -C
devbox# ktrace -C
devbox#
Bug #2000: ktrace -C loops forever
Issue #1991 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to tuxillo
Since this bug was reported we even got a qemu accelerator working (nvmm) and
everything seems to work perfectly fine.
Bug
Issue #1983 has been updated by tuxillo.
Status changed from New to Closed
Assignee set to tuxillo
We no longer use pkgsrc by default.
Bug #1983: Moving pkg_radd, pkg_search config to different location
Issue #1854 has been updated by tuxillo.
Status changed from New to Closed
Assignee set to tuxillo
Assuming the mentioned commit fixes the problem.
Bug #1854: Bugs while using encrypted HAMMER root fs
http://bugs.dragonflybsd.org/issues/1854#change-14304
Issue #1950 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to tuxillo
We no longer support i386.
Bug #1950: socket panic
http://bugs.dragonflybsd.org/issues/1950#change-14299
* Author: pavalos
Issue #1955 has been updated by tuxillo.
Category set to Kernel
Status changed from New to Closed
Assignee set to tuxillo
We no longer support i386.
Bug #1955: sowakeup panic
http://bugs.dragonflybsd.org/issues/1955#change-14298
* Author: pavalos
*
Issue #3314 has been reported by tuxillo.
Bug #3314: Bring virtio_console(4) from FreeBSD
http://bugs.dragonflybsd.org/issues/3314
* Author: tuxillo
* Status: New
* Priority: Normal
* Assignee: tuxillo
* Category: Driver
* Target version: 6.4
* Start
Issue #3305 has been updated by tuxillo.
Status changed from New to In Progress
Not sure if there are more outstanding points to make CBSD support in DFly
better, will find out and, if there aren't, I'll close it.
Bug #3305: CBSD: Add NVMM support in
Issue #3306 has been updated by tuxillo.
@dillon, I've gone ahead and pushed the modified version from aly to the repo.
The buffer to set the description is allocated with M_ZERO so I thought it was
good enough. @aly, thanks I've pushed the patch with your mods.
Issue #3306 has been updated by tuxillo.
Status changed from In Progress to Closed
% Done changed from 50 to 100
Applied in changeset
commit:dragonflybsd|f6994c54d4ef3b530f323130b6d2a46ec6805672.
Bug #3306: Add description support for ifconfig(8)
Issue #1921 has been updated by tuxillo.
Initial work commited in commit:c936cb6f
Bug #1921: we miss mlockall
http://bugs.dragonflybsd.org/issues/1921#change-14293
* Author: alexh
* Status: In Progress
* Priority: Normal
* Assignee: tuxillo
* Category:
Issue #1938 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee deleted (0)
vkernels are no supported anymore or at least until somebody is able to do the
big changes they need. Also, pc32 was removed long ago.
Ticket #1929 wurde aktualisiert von tuxillo.
Beschreibung aktualisiert
Status wurde von New zu Closed geändert
Zugewiesen an 0 wurde gelöscht
i386 is no longer supported, also not enough information to reproduce the issue.
Bug #1929: Panic on nightly
Issue #1912 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee deleted (0)
vkernels are not supported and probably won't be for a long time, if ever.
Bug #1912: diskless vkernel: corrupted files after "pkg_admin
Issue #1925 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee deleted (0)
The first issue seems that was solved at the time this was reported. With
regards to the second issue, apparently it was a typo while mounting the
fileystem where the 'b'
Issue #1921 has been updated by tuxillo.
Description updated
Category set to VM subsystem
Status changed from New to In Progress
Assignee changed from 0 to tuxillo
Priority changed from Low to Normal
We do have @mlockall(2)@ but only _MCL_FUTURE_ is currently supported.
_MCL_CURRENT_ still
Issue #1887 has been updated by tuxillo.
Status changed from Feedback to Closed
Hey, thanks for replying :-)
Closing.
Bug #1887: System freezes with syscons screen saver on and a high CPU load
http://bugs.dragonflybsd.org/issues/1887#change-14286
*
Issue #1887 has been updated by steve.
Hi,
This happened over eleven years ago on hardware that has long since
vanished. It has very probably been inadvertently fixed over the years.
It's certainly not worth any effort now.
On Sun, 15 May 2022 12:46:52 -0700
Issue #1887 has been updated by tuxillo.
Subject changed from System freeze - with logo_saver and high CPU load to
System freezes with syscons screen saver on and a high CPU load
Status changed from New to Feedback
Could not reproduce it, am I missing something? I tried in a VM, I loaded the
Issue #1880 has been updated by tuxillo.
Status changed from New to Closed
HAL is deprecated for 12 years now. D-Bus it's being used without issues in
modern DragonFly BSD releases via dports, we no longer use pkgsrc either.
Bug #1880: hal and dbus
Issue #1877 has been updated by tuxillo.
Description updated
Assignee deleted (0)
Target version changed from 6.4 to Unverifiable
Not enough information to setup a test in order to reproduce it.
Bug #1877: Freeze during 1st hammer cleanup after new
Issue #1832 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee deleted (0)
Information is too vague to be able to setup a test enviroment to see if the
issue can be reproduced.
Bug #1832: page fault panic
Issue #1862 has been updated by tuxillo.
Description updated
Status changed from New to Rejected
Assignee deleted (0)
Whatever that needs fixing, it will be done in #1856, closing.
Bug #1862: Multicast needs to be made MPSAFE without mp_lock
Issue #1816 has been updated by tuxillo.
Description updated
Status changed from New to Closed
% Done changed from 0 to 100
Already fixed some 12 years ago in this commit:
https://github.com/the-tcpdump-group/libpcap/commit/b26d8d2aa849c8021cdfa872901e82fb469460ef
We have a version that has
Issue #1769 has been updated by tuxillo.
Description updated
Target version changed from 6.4 to Unverifiable
Core dumps for i386, which is no longer supported. Also, note enough
information on how to reproduce it, moving to unverifiable.
Bug #1769:
Issue #1826 has been updated by tuxillo.
Description updated
Assignee deleted (0)
Target version changed from 6.4 to Unverifiable
Core dumps no longer available, not enough information. Moving to unverifiable.
Bug #1826: panic during boot: assertion
Issue #1808 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to tuxillo
Cannot reproduce:
root@dev03:~ # cat /boot/loader.conf
vfs.root.mountfrom="ufs:vbd0s1d"
tmpfs_load="YES"
root@dev03:~ # mount /tmp
root@dev03:~ #
root@dev03:~ #
Issue #1806 has been updated by tuxillo.
Status changed from New to Closed
% Done changed from 0 to 100
Unable to reproduce this issue, hence closing.
h3. Evidence
*SERVER*
root@dev01:/usr/src # sysctl hw.physmem
hw.physmem: 500301824
root@dev01:/usr/src # cat /etc/exports
/usr -alldirs
Issue #1597 has been updated by tuxillo.
Status changed from In Progress to Closed
Confirmed by dillon that it can be closed.
Bug #1597: panic: assertion: parent != NULL in hammer_cursor_removed_node
(v2.5.1.187.gc1543-DEV, X86_64)
Issue #582 has been updated by tuxillo.
Status changed from New to Closed
Assignee deleted (0)
PF has been updated at least twice since this was reported and additional work
has been done on top of it, too. Closing this issue.
Please report it on a new issue if it still happens in newer
Issue #1597 has been updated by tuxillo.
Category set to Kernel
Status changed from New to In Progress
Assignee set to dillon
% Done changed from 0 to 100
Mentioned patche was commited, commit:901ba05cd0e7874977a4a937d1b2f9a76ffb9c2d
commit 901ba05cd0e7874977a4a937d1b2f9a76ffb9c2d
Author:
Issue #1477 has been updated by tuxillo.
Description updated
Status changed from New to Closed
Assignee changed from 0 to alexh
% Done changed from 0 to 100
We have udev(8) since commit:2e7bf158f373428dba2c765c927f14d9e94f00a4,
commit:3a3826b3871c8c2f480bcba820c6da8f86700143
Issue #1727 has been updated by tuxillo.
Description updated
Status changed from New to Feedback
Assignee deleted (0)
Target version changed from 6.4 to Unverifiable
Bug #1727: CD boot panic (2.6.1) (usb?)
Issue #1593 has been updated by tuxillo.
Description updated
Category set to Kernel
Status changed from New to Feedback
Assignee changed from 0 to ftigeot
Target version changed from 6.4 to Unverifiable
Moving this to unverifiable, @ftigeot please if you think you can test it again
let us know.
Issue #1397 has been updated by tuxillo.
Status changed from New to Feedback
Assignee set to tuxillo
% Done changed from 0 to 90
The @jobs(1)@ utility calls whatever builtin the current shell uses, or it is
directly bypassed by the shell itself, example:
$ cat /usr/bin/jobs
#!/bin/sh
#
1 - 100 of 1961 matches
Mail list logo
