Page 13 of 16

Re: Jessie Q&A

Posted: Sat Feb 20, 2016 2:30 pm
by tetard_canadien
hello community

for a school project i use p0f, (passive fingerprinting tool)

for production, i use raspberry Model B RĂ©vision 2.0 512MB, (Sony), with Raspbian jessy,
for test in lab, i work with computer and kali

my problem
on raspbian (linux raspberry 401017),
- p0f is 2.0.8-2 (06-Sep-2006)
- list of operating system stop at win2000 / win 98

on kali (linux osboxes 4.0.0-kali),
- p0f is 3.08b (08-Nov-2014)
- list include win7&8

i try to update raspbian packadge, always same message... p0f is up to date !

so, how can i load 3.08b on my raspberry ? or who can update raspbian repository to the latest release ?

regards
Franck

Re: Jessie Q&A

Posted: Sat Feb 20, 2016 7:39 pm
by klricks
Raspbian is based on Debian. Debian follows a very strict and conservative strategy.... only allowing proven stable software and updates.
Therefore almost all software in the Raspbian repository is several revisions behind what might be available elsewhere.

If you want the latest then you will need to obtain the source code (if available) and compile yourself.

Re: Jessie Q&A

Posted: Sat Feb 20, 2016 8:58 pm
by tetard_canadien
for information

" Kali 2.0, new 4.0 kernel, now based on Debian Jessie "

it's also Debian jessie release like raspbian. so why can't i install, i try to compile software without succes maybe i'm too novice :?

Re: Jessie Q&A

Posted: Sun Feb 21, 2016 5:52 pm
by tetard_canadien
I suppose it's due to processor
ARM Raspberry versus AMD 64 pc

it's good ?
regards

Re: Jessie Q&A

Posted: Mon Feb 29, 2016 9:43 pm
by Enderguy_58
Hello,

After I updated raspbian on my raspberry pi 2 to the latest version, the volume icon is now missing from the tool bar.
Because of that, I don't have sound anymore. Am I missing something? How can I fix it?

Re: Jessie Q&A

Posted: Mon Feb 29, 2016 10:13 pm
by Bosse_B
From which version did you upgrade?
I did a fresh install instead of upgrade so I would not have problems with old stuff and I do have the loudspeaker icon on the task bar.

Notice tetard_canadien:
Raspberry Pi3 is released now and it is 64 bit!
Seems like a steal!

Re: Jessie Q&A

Posted: Mon Feb 29, 2016 10:21 pm
by GTR2Fan
Enderguy_58 wrote:After I updated raspbian on my raspberry pi 2 to the latest version, the volume icon is now missing from the tool bar. Because of that, I don't have sound anymore. Am I missing something? How can I fix it?
Right-click on the taskbar and select Add / Remove Panel Items, then click on Add. It should be in there somewhere. I've no idea why it went missing for you though.

Re: Jessie Q&A

Posted: Mon Feb 29, 2016 11:50 pm
by Enderguy_58
GTR2Fan wrote:
Enderguy_58 wrote:After I updated raspbian on my raspberry pi 2 to the latest version, the volume icon is now missing from the tool bar. Because of that, I don't have sound anymore. Am I missing something? How can I fix it?
Right-click on the taskbar and select Add / Remove Panel Items, then click on Add. It should be in there somewhere. I've no idea why it went missing for you though.
It's there but when I click on it to add it nothing happens

By the way I'm on berry boot. I don't know if that's important.

Re: Jessie Q&A

Posted: Tue Mar 01, 2016 8:09 pm
by Enderguy_58
Ok I found something. Is it normal that the /etc/alsa file is missing?

Re: Jessie Q&A

Posted: Tue Mar 01, 2016 11:03 pm
by Bosse_B
It i not present on my Raspbian Jessie from Feb 9 2016
And I do not have problems like you describe.

I have no idea what your "berry boot" means...

Re: Jessie Q&A

Posted: Tue Mar 01, 2016 11:11 pm
by Enderguy_58
Bosse_B wrote:It i not present on my Raspbian Jessie from Feb 9 2016
And I do not have problems like you describe.

