DesktopBSD 2.0 M1 released

Discussion in 'General Discussion' started by EchoD, Nov 9, 2015.

  1. EchoD

    EchoD Administrator
    Staff Member

    Joined:
    Mar 9, 2013
    Messages:
    98
    Likes Received:
    7
    Hello all. We are releasing the very first milestone version of DesktopBSD 2.0 tonight. Huge thanks to @malco_2001 for working tirelessly to get this release out the door.

    The included torrent includes a virtual machine file and a readme. You will need VirtualBox to run the appliance.

    Please help with seeding the torrent and feel free to upload the release (unmodified) to other distribution sites. Report issues, questions, and general feedback here on the forum. Have fun!
     
  2. n.sokhin

    n.sokhin Member

    Joined:
    Oct 14, 2015
    Messages:
    15
    Likes Received:
    2
    Nice!!! I am in game! My congratulations to all!
     
    EchoD likes this.
  3. SoloBSD

    SoloBSD Member

    Joined:
    Oct 12, 2015
    Messages:
    5
    Likes Received:
    2
    Rock and Roll!!!!
     
    EchoD likes this.
  4. bradlo

    bradlo Member

    Joined:
    Jul 8, 2015
    Messages:
    11
    Likes Received:
    1
    Good all DesktopBSD community!

    At the end there is life on this page of DesktopBSD? What a joy that the system DesktopBSD this of return, and release the next version which for years remained asleep.

    Where can I download the new version of test? In the mirror not this present DesktopBSD 2 , and I don't like to download from torrent.

    Greetings! :D
     
  5. n.sokhin

    n.sokhin Member

    Joined:
    Oct 14, 2015
    Messages:
    15
    Likes Received:
    2
    I hope that helps!
    Original DesktopBSD-2.0-M1.ova:
    https://drive.google.com/open?id=0B0BB9RjkOUFrMlRmV0JtYThWMDg
     
    #5 n.sokhin, Nov 11, 2015
    Last edited: Nov 13, 2015
  6. n.sokhin

    n.sokhin Member

    Joined:
    Oct 14, 2015
    Messages:
    15
    Likes Received:
    2
    First issue is... it`s completely freeze at some moment... and that moment unpredictable at first sight... I don`t know how-to diagnose that.

    It`s looks like this...

    DesktopBSD 2.png
     
    #6 n.sokhin, Nov 11, 2015
    Last edited: Nov 11, 2015
  7. pavroo

    pavroo New Member

    Joined:
    Nov 12, 2015
    Messages:
    2
    Likes Received:
    2
    EchoD likes this.
  8. EchoD

    EchoD Administrator
    Staff Member

    Joined:
    Mar 9, 2013
    Messages:
    98
    Likes Received:
    7
    @pavroo That's fantastic, thank you! Please include the Readme file if you're going to help with re-distributing files. We must include all documentation for legal reasons.
     
  9. pavroo

    pavroo New Member

    Joined:
    Nov 12, 2015
    Messages:
    2
    Likes Received:
    2
    Done.
     
    EchoD likes this.
  10. bradlo

    bradlo Member

    Joined:
    Jul 8, 2015
    Messages:
    11
    Likes Received:
    1
    Trying to test DesktopBSD 2, asks me for a key in the graph of the profile of the user, what is the key? You can not unzip the softrae.

    Gnome 3 is with systemd? It would be a good thing by default a desk light like Fluxbox or KDE.

    https://drive.google.com/open?id=0B0BB9RjkOUFrMlRmV0JtYThWMDg
     
  11. n.sokhin

    n.sokhin Member

    Joined:
    Oct 14, 2015
    Messages:
    15
    Likes Received:
    2
    Sorry my fault!
    Please find "readme.html" with this link:



    This image has Fluxbox and Gnome3. You can change it under gear icon.
    In general Gnome3 has dependencies with systemd on linux but i can`t clearly describe situation with BSD systems...
     
  12. dinsdale

    dinsdale Member

    Joined:
    Oct 22, 2015
    Messages:
    23
    Likes Received:
    13
    Hey All,

    I downloaded the ova and expanded it and it worked the first time (I take it octopkg is your new updater?). I left it running for a couple hours and it seemed to die (black screen, no response). When I rebooted the vm, the image no longer gets past the launchd initialization.

    DesktopBSD-error-startup.png

    I'll try recreating the vm and see what happens.

    edit: I wonder if this is related to https://github.com/desktopbsd/desktopbsd/issues/64


    Cheers,

    Dinsdale
     
    #12 dinsdale, Nov 22, 2015
    Last edited: Nov 22, 2015
  13. dinsdale

    dinsdale Member

    Joined:
    Oct 22, 2015
    Messages:
    23
    Likes Received:
    13
    So I created a new vm and it seems to be running fine.

    When trying to run octopkg I'm getting an error that I need gksu or kdesu. The error seems to be wrong as installing gksu doesn't help. However, when I went to manually run pkgng I got an error about missing libssl.so.8 and missing libcrypto.so.8. I created 2 links as so:
    #ln /usr/lib/libssl.so.7 /usr/lib/libssl.so.8
    #ln /usr/lib/libcrypto.so /usr/lib/libcrupto.8

    And then pkgng successfully installed gksu.

    Then after that although gksu didn't work, I was able to synchronize my database and installed a package through octopkg. So I am thinking the error could have been 1 of 2 things:

    1) missing libs noted above
    2)needed a first synchronization

    Thanks,
    Dinsdale
     
    #13 dinsdale, Nov 22, 2015
    Last edited: Nov 22, 2015
  14. n.sokhin

    n.sokhin Member

    Joined:
    Oct 14, 2015
    Messages:
    15
    Likes Received:
    2
    Hi dinsdale!
    Instead you can use pkg-static or pkg_static or something in that manner...
    And you are not alone with "no response machine", if you read all this thread.
    In my opinion errors like that is happen with drivers or with kernel... Because userland can`t be possible to freeze all system IMHO. But i don`t know how to resolve this.
    And yes... after first freeze your system goes to some recovery level when your filesystem works like readonly. And if you make "fsck", that fix all found troubles, and after that you can reboot to normal system. It`s give you ability to normal boot.
    At least it helps me...

    Cheers!
     
  15. dinsdale

    dinsdale Member

    Joined:
    Oct 22, 2015
    Messages:
    23
    Likes Received:
    13
    Yes, I saw your post. My system only seems to die when I leave it without user input for a few hours but perhaps it's the same. I was able to upgrade packages and play with some of the utilities and install software, so that's great. However, my second VM died overnight. :(

    I can confirm that both VMs have the same issue:

    launchd: dispatching job j=0x800a36c80
    getty[<incr>]: login_tty /dev/ttyv0: Operation not permitted

    It eventually ends in a kernel panic.
    DesktopBSD-error-kernel-panic.png

    Anyway, that's all I know so far.
    https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/term.html

    Edit: I was also able to take a screen shot of my startup and you are correct, root didn't unmount correctly, but there was also a lock reversal stack trace.
    DesktopBSD-startup-2.png

    Cheers!
    Dinsdale
     
    #15 dinsdale, Nov 22, 2015
    Last edited: Nov 22, 2015
  16. EchoD

    EchoD Administrator
    Staff Member

    Joined:
    Mar 9, 2013
    Messages:
    98
    Likes Received:
    7
    n.sokhin likes this.
  17. dinsdale

    dinsdale Member

    Joined:
    Oct 22, 2015
    Messages:
    23
    Likes Received:
    13
    Hey, no worries!

    Thanks to @n.sokhin, I was able to recover after running an fsck. In order to run a live CD however, I had to disable EFI in the Virtual Machine -> Settings -> System tab.

    Here is an exerpt from my syslogd.log file from last night:

    asl_input_parse: <39>Nov 22 00:10:20 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:10:30 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <39>Nov 22 00:10:30 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:10:40 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <39>Nov 22 00:10:40 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:10:50 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <39>Nov 22 00:10:50 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:11:00 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <39>Nov 22 00:11:00 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:11:10 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <39>Nov 22 00:11:10 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:11:20 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <39>Nov 22 00:11:20 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:11:30 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <39>Nov 22 00:11:30 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <39>Nov 22 00:11:40 launchd: dispatching job j=0x800a36c80 kickstart=1
    asl_input_parse: <35>Nov 22 00:11:40 getty[813]: login_tty /dev/ttyv0: Inappropriate ioctl for device
    asl_input_parse: <39>Nov 22 00:11:40 launchd: dispatching job j=0x800a36c80 kickstart=0
    asl_input_parse: <118>Nov 22 00:11:40 dbsd2m1 getty[813]: login_tty /dev/ttyv0: Inappropriate ioctl for device

    I have attached more of the logs to the post, it's full of these types of messages. There may be missing information as I did this:

    cat syslogd.log | grep "Nov 22"

    So there could be stuff missing.

    As you can see, it's the same process causing issues. I bet this is causing a race condition and eventually a kernel panic and there is a file descriptor locked when the root fs comes up dirty and read only.

    Cheers,

    Dinsdale
     

    Attached Files:

    malco_2001, KyBlackwolf and n.sokhin like this.
  18. malco_2001

    malco_2001 DesktopBSD Veteran

    Joined:
    Feb 22, 2015
    Messages:
    50
    Likes Received:
    14
    Thanks for sharing this dinsdale. Sorry I have not been able to reply sooner. By any chance were you leaving the virtual machine running for an extended amount of time, performing package upgrades, or installations? Do you have any other insight into what triggered this to happen?
     
  19. malco_2001

    malco_2001 DesktopBSD Veteran

    Joined:
    Feb 22, 2015
    Messages:
    50
    Likes Received:
    14
    Also n.sokhin the pkg issues you were seeing where you had to install gksu, and things broke down should be fixed by M2. I specifically locked the virtualbox-ose-additions package because I had to modify it by hand to make it work with VM changes in the kernel specific to NextBSD only. The next image will not use virtualbox-ose-addtions at all but a universal video driver.
     
  20. dinsdale

    dinsdale Member

    Joined:
    Oct 22, 2015
    Messages:
    23
    Likes Received:
    13
    Malco, I was doing all of the above! All those things are like the first thing I do on a system. I tried to run buildworld as well. Tee hee. But the length of runtime seems to be random. Sometimes I get a couple of hours out of it, sometimes a few minutes.