Re: Eclipse IDE
On 05/11/2017 10:33, Nils wrote: Is it possible to update Eclipse from the ubuntu repositories 3.8.1 version came out in September 2012 and today we are near 2018, so it would be very nice to update it. I never install Eclipse from the repositories, because it's always a significantly older version. I simply download it from eclipse.org directly and install it in my /opt folder. Charl -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Installation Media and supportability of i386 in 18.04 LTS Re: Ubuntu Desktop on i386
On 01/07/2016 21:05, Bryan Quigley wrote: Can you elaborate on what specific systems you are purchasing today that use 32-bit x86 (I believe the only vendors ever were AMD, Intel and VIA)? The chipsets are mostly AMD and Intel as you've stated. The vendor I purchase from mostly is iEi. They have a huge variety of form factors and chipsets, mostly AMD and Intel. Popular 32-bit systems include Intel Atom and AMD Geode. I have used some weird ones like the eBox that uses the DM Vortex86DX CPU, but you can no longer run Ubuntu on this anyway, because the architecture is too old. Also what is your usual expected EOL for these systems? I'll have to find out about EOL, but they'll continue to produce the systems for as long as the chips are available. So I guess the question is rather for how much longer AMD and Intel will produce 32-bit chipsets. In the field these systems can keep running for 10+ years even in harsh environments because they are designed for industrial conditions. However, once installed the operating system is seldom upgraded as its usually pretty hard to get to the devices and upgrades often bring unwanted problems, e.g. incompatibilities, removed packages, dropped support for devices or changes to the file system structure. So I only use LTS editions and allow for security updates, at least that provides 3-5 years of OS security. Dropped support for older architectures and hardware is a problem I run into more and more. Even things like dropping support for the alternative install CD created problems for me. I have considered switching to another flavor of Linux that still supports older architectures, but the convenience of Ubuntu makes it hard to switch. The new Snappy packages might make life a little easier again, but I haven't tried it yet. Fortunately, embedded systems seldom require GUI front-ends and web interfaces are preferred, so Server Edition still provides everything I need. Please don't forget the Edubuntu projects. Dropping support for 32-bit PCs could severely affect many of these community upliftment projects. Regards Charl -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Installation Media and supportability of i386 in 18.04 LTS Re: Ubuntu Desktop on i386
On 29/06/2016 15:37, Mark Shuttleworth wrote: Folks, I think we need to understand whether i386 won't be widely used for very small IoT devices and hence be important for developers targeting those. I accept i386 i no longer relevant for PC's and laptops, but I would not be surprised if 32-bit x86 is used in small 'embedded' environments. As an embedded developer I can comment on this... I use Ubuntu as my main platform on embedded system. There are still many viable 32-bit platforms that are being manufactured. This is mainly because they are so cheap. In my case I either: - use Server edition - use a lightweight desktop like LDE - build a custom deskop with openbox with limited features To me is is critical that at the very least Server Edition is supported. Edubuntu projects should also be considered as well. Many of these projects collect old PCs and build infrastructure for entire schools in Africa. To them 32-bit support will be crucial for as long as the machines can run. Regards Charl -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Change what is considered by apt-get as major amount of disk space
On 25/03/2015 18:52, Jim Cobley wrote: Trouble is your system may have a big disk whilst another (eg raspberry) will probably be very tight on space. Some people may consider 10Mb to be peanuts whilst others may think of it as gold dust. How to choose? Better to leave it as is - a bit dumb to some, informative to others and invaluable to a few more +1 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Pre-upgrade warnings and advice?
On 02/06/2014 21:49, Neal McBurnett wrote: Ubuntu support for upgrades naturally depends on exactly what is being upgraded. Use of software from outside the official Ubuntu repositories (PPA repositories or .deb files or tar.gz packages or the like) means upgrades may be more complicated for the user. It's always been my experience that when upgrading, all software that is not installed by default, are uninstalled and must be installed separately by the user after the upgrade. Mate would definitely fall in this category. (It is for this very reason that i don't upgrade every 6 months, and often skip a release or two.) However, all the settings of that software is still kept in the user home directory, so when you reinstalled the software, it should keep its configuration. Eg. if you use an email app other than Thunderbird, upon installing it after the upgrade, all your accounts and emails will be available again without having to configure it again. Problems can be expected, especially when using universe and multi-verse packages, since it does not necessarily go through the same rigorous testing before release. (For this reason I only upgrade 6 months after the release of a new version. Although it's nice to be cutting-edge, it does come with a risk (of being cut). Since Saucy, there is a useful app available in the PPAs which makes this process easier: *Aptik*. You can run it before the upgrade and it will record and save all the additional packages and PPA you have installed. If you run it again after the upgrade it allow you (to attempt) to restore all of those PPAs and packages again. In short, if you run a non-stock desktop, you need to be a bit more prudent when upgrading. Charl -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: sudoers
On 17/05/2014 14:11, Dimitri John Ledkov wrote: Whilst coding you may want to open up /dev/port, e.g. $ sudo chmod g+w /dev/port # if you need r/w access $ sudo adduser `id -un` kmem (re-login) This will open up /dev/port for r+w to yourself (well anyone in kmem group). This is slightly better than running things as root. Yes, I think that's a good solution. Thanks However, you'll need a solution to do something sensible in the finally shipped application. E.g. do start your application as root (or use setuid on the binary), execute ioperm()/iopl() to grant access to I/O ports you need, and after that drop privileges. For more info see http://www.tldp.org/HOWTO/IO-Port-Programming-2.html On the target platform the application is started up in rc.local and run as root, so no issues there. It's only during development that I need to debug as root. Thanks for the advice -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
sudoers
Hi Guys I recently struggled with an issue for quite a few days because of the way the /etc/sudoers file is laid out. I would like to make a suggestion to change it that would hopefully save others the same hassle. I wanted to debugging in Eclipse which required me to let Eclipse run gdb with sudo. However, for this to work, sudo must not ask for a password. So I've added the following entry in /etc/sudoers under the appropriate comment: # User privilege specification myuserALL=(root) NOPASSWD: /usr/bin/gdb Although the syntax is correct the entry was overridden by the 'admin' and 'sudo' group entries just a little further down, because my user was part of both the 'sudo' and 'admin' groups... # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL This resulted in my 'NOPASSWD:' flag to have no effect. This is because sudoers has the oddity that it uses the last matched rule, not the first! I would like to suggest that the 'admin' and 'sudo' entries be moved just above the comment # User privilege specification. This would ensure that any user/group specific added by a user will override the 'admin' and 'sudo' entries. If this is not appropriate, maybe simply adding a comment to the file to just to remind people of this rule would be a great help. However, such a comment should be added just above/below the # User/Group privilege specification comments so its easy to spot. Regards Charl -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: sudoers
On 17/05/2014 01:35, Dimitri John Ledkov wrote: On 16 May 2014 07:26, Charl Wentzel charl.went...@vodamail.co.za wrote: I wanted do to debugging in Eclipse which required me to let Eclipse run gdb with sudo. However, for this to work, sudo must not ask for a password. So I've added the following entry in /etc/sudoers under the appropriate comment: If you simply want to grant unrestricted permissions for gdb to attach to any process, you don't need to grant full sudo to it. Thanks, I'll have a look into it. Are there any other reasons why you want to run gdb as root from eclipse? Yes, I'm writing an application that works with /dev/port for setting IO states. I've looked into a few options, but none of the quite suited me: 1. Run Eclipse as root Running a program as root tends to mess up your config as permissions on config files sometimes end up with root permissions. Also, this means I can't write/debug that app inside Eclipse with my other programs, I'll have to run two instances of Eclipse instead of just one. 2. Using remote debugging You could start the debugger from the command line eg. sudo gdb my app and then connect to it from Eclipse via remote debugging. This just complicates the process, I want to have the ease of a IDE. So allowing Eclipse to start the debugger as root was the best and easiest solution so far. Charl -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