I have no idea what your "berry boot" means...
It's something that can boot two or more images one the same sd card and I think it just broke.
Retropie, an other image that I have on it, doesn't work properly anymore so this whole problem is probably because of Berryboot...

Edit: Retropie started having problems out of nowhere. No updates.

Re: Jessie Q&A

Posted: Wed Mar 02, 2016 7:53 am
by tetard_canadien
Notice tetard_canadien:
Raspberry Pi3 is released now and it is 64 bit!
Seems like a steal!
thanks for this information, i wait for Raspbian 64 bits and i should test

Re: Jessie Q&A

Posted: Tue Mar 15, 2016 8:52 pm
by Massi
to setup a bluetooth serial connection, on wheezy i did:
- entry in /etc/bluetooth/rfcomm.conf
- pincode in /var/lib/bluetooth/xx:xx:Xx:Xx:Xx/pincodes

how the hell is it possible that nothing of this is working on jessie?
i'm hating this so much!

is this the result of the new bluez?
i've found more than one having problems, but i couldn't understand where to setup the rfcomm and where to put pincodes (i neither can open /var/lib/bluetooth!!)..

any hint?

Re: Jessie Q&A

Posted: Wed Mar 16, 2016 7:10 pm
by Massi
Massi wrote:to setup a bluetooth serial connection, on wheezy i did:
- entry in /etc/bluetooth/rfcomm.conf
- pincode in /var/lib/bluetooth/xx:xx:Xx:Xx:Xx/pincodes

how the hell is it possible that nothing of this is working on jessie?
i'm hating this so much!

is this the result of the new bluez?
i've found more than one having problems, but i couldn't understand where to setup the rfcomm and where to put pincodes (i neither can open /var/lib/bluetooth!!)..

any hint?
so with bluetoothctl i could get my device paired connected and trusted
the entry in the var/lib/bluetooth directory is created by the tool itself, and this is ok

but

