Programming recommendations

Fixit7 · 03-09-2014, 09:10 PM

Quote:

Originally Posted by metaschima

If you know C, you can use gtk2 or gtk3 to make GUI programs. You can make console programs using just gcc and glibc.

I am considering using a command line compiler and make some script files to automate the assembly.

Andy

metaschima · 03-09-2014, 11:09 PM

If you use an IDE, it usually automates the build process. However, I usually use the command line and makefiles.

Doc CPU · 03-10-2014, 06:03 AM

Hi there,

Quote:

Originally Posted by Fixit7

How is sudo going to work when I am running Thunar for example ?

you start launch the entire Thunar process in sudo mode, if that is what you mean (I'm not quite sure if I understood you right this time).
You can also assign a password to the root user and then log in to the desktop as root, as I said earlier. But this is usually not recommended.

Quote:

Originally Posted by Fixit7

Quote:

They may have thought you wanted to log in to the GUI and desktop as root, which is in fact impossible with the default configuration of those distros.

The above is exactly what I want and so far only Puppy let's me.

That should make you contemplate. ;-)

Quote:

Originally Posted by Fixit7

I don't mind entering a password once for a computer session.
But everytime I want to mount something, etc is time consuming.

I see your point. I suggested you a way to achieve what you want, but nobody will really appreciate your approach of running the entire system as root.

[X] Doc CPU

sycamorex · 03-10-2014, 04:11 PM

Quote:

Originally Posted by Fixit7

I appreciate your good feedback. :-)

I have used Mint, Ubuntu, OpenSuse, and Debian.

When you say "feature packed" what do you mean.

Could you provide an example of something than another distro other than Puppy can do that Puppy can't ?

I know some have LibreOffice and Gimp that are already built-in, but package manager can easily install those program.

Take care,
Andy

When it comes to software, by default you'll have a limited range of only light weight applications. Of course, you can probably install more feature-rich applications but they may not be as nicely integrated with the system. In terms of hardware, because of its small size, it can't have drivers for a wide range of devices which can potentially be a problem when installing on some hardware (or adding new hardware). Obviously, if it recognises all your hardware, it's not a problem then. I don't use Puppy so can't really talk about specifics but I don't think it is even meant to compete with major distros on a desktop. Its focus is on speed, not features.

But then again, if you're happy with it, I'm not to going to tell you not to use it. I'd encourage you, though, to try distros such us Slackware or Arch where you won't get much hand-holding / restrictions. This, obviously, requires reading and following an ample amount of documentation to use it effectively and securely.

Fixit7 · 03-10-2014, 06:42 PM

Thanks, I install Slackware.
It did not include a menu entry for my Puppy 5.6.0.

Do you know what I need to add to lilo.conf so Puppy shows up as a pick on bootup?

I did not know if I needed to add a new "other" entry or something else.

Puppy is on sda5.

Thanks.

I think grub is much easier to use.

Code:

append=" vt.default_utf8=0"
boot = /dev/sda

#compact        # faster, but won't work on all systems.

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 600
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda1
  label = Windows XP
  table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda6
  label = Linux Slackware
  read-only
# Linux bootable partition config ends

sycamorex · 03-10-2014, 06:54 PM

Yes, another "other" entry should do.

Once you've edited /etc/lilo.conf make sure you run the 'lilo' command (as root) which will update the bootloader.

sycamorex · 03-10-2014, 06:57 PM

A few other things: Try to uncomment the 'compact' option from the lilo.conf file. It'll make the boot process quicker.

Have a look at a Slackware Documentation Project from my signature - you'll see a lot of info on how to configure and maintain Slackware.

Fixit7 · 03-10-2014, 08:34 PM

This did not work, there was not even a menu entry for Puppy on bootup ?

image = /boot/vmlinuz
root = /dev/sda5
label = Linux Puppy
read-only

astrogeek · 03-10-2014, 08:55 PM

Quote:

Originally Posted by Fixit7

This did not work, there was not even a menu entry for Puppy on bootup ?

image = /boot/vmlinuz
root = /dev/sda5
label = Linux Puppy
read-only

Did you run lilo again after making the change in lilo.conf?

Also, I don't think that you can have spaces in the label, try "Linux_Puppy".