despite this page
http://www.linuxfromscratch.org/blfs/vi ... bluez.html
the rfcomm.conf file is completely ignored (i tried with the "old" bluez4 format or simply putting rfcomm commands, since THERE'S NO DOCUMENTATION)
so the rfcomm device isn't created on system reboot

any "clean" idea to get the incredibly-now-hard-to-obtain autobind feature?

thanks

Re: Jessie Q&A

Posted: Tue Mar 22, 2016 3:49 pm
by scollins15
I have downloaded the 2016-02-26-raspbian-jessie-lite.img and provisioned an SD card for use with my brand new Pi 3 :D . I am having problems with my networking. I installed wicd-curses package and on some reboots the network connection does connect successfully on others it does not. I cannot seem to determine the issue. Help would be greatly appreciated. It seems to connect temporarily and then get disconnected. The wicd.log text follows:

Code: Select all

2016/03/22 15:39:19 :: ifconfig eth0
2016/03/22 15:39:19 :: ifconfig wlan0
2016/03/22 15:39:24 :: ifconfig eth0
2016/03/22 15:39:24 :: ifconfig wlan0
2016/03/22 15:39:29 :: ifconfig eth0
2016/03/22 15:39:29 :: ifconfig wlan0
2016/03/22 15:39:34 :: ifconfig eth0
2016/03/22 15:39:34 :: ifconfig wlan0
2016/03/22 15:39:39 :: ifconfig eth0
2016/03/22 15:39:39 :: ifconfig wlan0
2016/03/22 15:39:44 :: ifconfig eth0
2016/03/22 15:39:44 :: ifconfig wlan0
2016/03/22 15:39:48 :: ifconfig wlan0
2016/03/22 15:39:48 :: ifconfig eth0
2016/03/22 15:39:48 :: iwconfig wlan0
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:48 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:49 :: Reading wired profile wired-default
2016/03/22 15:39:49 :: found ip in configuration None
2016/03/22 15:39:49 :: found broadcast in configuration None
2016/03/22 15:39:49 :: found netmask in configuration None
2016/03/22 15:39:49 :: found gateway in configuration None
2016/03/22 15:39:49 :: found search_domain in configuration None
2016/03/22 15:39:49 :: found dns_domain in configuration None
2016/03/22 15:39:49 :: found dns1 in configuration None
2016/03/22 15:39:49 :: found dns2 in configuration None
2016/03/22 15:39:49 :: found dns3 in configuration None
2016/03/22 15:39:49 :: found beforescript in configuration None
2016/03/22 15:39:49 :: found afterscript in configuration None
2016/03/22 15:39:49 :: found predisconnectscript in configuration None
2016/03/22 15:39:49 :: found postdisconnectscript in configuration None
2016/03/22 15:39:49 :: found encryption_enabled in configuration None
2016/03/22 15:39:49 :: found default in configuration True
2016/03/22 15:39:49 :: found dhcphostname in configuration trusign-b3a3
2016/03/22 15:39:49 :: found lastused in configuration True
2016/03/22 15:39:49 :: found default in configuration True
2016/03/22 15:39:49 :: found default in configuration True
2016/03/22 15:39:51 :: ifconfig eth0
2016/03/22 15:39:51 :: iwconfig wlan0
2016/03/22 15:39:51 :: ifconfig wlan0
2016/03/22 15:39:53 :: iwconfig wlan0
2016/03/22 15:39:53 :: Executing /etc/network/if-down.d/resolvconf with params 
2016/03/22 15:39:53 :: /etc/network/if-down.d/resolvconf returned 0
2016/03/22 15:39:53 :: Executing /etc/network/if-down.d/upstart with params 
2016/03/22 15:39:53 :: /etc/network/if-down.d/upstart returned 0
2016/03/22 15:39:53 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2016/03/22 15:39:53 :: /etc/network/if-down.d/wpasupplicant returned 0
2016/03/22 15:39:53 :: /sbin/dhcpcd -k wlan0
2016/03/22 15:39:53 :: ifconfig wlan0 0.0.0.0 
2016/03/22 15:39:53 :: /sbin/ip route flush dev wlan0
2016/03/22 15:39:53 :: ifconfig wlan0 down
2016/03/22 15:39:54 :: ifconfig wlan0 up
2016/03/22 15:39:54 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2016/03/22 15:39:54 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2016/03/22 15:39:54 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2016/03/22 15:39:54 :: /etc/network/if-post-down.d/wireless-tools returned 0
2016/03/22 15:39:54 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2016/03/22 15:39:54 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2016/03/22 15:39:54 :: wpa_cli -i wlan0 terminate
2016/03/22 15:39:54 :: Executing /etc/network/if-down.d/resolvconf with params 
2016/03/22 15:39:54 :: /etc/network/if-down.d/resolvconf returned 0
2016/03/22 15:39:54 :: Executing /etc/network/if-down.d/upstart with params 
2016/03/22 15:39:54 :: /etc/network/if-down.d/upstart returned 0
2016/03/22 15:39:54 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2016/03/22 15:39:54 :: /etc/network/if-down.d/wpasupplicant returned 0
2016/03/22 15:39:54 :: /sbin/dhcpcd -k eth0
2016/03/22 15:39:54 :: ifconfig eth0 0.0.0.0 
2016/03/22 15:39:54 :: /sbin/ip route flush dev eth0
2016/03/22 15:39:54 :: ifconfig eth0 down
2016/03/22 15:39:54 :: ifconfig eth0 up
2016/03/22 15:39:54 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2016/03/22 15:39:54 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2016/03/22 15:39:54 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2016/03/22 15:39:54 :: /etc/network/if-post-down.d/wireless-tools returned 0
2016/03/22 15:39:54 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2016/03/22 15:39:54 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2016/03/22 15:39:54 :: wpa_cli -i eth0 terminate
2016/03/22 15:39:54 :: found lastused in configuration True
2016/03/22 15:39:54 :: Executing /etc/network/if-pre-up.d/wireless-tools with params 
2016/03/22 15:39:54 :: /etc/network/if-pre-up.d/wireless-tools returned 0
2016/03/22 15:39:54 :: Executing /etc/network/if-pre-up.d/wpasupplicant with params 
2016/03/22 15:39:54 :: /etc/network/if-pre-up.d/wpasupplicant returned 0
2016/03/22 15:39:54 :: Putting interface down
2016/03/22 15:39:54 :: ifconfig eth0 downGetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: 
2016/03/22 15:39:54 :: Releasing DHCP leases...
2016/03/22 15:39:54 :: /sbin/dhcpcd -k eth0
2016/03/22 15:39:54 :: Setting false IP...
2016/03/22 15:39:54 :: ifconfig eth0 0.0.0.0 
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: Stopping wpa_supplicant
2016/03/22 15:39:54 :: wpa_cli -i eth0 terminate
2016/03/22 15:39:54 :: Flushing the routing table...
2016/03/22 15:39:54 :: /sbin/ip route flush dev eth0
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: Putting interface up...
2016/03/22 15:39:54 :: ifconfig eth0 up
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:54 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:55 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:55 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:55 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:55 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:55 :: GetCurrentNetworkID: Returning -1, current network not found
2016/03/22 15:39:55 :: ifconfig wlan0
2016/03/22 15:39:55 :: ifconfig eth0
2016/03/22 15:39:55 :: Reading wired profile wired-default
2016/03/22 15:39:55 :: found ip in configuration None
2016/03/22 15:39:55 :: found broadcast in configuration None
2016/03/22 15:39:55 :: found netmask in configuration None
2016/03/22 15:39:55 :: found gateway in configuration None
2016/03/22 15:39:55 :: found search_domain in configuration None
2016/03/22 15:39:55 :: found dns_domain in configuration None
2016/03/22 15:39:55 :: found dns1 in configuration None
2016/03/22 15:39:55 :: found dns2 in configuration None
2016/03/22 15:39:55 :: found dns3 in configuration None
2016/03/22 15:39:55 :: found beforescript in configuration None
2016/03/22 15:39:55 :: found afterscript in configuration None
2016/03/22 15:39:55 :: found predisconnectscript in configuration None
2016/03/22 15:39:55 :: found postdisconnectscript in configuration None
2016/03/22 15:39:55 :: found encryption_enabled in configuration None
2016/03/22 15:39:55 :: found default in configuration True
2016/03/22 15:39:55 :: found dhcphostname in configuration trusign-b3a3
2016/03/22 15:39:55 :: found lastused in configuration True
2016/03/22 15:39:56 :: Running DHCP with hostname trusign-b3a3
2016/03/22 15:39:56 :: /sbin/dhcpcd -h trusign-b3a3 --noipv4ll eth0 
2016/03/22 15:39:56 :: dhcpcd[16304]: sending commands to master dhcpcd process
2016/03/22 15:39:56 :: 
2016/03/22 15:39:56 :: 
2016/03/22 15:39:56 :: DHCP connection successful
2016/03/22 15:39:56 :: Executing /etc/network/if-up.d/000resolvconf with params 
2016/03/22 15:39:56 :: /etc/network/if-up.d/000resolvconf returned 0
2016/03/22 15:39:56 :: Executing /etc/network/if-up.d/avahi-daemon with params 
2016/03/22 15:39:56 :: /etc/network/if-up.d/avahi-daemon returned 0
2016/03/22 15:39:56 :: Executing /etc/network/if-up.d/mountnfs with params 
2016/03/22 15:39:56 :: /etc/network/if-up.d/mountnfs returned 0
2016/03/22 15:39:56 :: Executing /etc/network/if-up.d/openssh-server with params 
2016/03/22 15:39:56 :: /etc/network/if-up.d/openssh-server returned 0
2016/03/22 15:39:56 :: Executing /etc/network/if-up.d/upstart with params 
2016/03/22 15:39:56 :: /etc/network/if-up.d/upstart returned 0
2016/03/22 15:39:56 :: Executing /etc/network/if-up.d/wpasupplicant with params 
2016/03/22 15:39:56 :: /etc/network/if-up.d/wpasupplicant returned 0
2016/03/22 15:39:56 :: Connecting thread exiting.
2016/03/22 15:39:56 :: IP Address is: None
2016/03/22 15:39:57 :: ifconfig eth0
2016/03/22 15:39:57 :: iwconfig wlan0
2016/03/22 15:39:57 :: ifconfig wlan0
2016/03/22 15:40:00 :: Sending connection attempt result success
2016/03/22 15:40:00 :: ifconfig eth0
2016/03/22 15:40:00 :: ifconfig wlan0
2016/03/22 15:40:00 :: Forced disconnect on
2016/03/22 15:40:00 :: iwconfig wlan0
2016/03/22 15:40:00 :: Executing /etc/network/if-down.d/resolvconf with params 
2016/03/22 15:40:00 :: /etc/network/if-down.d/resolvconf returned 0
2016/03/22 15:40:00 :: Executing /etc/network/if-down.d/upstart with params 
2016/03/22 15:40:00 :: /etc/network/if-down.d/upstart returned 0
2016/03/22 15:40:00 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2016/03/22 15:40:00 :: /etc/network/if-down.d/wpasupplicant returned 0
2016/03/22 15:40:00 :: /sbin/dhcpcd -k wlan0
2016/03/22 15:40:00 :: ifconfig wlan0 0.0.0.0 
2016/03/22 15:40:00 :: /sbin/ip route flush dev wlan0
2016/03/22 15:40:00 :: ifconfig wlan0 down
2016/03/22 15:40:00 :: ifconfig wlan0 up
2016/03/22 15:40:00 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2016/03/22 15:40:00 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2016/03/22 15:40:00 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2016/03/22 15:40:00 :: /etc/network/if-post-down.d/wireless-tools returned 0
2016/03/22 15:40:00 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2016/03/22 15:40:00 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2016/03/22 15:40:00 :: wpa_cli -i wlan0 terminate
2016/03/22 15:40:00 :: Executing /etc/network/if-down.d/resolvconf with params 
2016/03/22 15:40:00 :: /etc/network/if-down.d/resolvconf returned 0
2016/03/22 15:40:00 :: Executing /etc/network/if-down.d/upstart with params 
2016/03/22 15:40:00 :: /etc/network/if-down.d/upstart returned 0
2016/03/22 15:40:00 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2016/03/22 15:40:00 :: /etc/network/if-down.d/wpasupplicant returned 0
2016/03/22 15:40:00 :: /sbin/dhcpcd -k eth0
2016/03/22 15:40:00 :: ifconfig eth0 0.0.0.0 
2016/03/22 15:40:01 :: /sbin/ip route flush dev eth0
2016/03/22 15:40:01 :: ifconfig eth0 down
2016/03/22 15:40:01 :: ifconfig eth0 up
2016/03/22 15:40:01 :: Executing /etc/network/if-post-down.d/avahi-daemon with params 
2016/03/22 15:40:01 :: /etc/network/if-post-down.d/avahi-daemon returned 0
2016/03/22 15:40:01 :: Executing /etc/network/if-post-down.d/wireless-tools with params 
2016/03/22 15:40:01 :: /etc/network/if-post-down.d/wireless-tools returned 0
2016/03/22 15:40:01 :: Executing /etc/network/if-post-down.d/wpasupplicant with params 
2016/03/22 15:40:01 :: /etc/network/if-post-down.d/wpasupplicant returned 0
2016/03/22 15:40:01 :: wpa_cli -i eth0 terminate
2016/03/22 15:40:05 :: ifconfig eth0
2016/03/22 15:40:05 :: ifconfig wlan0

Re: Jessie Q&A

Posted: Tue Mar 22, 2016 8:32 pm
by DirkS
scollins15 wrote:I have downloaded the 2016-02-26-raspbian-jessie-lite.img and provisioned an SD card for use with my brand new Pi 3 :D . I am having problems with my networking. I installed wicd-curses package and on some reboots the network connection does connect successfully on others it does not. I cannot seem to determine the issue. Help would be greatly appreciated. It seems to connect temporarily and then get disconnected. The wicd.log text follows:
This is not really the best place to post this. Create a new topic in 'Troubleshooting'
I'm sure it will increase your chances of getting help with your issue

Re: Jessie Q&A

Posted: Wed Mar 30, 2016 7:57 pm
by Jimbo213Mo
2 Newbie questions:

A) How OFTEN is it recommended to run sudo apt-get update & upgrade on Jesse?
B) When will I know when I should upgrade the Raspian OS to the next version -and- How will I know if it will "break" Kodi ?

My system specs are in the signature.

Thanks, Jim

Re: Jessie Q&A

Posted: Wed Mar 30, 2016 10:11 pm
by DougieLawson
If it's a client machine only run apt-get monthly. If it's running as a server run it weekly. If you're working with the leading edge (rpi-update or BRANCH=next rpi-update) kernel and software then run it daily.

You won't know if it will break kodi, if kodi wasn't installed with apt-get.

Re: Jessie Q&A

Posted: Thu Mar 31, 2016 1:26 am
by Jimbo213Mo
thanks DougieLawson
reply: Kodi was also installed with apt-get so then "monthly" is the perfect answer for my single-user home Pi.

How about answering
B) When will I know when I should upgrade the Raspian OS to the next version

Thanks, Jimbo

Re: Jessie Q&A

Posted: Thu Mar 31, 2016 1:44 am
by DirkS
Jimbo213Mo wrote:B) When will I know when I should upgrade the Raspian OS to the next version
Please define 'next version'...
Do you mean the next RPF Raspbian Jessie release (as can be downloaded from https://www.raspberrypi.org/downloads/raspbian/)?
Or do you mean the successor of Raspbian / Debian Jessie?

Re: Jessie Q&A

Posted: Thu Mar 31, 2016 9:15 pm
by Jimbo213Mo
MANY thanks DirkS
DirkS wrote:
Jimbo213Mo wrote:B) When will I know when I should upgrade the Raspian OS to the next version
Please define 'next version'...
a) Do you mean the next RPF Raspbian Jessie release (as can be downloaded from https://www.raspberrypi.org/downloads/raspbian/)?
b) Or do you mean the successor of Raspbian / Debian Jessie?
Reply:
a) per the link: it appears that next RPF Raspbian Jessie release involves a format & re-burn of my SD card - correct?
b) yes - my intent was regarding the successor of Raspbian / Debian Jessie. Right now it seems 16.0 is not ready for the Pi since I am running Kodi [XBMC] per this article http://kodi.wiki/view/HOW-TO:Install_Ko ... i#Raspbian

Blessings, Jim

Re: Jessie Q&A

Posted: Fri Apr 01, 2016 1:21 am
by Max7
Hi,

I'm new to Linux and want to be proficient using the Linux terminal. Is it smart to use Debian documentation to aide and reference my learning of Raspbian? It's basically the same OS right?

The Raspbian website is kinda bare bones. ;)

Re: Jessie Q&A

Posted: Fri Apr 01, 2016 5:03 am
by gkreidl
Max7 wrote:Hi,

I'm new to Linux and want to be proficient using the Linux terminal. Is it smart to use Debian documentation to aide and reference my learning of Raspbian? It's basically the same OS right?

The Raspbian website is kinda bare bones. ;)
Yes, Raspbian Jessie is Debian Jessie compiled for ARMv6 HF.
There are some things reworked or added by the Foundation, though (separate archive.raspberrypi.org)

Re: Jessie Q&A

Posted: Fri Apr 01, 2016 4:26 pm
by Max7
gkreidl wrote:
Max7 wrote:Hi,

I'm new to Linux and want to be proficient using the Linux terminal. Is it smart to use Debian documentation to aide and reference my learning of Raspbian? It's basically the same OS right?

The Raspbian website is kinda bare bones. ;)
Yes, Raspbian Jessie is Debian Jessie compiled for ARMv6 HF.
There are some things reworked or added by the Foundation, though (separate archive.raspberrypi.org)
Is the repository and packages also different?

Re: Jessie Q&A

Posted: Fri Apr 01, 2016 4:51 pm
by gkreidl
Max7 wrote: Is the repository and packages also different?
Yes, two repositories ( http://archive.raspbian.org/ and http://archive.raspberrypi.org/ ) and sometimes different package versions (webkitgtk3, for example); the RPi repository takes precedence.